Daniel Hirtzbruch wrote:
> Hi,
>
> I noticed the same behaviour as deech - when I add classes to my own lib or
> even use a class in my app I wasn't using before, I have to run distclean
> and then source again (using svn trunk).
> Is this wanted? When I don't add new classes I don't need to run the
> generator and when I do add new files I have to use distclean before running
> the generator. Sounds confusing to me... ;-)
>   

Ok, so I
- created a new skeleton app with "create-application.py -n gui_nc"
- cd gui_nc; ./generate.py source
- ran the application ok
- added a new class: source/class/gui_nc/Myclass.js that adds another button
- changed the existing main class: source/class/gui_nc/Application.js:
     var o = new gui_nc.Myclass(doc);
- ./generate.py source again
- ran the application, both buttons show up, no error message

No need to run a clean job. So you guys have to be a bit more specific 
under which circumstances this misbehaviour shows up. Try to reproduce 
it in a skeleton.

If you add a new class to your library, and *reference* it in already 
used code (like above), 'generate.py source' is supposed to pick it up.

'source-all' will include all classes *known at that point in time*, so 
you can freely reference them in your code without re-running 
source/source-all. But if you *add* a new class, you have to re-run 
source-all so the new class is being picked up. If you are using 
'source', you also need to reference the class somewhere in already used 
code.

T.
 

> Thanks,
> Daniel
>
>
> Guilherme Aiolfi wrote:
>   
>> source will include just those files that you are using in your app (and
>> dependencies for those ones). So, it need to be called every time you use
>> a
>> new class (a class that was not used before in your code).
>> **source-all* will include all qooxdoo files. So you have to use
>> source-all
>> just once (or when you need to include a new file created by you).
>>
>> I use *distclean *just when I update qooxdoo. And *clean* just when I
>> think
>> that some changes I made have no effect for some reason related to cached
>> files (rarely).
>>
>> On Wed, Sep 30, 2009 at 3:54 PM, aditya siram
>> <[email protected]>wrote:
>>
>>     
>>> Hi all,
>>> I am using 0.8.3. What is the best way to run the generator after adding
>>> a
>>> class to a project?
>>>
>>> So assuming I have a working project after an initial "generate.py
>>> source-all", after adding a class should I run "generate.py source" or
>>> "generate.py source-all"? Also should I be doing a "generate.py clean" or
>>> "generate.py distclean" before I run the generator?
>>>
>>> I only ask because I have had issues where if I just add a class and run
>>> "generate.py source", the class name does not show up in the
>>> /source/script/projectname.js file and Firebug complains about an unknown
>>> constructor.
>>>
>>> thanks ...
>>> -deech
>>>
>>>       
>
>   

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to