icon URI string question

[panyasan]

Hi,

I was looking through the docs, to no avail. I want to use an image from the ones shipped with the qooxdoo sdk. So I put this at the beginning of the class file:

/* ************************************************************************
#embed(qx.icontheme/48/status/dialog-information.png)
************************************************************************ */

and instantiate an Image widget in my code:

this.__image = new qx.ui.basic.Image("icon/Tango/48/status/dialog-information.png");

However, when the code is executed, qooxdoo tries to load the image from a wrong location:

http://localhost:8080/Bibliograph/qooxdoo-contrib/qcl/trunk/application/access/source/qx/icon/Tango/48/status/dialog-information.png

That means, it tries to load it from the application path rather than the qooxdoo path. The LET section of my config.json begins like so

  "let" :
  {
    "APPLICATION"  : "access",
    "QOOXDOO_PATH" : "../../../../qooxdoo/trunk",
    "QXTHEME"      : "qx.theme.Modern",
    "API_EXCLUDE"  : ["qx.legacy.*","qx.test.*"],
    "LOCALES"      : [ "en" ],
    "CACHE"        : "cache",
    "ROOT"         : ".",

which is exaclty the same as in the skeletonApplication in qooxdoo-contrib, which works when built.

What do I need to do so that the image is loaded from the correct location?

Thanks,

Christian
     

[panyasan]

panyasan wrote:

and instantiate an Image widget in my code:

this.__image = new qx.ui.basic.Image("icon/Tango/48/status/dialog-information.png");

Sorry, used the wrong code snipped: it is

this.__image = new qx.ui.basic.Image("icon/48/status/dialog-information.png");

without the "Tango", which used to work before in another application, but is not working now. So the problem it the same, "Tango" or not.

[panyasan]

panyasan wrote:

panyasan wrote:

and instantiate an Image widget in my code:

this.__image = new qx.ui.basic.Image("icon/Tango/48/status/dialog-information.png");

Sorry, used the wrong code snipped: it is

this.__image = new qx.ui.basic.Image("icon/48/status/dialog-information.png");

without the "Tango", which used to work before in another application, but is not working now. So the problem it the same, "Tango" or not.

It is really strange. If I add

      qx.util.AliasManager.getInstance().add(
        "icon",
        qxlibraries.qx.resourceUri + "/" +
          qx.util.AliasManager.getInstance().resolve("icon")
      );

in my main() method, the network tab in firebug shows that the image is correctly loaded from

http://localhost:8080/Bibliograph/qooxdoo-contrib/qooxdoo/trunk/framework/source/resource/qx/icon/Tango/48/status/dialog-information.png

However, qooxdoo still displays a notice:

qx.ui.basic.Image[hp]: Unknown image: ../../../../../qooxdoo/trunk/framework/source/resource/qx/icon/Tango/48/status/dialog-information.png

and does not display the image.

I am at a loss what to do? Is there a config.json or Manfifest.json setting that I need to configure?

Thanks, Christian

[Ralf Nieuwenhuijsen-2]

Which version are you using?

I've noticed that in the trunk, I need to explicitely add qx as an asset.
Perhaps you are hit by the same bug?

Mvg,
Ralf

On Sun, Jul 5, 2009 at 12:26 PM, panyasan <info@...> wrote:

panyasan wrote:
>
>
>
> panyasan wrote:
>>
>> and instantiate an Image widget in my code:
>>
>> this.__image = new
>> qx.ui.basic.Image("icon/Tango/48/status/dialog-information.png");
>>
>
> Sorry, used the wrong code snipped: it is
>
> this.__image = new
> qx.ui.basic.Image("icon/48/status/dialog-information.png");
>
> without the "Tango", which used to work before in another application, but
> is not working now. So the problem it the same, "Tango" or not.
>

It is really strange. If I add

     qx.util.AliasManager.getInstance().add(
       "icon",
       qxlibraries.qx.resourceUri + "/" +
         qx.util.AliasManager.getInstance().resolve("icon")
     );

in my main() method, the network tab in firebug shows that the image is
correctly loaded from

http://localhost:8080/Bibliograph/qooxdoo-contrib/qooxdoo/trunk/framework/source/resource/qx/icon/Tango/48/status/dialog-information.png

However, qooxdoo still displays a notice:

qx.ui.basic.Image[hp]: Unknown image:
../../../../../qooxdoo/trunk/framework/source/resource/qx/icon/Tango/48/status/dialog-information.png

and does not display the image.

I am at a loss what to do? Is there a config.json or Manfifest.json setting
that I need to configure?

Thanks, Christian

--
View this message in context: http://www.nabble.com/icon-URI-string-question-tp24334470p24341818.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[panyasan]

Ralf Nieuwenhuijsen-2 wrote:

Which version are you using?

I've noticed that in the trunk, I need to explicitely add qx as an asset.
Perhaps you are hit by the same bug?

Yes sorry, forgot to mention that I am using trunk.  How do you work around this?

Thanks, Christian

[Ralf Nieuwenhuijsen-2]

I've put this below the other default asset in my application.json

#asset(qx/*)

So it looks like this: (where mp is the project name)

/* ************************************************************************

   Bla bla

   Copyright:
     Bla bla

   License:
      Bla bla

   Authors:
     * Bla bla

************************************************************************ */

/* ************************************************************************

#asset(mp/*)
#asset(qx/*)

************************************************************************ */

Greetings,
Ralf

On Sun, Jul 5, 2009 at 8:10 PM, panyasan <info@...> wrote:

Ralf Nieuwenhuijsen-2 wrote:
>
> Which version are you using?
>
> I've noticed that in the trunk, I need to explicitely add qx as an asset.
> Perhaps you are hit by the same bug?
>
>

Yes sorry, forgot to mention that I am using trunk.  How do you work around
this?

Thanks, Christian
--
View this message in context: http://www.nabble.com/icon-URI-string-question-tp24334470p24345451.html

Sent from the qooxdoo-devel mailing list archive at Nabble.com.


------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[panyasan]

Ralf Nieuwenhuijsen-2 wrote:

I've put this below the other default asset in my application.json

#asset(qx/*)

That did it! Thanks so much.

[panyasan]

panyasan wrote:

Ralf Nieuwenhuijsen-2 wrote:

I've put this below the other default asset in my application.json

#asset(qx/*)

That did it! Thanks so much.

However, will this mean that all icons will be copied over into a built version? I haven't quite understood the philosophy behind this. Before, the generator would automatically detect the images that were needed from the appropriate iconset determined by the theme. Maybe the devs can clear up the confusion.

Thanks,

C

[panyasan]

panyasan wrote:

Ralf Nieuwenhuijsen-2 wrote:

I've put this below the other default asset in my application.json

#asset(qx/*)

However, will this mean that all icons will be copied over into a built version?
C

Answering myself: of course it does. Now, this seems to mean that I have to put each and every icon file that I want to use into the asset section in addition to using it in the source code. Why was the old behavior changed? It seems redundant to me since the generator parses every source file anyways and can detect icon URI strings automatically. I am sure there are reasons for this, but I liked the old behavior much better...

C.