Hi Fritz,
Today Fritz Zaucker wrote:
> On Sat, 27 Feb 2016, John Spackman wrote:
>
> > How cool would it be if it automatically downloaded my contrib just
> > because your code referenced it? For new users, it would mean that any
> > example snippets work, out of the box. What do you think?
>
>
On Sat, 27 Feb 2016, John Spackman wrote:
> How cool would it be if it automatically downloaded my contrib just
> because your code referenced it? For new users, it would mean that any
> example snippets work, out of the box. What do you think?
I am not sure if automatic download is really the
nize them and
focus on keeping the core of the framework lean and effective with a clear
focus.
Is it a good idea?
Stefan
> Regards
> John
>
>
>
>
> From: d...@cost-savers.net
> Sent: Friday, February 26, 2016 9:34 AM
&g
t"
Subject: Re: [qooxdoo-devel] Component library
Derrell,
> qooxdoo apps already include only those GUI components that are actively
> used by the user's app. Yes, they're included in the qooxdoo source
code,
> but are otherwise unused.
Putting them in a separate libr
much
to do.
Regards
John
From: d...@cost-savers.net
Sent: Thursday, February 25, 2016 6:14 PM
To: qooxdoo-devel@lists.sourceforge.net
Subject: [qooxdoo-devel] Component library
After thinking back and forth we have tried to find out about how to make
the UI components
Derrell,
> qooxdoo apps already include only those GUI components that are actively
> used by the user's app. Yes, they're included in the qooxdoo source code,
> but are otherwise unused.
Putting them in a separate library fully accessible at genertion might increase
interest of community to add
qooxdoo apps already include only those GUI components that are actively
used by the user's app. Yes, they're included in the qooxdoo source code,
but are otherwise unused.
I would be opposed to removing them. That's going in the opposite direction
of making qooxdoo easier for new people to use. A
After thinking back and forth we have tried to find out about how to make the
UI components independent of the core of the framework.
It would be fantastic if it would be possible to uncouple dependencies other
than the core ones.
Imagine to have a UI component library, which is not decided by
