Re: [qooxdoo-commit] SF.net SVN: qooxdoo: [6546] branches/legacy_0_6_x/qooxdoo/frontend/ framework/source/class/qx/util/fsm/FiniteStateMachine.js

[Sebastian W. <in...@se...>]

Am 28.02.2007 um 20:26 schrieb Derrell.Lipman@UnwiredUniverse.com:

> Sebastian Werner <in...@se...> writes:
>
>> Come on :) This is a simple search and replace. I don't think this  
>> is  too
>> complicated. Why is this so disruptive? Should be doable in about   
>> 5 minutes
>
> I said, it's easy to do, but disruptive to others working on the  
> code who have
> no idea what these changes are.  I'm the point of contact for  
> updates to
> qooxdoo, and I don't have the time to do Samba qooxdoo support  
> right now.
> That's what I mean by disruptive.  The actual change is trivial.

Ok, I understand.

>
>> :) Maybe you can do it locally - without committing your  changes  
>> back?
>
> If I can do it quickly and easily...I'd like to use the migration  
> script, but
> with the legacy_0_6_x tree in a separate location, what command  
> line do I use?
> I'm trying this, but it tells me it can't find qx.OO so I guess I  
> need to do
> something to tell it where to find the qooxdoo tree.
>
> I'm using this command line from my skeleton-based directory  
> structure.  What
> additional options do I need?
>
> ../../../../../future-tests/qooxdoo.svn/legacy_0_6_x/qooxdoo/ 
> frontend/framework/tool/generator.py --class-path source/class -- 
> migrate-source --migration-target 0.6.6

Normally these are only warnings. Just ignore them and continue the  
with the migration. Otherwise you can add your qooxdoo class path and  
define and exclude the qooxdoo classes e.g.:

--class-path path/to/qooxdoo/frontend/framework/source/class -- 
exclude-without-dependencies qx.*


>
> (Hey, how about adding a "make migrate" target in the Makefile that  
> uses the
> already-set configuration?)

Yes, yes. Mhh, maybe we could add this. :) Please help us remembering  
an open a bug. During the current active development such feature  
wishes otherwise get forgotten...


>
>> Finally you need to update to 0.6.6 first, before updating to 0.7
>> later. This change is in 0.6.6 because it makes it possible to  
>> allow an easy
>> migration to 0.7 later. I hope you understand this.
>
> Yup, that's no problem.  When I have the time to work on the stuff,  
> I can do
> whatever migration is necessary, get everything working, and  
> explain to the
> others what changes are happening.  It's just that right now, that  
> itme isn't
> allocated.

Hope you have some time the next days. Just a quick check would be  
really helpful. The backport went better than thought, but this does  
not mean that all is working well, too.

Sebastian



>
> Derrell
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> qooxdoo-commit mailing list
> qoo...@li...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-commit