Indeed, you have to stick to the JSDoc syntax rules (which include /**
... */ comment decorations).
T.
On 06/27/2013 10:10 AM, fprijate wrote:
> Hi
>
> Sorry.
>
> Before I had asserts in block comments without '*' at the begining of
> every comment row, which
> was Ok:
>
> /***
>
>
Hi
Sorry.
Before I had asserts in block comments without '*' at the begining of
every comment row, which
was Ok:
/***
#assert(...)
***/
after change to
/***
@assert(...)
***/
doesn't work anymore.
Changing to
/**
*
* @assert(...)
*
*/
everything is OK
Hi
In trunk:
Using #asset (... ) there are deprecation warnings (which is OK).
But @asset (...) deosn't work any more ( it worked yesterday).
There are also warnings like:
Unable to parse JSDoc entry: @type member
Unable to parse JSDoc entry: @type String
regards
Franček
--
View this me
Amit Rana wrote:
> Hi,
>
> I was just going through the forum to find some information about handling
> resources in my qooxdoo application.
> I wanted to point out that the URL given below in the posts
> (http://qooxdoo.org/documentation/0.8/ui_overview?s=asset#resource_handling)
> looks old and
Hi,
I was just going through the forum to find some information about handling
resources in my qooxdoo application.
I wanted to point out that the URL given below in the posts
(http://qooxdoo.org/documentation/0.8/ui_overview?s=asset#resource_handling)
looks old and doesn't point to the correct p
Hello,
There are a few questions regarding #asset hint here in mail list but
unfortunately
they didn't help me.
My main question following: If I would like to use icons shipped with
qooxdoo sdk,
what is the best way to do this? There are several options described
in documentation [1].
So, the las
It works !
In fact, I didn't know (never try) the net folder of firebug.
This allow me to notice all not loaded files and it was not my qooXdoo
code but some apache stuff.
Thanks !
On 30 Sep 2008, at 01:19, Petr Kobalíček wrote:
> Hi Jean,
>
> #asset is only evaluated at build time.
>
> Are y
I'm not using qxbuild, what is it ?
I'm using a pre build of qooXdoo 0.8, then all I have to do is include
qooXdoo file, I don't have to use Python and toolchain anymore.
The price is qooXdoo lib size witch is not optimize.
The benefit is built time witch is instant.
On 30 Sep 2008, at 01:19, P
Hi Jean,
#asset is only evaluated at build time.
Are you still using qxbuild ?
NOTE:
If you add "icons" to alias manager, you should use relative path to
icon. For example:
qx.util.AliasManager.getInstance().add("icons", "/icons/");
var listButton = new qx.ui.toolbar.Button("List",
"icons/24x2
Hi,
Is #asset evaluate at runtime or only as I assume at build time during
the python script (toolchain) ?
I experienced issue loading icon but remember I don't use the
toolchain, I "simply" include qooXdoo lib.
This is the way I unsuccessfully try to load icon :
qx.util.AliasManager.getIns
[EMAIL PROTECTED] wrote:
>> By compile do they mean generate? There is no compiling going on with
>> qooxdoo is there?
>>
>
> And why not? We parse Javascript, create an AST, do transformations on it,
> and write Javascript out again.
>
it is pretty interesting... js to js, I mean
>
>
> At the top of Application.js I see #asset and it is in a comment block.
> I read the generator_config article and see that they are compiler hints.
>
> By compile do they mean generate? There is no compiling going on with
> qooxdoo is there?
And why not? We parse Javascript, create an AST, do t
At the top of Application.js I see #asset and it is in a comment block.
I read the generator_config article and see that they are compiler hints.
By compile do they mean generate? There is no compiling going on with
qooxdoo is there?
is there any more documentation about #asset? I'm still no
13 matches
Mail list logo
