I think you just touched the main reason (in my oppinion). It's very hard to
get into the api itself and the UI desinger makes you start a project
quickly. That's in my oppinion the greatest advantage on having it.
No dia 14 de Set de 2011 12:51, "Burak Arslan"
escreveu:
> On 09/14/11 15:31, Migue
Hi Burak,
Today Burak Arslan wrote:
> tobi, maybe you knew that already, but you can use "promote widget" in
> the context menu to put your own classes in the instantiation line that
> behave like the displayed widget. (you should use the c++ namespace
> separator though, which is '::')
ah ... n
On 09/14/11 15:31, Miguel Manso wrote:
>
> Anyone using it for a complete project?
>
>
me :) (i'm the author)
it's gotten no recent development recently because it does everything we
need it to do. so it's not by all means an abandoned project.
http://github.com/arskom/jsqt link is the more rece
Hi Miguel,
Today Miguel Manso wrote:
> Anyone using it for a complete project?
I tried, but I found that I am much more comfortable working with
the code, as qooxdoo is so modular and easy to enhance and
customize. I kept running into problems with the gui designer
aproach which relies on predef
Anyone using it for a complete project?
No dia 14 de Set de 2011 12:29, "Tobias Oetiker" escreveu:
> There is also
>
> http://code.google.com/p/jsqt/
>
> (or rather https://github.com/arskom/JsQt)
>
> which works by compiling qt designer output to qooxoo
>
> cheers
> tobi
>
> Today Derrell Lipman
There is also
http://code.google.com/p/jsqt/
(or rather https://github.com/arskom/JsQt)
which works by compiling qt designer output to qooxoo
cheers
tobi
Today Derrell Lipman wrote:
> On Wed, Sep 14, 2011 at 08:08, Miguel Manso wrote:
>
> > Hi there,
> >
> > We've worked several months on a
I think that with such thing a lot of newcommers could appear.
No dia 14 de Set de 2011 12:24, "Derrell Lipman" <
[email protected]> escreveu:
> On Wed, Sep 14, 2011 at 08:08, Miguel Manso wrote:
>
>> Hi there,
>>
>> We've worked several months on a project 100% with qooxdoo.
>>
>
On Wed, Sep 14, 2011 at 08:08, Miguel Manso wrote:
> Hi there,
>
> We've worked several months on a project 100% with qooxdoo.
>
> One of the developers left and the learning curve for a new one to
> come in is VERY high.
>
> Did anyone thought on a UI designer for qooxdoo? I think that with
> th
Hi there,
We've worked several months on a project 100% with qooxdoo.
One of the developers left and the learning curve for a new one to
come in is VERY high.
Did anyone thought on a UI designer for qooxdoo? I think that with
this this learning curve I'm talking about would be a lot smaller
beca
