Hi John, > Hi Stefan > > I hadn't seen this when I replied earlier, but reading it now I think that > this touches on the discussions ages ago about how to integrate > contributions into builds. > > If bringing in outside contributions could be simplified, then the > location and control of components, whether UI components or something > else, becomes less of an issue. > > Ideally I'd like to see something where creating a contrib was no harder > than pushing to github, and using one was no harder than referencing a > github url. If there was also a unified namespace, then just referencing a > class could cause the compiler to include the contrib; for example, my > qx-serverobjects uses the namespace .zenesis.qx.remote and obviously I own > zenesis.com so I should be able to define a mapping to my github release > somehow. > > 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?
Exactly this is our idea about it. It should be seemlessly integrated. The cloud should be used. An automatic behaviour when referenced bothers new users less and they can focus on less details...i.e. they need less reading of manuals etc...that is something for framework developers. With a contribution system where also the existing GUI components are contributed but maybe called "core", it is possible to easily contribute and then the community will test it and approve the component after certain rules set up. KISS Keep It Stupid Simple but increase flexibility... A contributor sends a pull request to one collecting repository of GUI components. It will then be tested and approved or not etc. When generating the application all references are checked against this repository and prints a warning message of an unapproved component is referenced etc. It makes it easier to expand the set of GUI components, versionize 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 > To: "qooxdoo Development" <qooxdoo-devel@lists.sourceforge.net> > 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 library fully accessible at genertion might > increase interest of community to add their UI components and the API would > be clearer than today... > >> I would be opposed to removing them. That's going in the opposite > direction >> of making qooxdoo easier for new people to use. A related option that I >> wouldn't oppose (but don't see a very good reason for implementing) is > to >> create a GUI "library" (in qooxdoo parlance) that is by default included > in >> config.json (or whatever build system is used). An advanced user could >> choose to remove that library entry from config.json to entirely > decouple >> the core GUI code. Again, though, I don't think this is necessary, as > users >> are free to create whatever GUI they like, and as long as they have > their >> own namespace, have no concern of including qooxdoo core GUI > functionality >> in their app. > > Not removing them but moving them into a separate library list where they > can be accessed and used at compilation. Versions of them can then be > handled easier. > The doc and everything would be the same. In practice no difference except > that other users might be interested to use one of the components and can > then easily add it without getting all qooxdoo. A structure more like > jquery using git to hold the components and for a list of accepted, tested > and approved components, but with qooxdoo's complexity. Many developers use > jquery, which still is very successful, of this reason...easy to access and > use without studying a whole framework... > > It might also force the core to be even leaner and modularized without > extra overhead. > > I think your last sentence is a concern for new users...overhead and > complexity....steep learning curve > > Stefan > >> Derrell >> >> >> On Thu, Feb 25, 2016 at 1:02 PM <d...@cost-savers.net> wrote: >> >>> 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 the >>> qooxdoo team and not a compulsory unit coupled unconditionally to the >>> core... >>> >>> If that would be possible to do, then the core team can focus on core >>> development, while anyone can contribute with UI components. The current > so >>> called core UI components would be available separately and loadable on >>> demand but uncoupled from the core. >>> >>> What do you say about that? Any ideas? Pros and cons? >>> >>> Stefan >>> >>> >>> > ---------------------------------------------------------------------------- > -- >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>> _______________________________________________ >>> qooxdoo-devel mailing list >>> qooxdoo-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> > >> > ---------------------------------------------------------------------------- > -- >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > >> _______________________________________________ >> qooxdoo-devel mailing list >> qooxdoo-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ---------------------------------------------------------------------------- > -- > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
