Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 04/10/2013 09:48 AM, Tobias Koller (GERMO GmbH) wrote: > Hi, > > the whole migration was too much work for me and so I decided to just create > a new 2.1-application and copy one class after the other and modify them. > I'm not finished yet but it looks good and I will finish "migration" in the > next view days. Ok, that's fine if it works for you. I guess in the end you will be doing much of the same work as if you went through the migration process I described, but without the benefit of always having your app complete and running (since this was our goal when we designed this approach). But nevermind. T. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 04/10/2013 09:48 AM, Tobias Koller (GERMO GmbH) wrote: > Hi, > > the whole migration was too much work for me and so I decided to just create > a new 2.1-application and copy one class after the other and modify them. > I'm not finished yet but it looks good and I will finish "migration" in the > next view days. Ok, that's fine if it works for you. I guess in the end you will be doing much of the same work as if you went through the migration process I described, but without the benefit of always having your app complete and running (since this was our goal when we designed this approach). But nevermind. T. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi, the whole migration was too much work for me and so I decided to just create a new 2.1-application and copy one class after the other and modify them. I'm not finished yet but it looks good and I will finish "migration" in the next view days. Thanks anyway for your answer! Tobi -Ursprüngliche Nachricht- Von: thron7 [mailto:[email protected]] Gesendet: Dienstag, 9. April 2013 19:46 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 04/03/2013 03:00 PM, Tobias Koller (GERMO GmbH) wrote: > Hi list, > > I finally created my application with all the new features I needed under qx > 0.7.4. > Everything worked fine till yesterday ;) > > The windows-update installed IE10 on my machine and my application didn't > work anymore. > A known problem (Invalid Character DOM Exception in IE9) occurred. I could > fix it in 0.7.4 but many other things didn't work too. > My colleague are also using IE10 and on there machine everything works > without problems... > > So I decided to give the migration from 0.7 to 2.2.1 a second chance > ;) > > I migrated my application to 0.8 but still with all legacy-widgets included. > And here I really need your help. > > I followed the migration-guide from > http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07#man > ual_work But I just don't know what to do with this > future-embed-thing. I presume you also looked through the "Porting parts" section. Is your app working after the migration (Checkpoint 2)? 0.8 has both the legacy widget system and the new widget system in the library. The whole idea is to have a working app while step-wise switching from legacy to new-style widgets. At this stage your entire application uses 0.7-style widgets, but runs on a 0.8 runtime. The first step is to move your main application class over to the new layer. Did you reach Checkpoint 3?! There is also a list-style document for API changes to keep an eye on (I'm not sure how much the automatic migration covers those): [] http://attic.qooxdoo.org/documentation/0.8/migration_notes_from_07 Now you can step-wise move your custom classes, as described for feedreader.view.Tree. When you change the class itself, you need to wrap it inside your main application class (or wherever you instantiate the migrated class). This is the point where the future-embed-thing comes in! You need to wrap the instance of the migrated class into this qx.legacy.ui.embed.Future() thing. This ensures that old and new GUI classes continue to run together. After much laboring you will have removed all qx.legacy.* references from your application code *except* for the qx.legacy.ui.embed.Future thingies. You then only need to "unwrap" those and use the original widget instances in their place. This would be the last step, and you would then be free of all qx.legacy.* calls. It might look intimidating but the process has been successfully applied to various, sometimes big, applications. > > Could someone help me here? > > Some of my questions are: > 1. what to do with f.e. > qx.legacy.util.AliasManager.getInstance("myicons", ...).add ? this is > no Mh, .getInstance() doesn't take any arguments, neither in the 0.7 nor in the 0.8 API!? > widget. Can I just use it without the future-widget? Yes, give it a shot. You might need to consult the wiki and API docs to make sure the old method is still available, or find its replacement. > When I remove the "legacy" my application will not show any icon > anymore... This can't be a big deal, AliasManager is such a trivial class ... Just stick to the new API and put the calls straight. You can call the AliasManager in the browser console to check what aliases get resolved to. > > 2. how to use the future-widget in detail? How to layout it? There is not much more detail to care about. You use the Future instance with I guess the 0.7 layouting as long as the container is a 0.7 legacy container. Once you migrate the container, you use the 0.8 layout facilities. > > Do I have to remove all legacy-widgets ( I have 259 legacy-widgets included > in my project ;)) before migrating to 2.2.1? > Or can I just do the next migration and then remove the legacy-widgets? No, you should get rid of all the legacy stuff before doing the next migration step. You can then go from 0.8 to 2.1.1 in one go. 259 is a decent piece of work, but we migrated apps with around 800 custom classes :-). HTH, T. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. D
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 04/03/2013 03:00 PM, Tobias Koller (GERMO GmbH) wrote:
> Hi list,
>
> I finally created my application with all the new features I needed under qx
> 0.7.4.
> Everything worked fine till yesterday ;)
>
> The windows-update installed IE10 on my machine and my application didn't
> work anymore.
> A known problem (Invalid Character DOM Exception in IE9) occurred. I could
> fix it in 0.7.4 but many other things didn't work too.
> My colleague are also using IE10 and on there machine everything works
> without problems...
>
> So I decided to give the migration from 0.7 to 2.2.1 a second chance ;)
>
> I migrated my application to 0.8 but still with all legacy-widgets included.
> And here I really need your help.
>
> I followed the migration-guide from
> http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07#manual_work
> But I just don't know what to do with this future-embed-thing.
I presume you also looked through the "Porting parts" section. Is your
app working after the migration (Checkpoint 2)? 0.8 has both the legacy
widget system and the new widget system in the library. The whole idea
is to have a working app while step-wise switching from legacy to
new-style widgets.
At this stage your entire application uses 0.7-style widgets, but runs
on a 0.8 runtime. The first step is to move your main application class
over to the new layer. Did you reach Checkpoint 3?!
There is also a list-style document for API changes to keep an eye on
(I'm not sure how much the automatic migration covers those):
[] http://attic.qooxdoo.org/documentation/0.8/migration_notes_from_07
Now you can step-wise move your custom classes, as described for
feedreader.view.Tree. When you change the class itself, you need to wrap
it inside your main application class (or wherever you instantiate the
migrated class). This is the point where the future-embed-thing comes
in! You need to wrap the instance of the migrated class into this
qx.legacy.ui.embed.Future() thing. This ensures that old and new GUI
classes continue to run together.
After much laboring you will have removed all qx.legacy.* references
from your application code *except* for the qx.legacy.ui.embed.Future
thingies. You then only need to "unwrap" those and use the original
widget instances in their place. This would be the last step, and you
would then be free of all qx.legacy.* calls.
It might look intimidating but the process has been successfully applied
to various, sometimes big, applications.
>
> Could someone help me here?
>
> Some of my questions are:
> 1. what to do with f.e. qx.legacy.util.AliasManager.getInstance("myicons",
> ...).add ? this is no
Mh, .getInstance() doesn't take any arguments, neither in the 0.7 nor in
the 0.8 API!?
> widget. Can I just use it without the future-widget?
Yes, give it a shot. You might need to consult the wiki and API docs to
make sure the old method is still available, or find its replacement.
> When I remove the "legacy" my application will not show any icon
> anymore...
This can't be a big deal, AliasManager is such a trivial class ... Just
stick to the new API and put the calls straight. You can call the
AliasManager in the browser console to check what aliases get resolved to.
>
> 2. how to use the future-widget in detail? How to layout it?
There is not much more detail to care about. You use the Future instance
with I guess the 0.7 layouting as long as the container is a 0.7 legacy
container. Once you migrate the container, you use the 0.8 layout
facilities.
>
> Do I have to remove all legacy-widgets ( I have 259 legacy-widgets included
> in my project ;)) before migrating to 2.2.1?
> Or can I just do the next migration and then remove the legacy-widgets?
No, you should get rid of all the legacy stuff before doing the next
migration step. You can then go from 0.8 to 2.1.1 in one go. 259 is a
decent piece of work, but we migrated apps with around 800 custom
classes :-).
HTH,
T.
--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi list,
I finally created my application with all the new features I needed under qx
0.7.4.
Everything worked fine till yesterday ;)
The windows-update installed IE10 on my machine and my application didn't work
anymore.
A known problem (Invalid Character DOM Exception in IE9) occurred. I could fix
it in 0.7.4 but many other things didn't work too.
My colleague are also using IE10 and on there machine everything works without
problems...
So I decided to give the migration from 0.7 to 2.2.1 a second chance ;)
I migrated my application to 0.8 but still with all legacy-widgets included.
And here I really need your help.
I followed the migration-guide from
http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07#manual_work
But I just don't know what to do with this future-embed-thing.
Could someone help me here?
Some of my questions are:
1. what to do with f.e. qx.legacy.util.AliasManager.getInstance("myicons",
...).add ? this is no widget. Can I just use it without the future-widget?
When I remove the "legacy" my application will not show any icon
anymore...
2. how to use the future-widget in detail? How to layout it?
Do I have to remove all legacy-widgets ( I have 259 legacy-widgets included in
my project ;)) before migrating to 2.2.1?
Or can I just do the next migration and then remove the legacy-widgets?
Thanks a lot!
Tobi
-Ursprüngliche Nachricht-
Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]]
Gesendet: Montag, 25. Februar 2013 07:00
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Thanks for your help.
But i spend almost 2 days for trying to convert the app to 0.8.
I found a way to use the 0.7-version with our new restfull webservices.
After I made all changes in my application I may have the time to create a
complete new application under qooxdoo 2.1.x.
I have one more question (qx 0.7.4):
We have a restful-webservice which needs authentication (f.e.
http://localhost/myapp/documents) When I enter a wrong combination of
user/password, the browser automatically opens a login-promt because our
webservice-framework throws a 401-error.
Is there any way, except of not throwing a 401-error, to prevent the browser to
open this login-promt?
Of course we could throw another error-code but that wouldn't be a correct
solution.
Thanks
-Ursprüngliche Nachricht-
Von: thron7 [mailto:[email protected]]
Gesendet: Freitag, 22. Februar 2013 12:10
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/22/2013 11:04 AM, Fritz Zaucker wrote:
> Hi Tobias
>
> On Fri, 22 Feb 2013, Tobias Koller \(GERMO GmbH\) wrote:
>
>> After including the ".theme.*" I was able to start my application and
>> I thought that's it, but unfortunately it doesn't work.
>>
>> F.e. all the events I fire (with this.dispatchevent) doesn't work. No
>> EventListener is starting after event was fired.
'dispatchevent' is still supported in 0.8, but the listener API changed (see
further). So maybe your custom events are just not registered properly. That
should be easy to find out. Locate a listener that is not responding and check
the return value from the addListener call.
> This sounds strange ... can you isolate this by pulling some small
> part out of your application?
>
>> Maybe I should create a complete new application with qooxdoo 2.1.1...
> we have several applications that started with 0.7 and are now using
> trunk
> (pre2.2) successfully. We did, however, follow the Qooxdoo development
> as closely as possible, so the migration steps were usually small. But
> I wouldn't just give up if I were you. Although rewriting an
> application with all the experiences of the first version usually give
> a much better second version ... ;-) ... but I think if you went this
> route it should not be just because Qooxdoo changed ...
>
> Did you carefully read the migration.log files? Perhaps you missed
> some manual changes that are required?
Indeed, the event system was changed with 0.8, but the changes were mostly
automatic. Your migration.log should be full of them. The
0.8-alpha2 release notes had an entire section devoted to events [1].
T.
[1] http://qooxdoo.org/project/release_notes/0.8-alpha2#events
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi Martijn, but this will not solve the problem: “…Because the user name and password are correct, the browser will not popup a dialog box. If they are incorrect, the browser will do this, even for an asynchronous call! “ We solved it the way I descripted yesterday. Thanks. Tobias Von: Martijn Verbrugh [mailto:[email protected]] Gesendet: Dienstag, 26. Februar 2013 09:23 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? FYI: http://www.berenddeboer.net/rest/authentication.html#login-page Regards, Martijn. -Original message- > From:Tobias Koller (GERMO GmbH) > Sent: Monday 25th February 2013 17:06 > To: qooxdoo Development > Subject: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > Yes i listened to every event and none off them is fired before the > browser-login promt appears. > > I guess I have to use a workaround. > We are using our own Restful-webservice-framework which will (since today ;)) > check, if a Requestheader ("X-GERMO-No-Auth-Header") was sent. > If this header was sent > (myrequest.setRequestHeader("X-GERMO-No-Auth-Header","1");) the response will > not include the "WWW-Authenticate"-Header (but still ErrorCode 401). > And because all browsers will only show the login-promt if this header is > set, I'm happy ;) > > > -Ursprüngliche Nachricht- > Von: thron7 [mailto:[email protected]] > Gesendet: Montag, 25. Februar 2013 16:45 > An: qooxdoo Development > Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > I'm not sure if you can override browser behavior, but have you tried > listening for the "failed" event?! > > T. > > On 02/25/2013 09:14 AM, Tobias Koller (GERMO GmbH) wrote: > > I'm using like this: > > > >get : function(path) > >{ > >var url = this.getBaseUrl() + "/" + path; > > > > > >var r = new > > qx.io.remote.Request(url,"GET",qx.util.Mime.JSON); > >r.setUsername(this.getUsername()); > >r.setPassword(this.getPassword()); > >r.setAsynchronous(false); > >r.setUseBasicHttpAuth(true); > >r.setTimeout(20); > > > > > >var ret = ""; > > > >r.addEventListener("completed", function(e){ > >ret = e.getContent(); > >alert(ret["Name"]); > > > > },this); > > > >r.send(); > >}, > > > > > > -Ursprüngliche Nachricht- > > Von: thron7 [mailto:[email protected]] > > Gesendet: Montag, 25. Februar 2013 09:06 > > An: qooxdoo Development > > Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > > > > > On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote: > >> Thanks for your help. > >> > >> But i spend almost 2 days for trying to convert the app to 0.8. > >> I found a way to use the 0.7-version with our new restfull webservices. > >> After I made all changes in my application I may have the time to create a > >> complete new application under qooxdoo 2.1.x. > >> > >> I have one more question (qx 0.7.4): > >> > >> We have a restful-webservice which needs authentication (f.e. > >> http://localhost/myapp/documents <http://localhost/myapp/documents> ) When > >> I enter a wrong combination of user/password, the browser automatically > >> opens a login-promt because our webservice-framework throws a 401-error. > >> Is there any way, except of not throwing a 401-error, to prevent the > >> browser to open this login-promt? > > Well, *how* is the REST resource being requested? Are you setting an > > iframe's URL to it? Or are you using one of the qooxdoo IO APIs? > > > > T. > > > > > > -- > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite for > > free today: > > http://p.sf.net/sfu/appdyn_d2d_feb >
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
FYI: http://www.berenddeboer.net/rest/authentication.html#login-page <http://www.berenddeboer.net/rest/authentication.html#login-page> Regards, Martijn. -Original message- > From:Tobias Koller (GERMO GmbH) mailto:[email protected]> > > Sent: Monday 25th February 2013 17:06 > To: qooxdoo Development <mailto:[email protected]> > > Subject: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > Yes i listened to every event and none off them is fired before the > browser-login promt appears. > > I guess I have to use a workaround. > We are using our own Restful-webservice-framework which will (since today ;)) > check, if a Requestheader ("X-GERMO-No-Auth-Header") was sent. > If this header was sent > (myrequest.setRequestHeader("X-GERMO-No-Auth-Header","1");) the response will > not include the "WWW-Authenticate"-Header (but still ErrorCode 401). > And because all browsers will only show the login-promt if this header is > set, I'm happy ;) > > > -Ursprüngliche Nachricht- > Von: thron7 [mailto:[email protected] > <mailto:[email protected]> ] > Gesendet: Montag, 25. Februar 2013 16:45 > An: qooxdoo Development > Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > I'm not sure if you can override browser behavior, but have you tried > listening for the "failed" event?! > > T. > > On 02/25/2013 09:14 AM, Tobias Koller (GERMO GmbH) wrote: > > I'm using like this: > > > > get : function(path) > > { > > var url = this.getBaseUrl() + "/" + path; > > > > > > var r = new > > qx.io.remote.Request(url,"GET",qx.util.Mime.JSON); > > r.setUsername(this.getUsername()); > > r.setPassword(this.getPassword()); > > r.setAsynchronous(false); > > r.setUseBasicHttpAuth(true); > > r.setTimeout(20); > > > > > > var ret = ""; > > > > r.addEventListener("completed", function(e){ > > ret = e.getContent(); > > alert(ret["Name"]); > > > > },this); > > > > r.send(); > > }, > > > > > > -Ursprüngliche Nachricht- > > Von: thron7 [mailto:[email protected] > > <mailto:[email protected]> ] > > Gesendet: Montag, 25. Februar 2013 09:06 > > An: qooxdoo Development > > Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? > > > > > > On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote: > >> Thanks for your help. > >> > >> But i spend almost 2 days for trying to convert the app to 0.8. > >> I found a way to use the 0.7-version with our new restfull webservices. > >> After I made all changes in my application I may have the time to create a > >> complete new application under qooxdoo 2.1.x. > >> > >> I have one more question (qx 0.7.4): > >> > >> We have a restful-webservice which needs authentication (f.e. > >> http://localhost/myapp/documents) When I enter a wrong combination of > >> user/password, the browser automatically opens a login-promt because our > >> webservice-framework throws a 401-error. > >> Is there any way, except of not throwing a 401-error, to prevent the > >> browser to open this login-promt? > > Well, *how* is the REST resource being requested? Are you setting an > > iframe's URL to it? Or are you using one of the qooxdoo IO APIs? > > > > T. > > > > > > -- > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite for > > free today: > > http://p.sf.net/sfu/appdyn_d2d_feb <http://p.sf.net/sfu/appdyn_d2d_feb> > > ___ > > qooxdoo-devel mailing list > > [email protected] > > <mailto:[email protected]> > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-deve
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Yes i listened to every event and none off them is fired before the
browser-login promt appears.
I guess I have to use a workaround.
We are using our own Restful-webservice-framework which will (since today ;))
check, if a Requestheader ("X-GERMO-No-Auth-Header") was sent.
If this header was sent
(myrequest.setRequestHeader("X-GERMO-No-Auth-Header","1");) the response will
not include the "WWW-Authenticate"-Header (but still ErrorCode 401).
And because all browsers will only show the login-promt if this header is set,
I'm happy ;)
-Ursprüngliche Nachricht-
Von: thron7 [mailto:[email protected]]
Gesendet: Montag, 25. Februar 2013 16:45
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
I'm not sure if you can override browser behavior, but have you tried listening
for the "failed" event?!
T.
On 02/25/2013 09:14 AM, Tobias Koller (GERMO GmbH) wrote:
> I'm using like this:
>
> get : function(path)
> {
> var url = this.getBaseUrl() + "/" + path;
>
>
> var r = new
> qx.io.remote.Request(url,"GET",qx.util.Mime.JSON);
> r.setUsername(this.getUsername());
> r.setPassword(this.getPassword());
> r.setAsynchronous(false);
> r.setUseBasicHttpAuth(true);
> r.setTimeout(20);
>
>
> var ret = "";
>
> r.addEventListener("completed", function(e){
> ret = e.getContent();
> alert(ret["Name"]);
>
> },this);
>
> r.send();
> },
>
>
> -----Ursprüngliche Nachricht-
> Von: thron7 [mailto:[email protected]]
> Gesendet: Montag, 25. Februar 2013 09:06
> An: qooxdoo Development
> Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
>
>
> On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote:
>> Thanks for your help.
>>
>> But i spend almost 2 days for trying to convert the app to 0.8.
>> I found a way to use the 0.7-version with our new restfull webservices.
>> After I made all changes in my application I may have the time to create a
>> complete new application under qooxdoo 2.1.x.
>>
>> I have one more question (qx 0.7.4):
>>
>> We have a restful-webservice which needs authentication (f.e.
>> http://localhost/myapp/documents) When I enter a wrong combination of
>> user/password, the browser automatically opens a login-promt because our
>> webservice-framework throws a 401-error.
>> Is there any way, except of not throwing a 401-error, to prevent the browser
>> to open this login-promt?
> Well, *how* is the REST resource being requested? Are you setting an iframe's
> URL to it? Or are you using one of the qooxdoo IO APIs?
>
> T.
>
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics Download AppDynamics Lite for free
> today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics Download AppDynamics Lite
> for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
I'm not sure if you can override browser behavior, but have you tried
listening for the "failed" event?!
T.
On 02/25/2013 09:14 AM, Tobias Koller (GERMO GmbH) wrote:
> I'm using like this:
>
> get : function(path)
> {
> var url = this.getBaseUrl() + "/" + path;
>
>
> var r = new
> qx.io.remote.Request(url,"GET",qx.util.Mime.JSON);
> r.setUsername(this.getUsername());
> r.setPassword(this.getPassword());
> r.setAsynchronous(false);
> r.setUseBasicHttpAuth(true);
> r.setTimeout(20);
>
>
> var ret = "";
>
> r.addEventListener("completed", function(e){
> ret = e.getContent();
> alert(ret["Name"]);
>
> },this);
>
> r.send();
> },
>
>
> -Ursprüngliche Nachricht-----
> Von: thron7 [mailto:[email protected]]
> Gesendet: Montag, 25. Februar 2013 09:06
> An: qooxdoo Development
> Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
>
>
> On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote:
>> Thanks for your help.
>>
>> But i spend almost 2 days for trying to convert the app to 0.8.
>> I found a way to use the 0.7-version with our new restfull webservices.
>> After I made all changes in my application I may have the time to create a
>> complete new application under qooxdoo 2.1.x.
>>
>> I have one more question (qx 0.7.4):
>>
>> We have a restful-webservice which needs authentication (f.e.
>> http://localhost/myapp/documents) When I enter a wrong combination of
>> user/password, the browser automatically opens a login-promt because our
>> webservice-framework throws a 401-error.
>> Is there any way, except of not throwing a 401-error, to prevent the browser
>> to open this login-promt?
> Well, *how* is the REST resource being requested? Are you setting an iframe's
> URL to it? Or are you using one of the qooxdoo IO APIs?
>
> T.
>
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics Download AppDynamics Lite for free
> today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
I'm using like this:
get : function(path)
{
var url = this.getBaseUrl() + "/" + path;
var r = new
qx.io.remote.Request(url,"GET",qx.util.Mime.JSON);
r.setUsername(this.getUsername());
r.setPassword(this.getPassword());
r.setAsynchronous(false);
r.setUseBasicHttpAuth(true);
r.setTimeout(20);
var ret = "";
r.addEventListener("completed", function(e){
ret = e.getContent();
alert(ret["Name"]);
},this);
r.send();
},
-Ursprüngliche Nachricht-
Von: thron7 [mailto:[email protected]]
Gesendet: Montag, 25. Februar 2013 09:06
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote:
> Thanks for your help.
>
> But i spend almost 2 days for trying to convert the app to 0.8.
> I found a way to use the 0.7-version with our new restfull webservices.
> After I made all changes in my application I may have the time to create a
> complete new application under qooxdoo 2.1.x.
>
> I have one more question (qx 0.7.4):
>
> We have a restful-webservice which needs authentication (f.e.
> http://localhost/myapp/documents) When I enter a wrong combination of
> user/password, the browser automatically opens a login-promt because our
> webservice-framework throws a 401-error.
> Is there any way, except of not throwing a 401-error, to prevent the browser
> to open this login-promt?
Well, *how* is the REST resource being requested? Are you setting an iframe's
URL to it? Or are you using one of the qooxdoo IO APIs?
T.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/25/2013 06:59 AM, Tobias Koller (GERMO GmbH) wrote: > Thanks for your help. > > But i spend almost 2 days for trying to convert the app to 0.8. > I found a way to use the 0.7-version with our new restfull webservices. > After I made all changes in my application I may have the time to create a > complete new application under qooxdoo 2.1.x. > > I have one more question (qx 0.7.4): > > We have a restful-webservice which needs authentication (f.e. > http://localhost/myapp/documents) > When I enter a wrong combination of user/password, the browser automatically > opens a login-promt because our webservice-framework throws a 401-error. > Is there any way, except of not throwing a 401-error, to prevent the browser > to open this login-promt? Well, *how* is the REST resource being requested? Are you setting an iframe's URL to it? Or are you using one of the qooxdoo IO APIs? T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Thanks for your help. But i spend almost 2 days for trying to convert the app to 0.8. I found a way to use the 0.7-version with our new restfull webservices. After I made all changes in my application I may have the time to create a complete new application under qooxdoo 2.1.x. I have one more question (qx 0.7.4): We have a restful-webservice which needs authentication (f.e. http://localhost/myapp/documents) When I enter a wrong combination of user/password, the browser automatically opens a login-promt because our webservice-framework throws a 401-error. Is there any way, except of not throwing a 401-error, to prevent the browser to open this login-promt? Of course we could throw another error-code but that wouldn't be a correct solution. Thanks -Ursprüngliche Nachricht- Von: thron7 [mailto:[email protected]] Gesendet: Freitag, 22. Februar 2013 12:10 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/22/2013 11:04 AM, Fritz Zaucker wrote: > Hi Tobias > > On Fri, 22 Feb 2013, Tobias Koller \(GERMO GmbH\) wrote: > >> After including the ".theme.*" I was able to start my application and >> I thought that's it, but unfortunately it doesn't work. >> >> F.e. all the events I fire (with this.dispatchevent) doesn't work. No >> EventListener is starting after event was fired. 'dispatchevent' is still supported in 0.8, but the listener API changed (see further). So maybe your custom events are just not registered properly. That should be easy to find out. Locate a listener that is not responding and check the return value from the addListener call. > This sounds strange ... can you isolate this by pulling some small > part out of your application? > >> Maybe I should create a complete new application with qooxdoo 2.1.1... > we have several applications that started with 0.7 and are now using > trunk > (pre2.2) successfully. We did, however, follow the Qooxdoo development > as closely as possible, so the migration steps were usually small. But > I wouldn't just give up if I were you. Although rewriting an > application with all the experiences of the first version usually give > a much better second version ... ;-) ... but I think if you went this > route it should not be just because Qooxdoo changed ... > > Did you carefully read the migration.log files? Perhaps you missed > some manual changes that are required? Indeed, the event system was changed with 0.8, but the changes were mostly automatic. Your migration.log should be full of them. The 0.8-alpha2 release notes had an entire section devoted to events [1]. T. [1] http://qooxdoo.org/project/release_notes/0.8-alpha2#events -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/22/2013 11:04 AM, Fritz Zaucker wrote: > Hi Tobias > > On Fri, 22 Feb 2013, Tobias Koller \(GERMO GmbH\) wrote: > >> After including the ".theme.*" I was able to start my application and I >> thought that's it, but unfortunately it doesn't work. >> >> F.e. all the events I fire (with this.dispatchevent) doesn't work. No >> EventListener is starting after event was fired. 'dispatchevent' is still supported in 0.8, but the listener API changed (see further). So maybe your custom events are just not registered properly. That should be easy to find out. Locate a listener that is not responding and check the return value from the addListener call. > This sounds strange ... can you isolate this by pulling some small part out > of your application? > >> Maybe I should create a complete new application with qooxdoo 2.1.1... > we have several applications that started with 0.7 and are now using trunk > (pre2.2) successfully. We did, however, follow the Qooxdoo development as > closely as possible, so the migration steps were usually small. But I > wouldn't just give up if I were you. Although rewriting an application with > all the experiences of the first version usually give a much better second > version ... ;-) ... but I think if you went this route it should not be just > because Qooxdoo changed ... > > Did you carefully read the migration.log files? Perhaps you missed some > manual changes that are required? Indeed, the event system was changed with 0.8, but the changes were mostly automatic. Your migration.log should be full of them. The 0.8-alpha2 release notes had an entire section devoted to events [1]. T. [1] http://qooxdoo.org/project/release_notes/0.8-alpha2#events -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi Tobias On Fri, 22 Feb 2013, Tobias Koller \(GERMO GmbH\) wrote: > After including the ".theme.*" I was able to start my application and I > thought that's it, but unfortunately it doesn't work. > > F.e. all the events I fire (with this.dispatchevent) doesn't work. No > EventListener is starting after event was fired. This sounds strange ... can you isolate this by pulling some small part out of your application? > Maybe I should create a complete new application with qooxdoo 2.1.1... we have several applications that started with 0.7 and are now using trunk (pre2.2) successfully. We did, however, follow the Qooxdoo development as closely as possible, so the migration steps were usually small. But I wouldn't just give up if I were you. Although rewriting an application with all the experiences of the first version usually give a much better second version ... ;-) ... but I think if you went this route it should not be just because Qooxdoo changed ... Did you carefully read the migration.log files? Perhaps you missed some manual changes that are required? Cheers, Fritz -- 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 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
This is my complete config.json
{
"name": "myapp",
"include" :
[
{
"path" : "${QOOXDOO_PATH}/tool/data/config/application.json"
}
],
"export" :
[
"api",
"build",
"clean",
"distclean",
"fix",
"inspector",
"lint",
"migration",
"pretty",
"profiling",
"source",
"source-all",
"test",
"test-source",
"translation"
],
"let" :
{
"APPLICATION" : "myapp",
"QOOXDOO_PATH" : "../qooxdoo-0.8.3-sdk",
"QXTHEME" : "qx.theme.Modern",
"API_EXCLUDE" : ["qx.test.*"],
"LOCALES" : [ "de" ],
"CACHE": "${TMPDIR}/cache",
"ROOT" : "."
},
"jobs" :
{
"common" :
{
"include" :
[
"${QXTHEME}",
"qx.legacy.theme.ClassicRoyale",
"${APPLICATION}.Application",
"${APPLICATION}.theme.*"
],
"settings" :
{
"qx.legacy.theme" : "${APPLICATION}.theme.Classic"
}
}
}
}
I just added "${APPLICATION}.theme.*" and "${APPLICATION}.theme.Classic"
I'm using the standard-source-job.
After including the ".theme.*" I was able to start my application and I
thought that's it, but unfortunately it doesn't work.
F.e. all the events I fire (with this.dispatchevent) doesn't work. No
EventListener is starting after event was fired.
Maybe I should create a complete new application with qooxdoo 2.1.1...
Von: thron7 [mailto:[email protected]]
Gesendet: Freitag, 22. Februar 2013 10:39
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
On 02/21/2013 05:49 PM, Tobias Koller (GERMO GmbH) wrote:
After trying around millions of things i finally got the
solution.
I added this
"${APPLICATION}.theme.*"
To the "include"-part of the config.json and now the theme is
getting loaded correctly.
Mh, this is strange. The value of the QXTHEME macro is by default
included in the "include" list of the compile jobs. Is your config.json
including application.json? Are you using the standard "source" job, or
have you written your own? You can see the fully expanded job when you
run the generator with the '-v' flag, that might help to sort out
things.
T.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/21/2013 05:49 PM, Tobias Koller (GERMO GmbH) wrote:
qooxdoo 0.7 with current qooxdoo-version mix ?
After trying around millions of things i finally got the solution.
I added this
"${APPLICATION}.theme.*"
To the "include"-part of the config.json and now the theme is getting
loaded correctly.
Mh, this is strange. The value of the QXTHEME macro is by default
included in the "include" list of the compile jobs. Is your config.json
including application.json? Are you using the standard "source" job, or
have you written your own? You can see the fully expanded job when you
run the generator with the '-v' flag, that might help to sort out things.
T.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
After trying around millions of things i finally got the solution.
I added this
"${APPLICATION}.theme.*"
To the "include"-part of the config.json and now the theme is getting
loaded correctly.
Thanks.
Tobi
Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]]
Gesendet: Donnerstag, 21. Februar 2013 16:56
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
Ok, sorry for all my mails but i'm getting closer to solution ;)
i just noticed that in the config.json-file there is a
qx.legacy.theme-Setting which I set now to myapp.theme.Classic.
The compiler doesn't crash anymore but now I'm getting this error:
Error: The meta theme to use is not available: myapp.theme.Classic
I debugged the qx.Theme.define-method and all themes (qx.theme...) are
registered but not myapp.theme.Classic.
Can somebody help me here?
Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]]
Gesendet: Donnerstag, 21. Februar 2013 16:01
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
Hello,
I found out that my own theme has to start with qx.Theme.define and not
with qx.legacy.theme.define.
But how can I use a legacy-theme in my config.json ?
Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]]
Gesendet: Donnerstag, 21. Februar 2013 12:58
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
Thanks for your detailed answer.
Yes, I discovered this documentations already and checked also the
theming-section.
But when I Change the configuration from
"let" : {..., "QXTHEME" : "qx.theme.Modern",... },
To
"let" : {...,"QXTHEME" : "myapp.theme.Classic",...},
my generate.py source stops in the middle of compiling...
this is the last entry from the generate.py-logfile.
>>> Scanning libraries...
- Use memory cache for
C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework
- Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp
>>> Loaded 2 libraries
>>> Preparing include configuration...
- Including 3 items smart, 0 items explicit
- Expanding expressions...
When I don't change the config.json file the log looks like this:
>>> Scanning libraries...
- Use memory cache for
C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework
- Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp
>>> Loaded 2 libraries
>>> Preparing include configuration...
- Including 3 items smart, 0 items explicit
- Expanding expressions...
>>> Preparing exclude configuration...
- Excluding 0 items smart, 0 items explicit
- Expanding expressions...
There is no error message or anything else.
Thanks.
tobi
Von: thron7 [mailto:[email protected]]
Gesendet: Donnerstag, 21. Februar 2013 12:34
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
On 02/21/2013 12:01 PM, Tobias Koller (GERMO GmbH) wrote:
Hi thron,
I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to
finish it (with still all legacy-namespaces included).
Now I have a problem with the theming.
In my application I'm using my own theme with some alias for
Colors, borders ,.
These themes are inherited from the qx.legacy.theme-classes.
My "make-file" from 0.7.4 has this setting:
APPLICATION_THEME = myapp.theme.Classic
How can I set this theme to be my default-theme in 0.8.3 ?
Do I have to change the config.json-file here?
Exactly. In the config.json file, in the top-level "let" section, set
"QXTHEME" : "myapp.theme.Classic"
That should do the trick. You probably already discovered the migration
guide 0.7 -> 0.8, which is part of the 0.8 documentation:
http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07
On that page, there is also a link to a dedicated page dealing with
mappings of old Makefile macros to new config settings:
http://attic.qooxdoo.org/documentation/0.8/migration_makefile
Mind, though, that config settings have also evolved since 0.8, so you
might want to cross-check the information of that page with the current
(2.1.x) settings:
http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_ma
cros.html
http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_re
f.html
(Though tedious, once you address the 0.8.3 -> 2.1.1 migration, it might
be a good idea to go through the "Migration" sections of the release
notes of all intervening releases:
http://qooxdoo.org/project/release_no
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Ok, sorry for all my mails but i'm getting closer to solution ;) i just noticed that in the config.json-file there is a qx.legacy.theme-Setting which I set now to myapp.theme.Classic. The compiler doesn't crash anymore but now I'm getting this error: Error: The meta theme to use is not available: myapp.theme.Classic I debugged the qx.Theme.define-method and all themes (qx.theme...) are registered but not myapp.theme.Classic. Can somebody help me here? Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]] Gesendet: Donnerstag, 21. Februar 2013 16:01 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? Hello, I found out that my own theme has to start with qx.Theme.define and not with qx.legacy.theme.define. But how can I use a legacy-theme in my config.json ? Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]] Gesendet: Donnerstag, 21. Februar 2013 12:58 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? Thanks for your detailed answer. Yes, I discovered this documentations already and checked also the theming-section. But when I Change the configuration from "let" : {..., "QXTHEME" : "qx.theme.Modern",... }, To "let" : {...,"QXTHEME" : "myapp.theme.Classic",...}, my generate.py source stops in the middle of compiling... this is the last entry from the generate.py-logfile. >>> Scanning libraries... - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp >>> Loaded 2 libraries >>> Preparing include configuration... - Including 3 items smart, 0 items explicit - Expanding expressions... When I don't change the config.json file the log looks like this: >>> Scanning libraries... - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp >>> Loaded 2 libraries >>> Preparing include configuration... - Including 3 items smart, 0 items explicit - Expanding expressions... >>> Preparing exclude configuration... - Excluding 0 items smart, 0 items explicit - Expanding expressions... There is no error message or anything else. Thanks. tobi Von: thron7 [mailto:[email protected]] Gesendet: Donnerstag, 21. Februar 2013 12:34 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/21/2013 12:01 PM, Tobias Koller (GERMO GmbH) wrote: Hi thron, I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to finish it (with still all legacy-namespaces included). Now I have a problem with the theming. In my application I'm using my own theme with some alias for Colors, borders ,. These themes are inherited from the qx.legacy.theme-classes. My "make-file" from 0.7.4 has this setting: APPLICATION_THEME = myapp.theme.Classic How can I set this theme to be my default-theme in 0.8.3 ? Do I have to change the config.json-file here? Exactly. In the config.json file, in the top-level "let" section, set "QXTHEME" : "myapp.theme.Classic" That should do the trick. You probably already discovered the migration guide 0.7 -> 0.8, which is part of the 0.8 documentation: http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07 On that page, there is also a link to a dedicated page dealing with mappings of old Makefile macros to new config settings: http://attic.qooxdoo.org/documentation/0.8/migration_makefile Mind, though, that config settings have also evolved since 0.8, so you might want to cross-check the information of that page with the current (2.1.x) settings: http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_ma cros.html http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_re f.html (Though tedious, once you address the 0.8.3 -> 2.1.1 migration, it might be a good idea to go through the "Migration" sections of the release notes of all intervening releases: http://qooxdoo.org/project/release_notes). T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hello, I found out that my own theme has to start with qx.Theme.define and not with qx.legacy.theme.define. But how can I use a legacy-theme in my config.json ? Von: Tobias Koller (GERMO GmbH) [mailto:[email protected]] Gesendet: Donnerstag, 21. Februar 2013 12:58 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? Thanks for your detailed answer. Yes, I discovered this documentations already and checked also the theming-section. But when I Change the configuration from "let" : {..., "QXTHEME" : "qx.theme.Modern",... }, To "let" : {...,"QXTHEME" : "myapp.theme.Classic",...}, my generate.py source stops in the middle of compiling... this is the last entry from the generate.py-logfile. >>> Scanning libraries... - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp >>> Loaded 2 libraries >>> Preparing include configuration... - Including 3 items smart, 0 items explicit - Expanding expressions... When I don't change the config.json file the log looks like this: >>> Scanning libraries... - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework - Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp >>> Loaded 2 libraries >>> Preparing include configuration... - Including 3 items smart, 0 items explicit - Expanding expressions... >>> Preparing exclude configuration... - Excluding 0 items smart, 0 items explicit - Expanding expressions... There is no error message or anything else. Thanks. tobi Von: thron7 [mailto:[email protected]] Gesendet: Donnerstag, 21. Februar 2013 12:34 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/21/2013 12:01 PM, Tobias Koller (GERMO GmbH) wrote: Hi thron, I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to finish it (with still all legacy-namespaces included). Now I have a problem with the theming. In my application I'm using my own theme with some alias for Colors, borders ,. These themes are inherited from the qx.legacy.theme-classes. My "make-file" from 0.7.4 has this setting: APPLICATION_THEME = myapp.theme.Classic How can I set this theme to be my default-theme in 0.8.3 ? Do I have to change the config.json-file here? Exactly. In the config.json file, in the top-level "let" section, set "QXTHEME" : "myapp.theme.Classic" That should do the trick. You probably already discovered the migration guide 0.7 -> 0.8, which is part of the 0.8 documentation: http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07 On that page, there is also a link to a dedicated page dealing with mappings of old Makefile macros to new config settings: http://attic.qooxdoo.org/documentation/0.8/migration_makefile Mind, though, that config settings have also evolved since 0.8, so you might want to cross-check the information of that page with the current (2.1.x) settings: http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_ma cros.html http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_re f.html (Though tedious, once you address the 0.8.3 -> 2.1.1 migration, it might be a good idea to go through the "Migration" sections of the release notes of all intervening releases: http://qooxdoo.org/project/release_notes). T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Thanks for your detailed answer.
Yes, I discovered this documentations already and checked also the
theming-section.
But when I Change the configuration from
"let" : {..., "QXTHEME" : "qx.theme.Modern",... },
To
"let" : {...,"QXTHEME" : "myapp.theme.Classic",...},
my generate.py source stops in the middle of compiling...
this is the last entry from the generate.py-logfile.
>>> Scanning libraries...
- Use memory cache for
C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework
- Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp
>>> Loaded 2 libraries
>>> Preparing include configuration...
- Including 3 items smart, 0 items explicit
- Expanding expressions...
When I don't change the config.json file the log looks like this:
>>> Scanning libraries...
- Use memory cache for
C:\data\eclipse\qooxdoo\0.8.3\qooxdoo-0.8.3-sdk\framework
- Use memory cache for C:\data\eclipse\qooxdoo\0.8.3\myapp
>>> Loaded 2 libraries
>>> Preparing include configuration...
- Including 3 items smart, 0 items explicit
- Expanding expressions...
>>> Preparing exclude configuration...
- Excluding 0 items smart, 0 items explicit
- Expanding expressions...
There is no error message or anything else.
Thanks.
tobi
Von: thron7 [mailto:[email protected]]
Gesendet: Donnerstag, 21. Februar 2013 12:34
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version
mix ?
On 02/21/2013 12:01 PM, Tobias Koller (GERMO GmbH) wrote:
Hi thron,
I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to
finish it (with still all legacy-namespaces included).
Now I have a problem with the theming.
In my application I'm using my own theme with some alias for
Colors, borders ,.
These themes are inherited from the qx.legacy.theme-classes.
My "make-file" from 0.7.4 has this setting:
APPLICATION_THEME = myapp.theme.Classic
How can I set this theme to be my default-theme in 0.8.3 ?
Do I have to change the config.json-file here?
Exactly. In the config.json file, in the top-level "let" section, set
"QXTHEME" : "myapp.theme.Classic"
That should do the trick. You probably already discovered the migration
guide 0.7 -> 0.8, which is part of the 0.8 documentation:
http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07
On that page, there is also a link to a dedicated page dealing with
mappings of old Makefile macros to new config settings:
http://attic.qooxdoo.org/documentation/0.8/migration_makefile
Mind, though, that config settings have also evolved since 0.8, so you
might want to cross-check the information of that page with the current
(2.1.x) settings:
http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_ma
cros.html
http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_re
f.html
(Though tedious, once you address the 0.8.3 -> 2.1.1 migration, it might
be a good idea to go through the "Migration" sections of the release
notes of all intervening releases:
http://qooxdoo.org/project/release_notes).
T.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/21/2013 12:01 PM, Tobias Koller (GERMO GmbH) wrote: qooxdoo 0.7 with current qooxdoo-version mix ? Hi thron, I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to finish it (with still all legacy-namespaces included). Now I have a problem with the theming. In my application I'm using my own theme with some alias for Colors, borders ,. These themes are inherited from the qx.legacy.theme-classes. My "make-file" from 0.7.4 has this setting: APPLICATION_THEME = myapp.theme.Classic How can I set this theme to be my default-theme in 0.8.3 ? Do I have to change the config.json-file here? Exactly. In the config.json file, in the top-level "let" section, set "QXTHEME" : "myapp.theme.Classic" That should do the trick. You probably already discovered the migration guide 0.7 -> 0.8, which is part of the 0.8 documentation: http://attic.qooxdoo.org/documentation/0.8/migration_guide_from_07 On that page, there is also a link to a dedicated page dealing with mappings of old Makefile macros to new config settings: http://attic.qooxdoo.org/documentation/0.8/migration_makefile Mind, though, that config settings have also evolved since 0.8, so you might want to cross-check the information of that page with the current (2.1.x) settings: http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_macros.html http://manual.qooxdoo.org/2.1.x/pages/tool/generator/generator_config_ref.html (Though tedious, once you address the 0.8.3 -> 2.1.1 migration, it might be a good idea to go through the "Migration" sections of the release notes of all intervening releases: http://qooxdoo.org/project/release_notes). T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi thron, I'm still converting my 0.7.4 to 0.8.3 and I guess I'm close to finish it (with still all legacy-namespaces included). Now I have a problem with the theming. In my application I'm using my own theme with some alias for Colors, borders ,. These themes are inherited from the qx.legacy.theme-classes. My "make-file" from 0.7.4 has this setting: APPLICATION_THEME = myapp.theme.Classic How can I set this theme to be my default-theme in 0.8.3 ? Do I have to change the config.json-file here? Tobi Von: thron7 [mailto:[email protected]] Gesendet: Mittwoch, 20. Februar 2013 14:55 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/20/2013 02:29 PM, Tobias Koller (GERMO GmbH) wrote: Hi, thanks for your quick answer. I will try to upgrade and will let you know if it worked ;) Make sure you follow up on all the migration warnings and hints you get, both during the run of the migration job (see the migration.log file), as well as at runtime in the browser console. There might be some important modifications being necessary to do by hand, which you are only alerted about (as they cannot be automatized). If you are then "clean" after migrating to 0.8.3, do the migration to 2.1.1, and repeat the clean-up process. T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/20/2013 02:29 PM, Tobias Koller (GERMO GmbH) wrote: qooxdoo 0.7 with current qooxdoo-version mix ? Hi, thanks for your quick answer. I will try to upgrade and will let you know if it worked ;) Make sure you follow up on all the migration warnings and hints you get, both during the run of the migration job (see the migration.log file), as well as at runtime in the browser console. There might be some important modifications being necessary to do by hand, which you are only alerted about (as they cannot be automatized). If you are then "clean" after migrating to 0.8.3, do the migration to 2.1.1, and repeat the clean-up process. T. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
Hi, thanks for your quick answer. I will try to upgrade and will let you know if it worked ;) Thanks! Von: thron7 [mailto:[email protected]] Gesendet: Mittwoch, 20. Februar 2013 14:24 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ? On 02/20/2013 01:27 PM, Tobias Koller (GERMO GmbH) wrote: Hello everybody, three years ago I unsubscriped from this mailinglist because we didn't have to change anything on our qooxdoo-application till today. But now we have to change the complete communication from our qooxdoo 0.7-app (till now it was qooxdooàqx.io.remote.RequestàPHP) to qooxdooàRESTful Webservices without any PHP-backend at all. Like I wrote in the title we still use qooxdoo 0.7 (verrry old I know) but we can't migrate it to the current version. I guess no converter could handle that ;) I'm not so sure about this, the qooxdoo migration tool is quite useful. We migrated multiple projects from 0.7. The only thing to note is that you need to first migrate to qooxdoo 0.8.3, and then from 0.8.3 onwards to 2.1. Shouldn't be too hard. So my question is if its possible to just use the communication-parts (f.e. qx.bom.request.Jsonp();) of the current qooxdooversion 2.1 within qooxdoo 0.7? I'd rather doubt that. qx.bom.request.Json draws in a substantial number of dependencies, among them a lot of qx.bom.*, qx.lang.* and qx.core.* class. You would have to import them all, and would certainly run into conflicts with existing classes in 0.7. Try the migration. T. Thanks a lot. Tobi -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] qooxdoo 0.7 with current qooxdoo-version mix ?
On 02/20/2013 01:27 PM, Tobias Koller (GERMO GmbH) wrote: qooxdoo 0.7 with current qooxdoo-version mix ? Hello everybody, three years agoIunsubscriped from this mailinglist because we didn'thave tochange anything on our qooxdoo-applicationtill today. But now we have to change the complete communication from our qooxdoo 0.7-app(till now it was qooxdooàqx.io.remote.RequestàPHP) toqooxdooàRESTful Webserviceswithout any PHP-backend at all. Like I wrote in the title we still use qooxdoo 0.7 (verrry old I know) but we can't migrate it to the current version. I guess no converter could handle that ;) I'm not so sure about this, the qooxdoo migration tool is quite useful. We migrated multiple projects from 0.7. The only thing to note is that you need to first migrate to qooxdoo 0.8.3, and then from 0.8.3 onwards to 2.1. Shouldn't be too hard. So my question is if its possible to just use the communication-parts(f.e.qx.bom.request.Jsonp();)of the current qooxdooversion 2.1 within qooxdoo 0.7? I'd rather doubt that. qx.bom.request.Json draws in a substantial number of dependencies, among them a lot of qx.bom.*, qx.lang.* and qx.core.* class. You would have to import them all, and would certainly run into conflicts with existing classes in 0.7. Try the migration. T. Thanks a lot. Tobi -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
