gmane.comp.lang.javascript.qooxdoo.devel

0.8 migration report

Hi all,

Here is my experience with migrating my code to 0.8. It was quite a
painful experience for me...

In the hope you can make it a more pleasant experience for others,
here are my comments about the migration itself. I also had many
issues in 0.8 which made the migration painful, but since those are
not specific to migrating from an earlier version, I'll post those
which are not fixed yet in trunk in separate messages.

These comments are after an attempt to follow the guidelines at:
http://qooxdoo.org/documentation/0.8/migration_guide_from_07

* I abandoned trying to go through the advertised "legacy" route (way
"1" in the guide). It just didn't work for me and made me loose much
time instead of saving some... The problem is that when you want to go
through "route 2", there are apparently no automated script to help
you: you have lots of "legacy" references that you need to get rid of.
It would be nice if there was a migration path for those who would
like to go straight to non-legacy crippled 0.8, as the migration
script could have done automatically much of the ".legacy" stripping I
had to do.

* I had to add #asset hints to my code, while it previously worked without.

* I had to add these lines (copied from the skeleton) to my
Application.js, to have debugging output. Couldn't find this mentioned
anywhere, and the migration script could have added that
automatically...

(Continue reading)

headers

Helder Magalhães | 8 Oct 10:46

Re: 0.8 migration report


Gaetan de Menten wrote:
> 
> * I had to add #asset hints to my code, while it previously worked
> without.
> 
> * I had to add these lines (copied from the skeleton) to my
> Application.js, to have debugging output. Couldn't find this mentioned
> anywhere, and the migration script could have added that
> automatically...
> 
>             if (qx.core.Variant.isSet("qx.debug", "on")) {
>                 qx.log.appender.Native;
>                 qx.log.appender.Console;
>             }
> 
> * Also not mentioned in the doc, I had to change all occurences of
> adding several items to a menu at once to one item per call:
> -            file_menu.add(new_mb, open_mb, save_mb);
> +            file_menu.add(new_mb);
> +            file_menu.add(open_mb);
> +            file_menu.add(save_mb);
> 
> * This was mentioned in the doc but could have easily been done
> automatically:
>  qx.util.Mime.XML -> "application/xml"
> 
> * table.model.Simple: _rowArr was renamed to __rowArr and wasn't
> mentioned in the doc. This is a private variable but should be
> mentioned in the "migration notes" anyway as people using a custom

(Continue reading)

headers

thron7 | 8 Oct 16:47

Re: 0.8 migration report


Gaetan de Menten wrote:
> Hi all,
>
> Here is my experience with migrating my code to 0.8. It was quite a
> painful experience for me...
>
> In the hope you can make it a more pleasant experience for others,
> here are my comments about the migration itself. I also had many
> issues in 0.8 which made the migration painful, but since those are
> not specific to migrating from an earlier version, I'll post those
> which are not fixed yet in trunk in separate messages.
>
> These comments are after an attempt to follow the guidelines at:
> http://qooxdoo.org/documentation/0.8/migration_guide_from_07
>
> * I abandoned trying to go through the advertised "legacy" route (way
> "1" in the guide). It just didn't work for me and made me loose much
> time instead of saving some... 

Could you elaborate what exactly made you stop in this track?!

> The problem is that when you want to go
> through "route 2", there are apparently no automated script to help
> you: you have lots of "legacy" references that you need to get rid of.
> It would be nice if there was a migration path for those who would
> like to go straight to non-legacy crippled 0.8, as the migration
> script could have done automatically much of the ".legacy" stripping I
> had to do.
>

(Continue reading)

headers

Ian Horst | 8 Oct 17:16

Re: 0.8 migration report

It didn't work for me too. So I went the same route. Manually moving legacy staff to 0.8.

Ian Horst

thron7 wrote:
> 
> Gaetan de Menten wrote:
>> Hi all,
>>
>> Here is my experience with migrating my code to 0.8. It was quite a
>> painful experience for me...
>>
>> In the hope you can make it a more pleasant experience for others,
>> here are my comments about the migration itself. I also had many
>> issues in 0.8 which made the migration painful, but since those are
>> not specific to migrating from an earlier version, I'll post those
>> which are not fixed yet in trunk in separate messages.
>>
>> These comments are after an attempt to follow the guidelines at:
>> http://qooxdoo.org/documentation/0.8/migration_guide_from_07
>>
>> * I abandoned trying to go through the advertised "legacy" route (way
>> "1" in the guide). It just didn't work for me and made me loose much
>> time instead of saving some... 
> 
> Could you elaborate what exactly made you stop in this track?!
> 
>> The problem is that when you want to go
>> through "route 2", there are apparently no automated script to help
>> you: you have lots of "legacy" references that you need to get rid of.

(Continue reading)

headers

Gaetan de Menten | 8 Oct 17:24

Re: 0.8 migration report

On Wed, Oct 8, 2008 at 4:47 PM, thron7 <thron7 <at> users.sourceforge.net> wrote:
>
> Gaetan de Menten wrote:
>> Hi all,
>>
>> Here is my experience with migrating my code to 0.8. It was quite a
>> painful experience for me...
>>
>> In the hope you can make it a more pleasant experience for others,
>> here are my comments about the migration itself. I also had many
>> issues in 0.8 which made the migration painful, but since those are
>> not specific to migrating from an earlier version, I'll post those
>> which are not fixed yet in trunk in separate messages.
>>
>> These comments are after an attempt to follow the guidelines at:
>> http://qooxdoo.org/documentation/0.8/migration_guide_from_07
>>
>> * I abandoned trying to go through the advertised "legacy" route (way
>> "1" in the guide). It just didn't work for me and made me loose much
>> time instead of saving some...
>
> Could you elaborate what exactly made you stop in this track?!

It just didn't work. I had a blank page, no error message, no message
in the console (but I probably didn't find the way to enable debug
messages yet). It tried for several hours to get it to work then
abandoned, got rid of all the legacy stuff (doing the simple renames
as well) and it started to work quite quickly. With errors at first
but I fixed them as I went. The big difference was that at least
something appeared and some errors showed up.

(Continue reading)

headers

Jim Hunter | 9 Oct 00:25

Re: 0.8 migration report

I have to admit that I didn't get the legacy route to work straight off either and went to manually re-writing the classes after it converted them to legacy classes. I needed to re-write most of my classes anyway because they are heavily based on layouts and that is totally changed in .8. So I simply have started from the outer frames and working my way into the more detailed classes and so far it's working well. I have to admit that the new layout system is a little more coding but I like the way they work much better.

And as for the new config.json file as compared to the older config, I don't like it (yet). There is a nice document that tells what all the section are but really doesn't tell you how to use this new config file to your benefit. I still haven't found anyone that can tell me what change to make to the config.json file so that when I generate a script or build version of my application I get ALL my classes and ALL qooxdoo classes included. I generate a lot of Javascript code on the server and there may not be any references to those classes in my exposed code so I need everything included (for now, I will do a code review after everything is running and cull down what gets included to only include the classes that are actually used).

Thanks,
Jim

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

headers

Gaetan de Menten | 9 Oct 08:44

Re: 0.8 migration report

On Thu, Oct 9, 2008 at 12:25 AM, Jim Hunter <jim <at> epiuniverse.com> wrote:

> And as for the new config.json file as compared to the older config, I don't
> like it (yet). There is a nice document that tells what all the section are
> but really doesn't tell you how to use this new config file to your benefit.

I feel the same. Even though I *now* realize the generator docs are
great, I initially took quite a while to find what was the new names
of keys I needed to change, and what the new default values are. As
someone said in another thread, a migration guide (or even script) for
config files would be nice. It would probably include a list of old
Makefile variable -> new config.json key.

Also, the wording at:
http://qooxdoo.org/documentation/0.8/generator
seem outdated.

--

-- 
Gaëtan de Menten
http://openhex.org

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

headers

Andreas Ecker | 9 Oct 09:09

Re: 0.8 migration report

Howdy!

> > And as for the new config.json file as compared to the older config, I don't
> > like it (yet). There is a nice document that tells what all the section are
> > but really doesn't tell you how to use this new config file to your benefit.

Yes, the documentation should be extended to make it easier to get
started with customizations to the build process. I'm sure Thomas will
come up with some great user guide (working on that next week as he has
two days off now).

> I feel the same. Even though I *now* realize the generator docs are
> great, I initially took quite a while to find what was the new names
> of keys I needed to change, and what the new default values are. As
> someone said in another thread, a migration guide (or even script) for
> config files would be nice. It would probably include a list of old
> Makefile variable -> new config.json key.

Such a list was planned, and a link exists in the migration guide. It
just couldn't be finished by Jonny before his vacation. I'm sure he'll
be adding the most relevant transitions when he returns next week.

> Also, the wording at:
> http://qooxdoo.org/documentation/0.8/generator
> seem outdated.

Oops, thanks, replace the outdated info,

Andreas

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/