[ews.eclipse.technology.rap] Re: Writing custom widgets is hell on earth

[Niels Lippke <nlippke@xxxxxx>]

Hi Stefan,

in my case, I do all the layout stuff in SWT. So I cannot use plain js 
for the developement. Otherwise I'd have to do things, twice.

Which environment (plugins) do you use for qooxdoo-development?

Niels

Stefan Roeck schrieb:
> Hi Niels,
>
> I would recommend to write and test Custom Widgets on the qooxdoo side 
> only at first. If everything is working there you can add the RAP part. 
> The shortens your development cycles because you simply have to save 
> your JS-file and refresh your browser instead of restarting the OSGi 
> stuff all the time.
>
> Regards,
> Stefan.
>
>
> Niels Lippke schrieb:
> > Hi,
> >
> > Writing custom widgets for RAP is really an annoying task, at least
> > the way I do it.
> >
> > Whenever somethings wrong in my .js files my Test-Application starts 
> > with an empy screen and the only way for me is to comment out code 
> > fragements, to see where the problem is. And even this does not always 
> > lead to a result.
> >
> > The only thing I can seen in my debug window is
> >
> > qx.core.Init[4]: qooxdoo 0.7.4 (r16878) [debug]
> > 000406 DEBUG: qx.core.Init[4]: loaded 242 classes
> > 000406 DEBUG: qx.core.Init[4]: loaded 3 interfaces
> > 000406 DEBUG: qx.core.Init[4]: loaded 7 mixins
> > 000406 DEBUG: qx.core.Init[4]: loaded 0 themes
> > 000406 DEBUG: qx.core.Init[4]: loaded 0 locales
> > 000406 DEBUG: qx.core.Init[4]: client: mshtml-7.0/win/de
> > 000406 DEBUG: qx.core.Init[4]: browser: explorer/vml
> > 000406 DEBUG: qx.core.Init[4]: application: 
> > org.eclipse.swt.Application[13]
> >
> > and that's it.
> >
> > This keeps me busy for hours to produce small pieces of code. And this 
> > is really frustrating. I'm new to the qooxdoo stuff and I really don't 
> > expect wonders by myself. But this is definitly not the way developers 
> > (like me) should work.
> >
> > I'm using the JSEclipse-Plugin to have at least syntax checks for my 
> > .js files.
> >
> > So, to the experienced ones: Is there any way how to deal with the 
> > Javascript-stuff, reasonably?
> >
> > Thanks, Niels