Thanks for all the feedback. I don't understand why things happen as they
do, but I tried to build my app 3 times and all three times when I ran it I
got a failure on qx.util.Json with the error that it wasn't a class. And
when I used FireBug and tested for the class it didn't exist. But just now,
after updating the generate.py file, it compiled and my app is running just
fine. Updateing the python file was the only change made from when it didn't
work to when it did work.
Well, at least right now it seems to be working. Now to test it against IE
and see if any of the issues I have are gone.
Thanks for your assistance,
Jim
On Wed, Sep 21, 2011 at 11:41 AM, thron7 <[email protected]>wrote:
> **
> Now we're slowly getting there...
>
>
> On 09/21/2011 07:47 PM, Jim Hunter wrote:
>
> I think I know why there were no changes made for 1.5. The dat file in the
> 1.5 patches folder in the migration folder is empty!
>
>
> That's only half true, and now I'm beginning to understand where you
> diverted. The 1.5 migration folder contains two subfolders, one of them
> being the 'patches' folder, which, yes, only contains an empty file. But
> this is correct, as they were no patches for this release relative to 1.4.x.
> This is not uncommon.
>
> On the other hand, there is the subfolder 'info' which contains entries
> which inform/warn about certain things when migrating. Those files are most
> often used for deprecation warnings. In the case of 1.5, one of the things
> being deprecated is qx.util.Json. But the class is *still there*, fully
> functional, with all methods. So you should have no problem to use
> qx.util.Json.stringify (which you mentioned in your initial posting). Just
> fire up your app which should run fine.
>
>
> There are no instructions to execute, that's why nothing was changed. I
> can't imagine that there are no change from 1.4.2 to 1.5.
>
>
> As I said there weren't any. You're complaining we're keeping the API
> stable :-).
>
> You should keep a copy of the migration log, and step-by-step follow the
> information messages, e.g. by changing occurrences of qx.util.Json to
> qx.lang.Json. But you can take as long as you want to do that while you are
> using 1.5. APIs deprecated in 1.5 will only be removed with 1.6.
>
>
>
> Can someone send me a file with actual patch code in it for 1.5?
>
>
> Don't do this. If you feel unsure about what the migration process does,
> just have a look in the release notes [1]. All important API changes are
> usually also mentioned there.
>
>
> T.
>
> [1] http://qooxdoo.org/about/release_notes/1.5#migration
>
>
>
>
> Thanks,
> Jim
>
>
> On Wed, Sep 21, 2011 at 10:30 AM, Jim Hunter <[email protected]> wrote:
>
>> Any other suggestions, anyone? The config.json is pointing to the correct
>> qooxdoo, running generate.py info shows that the version of qooxdoo is 1.5
>> and I made sure that I have a current version of generate.py in my
>> application folder. Yet, when I run the migration it still stops at 1.4.2.
>>
>> So I am still open to suggestions here.
>>
>> Thanks,
>> Jim
>>
>>
>>
>> On Tue, Sep 20, 2011 at 11:51 PM, thron7
>> <[email protected]>wrote:
>>
>>> The fact that the migration process is only upgrading to 1.4.2 means
>>> that your app relates to a 1.4.2 installation on your machine. It doesn't
>>> matter where you put your project files, you could burry them deep into the
>>> 1.5 framework. For your project the only relevant link to the qooxdoo
>>> installation is the QOOXDOO_PATH entry in its config.json. If this points to
>>> a 1.4.2 installation, this will be used. Change QOOXDOO_PATH in config.json,
>>> and if you have an old (<1.2) generate.py, create a skeleton somewhere with
>>> create-application.py and copy its generate.py file over to your project.
>>> Before and after you can run 'generate.py info' which will tell you which
>>> SDK it is using. Make sure it says "Framework version: 1.5" before you start
>>> migrating.
>>>
>>> T.
>>>
>>>
>>> On 09/21/2011 02:38 AM, Jim Hunter wrote:
>>>
>>> I have tried twice now to upgrade to 1.5 without success. Looking at
>>> the migration log, it is only upgrading to 1.4.2 and never upgrades to 1.5.
>>> The issue that I initially see (I haven't gotten past this issue yet to see
>>> if there are more things that didn't get migrated), is that I use
>>> qx.util.Json.stringify() in many places and this is removed in 1.5 and
>>> replaced with a new method but my code was not modified. As a matter fo
>>> fact, there were only a small handfull of changes and I was trying to
>>> migrate from 1.3pre to 1.5. I think there should have been more then 2 types
>>> of changes (about 10 instances in about 140 classes). Has anyone else run
>>> into this and how do I fix it?
>>>
>>> My steps were:
>>>
>>> 1) Download 1.5 SDK and extract it (renamed the folder to be the same
>>> name as what I use daily for my development to eliminate path issues)
>>> 2) Copied my project files into the Application folder (so that I am not
>>> effecting working code)
>>> 3) ran the migrate script. (generate.py migration and I even tried
>>> starting the migration at 1.0 besides starting at 1.2 and 1.3)
>>>
>>> I don't think it gets any more complicated then this.
>>>
>>> Thanks,
>>> Jim
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure contains a
>>> definitive record of customers, application performance, security
>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>> sense of it. Business sense. IT sense. Common
>>> sense.http://p.sf.net/sfu/splunk-d2dcopy1
>>>
>>>
>>> _______________________________________________
>>> qooxdoo-devel mailing
>>> [email protected]https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure contains a
>>> definitive record of customers, application performance, security
>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>> sense of it. Business sense. IT sense. Common sense.
>>> http://p.sf.net/sfu/splunk-d2dcopy1
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common
> sense.http://p.sf.net/sfu/splunk-d2dcopy1
>
>
> _______________________________________________
> qooxdoo-devel mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
