| Split of RWT into host and fragment [message #82133] |
Wed, 09 April 2008 13:01  |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi everybody,
today I have splitted RWT into a host bundle and q07 fragment. This was done
to enable us to start working on the upcomming qooxdoo 0.8 version. Note
that the current available team project set doesn't work, since the fragment
is not included yet. As there is still some work to do (the test bundle was
also splitted up into different fragments) I do not recommend to use
CVS-Head at the moment. We intend to provide updated team project set,
launch configs, docu etc. tomorrow (2008-04-10). Sorry for any inconvenience
that results from this.
Ciao
Frank
|
|
|
|
|
| Re: Split of RWT into host and fragment [message #83051 is a reply to message #82977] |
Tue, 15 April 2008 10:02  |
| Eclipse User |
|
|
|
Originally posted by: benjamin.wolff.web.de
doh! in all the hurry i totally overlooked the launch-config. works like
a charm again ;). thx!!
just to understand:
these are the first steps to seperate the RWT api from the underlying
framework implementation that represents the widgets in the browser, right?
i assume that q07 means qooxdoo 0.7, so in the future it is possible to
change to another framework by just replacing the q07 bundle with
another bundle that uses another framework. correct me if i'm wrong :).
great job so far! this could mean that in future it is even possible to
work with IE6 by using another js framework since qooxdoo isn't going to
support IE6 (as i heard).
keep on the good work! :)
mfg
ben w.
Frank Appel schrieb:
> Hi,
>
> did you also update your launch-config and added the q07 fragment to the
> bundle list?
>
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Ben W. [mailto:benjamin.wolff@web.de]
> Bereitgestellt: Montag, 14. April 2008 19:28
> Bereitgestellt in: eclipse.technology.rap
> Unterhaltung: Split of RWT into host and fragment
> Betreff: Re: Split of RWT into host and fragment
>
>
> Hi!
>
> i updated my cvs projects with the new team project set from RAP, there
> are no compiling errors so far. when i want to start my application
> (nothing changed there), several exceptions are thrown. what do i have
> to change in my sourcecode/projects?!
>
> java.lang.ExceptionInInitializerError
> at
> org.eclipse.rwt.internal.lifecycle.DisplayUtil.writeLibrarie s(DisplayUti
> l.java:66)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandlerConf igurer.getLi
> braries(LifeCycleServiceHandlerConfigurer.java:202)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandlerConf igurer.getTe
> mplateOfStartupPage(LifeCycleServiceHandlerConfigurer.java:6 0)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.load(BrowserS urvey.java:1
> 23)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.renderScript( BrowserSurve
> y.java:90)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.sendBrowserSu rvey(Browser
> Survey.java:51)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.int ernalService
> (LifeCycleServiceHandler.java:180)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.acc ess$1(LifeCy
> cleServiceHandler.java:168)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler$Lif eCycleServic
> eHandlerSync.doService(LifeCycleServiceHandler.java:133)
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync.servic
> eInternal(RWTLifeCycleServiceHandlerSync.java:47)
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync.servic
> e(RWTLifeCycleServiceHandlerSync.java:35)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.ser vice(LifeCyc
> leServiceHandler.java:140)
> at
> org.eclipse.rwt.internal.service.ServiceManager$HandlerDispa tcher.servic
> e(ServiceManager.java:100)
> at
> org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelega te.java:61)
> at
> org.eclipse.ui.internal.servlet.RequestHandler.service(Reque stHandler.ja
> va:52)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequ
> est(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(Prox
> yServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServ
> let.java:59)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpSe
> rviceServlet.service(HttpServerManager.java:270)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:428)
> at
> org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHan dler.java:67
> 7)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:568)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> at org.mortbay.http.HttpServer.service(HttpServer.java:909)
> at
> org.mortbay.http.HttpConnection.service(HttpConnection.java: 820)
> at
> org.mortbay.http.HttpConnection.handleNext(HttpConnection.ja va:986)
> at
> org.mortbay.http.HttpConnection.handle(HttpConnection.java:8 37)
> at
> org.mortbay.http.SocketListener.handleConnection(SocketListe ner.java:245
> )
> at
> org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:3 57)
> at
> org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:5 34)
>
> Caused by: java.lang.RuntimeException: Could not load facade for
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade
> at
> org.eclipse.rwt.internal.FacadesInitializer.load(FacadesInit ializer.java
> :26)
> at
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade . <clinit>(Di
> splayLCAFacade.java:29)
> ... 33 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade Impl
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(
> BundleLoader.java:481)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLo
> ader.java:397)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLo
> ader.java:385)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(Defau
> ltClassLoader.java:87)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at
> org.eclipse.rwt.internal.FacadesInitializer.load(FacadesInit ializer.java
> :22)
> ... 34 more
>
>
>
> Frank Appel schrieb:
>> Hi everybody,
>>
>> today I have splitted RWT into a host bundle and q07 fragment. This
>> was done to enable us to start working on the upcomming qooxdoo 0.8
>> version. Note that the current available team project set doesn't
>> work, since the fragment is not included yet. As there is still some
>> work to do (the test bundle was also splitted up into different
>> fragments) I do not recommend to use CVS-Head at the moment. We intend
>
>> to provide updated team project set, launch configs, docu etc.
>> tomorrow (2008-04-10). Sorry for any inconvenience that results from
> this.
>>
>> Ciao
>> Frank
>>
>>
>
|
|
|
| Re: Split of RWT into host and fragment [message #83066 is a reply to message #83051] |
Tue, 15 April 2008 10:34 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi again,
> these are the first steps to seperate the RWT api
> from the underlying framework implementation that
> represents the widgets in the browser, right?
Yes
> i assume that q07 means qooxdoo 0.7, so in the future
> it is possible to change to another framework by just
> replacing the q07 bundle with another bundle that uses
> another framework. correct me if i'm wrong :).
That's right, but note that it will be a while till this
is available though. This first steps are done to switch
over to the qooxdoo 0.8 version.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Ben W. [mailto:benjamin.wolff@web.de]
Bereitgestellt: Dienstag, 15. April 2008 16:03
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Split of RWT into host and fragment
Betreff: Re: Split of RWT into host and fragment
doh! in all the hurry i totally overlooked the launch-config. works like
a charm again ;). thx!!
just to understand:
these are the first steps to seperate the RWT api from the underlying
framework implementation that represents the widgets in the browser,
right?
i assume that q07 means qooxdoo 0.7, so in the future it is possible to
change to another framework by just replacing the q07 bundle with
another bundle that uses another framework. correct me if i'm wrong :).
great job so far! this could mean that in future it is even possible to
work with IE6 by using another js framework since qooxdoo isn't going to
support IE6 (as i heard).
keep on the good work! :)
mfg
ben w.
Frank Appel schrieb:
> Hi,
>
> did you also update your launch-config and added the q07 fragment to
> the bundle list?
>
>
> Ciao
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Ben W. [mailto:benjamin.wolff@web.de]
> Bereitgestellt: Montag, 14. April 2008 19:28 Bereitgestellt in:
> eclipse.technology.rap
> Unterhaltung: Split of RWT into host and fragment
> Betreff: Re: Split of RWT into host and fragment
>
>
> Hi!
>
> i updated my cvs projects with the new team project set from RAP,
> there are no compiling errors so far. when i want to start my
> application (nothing changed there), several exceptions are thrown.
> what do i have to change in my sourcecode/projects?!
>
> java.lang.ExceptionInInitializerError
> at
> org.eclipse.rwt.internal.lifecycle.DisplayUtil.writeLibrarie s(DisplayU
> ti
> l.java:66)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandlerConf igurer.get
> Li
> braries(LifeCycleServiceHandlerConfigurer.java:202)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandlerConf igurer.get
> Te
> mplateOfStartupPage(LifeCycleServiceHandlerConfigurer.java:6 0)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.load(BrowserS urvey.java
> :1
> 23)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.renderScript( BrowserSur
> ve
> y.java:90)
> at
> org.eclipse.rwt.internal.service.BrowserSurvey.sendBrowserSu rvey(Brows
> er
> Survey.java:51)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.int ernalServi
> ce
> (LifeCycleServiceHandler.java:180)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.acc ess$1(Life
> Cy
> cleServiceHandler.java:168)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler$Lif eCycleServ
> ic
> eHandlerSync.doService(LifeCycleServiceHandler.java:133)
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync.serv
> ic
> eInternal(RWTLifeCycleServiceHandlerSync.java:47)
> at
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycleServiceHandle rSync.serv
> ic
> e(RWTLifeCycleServiceHandlerSync.java:35)
> at
> org.eclipse.rwt.internal.service.LifeCycleServiceHandler.ser vice(LifeC
> yc
> leServiceHandler.java:140)
> at
> org.eclipse.rwt.internal.service.ServiceManager$HandlerDispa tcher.serv
> ic
> e(ServiceManager.java:100)
> at
>
org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelega te.java:61)
> at
> org.eclipse.ui.internal.servlet.RequestHandler.service(Reque stHandler.
> ja
> va:52)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRe
> qu
> est(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(Pr
> ox
> yServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxySe
> rv
> let.java:59)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttp
> Se
> rviceServlet.service(HttpServerManager.java:270)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:428)
> at
> org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHan dler.java:
> 67
> 7)
> at
>
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:568)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> at org.mortbay.http.HttpServer.service(HttpServer.java:909)
> at
> org.mortbay.http.HttpConnection.service(HttpConnection.java: 820)
> at
> org.mortbay.http.HttpConnection.handleNext(HttpConnection.ja va:986)
> at
> org.mortbay.http.HttpConnection.handle(HttpConnection.java:8 37)
> at
> org.mortbay.http.SocketListener.handleConnection(SocketListe ner.java:2
> 45
> )
> at
> org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:3 57)
> at
> org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:5 34)
>
> Caused by: java.lang.RuntimeException: Could not load facade for
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade
> at
> org.eclipse.rwt.internal.FacadesInitializer.load(FacadesInit ializer.ja
> va
> :26)
> at
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade . <clinit>(
> Di
> splayLCAFacade.java:29)
> ... 33 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCAFacade Impl
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInterna
> l(
> BundleLoader.java:481)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(Bundle
> Lo
> ader.java:397)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(Bundle
> Lo
> ader.java:385)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(Def
> au
> ltClassLoader.java:87)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at
> org.eclipse.rwt.internal.FacadesInitializer.load(FacadesInit ializer.ja
> va
> :22)
> ... 34 more
>
>
>
> Frank Appel schrieb:
>> Hi everybody,
>>
>> today I have splitted RWT into a host bundle and q07 fragment. This
>> was done to enable us to start working on the upcomming qooxdoo 0.8
>> version. Note that the current available team project set doesn't
>> work, since the fragment is not included yet. As there is still some
>> work to do (the test bundle was also splitted up into different
>> fragments) I do not recommend to use CVS-Head at the moment. We
>> intend
>
>> to provide updated team project set, launch configs, docu etc.
>> tomorrow (2008-04-10). Sorry for any inconvenience that results from
> this.
>>
>> Ciao
>> Frank
>>
>>
>
|
|
|
|
|
| Re: Split of RWT into host and fragment [message #86588 is a reply to message #86352] |
Thu, 08 May 2008 05:35 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
qooxdoo works on IE 6. But as you've already encountered, if you're
running a non trivial sized app it is slow - very slow. But this is case
with all non trivial rich internet applications on IE 6, nevertheless
which javascript library is used. The root cause of this is the browser
itself, which is outdated. Microsoft forced the automatic update to IE 7
already on Feb. 12 via WSUS (Windows Server Update Services). So there
isn't much we can do about this.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Ben W. [mailto:benjamin.wolff@web.de]
Bereitgestellt: Dienstag, 6. Mai 2008 20:59
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Split of RWT into host and fragment
Betreff: Re: Split of RWT into host and fragment
hm, i thought i've read it in this newsgroup somewhere, but i couldn't
find it using the search. you can take a look at the "IE vs Firefox
performance" or "runs so slowly in IE" threads.
maybe i've read it in a bug comment, maybe i haven't read it anywhere at
all :).
the best thing would be to ask the qooxdoo ppl whether they are
planning/able to improve performance with IE6 since this is almost
unusable in this constellation. and this can be a serious problem when
you develop for a big company which is running IE6 in a worldwide
domain. It can't just be updated for a little RAP webapp, i'm struggling
with this problem as well :)
greetings
-ben
stefan.hansel@tolina.de schrieb:
> >> great job so far! this could mean that in future it is even
> possible to >> work with IE6 by using another js framework since
> qooxdoo isn't going to >> support IE6 (as i heard).
>
> Where did you hear that? That what would be a desaster for us.
> Could you give any references ?
|
|
|
Powered by
FUDForum. Page generated in 0.13513 seconds
Home