I agree.
On May 13, 9:02 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > Massimo, we can take the ideas for plugin metadata and use it for > applications as well? > > Change the name from plugincentral to web2pycentral. We can start an > open source version of the web2pycentral and decide who can work on > it. > > -- > Thadeus > > On Thu, May 13, 2010 at 2:07 PM, Jason Brower <encomp...@gmail.com> wrote: > > I say we move forward with this one as it doesn't need so much work as > > with the plugins. At least at first thought. It's just additional > > metadata in the application. I think some simple xml/html would do the > > trick. Just what data if for someone else to think about. :D > > But I think it's awesome. > > Best Regards, > > Jason Brower > > > On Thu, 2010-05-13 at 09:13 -0700, mdipierro wrote: > >> This is a good idea. > > >> On May 13, 11:09 am, blackthorne <francisco....@gmail.com> wrote: > >> > ok, this one may be interesting... > > >> > Currently, we can install web2py apps in one of 3 ways. uploading it, > >> > providing its url or putting the files in the applications folder > >> > manually. Nothing wrong with this but seems to me that with little > >> > effort we could take this beyond. > >> > Think about an integrated (web) interface that allowed you to search > >> > or browser appliances and show its details when requested. This could > >> > happen inside the web2py framework and you could even install it by > >> > pressing a button (actually it just needs to use the already existing > >> > "download/provide url" option inside). > >> > I think this could improve user/developer experience but that's not > >> > all... > >> > Applications could have versions, and a changelog that could make part > >> > of the details of the application and an "update" option, so that > >> > users could keep all their apps on the edge. > > >> > Who's with me? > > >> > Thank you, best regards
