Hi Fritz,
Thanks for your reply. Yes, I realise 1.0 is out. I have three other
Qx 0.8 web-clients in a suite of tools, so my first goal is to bring
this (biggest) legacy app into line with the others. We may or may
not migrate them all to Qx 1.0 from there.
Yes, I used the migration script -- it created the instances of qx.legacy.
Do you mean you were happy leaving some legacy parts in your
application in production? Or just in development while finishing the
migration work?
Also, an observation: it appears from the documentation here[1] that
the ultimate goal is to end up with code full of this:
this._widget = new x.y.z.Widget();
var future = new qx.legacy.ui.embed.Future().set({
width : "100%",
height : "100%",
content : this._widget
});
container.add(future);
Clearly that is not the desired end point. But the final migration
step, from the above code to pure 0.8 code is omitted.
Cheers,
Simon
[1] http://qooxdoo.org/documentation/0.8/migration_guide_from_07
On Mon, Jan 18, 2010 at 6:39 PM, Fritz Zaucker-2 [via qooxdoo]
<[email protected]> wrote:
> Hi Simon,
>
> you do realize that Qx 1.0 is out? As its relatively close to the 0.8 line,
> I'd recommend to migrate to 1.0.
>
> I assume that you used the Qx migration script? Most likely that the best
> you can do for automating the process. I'd assume that of the >1,000 lines
> of qx.legacy in your code a lot of them will have the same underlying
> reason. I'd not be surprised if at least some of them can be handled by
> search/replace in your editor or (a bit more powerful) with a "skript" along
> the line
>
> perl -p -i -e 's/some_regexp/replacement/'
>
> In a (not that large) migration project I was very happy with the Qx
> approach of being able to run the old application with the help of the
> qx.legacy class and just migrate step by step. Sometimes I thought
> afterwards I could have used bigger steps in making the transition for
> efficiency.
>
> Good luck and best regards,
> Fritz
>
> On Sun, 17 Jan 2010, waysoftheearth wrote:
>
>> Hello List,
>>
>> I am looking at migrating a reasonably large project up to Qx 0.8. In a
>> development sandbox we have migrated 435 js source files from 0.6 to 0.7.
>> Given that took several weeks of effort (and still requires polish), the
>> migration from 0.7 to 0.8 looks daunting. There are well over 1,000
>> occurrences of "qx.legacy" in the migrated 0.7 source code, for example,
>> each requiring manual attention.
>>
>> I wonder if anyone on the list can offer any advice as to an efficient
>> migration strategy? Has anyone built/used any particular tools that make
>> facilitate the process?
>>
>> Thanks,
>> Simon
> --
> Oetiker+Partner AG tel: +41 62 775 9903 (direct)
> Fritz Zaucker +41 62 775 9900 (switch board)
> Aarweg 15 +41 79 675 0630 (mobile)
> CH-4600 Olten fax: +41 62 775 9905
> Schweiz web: www.oetiker.ch
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ________________________________
> View message @
> http://n2.nabble.com/Advice-for-migration-large-legacy-project-tp4411713p4412326.html
> To unsubscribe from Advice for migration large legacy project, click here.
>
--
View this message in context:
http://n2.nabble.com/Advice-for-migration-large-legacy-project-tp4411713p4416579.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
