Lisp HUG Maillist Archive

LWP6.0 "Other types of images are not implemented"

Why can it not load images using LWP6.0 on Linux? I get the following
error "Other types of images are not implemented". There is no mention
anywhere that loading images is not supported so what gives?

-- 
Ryan Hope, M.S.
CogWorks Lab
Department of Cognitive Science
Rensselaer Polytechnic Institute


Re: LWP6.0 "Other types of images are not implemented"


On Oct 30, 2010, at 10:09 AM, Ryan Hope wrote:

> 
> Why can it not load images using LWP6.0 on Linux? I get the following
> error "Other types of images are not implemented". There is no mention
> anywhere that loading images is not supported so what gives?

The question is a little elliptical, but I recognize the error message as being one that CAPI displays when you try to load a graphic file with load-image, or by passing an :image argument to a CAPI initializer, when the graphic format of the file is not supported by CAPI on the platform you're using.

It means you tried to load a graphic that is not supported by CAPI on your platform. 

The graphic formats that are supported vary by platform. Presumably, on each platform, they are the ones that the Lispworks implementors felt they could easily support using libraries that they could count on having available on the platform.



Re: LWP6.0 "Other types of images are not implemented"

On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:

> The graphic formats that are supported vary by platform. Presumably, on  
> each platform, they are the ones that the Lispworks implementors felt  
> they could easily support using libraries that they could count on  
> having available on the platform.

Because, since Lispworks is a commercial product, they probably cannot use  
freely available graphics libraries and have to write their own. That  
brings a natural limit how many formats you may have available without the  
adverse effect on the actual core product development, but that should not  
be that much of a trouble, since you probably can convert your own image  
files into one of the supported formats without the need to drink coffee  
at night.


Re: LWP6.0 "Other types of images are not implemented"

2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
>
> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
>
>> The graphic formats that are supported vary by platform. Presumably, on
>> each platform, they are the ones that the Lispworks implementors felt they
>> could easily support using libraries that they could count on having
>> available on the platform.
>
> Because, since Lispworks is a commercial product, they probably cannot use
> freely available graphics libraries and have to write their own. That brings
> a natural limit how many formats you may have available without the adverse
> effect on the actual core product development, but that should not be that
> much of a trouble, since you probably can convert your own image files into
> one of the supported formats without the need to drink coffee at night.
>
>

libpng & libjpeg should be free enough; that just leaves, oh, a
hundred or so other formats. :D

Still, what image types is Ryan attempting to use, and what types are
supported by CAPI?

-- 
====
Q. How many Prolog programmers does it take to change a lightbulb?
A. No.


Re: LWP6.0 "Other types of images are not implemented"

I am trying to load PNG files...

Below is the backtrace:

Call to ERROR
Call to GRAPHICS-PORTS:CONVERT-EXTERNAL-IMAGE
Call to GRAPHICS-PORTS:LOAD-IMAGE
Call to CAPI::INSTALL-ONE-BUTTON-IMAGE
Call to CAPI::MAP-BUTTON-IMAGES
Call to (METHOD CAPI-LIBRARY:FINALIZE-REPRESENTATION
(CAPI-GTK-LIBRARY::BUTTON-REPRESENTATION))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to CLOS::NEXT-METHOD-CALL-1
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to CLOS::NEXT-METHOD-CALL-1
Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
Call to CLOS::NEXT-METHOD-CALL-1
Call to (METHOD CAPI::CREATE :AROUND (CAPI:INTERFACE))
Call to CLOS::METHOD-COMBINATION-TEMPLATE
Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
Call to (METHOD CAPI::DO-DISPLAY-AUX (T T T))
Call to (SUBFUNCTION CAPI::DEFAULT-TOP-LEVEL
CAPI::INITIALIZE-AND-PROCESS-EVENTS)
Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
Call to MP::PROCESS-SG-FUNCTION

2010/11/1 Martin Simmons <martin@lispworks.com>:
>
> The LW Personal Edition uses GTK+, which has its own image converters, so I
> think the problem lies elsewhere.
>
> --
> Martin Simmons
> LispWorks Ltd
> http://www.lispworks.com/
>
>
>>>>>> On Mon, 1 Nov 2010 01:17:31 +0800, Chun Tian (binghe) said:
>>
>> Related LispWorks document [1] said that LWL use imlib (version 1.x but 2.x
>> in my test) to access external image, and imlib1 depends on libpng/libjpeg.
>>
>> --binghe
>>
>> [1] http://www.lispworks.com/documentation/lw60/CAPUG-M/html/capiuser-m-175.htm#pgfId-905296
>>
>> 在 2010-10-31,06:59, Sztefan Edwards 写道:
>>
>> >
>> > 2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
>> >>
>> >> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
>> >>
>> >>> The graphic formats that are supported vary by platform. Presumably, on
>> >>> each platform, they are the ones that the Lispworks implementors felt they
>> >>> could easily support using libraries that they could count on having
>> >>> available on the platform.
>> >>
>> >> Because, since Lispworks is a commercial product, they probably cannot use
>> >> freely available graphics libraries and have to write their own. That brings
>> >> a natural limit how many formats you may have available without the adverse
>> >> effect on the actual core product development, but that should not be that
>> >> much of a trouble, since you probably can convert your own image files into
>> >> one of the supported formats without the need to drink coffee at night.
>> >>
>> >>
>> >
>> > libpng & libjpeg should be free enough; that just leaves, oh, a
>> > hundred or so other formats. :D
>> >
>> > Still, what image types is Ryan attempting to use, and what types are
>> > supported by CAPI?
>> >
>> > --
>> > ====
>> > Q. How many Prolog programmers does it take to change a lightbulb?
>> > A. No.
>> >
>>
>
>



-- 
Ryan Hope, M.S.
CogWorks Lab
Department of Cognitive Science
Rensselaer Polytechnic Institute


Re: LWP6.0 "Other types of images are not implemented"

Neither of the examples below work:

Ex1:
(capi:contain (make-instance 'capi:push-button :image
(gp:read-external-image (merge-pathnames
"images/icons/mail-forward.png" (directory-namestring
(asdf:system-definition-pathname 'cogworld))))))

Ex2:
(gp:register-image-translation 'img-email (gp:read-external-image
(merge-pathnames "images/icons/mail-forward.png" base)))
(capi:contain (make-instance 'capi:push-button :image 'img-email))

On Tue, Feb 22, 2011 at 11:34 PM, Ryan Hope <rmh3093@gmail.com> wrote:
> I am trying to load PNG files...
>
> Below is the backtrace:
>
> Call to ERROR
> Call to GRAPHICS-PORTS:CONVERT-EXTERNAL-IMAGE
> Call to GRAPHICS-PORTS:LOAD-IMAGE
> Call to CAPI::INSTALL-ONE-BUTTON-IMAGE
> Call to CAPI::MAP-BUTTON-IMAGES
> Call to (METHOD CAPI-LIBRARY:FINALIZE-REPRESENTATION
> (CAPI-GTK-LIBRARY::BUTTON-REPRESENTATION))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to CLOS::NEXT-METHOD-CALL-1
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to CLOS::NEXT-METHOD-CALL-1
> Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
> Call to CLOS::NEXT-METHOD-CALL-1
> Call to (METHOD CAPI::CREATE :AROUND (CAPI:INTERFACE))
> Call to CLOS::METHOD-COMBINATION-TEMPLATE
> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> Call to (METHOD CAPI::DO-DISPLAY-AUX (T T T))
> Call to (SUBFUNCTION CAPI::DEFAULT-TOP-LEVEL
> CAPI::INITIALIZE-AND-PROCESS-EVENTS)
> Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
> Call to MP::PROCESS-SG-FUNCTION
>
> 2010/11/1 Martin Simmons <martin@lispworks.com>:
>>
>> The LW Personal Edition uses GTK+, which has its own image converters, so I
>> think the problem lies elsewhere.
>>
>> --
>> Martin Simmons
>> LispWorks Ltd
>> http://www.lispworks.com/
>>
>>
>>>>>>> On Mon, 1 Nov 2010 01:17:31 +0800, Chun Tian (binghe) said:
>>>
>>> Related LispWorks document [1] said that LWL use imlib (version 1.x but 2.x
>>> in my test) to access external image, and imlib1 depends on libpng/libjpeg.
>>>
>>> --binghe
>>>
>>> [1] http://www.lispworks.com/documentation/lw60/CAPUG-M/html/capiuser-m-175.htm#pgfId-905296
>>>
>>> 在 2010-10-31,06:59, Sztefan Edwards 写道:
>>>
>>> >
>>> > 2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
>>> >>
>>> >> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
>>> >>
>>> >>> The graphic formats that are supported vary by platform. Presumably, on
>>> >>> each platform, they are the ones that the Lispworks implementors felt they
>>> >>> could easily support using libraries that they could count on having
>>> >>> available on the platform.
>>> >>
>>> >> Because, since Lispworks is a commercial product, they probably cannot use
>>> >> freely available graphics libraries and have to write their own. That brings
>>> >> a natural limit how many formats you may have available without the adverse
>>> >> effect on the actual core product development, but that should not be that
>>> >> much of a trouble, since you probably can convert your own image files into
>>> >> one of the supported formats without the need to drink coffee at night.
>>> >>
>>> >>
>>> >
>>> > libpng & libjpeg should be free enough; that just leaves, oh, a
>>> > hundred or so other formats. :D
>>> >
>>> > Still, what image types is Ryan attempting to use, and what types are
>>> > supported by CAPI?
>>> >
>>> > --
>>> > ====
>>> > Q. How many Prolog programmers does it take to change a lightbulb?
>>> > A. No.
>>> >
>>>
>>
>>
>
>
>
> --
> Ryan Hope, M.S.
> CogWorks Lab
> Department of Cognitive Science
> Rensselaer Polytechnic Institute
>



-- 
Ryan Hope, M.S.
CogWorks Lab
Department of Cognitive Science
Rensselaer Polytechnic Institute


Re: LWP6.0 "Other types of images are not implemented"

Sorry Ex2 should have been this:

(gp:register-image-translation 'img-email (gp:read-external-image
(merge-pathnames "images/icons/mail-forward.png"
(asdf:system-definition-pathname 'cogworld))))
(capi:contain (make-instance 'capi:push-button :image 'img-email))

On Wed, Feb 23, 2011 at 1:24 AM, Ryan Hope <rmh3093@gmail.com> wrote:
> Neither of the examples below work:
>
> Ex1:
> (capi:contain (make-instance 'capi:push-button :image
> (gp:read-external-image (merge-pathnames
> "images/icons/mail-forward.png" (directory-namestring
> (asdf:system-definition-pathname 'cogworld))))))
>
> Ex2:
> (gp:register-image-translation 'img-email (gp:read-external-image
> (merge-pathnames "images/icons/mail-forward.png" base)))
> (capi:contain (make-instance 'capi:push-button :image 'img-email))
>
> On Tue, Feb 22, 2011 at 11:34 PM, Ryan Hope <rmh3093@gmail.com> wrote:
>> I am trying to load PNG files...
>>
>> Below is the backtrace:
>>
>> Call to ERROR
>> Call to GRAPHICS-PORTS:CONVERT-EXTERNAL-IMAGE
>> Call to GRAPHICS-PORTS:LOAD-IMAGE
>> Call to CAPI::INSTALL-ONE-BUTTON-IMAGE
>> Call to CAPI::MAP-BUTTON-IMAGES
>> Call to (METHOD CAPI-LIBRARY:FINALIZE-REPRESENTATION
>> (CAPI-GTK-LIBRARY::BUTTON-REPRESENTATION))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to CLOS::NEXT-METHOD-CALL-1
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to CLOS::NEXT-METHOD-CALL-1
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
>> Call to CLOS::NEXT-METHOD-CALL-1
>> Call to (METHOD CAPI::CREATE :AROUND (CAPI:INTERFACE))
>> Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> Call to (METHOD CAPI::DO-DISPLAY-AUX (T T T))
>> Call to (SUBFUNCTION CAPI::DEFAULT-TOP-LEVEL
>> CAPI::INITIALIZE-AND-PROCESS-EVENTS)
>> Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
>> Call to MP::PROCESS-SG-FUNCTION
>>
>> 2010/11/1 Martin Simmons <martin@lispworks.com>:
>>>
>>> The LW Personal Edition uses GTK+, which has its own image converters, so I
>>> think the problem lies elsewhere.
>>>
>>> --
>>> Martin Simmons
>>> LispWorks Ltd
>>> http://www.lispworks.com/
>>>
>>>
>>>>>>>> On Mon, 1 Nov 2010 01:17:31 +0800, Chun Tian (binghe) said:
>>>>
>>>> Related LispWorks document [1] said that LWL use imlib (version 1.x but 2.x
>>>> in my test) to access external image, and imlib1 depends on libpng/libjpeg.
>>>>
>>>> --binghe
>>>>
>>>> [1] http://www.lispworks.com/documentation/lw60/CAPUG-M/html/capiuser-m-175.htm#pgfId-905296
>>>>
>>>> 在 2010-10-31,06:59, Sztefan Edwards 写道:
>>>>
>>>> >
>>>> > 2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
>>>> >>
>>>> >> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
>>>> >>
>>>> >>> The graphic formats that are supported vary by platform. Presumably, on
>>>> >>> each platform, they are the ones that the Lispworks implementors felt they
>>>> >>> could easily support using libraries that they could count on having
>>>> >>> available on the platform.
>>>> >>
>>>> >> Because, since Lispworks is a commercial product, they probably cannot use
>>>> >> freely available graphics libraries and have to write their own. That brings
>>>> >> a natural limit how many formats you may have available without the adverse
>>>> >> effect on the actual core product development, but that should not be that
>>>> >> much of a trouble, since you probably can convert your own image files into
>>>> >> one of the supported formats without the need to drink coffee at night.
>>>> >>
>>>> >>
>>>> >
>>>> > libpng & libjpeg should be free enough; that just leaves, oh, a
>>>> > hundred or so other formats. :D
>>>> >
>>>> > Still, what image types is Ryan attempting to use, and what types are
>>>> > supported by CAPI?
>>>> >
>>>> > --
>>>> > ====
>>>> > Q. How many Prolog programmers does it take to change a lightbulb?
>>>> > A. No.
>>>> >
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Ryan Hope, M.S.
>> CogWorks Lab
>> Department of Cognitive Science
>> Rensselaer Polytechnic Institute
>>
>
>
>
> --
> Ryan Hope, M.S.
> CogWorks Lab
> Department of Cognitive Science
> Rensselaer Polytechnic Institute
>



-- 
Ryan Hope, M.S.
CogWorks Lab
Department of Cognitive Science
Rensselaer Polytechnic Institute


Re: LWP6.0 "Other types of images are not implemented"

>>>>> On Wed, 23 Feb 2011 01:24:57 +0000, Ryan Hope said:
> 
> Neither of the examples below work:
> 
> Ex1:
> (capi:contain (make-instance 'capi:push-button :image
> (gp:read-external-image (merge-pathnames
> "images/icons/mail-forward.png" (directory-namestring
> (asdf:system-definition-pathname 'cogworld))))))
> 
> Ex2:
> (gp:register-image-translation 'img-email (gp:read-external-image
> (merge-pathnames "images/icons/mail-forward.png" base)))
> (capi:contain (make-instance 'capi:push-button :image 'img-email))

Sorry, non-BMP images only work for output-pane at the moment on Linux and
Windows.  We will fix it.


> 
> On Tue, Feb 22, 2011 at 11:34 PM, Ryan Hope <rmh3093@gmail.com> wrote:
> > I am trying to load PNG files...
> >
> > Below is the backtrace:
> >
> > Call to ERROR
> > Call to GRAPHICS-PORTS:CONVERT-EXTERNAL-IMAGE
> > Call to GRAPHICS-PORTS:LOAD-IMAGE
> > Call to CAPI::INSTALL-ONE-BUTTON-IMAGE
> > Call to CAPI::MAP-BUTTON-IMAGES
> > Call to (METHOD CAPI-LIBRARY:FINALIZE-REPRESENTATION
> > (CAPI-GTK-LIBRARY::BUTTON-REPRESENTATION))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to CLOS::NEXT-METHOD-CALL-1
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to CLOS::NEXT-METHOD-CALL-1
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
> > Call to CLOS::NEXT-METHOD-CALL-1
> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:INTERFACE))
> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
> > Call to (METHOD CAPI::DO-DISPLAY-AUX (T T T))
> > Call to (SUBFUNCTION CAPI::DEFAULT-TOP-LEVEL
> > CAPI::INITIALIZE-AND-PROCESS-EVENTS)
> > Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
> > Call to MP::PROCESS-SG-FUNCTION
> >
> > 2010/11/1 Martin Simmons <martin@lispworks.com>:
> >>
> >> The LW Personal Edition uses GTK+, which has its own image converters, so I
> >> think the problem lies elsewhere.
> >>
> >> --
> >> Martin Simmons
> >> LispWorks Ltd
> >> http://www.lispworks.com/
> >>
> >>
> >>>>>>> On Mon, 1 Nov 2010 01:17:31 +0800, Chun Tian (binghe) said:
> >>>
> >>> Related LispWorks document [1] said that LWL use imlib (version 1.x but 2.x
> >>> in my test) to access external image, and imlib1 depends on libpng/libjpeg.
> >>>
> >>> --binghe
> >>>
> >>> [1] http://www.lispworks.com/documentation/lw60/CAPUG-M/html/capiuser-m-175.htm#pgfId-905296
> >>>
> >>> 在 2010-10-31,06:59, Sztefan Edwards 写道:
> >>>
> >>> >
> >>> > 2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
> >>> >>
> >>> >> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
> >>> >>
> >>> >>> The graphic formats that are supported vary by platform. Presumably, on
> >>> >>> each platform, they are the ones that the Lispworks implementors felt they
> >>> >>> could easily support using libraries that they could count on having
> >>> >>> available on the platform.
> >>> >>
> >>> >> Because, since Lispworks is a commercial product, they probably cannot use
> >>> >> freely available graphics libraries and have to write their own. That brings
> >>> >> a natural limit how many formats you may have available without the adverse
> >>> >> effect on the actual core product development, but that should not be that
> >>> >> much of a trouble, since you probably can convert your own image files into
> >>> >> one of the supported formats without the need to drink coffee at night.
> >>> >>
> >>> >>
> >>> >
> >>> > libpng & libjpeg should be free enough; that just leaves, oh, a
> >>> > hundred or so other formats. :D
> >>> >
> >>> > Still, what image types is Ryan attempting to use, and what types are
> >>> > supported by CAPI?
> >>> >
> >>> > --
> >>> > ====
> >>> > Q. How many Prolog programmers does it take to change a lightbulb?
> >>> > A. No.
> >>> >
> >>>
> >>
> >>
> >
> >
> >
> > --
> > Ryan Hope, M.S.
> > CogWorks Lab
> > Department of Cognitive Science
> > Rensselaer Polytechnic Institute
> >
> 
> 
> 
> -- 
> Ryan Hope, M.S.
> CogWorks Lab
> Department of Cognitive Science
> Rensselaer Polytechnic Institute
> 

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/


Re: LWP6.0 "Other types of images are not implemented"

Any ETA on such a fix?

On Wed, Feb 23, 2011 at 1:20 PM, Martin Simmons <martin@lispworks.com> wrote:
>
>>>>>> On Wed, 23 Feb 2011 01:24:57 +0000, Ryan Hope said:
>>
>> Neither of the examples below work:
>>
>> Ex1:
>> (capi:contain (make-instance 'capi:push-button :image
>> (gp:read-external-image (merge-pathnames
>> "images/icons/mail-forward.png" (directory-namestring
>> (asdf:system-definition-pathname 'cogworld))))))
>>
>> Ex2:
>> (gp:register-image-translation 'img-email (gp:read-external-image
>> (merge-pathnames "images/icons/mail-forward.png" base)))
>> (capi:contain (make-instance 'capi:push-button :image 'img-email))
>
> Sorry, non-BMP images only work for output-pane at the moment on Linux and
> Windows.  We will fix it.
>
>
>>
>> On Tue, Feb 22, 2011 at 11:34 PM, Ryan Hope <rmh3093@gmail.com> wrote:
>> > I am trying to load PNG files...
>> >
>> > Below is the backtrace:
>> >
>> > Call to ERROR
>> > Call to GRAPHICS-PORTS:CONVERT-EXTERNAL-IMAGE
>> > Call to GRAPHICS-PORTS:LOAD-IMAGE
>> > Call to CAPI::INSTALL-ONE-BUTTON-IMAGE
>> > Call to CAPI::MAP-BUTTON-IMAGES
>> > Call to (METHOD CAPI-LIBRARY:FINALIZE-REPRESENTATION
>> > (CAPI-GTK-LIBRARY::BUTTON-REPRESENTATION))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to CLOS::NEXT-METHOD-CALL-1
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI:MAP-PANE-CHILDREN (CAPI:LAYOUT T))
>> > Call to (METHOD CAPI::REDO-LAYOUT (CAPI:LAYOUT))
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:LAYOUT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to CLOS::NEXT-METHOD-CALL-1
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI::LIBRARY-ELEMENT))
>> > Call to CLOS::NEXT-METHOD-CALL-1
>> > Call to (METHOD CAPI::CREATE :AROUND (CAPI:INTERFACE))
>> > Call to CLOS::METHOD-COMBINATION-TEMPLATE
>> > Call to (METHOD CAPI::ENSURE-PANE-CREATED (CAPI::LIBRARY-ELEMENT))
>> > Call to (METHOD CAPI::DO-DISPLAY-AUX (T T T))
>> > Call to (SUBFUNCTION CAPI::DEFAULT-TOP-LEVEL
>> > CAPI::INITIALIZE-AND-PROCESS-EVENTS)
>> > Call to CAPI::INITIALIZE-AND-PROCESS-EVENTS
>> > Call to MP::PROCESS-SG-FUNCTION
>> >
>> > 2010/11/1 Martin Simmons <martin@lispworks.com>:
>> >>
>> >> The LW Personal Edition uses GTK+, which has its own image converters, so I
>> >> think the problem lies elsewhere.
>> >>
>> >> --
>> >> Martin Simmons
>> >> LispWorks Ltd
>> >> http://www.lispworks.com/
>> >>
>> >>
>> >>>>>>> On Mon, 1 Nov 2010 01:17:31 +0800, Chun Tian (binghe) said:
>> >>>
>> >>> Related LispWorks document [1] said that LWL use imlib (version 1.x but 2.x
>> >>> in my test) to access external image, and imlib1 depends on libpng/libjpeg.
>> >>>
>> >>> --binghe
>> >>>
>> >>> [1] http://www.lispworks.com/documentation/lw60/CAPUG-M/html/capiuser-m-175.htm#pgfId-905296
>> >>>
>> >>> 在 2010-10-31,06:59, Sztefan Edwards 写道:
>> >>>
>> >>> >
>> >>> > 2010/10/30 Yuri Davidovsky <yury.davidouski2@mail.dcu.ie>:
>> >>> >>
>> >>> >> On Sat, 30 Oct 2010 17:20:44 +0100, mikel evins <mevins@me.com> wrote:
>> >>> >>
>> >>> >>> The graphic formats that are supported vary by platform. Presumably, on
>> >>> >>> each platform, they are the ones that the Lispworks implementors felt they
>> >>> >>> could easily support using libraries that they could count on having
>> >>> >>> available on the platform.
>> >>> >>
>> >>> >> Because, since Lispworks is a commercial product, they probably cannot use
>> >>> >> freely available graphics libraries and have to write their own. That brings
>> >>> >> a natural limit how many formats you may have available without the adverse
>> >>> >> effect on the actual core product development, but that should not be that
>> >>> >> much of a trouble, since you probably can convert your own image files into
>> >>> >> one of the supported formats without the need to drink coffee at night.
>> >>> >>
>> >>> >>
>> >>> >
>> >>> > libpng & libjpeg should be free enough; that just leaves, oh, a
>> >>> > hundred or so other formats. :D
>> >>> >
>> >>> > Still, what image types is Ryan attempting to use, and what types are
>> >>> > supported by CAPI?
>> >>> >
>> >>> > --
>> >>> > ====
>> >>> > Q. How many Prolog programmers does it take to change a lightbulb?
>> >>> > A. No.
>> >>> >
>> >>>
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Ryan Hope, M.S.
>> > CogWorks Lab
>> > Department of Cognitive Science
>> > Rensselaer Polytechnic Institute
>> >
>>
>>
>>
>> --
>> Ryan Hope, M.S.
>> CogWorks Lab
>> Department of Cognitive Science
>> Rensselaer Polytechnic Institute
>>
>
> --
> Martin Simmons
> LispWorks Ltd
> http://www.lispworks.com/
>
>



-- 
Ryan Hope, M.S.
CogWorks Lab
Department of Cognitive Science
Rensselaer Polytechnic Institute


Updated at: 2020-12-10 08:38 UTC