On Feb 26, 5:37 pm, chris thatcher <thatcher.christop...@gmail.com> wrote: > I get both sides, though I'm sure there are more than two ;) What I'm > hoping is that we can keep jQuery simple, clean elegant (we could burden > plugin developers just a little more to pass muster.) Let UI focus on > widgets. And add a spot for the railable patterns we need to scale to > satisfy the next generation (meaning about 2 years at this point). > > the mvc stuff should pass all the ussual tests: look, feel, taste like > jQuery. be small and effiecient and focused on real problems that arent > alreay solved.
+1. What I think Justin is proposing is to provide a framework that would *enforce* conventions, libraries/plugins and good practices. Note that, at least in my opinion, it's very different to show or define conventions in the docs than forcing them. I don't think the jQuery core should be changed, extended or branched in any way. Most of the things we "need" for this are already there (JMVC, QUnit, YUI Compressor, JSDoc, JSpec, ...). I believe that the point, however, is to provide a framework with a defined structure, where a developer shouldn't have to go over the docs to see what's the convention for doing X is. I feel that slowly more and more users will be developing larger projects, and maybe it would be useful to provide an out of the box solution where you could do something like: ~: jqcmd _project_name_ (init a project with default plugins as well as testing/debugging libraries and a well defined folder structure) ~: jqcmd plugin list ~: jqcmd plugin install _name_or_url_ ~: jqcmd generate plugin _name_ ~: jqcmd generate test _name_ ~: jqcmd tests:run In any case, I think what John listed are the steps just needed and would be the base for building such a tool. > Needs code: > - Widget utility (I'm working on this) > - Debugging utility > - Static plugin analyzer > Need a tutorial to cover the concepts of (I'm working on this): > - Encapsulation > - Extensibility > - Modularity > Needs (defined/documented) conventions: > - File names > - Method names > - Method structures > - Testing > - Documentation > - Packaging So I think it's time to help with that first and then see where all these definitions takes us. Is there a place where all this stuff is being discussed (separatedly)? --Luciano. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
