On May 13, 2010, at 9:26 AM, Thadeus Burgess wrote: > This is similar to how PluginCentral will be designed, if we ever get > that spec finalised =)
It'd be reasonable to do both at the same site. > > -- > Thadeus > > > > > > On Thu, May 13, 2010 at 11:14 AM, blackthorne <[email protected]> wrote: >> One more thing, web2py could have a list of repositories url, with the >> default the one we can find on the official website but also the >> possibility to add other non-official ones as well as mirrors. >> Technically web2py could interact with each repository by a simple >> specification in XML-RPC or something, to list, search, download >> (which could also work for update) and peek. >> Finally, on a second stage there could even be a submit app option so >> you could submit apps for moderation and further release, seamlessly. >> >> Thanks >> >> On May 13, 5:09 pm, blackthorne <[email protected]> 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 >>
