Not a problem for me, but what about the migration itself, is my new
application working in 0.7 PRE still continue to work well with the official
0.7 release ?
Thanks Sebastian
Sebastian Werner wrote:
>
> Currently the output uses 2 spaces for indention. You can however
> easily search and replace this in any editor.
>
> We will try to make at least this setting configurable until 0.7.
>
> Sebastian
>
>
> Am 20.02.2007 um 20:48 schrieb ericson:
>
>>
>> Just a though, if I migrate now with 7.0 PRE , is the code will tay
>> compatible with the 0.7 release ?
>>
>> Thanks in advance
>>
>> PS: I'm using this syntax with tabs,
>>
>> if (blabla) {
>> }
>>
>> so i the migration tool works that way, it's ok for me :)
>>
>>
>> Derrell.Lipman wrote:
>>>
>>> In testing the migration from 0.6.5 to 0.7(pre), I had two
>>> failures, and
>>> some
>>> problems for which I provide suggestions/requests...
>>>
>>> Failures (both previously reported):
>>>
>>> 1. An abstract class that has a singleton pattern for testing was
>>> previously
>>> able to be used as an abstract class, but the migration
>>> converts it to
>>> a
>>> singleton which can not be extended as an abstract class.
>>>
>>> 2. A class defined with no superclass is properly migrated, but at
>>> runtime
>>> the
>>> new Clazz structure is overwritten because of incorrect copying
>>> of the
>>> qx.OO class definition from input to output.
>>>
>>>
>>> Generally, the migration went well. I did find, though, that it
>>> restructured
>>> the code *style* which I found quite annoying. I don't think that
>>> there
>>> is
>>> any reason that if I nicely structure an array or object, or put
>>> my braces
>>> at
>>> the beginning of the "next" line, that the migration should move
>>> things
>>> around
>>> and "unstructure" or "restructure" it. Braces movement seems most
>>> prevalent
>>> with the construct method, but I saw it elsewhere as well --
>>> particularly
>>> with
>>> my nicely indented structured arrays and objects. The style
>>> generated by
>>> the
>>> migration is, like in traditional qooxdoo source, mixed, not
>>> consistent.
>>>
>>> It took me a couple of hours to fix up the code style again, and
>>> that was
>>> on
>>> only a few of days worth of development. I expect that those with
>>> large
>>> projects needing migration will find themselves with quite a bit
>>> of manual
>>> labor ahead of them if they care about maintaining a consistent code
>>> style, or
>>> one that doesn't exactly match what the migration is creating.
>>>
>>> Since the migration appears to be "rewriting" much of the code, I
>>> suggest
>>> that
>>> there be a flag (or set of flags, similar to what the "indent"
>>> program
>>> provides) to allow the migration to maintain a consistent style
>>> agreeable
>>> to
>>> the developer. If nothing else, then a "braces at end of line" vs
>>> "braces
>>> at
>>> beginning of next line" option would be quite helpful, and arrays and
>>> objects
>>> should not be restructured.
>>>
>>> Cheers,
>>>
>>> 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-devel mailing list
>>> qooxdoo-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Experience-with-
>> migration-to-0.7-tf3255161.html#a9068994
>> Sent from the qooxdoo-devel mailing list archive at Nabble.com.
>>
>>
>> ----------------------------------------------------------------------
>> ---
>> 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-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> -------------------------------------------------------------------------
> 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-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
--
View this message in context:
http://www.nabble.com/Experience-with-migration-to-0.7-tf3255161.html#a9069695
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
-------------------------------------------------------------------------
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-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
