[web2py] Re: web2py - Best Practice
I apologise to the group that I have not been able to pursue this over the past few weeks. My idea to get the ball rolling was to try and create a google groups like 'forum' on gae or fluxflex using the comments widget from the plugin_wiki as a base. (Whilst it would be easy to just start a new google group it seems to me a simple web2py based app would be a much better way to start. Indeed the forum could be our first application) From there we could discuss the way forward as I believe this overall project is as much about co-ordination of the functionality, look and feel, documentation, installation process, plugin options, hosting, version control, etc. as it is about the actual code itself. There have been some excellent new initiatives since my first message including instant press 2.0, instant admin and simple cms. I was unable to create the 'forum' mostly due to lack of technical confidence and now a new job. So rather than abandon the project, I was wondering if there was anyone else out there that may be interested in creating a 'forum' (ie google groups clone) on gae or flexflux or somewhere appropriate. If there is no one but there is still interest in the project, then in a few weeks I will look at creating a google group, something like web2py-applications. Cheers, nic
[web2py] Re: web2py - Best Practice
How about a PHPBB/Vbulletin clone...but better?
[web2py] Re: web2py - Best Practice
maybe we could add to this project: http://pyforum.org (afaik author is also in this forum :))
[web2py] Re: web2py - Best Practice
In addition to full applications, we should also consider building plugin functionality that would be widely useful. Two things that come to mind: - Full-text search abstraction layer -- something that could potentially work with multiple search backends, similar to http://haystacksearch.org/and http://code.google.com/p/django-fts/. - Async realtime/chat functionality -- maybe build on the comet_messaging.pyhttp://code.google.com/p/web2py/source/browse/gluon/contrib/comet_messaging.pyapproach, or look into a greenlet approach, as described here: http://bottlepy.org/docs/dev/async.html. Anthony On Wednesday, July 13, 2011 1:45:18 AM UTC-4, nic wrote: Dear friends, I am a huge web2py fan and would like to propose an idea to the community. I understand that web2py is a development environment and has it’s roots as an educational platform. One of the things that I have personally found most useful are the free appliances. However as web2py has matured over time a lot of these have become dated and as new developments have emerged I have often been confused about best practices going forward. I would like to propose that we develop a suite of products (open source of course) based on the best practices of web2py that would be: Useful and usable by non-programmers Serve as a focal point for the community on just how great web2py could be Serve as a template for developers To be clear the idea is to create a separate project from web2py itself and then find the best of breed products and develop them in web2py. Things like: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... The focus would be on producing complete usable and beautiful applications. I feel that the creation of a separate project will have some important advantages such as: We can create a “brand” around the products. It will not “hijack” the core web2py focus. Can have separate focus such as functionality and look and feel Can include complimentary, tested projects such as open source icons and skins Can have it’s own development cycle, (eg release every 6 months) Can have it’s own repositories etc. Ultimately the products could be made available by web hosts just by the click of a button just like the php ones are now. I am very interested in the thoughts of the community and if there is interest I will move to the next step and create a site (probably on GAE) for further discussion such as: decide on a name decide on goals decide on processes find a home decide on products etc ...
[web2py] Re: web2py - Best Practice
I am all for this! Massimo On Jul 13, 12:45 am, nic nicbythe...@gmail.com wrote: Dear friends, I am a huge web2py fan and would like to propose an idea to the community. I understand that web2py is a development environment and has it’s roots as an educational platform. One of the things that I have personally found most useful are the free appliances. However as web2py has matured over time a lot of these have become dated and as new developments have emerged I have often been confused about best practices going forward. I would like to propose that we develop a suite of products (open source of course) based on the best practices of web2py that would be: Useful and usable by non-programmers Serve as a focal point for the community on just how great web2py could be Serve as a template for developers To be clear the idea is to create a separate project from web2py itself and then find the best of breed products and develop them in web2py. Things like: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... The focus would be on producing complete usable and beautiful applications. I feel that the creation of a separate project will have some important advantages such as: We can create a “brand” around the products. It will not “hijack” the core web2py focus. Can have separate focus such as functionality and look and feel Can include complimentary, tested projects such as open source icons and skins Can have it’s own development cycle, (eg release every 6 months) Can have it’s own repositories etc. Ultimately the products could be made available by web hosts just by the click of a button just like the php ones are now. I am very interested in the thoughts of the community and if there is interest I will move to the next step and create a site (probably on GAE) for further discussion such as: decide on a name decide on goals decide on processes find a home decide on products etc ...
Re: [web2py] Re: web2py - Best Practice
like this, +1
[web2py] Re: web2py - Best Practice
On Wednesday, July 13, 2011 7:45:18 AM UTC+2, nic wrote: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... How about an issue tracker? We're currently using Redmine, and it's really clunky and features very high memory consumption.It has a lot more features compared to Trac, however. Google Code is tricky for companies to use as their internal issue tracker.
Re: [web2py] Re: web2py - Best Practice
On 13.7.2011 10:23, cjrh wrote: On Wednesday, July 13, 2011 7:45:18 AM UTC+2, nic wrote: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... How about an issue tracker? We're currently using Redmine, and it's really clunky and features very high memory consumption.It has a lot more features compared to Trac, however. Google Code is tricky for companies to use as their internal issue tracker. Issue tracker sounds very nice. 1+, online store also. Why not add an Office suite to and we can skip all other programs :=) If you need help with setting up and creating the workplace for this project let us know. Kenneth
[web2py] Re: web2py - Best Practice
On Jul 13, 1:05 pm, Marin Pranjic marin.pran...@gmail.com wrote: On Wed, Jul 13, 2011 at 7:45 AM, nic nicbythe...@gmail.com wrote: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... This is great idea, I had it few months ago, but never wrote it here. Next week I'll start programming a Forum software (with web2py ofc). Main goals are: optimized performance and powerful plug-in system. I will open few discussions here, very soon. My idea was to make every popular PHP app. done with web2py. Few more ideas: - web-based email application (like SquirrelMail etc) - database managment (like phpmyadmin, phppgadmin etc) - system administration (like cpanel) a simple ERP like the php weberp or dolibarr, or the phyton tryton?
Re: [web2py] Re: web2py - Best Practice
+1 On Wed, Jul 13, 2011 at 7:37 AM, newnomad uti...@gmail.com wrote: On Jul 13, 1:05 pm, Marin Pranjic marin.pran...@gmail.com wrote: On Wed, Jul 13, 2011 at 7:45 AM, nic nicbythe...@gmail.com wrote: A Wiki / Blog / CMS / Forum An Online Store A Personal Accounting System A Media Center etc ... This is great idea, I had it few months ago, but never wrote it here. Next week I'll start programming a Forum software (with web2py ofc). Main goals are: optimized performance and powerful plug-in system. I will open few discussions here, very soon. My idea was to make every popular PHP app. done with web2py. Few more ideas: - web-based email application (like SquirrelMail etc) - database managment (like phpmyadmin, phppgadmin etc) - system administration (like cpanel) a simple ERP like the php weberp or dolibarr, or the phyton tryton?
[web2py] Re: web2py - Best Practice
I think this is a worthwhile aspiration but I suspect we will only get there organically. The problem with some of those categories is that there are multiple good solutions that make it difficult to decide to use a probably inferior solution. I was beginning to create a generic shopping cart but went a little nuts and turned it into pricetack.com which is more specialized.
[web2py] Re: web2py - Best Practice
Great !!! Looks like there is some interest. Thanks for all the comments. I totally agree it's important to figure out what the compelling use case is for them, and how the necessary thousands of developer hours are going to get committed and coordinated to make it happen Unless someone has a better idea as a first step, I will create a wiki on gae using the vanilla plugin_wiki. (which I think is fantastic) From there we can set up a discussion board to flesh out the goals of the project.
Re: [web2py] Re: web2py - Best Practice
I like this as well! On Wed, Jul 13, 2011 at 10:54 PM, nic nicbythe...@gmail.com wrote: Great !!! Looks like there is some interest. Thanks for all the comments. I totally agree it's important to figure out what the compelling use case is for them, and how the necessary thousands of developer hours are going to get committed and coordinated to make it happen Unless someone has a better idea as a first step, I will create a wiki on gae using the vanilla plugin_wiki. (which I think is fantastic) From there we can set up a discussion board to flesh out the goals of the project.
