Hi Petr
Personally this has not bothered me until recently when I’ve had to do some
traditional web front ends - q/qxweb is not compatible with any nice UI
widgets, so for “thin” front end I use requirejs, jquery, knockoutjs, etc … and
a home made qx.Class. I agree that Qooxdoo is not really suitable for that
kind of development, but mostly because the qxweb provides very little compared
to what is already out there and more established - this is a shame because
it’s 95% of the way to being useful, a little more effort and it could have a
good chance.
On the backend and for “thick” web clients the generator is essential (although
slow), although I’m not sure I agree that a lot of code is unused.
Regards
John
On 10 Sep 2014, at 12:08, Petr Kobalíček <kobalicek.p...@gmail.com> wrote:
> I know how the generator works, but I think that it's not just an advantage,
> but also a huge disadvantage. If you check out qooxdoo source code, there is
> a lot of code nobody needs, but is included, and it's hard to remove it.
>
> I really believe that "qooxdoo" way is no longer needed. Qooxdoo should be
> split into some packages and every contrib would just include dependencies,
> it would be also much easier that one contrib depends on other.
>
> But, I know it's not easy, and I know that qooxdoo is rather static than
> dynamic. For example theming contribs is another issue for me.
>
> In the end I don't know if I will ever use qooxdoo again for a new project,
> and I'm maybe the only one here who doesn't like generator :-)
>
> On Wed, Sep 10, 2014 at 12:20 PM, panyasan <i...@bibliograph.org> wrote:
> Hi Petr,
>
> but as far as I can see, you cannot use contribs without the generator and
> you cannot include them as client-side dependencies. They are libraries that
> create *compile time* dependencies that are sorted out very efficiently by
> the generator (think of part generation). Isn't bower meant for libraries
> that are mostly independent of each other that have *runtime* dependencies?
> They might depend on each other, but this is outside of the qooxdoo
> workflow.
>
> Cheers,
> Christian
>
>
>
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586169.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
