Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
Love this idea.
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
On 13 June 2011 14:38, Marin Pranjic marin.pran...@gmail.com wrote: I think that template app should be minimal. On Mon, Jun 13, 2011 at 2:33 PM, Martín Mulone mulone.mar...@gmail.comwrote: I prefer the way to select the application you want to install, only welcome in main web2py and the others over a repository. New: You want to install? - welcome (default) - welcome jquery ui - wiki - xxx +1 -- May grace and peace be yours in abundance through the full knowledge of God and of Jesus our Lord! His divine power has given us everything we need for life and godliness through the full knowledge of the one who called us by his own glory and excellence. 2 Pet. 1:2b,3a
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
OK I vote for jquery ui inclusion.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
I use JQuery UI via Google's CDN http://code.google.com/apis/libraries/devguide.html#jqueryUI so would not want it included.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
I second this. I think pulling jQuery and jQuery UI from a CDN is the way to go.
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
Sometime ago the welcome app has this , getting jquery from a cdn, and was a mess, the problem is when you are not connected to the internet, making the app really slow. 2011/6/14 Matt Gorecki m...@goelephant.com I second this. I think pulling jQuery and jQuery UI from a CDN is the way to go. -- http://martin.tecnodoc.com.ar
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
-1 for this. I realize jquery is by far the most popular js framework, but I think it would be better to be js agnostic. In fact I would like to see more examples using other frameworks, like dojo, angular.js, or yui3. I've seen quite a number of posts about people using other frameworks instead of jquery, particularly dojo, (see: http://blog.rebeccamurphey.com/2009/11/12/dojo-confessions-or-how-i-gave-up-my-jquery-security-blanket-and-lived-to-tell-the-tale for example) and I think its an impediment to tie the web2py framework too closely to one of these despite it's popularity.
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
Best of both worlds:
script
src=//ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js/script
scriptwindow.jQuery || document.write(script
src='{{=URL('static','js/jquery.js')}}'\x3C/script)/script
Not sure the Jquery UI equivalent.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
I agree jQueryUI should not be included as a default. I use jQueryUI but only pull it in for the views that need it. It is one css and one js. The other thing to remember is if you go to the jQueryUI download page the form allows you to build a custom version specific to the features in use with the particular application. Some of the components are large enough that I wouldn't want to load them if I don't need them.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
True about plugin_wiki, but not everyone uses it. I know I don't, just because I am mostly developing internal enterprise applications that do CRUD operations on a database. Also, there are other plugins that require jQuery UI, so having those plugins include their own version of it is a bad idea, unless you make plugin_wiki a dependency of every plugin that needs jQuery UI. That was my main motivation for wanting it in the core, was that plugins don't need their own installation of it and you don't have to deal with multiple themes and things like that. After thinking about this a bit more, maybe it would a good idea to move jQuery UI from plugin_wiki to its own plugin. That way it doesn't add bloat to applications that don't need it. You install the plugin_ui or whatever you want to call it, then other plugins or applications that want to use jQuery UI can just make plugin_ui a requirement without having to pull in the entire functionality of plugin_wiki. Would this be a better solution?
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
I prefer the way to select the application you want to install, only welcome in main web2py and the others over a repository. New: You want to install? - welcome (default) - welcome jquery ui - wiki - xxx 2011/6/13 Ross Peoples ross.peop...@gmail.com True about plugin_wiki, but not everyone uses it. I know I don't, just because I am mostly developing internal enterprise applications that do CRUD operations on a database. Also, there are other plugins that require jQuery UI, so having those plugins include their own version of it is a bad idea, unless you make plugin_wiki a dependency of every plugin that needs jQuery UI. That was my main motivation for wanting it in the core, was that plugins don't need their own installation of it and you don't have to deal with multiple themes and things like that. After thinking about this a bit more, maybe it would a good idea to move jQuery UI from plugin_wiki to its own plugin. That way it doesn't add bloat to applications that don't need it. You install the plugin_ui or whatever you want to call it, then other plugins or applications that want to use jQuery UI can just make plugin_ui a requirement without having to pull in the entire functionality of plugin_wiki. Would this be a better solution? -- http://martin.tecnodoc.com.ar
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
I think that template app should be minimal. On Mon, Jun 13, 2011 at 2:33 PM, Martín Mulone mulone.mar...@gmail.comwrote: I prefer the way to select the application you want to install, only welcome in main web2py and the others over a repository. New: You want to install? - welcome (default) - welcome jquery ui - wiki - xxx 2011/6/13 Ross Peoples ross.peop...@gmail.com True about plugin_wiki, but not everyone uses it. I know I don't, just because I am mostly developing internal enterprise applications that do CRUD operations on a database. Also, there are other plugins that require jQuery UI, so having those plugins include their own version of it is a bad idea, unless you make plugin_wiki a dependency of every plugin that needs jQuery UI. That was my main motivation for wanting it in the core, was that plugins don't need their own installation of it and you don't have to deal with multiple themes and things like that. After thinking about this a bit more, maybe it would a good idea to move jQuery UI from plugin_wiki to its own plugin. That way it doesn't add bloat to applications that don't need it. You install the plugin_ui or whatever you want to call it, then other plugins or applications that want to use jQuery UI can just make plugin_ui a requirement without having to pull in the entire functionality of plugin_wiki. Would this be a better solution? -- http://martin.tecnodoc.com.ar
Re: [web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
Yes Martin, I think the idea of giving a choice of New 'Welcome XXX' is great. As you have found with Instant Press, it isn't always convenient to make fundamental site features as a plugin. There is little difference in principle between a 'New Welcome' app and the existing appliances. However, I think to qualify as a 'New Welcome' the developer(s) should have some commitment to maintain the code and keep the repo up to date. At present, many of the appliances are out of date and this has reduced confidence in using them.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
Jquery ui can be installed in one line of code so I'm not exactly sure what is being proposed.
[web2py] Re: Discussion: Thoughts about including jQuery UI in core web2py?
You get jquery ui when you install pugin_wiki On Jun 12, 7:32 pm, pbreit pbreitenb...@gmail.com wrote: I agree with Villas. I think Jquery UI needs to earn its way in. I haven't really seen much that makes it a must-have at this point and I appreciate Web2py remaining relatively lean. But I'd love to be proven wrong.
