To be honest I really don't like this npm idea, for me it should be:
npm - server
bower - client
Even if you have to precompile qooxdoo to be used with bower it would be
much better than using it as npm with generator. The problem I see is that
qooxdoo tries to be for everything, which is simply impossible to achieve
for the current dev-team.
Cheers,
Petr
On Wed, Sep 10, 2014 at 11:46 AM, <d...@cost-savers.net> wrote:
> Hej C!
>
> > If this is not a priority of the qooxdoo devs, maybe we should move
> ahead and
> > agree on a standard format to publish contribs as npm modules? That
> would be
> > my personal favorite. Technically, this is very easy, since one can
> install
> > them using npm and then in config.json point to the location of the
> Manifest
> > file.
>
> I do not vote for this. I would rather see a qooxdoo module, but with
> possibility to install it with npm too for those outside the very tiny
> qooxdoo community. Some kind of double factoring if possible. Maybe it
> might broaden the user base...
>
> > To insure discoverability of the contribs, we could agree on a common
> prefix
> > of the npm modules (for example "qx-contrib-").
>
> Don't like this at all as it only indicates modules to be usable by
> qooxdoo. Freedom of name giving!
>
> Publish the modules in already existing contrib catalog and in npm modules
> catalog instead.
>
> > What do others think? Sorry to promote the fragmentation of the
> contribution
> > architecture, but I don't see anything happening and I don't want to use
> the
> > current system anymore.
>
> Why do you want this fragmentation, if you don't want to use qooxdoo
> anymore?
>
> Very little is happening to qooxdoo nowadays, which is a pity.
> Unfortunately, we realize a slow suffocation death of qooxdoo...;-(
> Maybe it could have been prevented by a truly open community and project
> owner with joined forces...who knows. It seems to be too late today.
> Our development team is the first to feel sadness about it... In the
> history many very good tech projects have failed on management.
>
> Stefan
>
> > C.
> >
> >
> >
> > --
> > View this message in context:
> http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586165.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
