cool thing.

I've done the yaml configurator as an app, I will share it soon but it
would be nice to see it integrated with web2py as if it was a filetype
handler, just like there is for .py files and htmledit for html
files, ...

I've also made a draft for an app spec, here it is:
w2py app spec
- name
- version
- description
- deps
- author
- license
- price
- readme
- contact
- url

I am aware we could make more from the "readme" field that such as pre/
post installation notes, this is a draft...

Massimo, do you want to make this centralized or distributed as in
suggested in this thread ( 
http://groups.google.com/group/web2py/msg/702388f49e84e15a?
)?

Thank you,
Best regards

On May 16, 7:52 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> I am happy to merge option 2) withhttp://web2py.com/appliances
>
> On May 14, 8:38 am, blackthorne <francisco....@gmail.com> wrote:
>
>
>
> > yes.
>
> > So I see on this thread 2 or 3 different ideas and a small roadmap:
> > - this web conf (YAML) editor as a first step to create/edit app
> > metadata based on a specification (yet to build). This is a general
> > application which can be applied to any yaml file in different
> > scenarios.
> > - On a second step, the Appliance Remote Manager (it should be called
> > something like web2py app supermarket)
> > - applying this to plugins/slices [?].
>
> > So, anyone open to share efforts to make this thing happen?
>
> > On May 14, 2:13 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > I think I will make a web yaml editor which should be perfect for 
> > > > configurating things with a browser...
>
> > > I can see many applications for it, for example a way to edit tables.
> > > It would be nice if it were possible to constrain the structure of the
> > > accessible yaml (for example the field types when describing a table).
> > > I would use jsTree.
>
> > > On May 14, 8:08 am, blackthorne <francisco....@gmail.com> wrote:
>
> > > > that's exactly what I am suggesting.
> > > > speaking about that, I think I will make a web yaml editor which
> > > > should be perfect for configurating things with a browser...
>
> > > > On May 14, 2:01 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > > There is LICENSE and ABOUT. We can add another file where to keep
> > > > > metadata and make edtable via admin as with ABOUT.
>
> > > > > On May 14, 5:14 am, blackthorne <francisco....@gmail.com> wrote:
>
> > > > > > Maybe, before going further with this there should be a place in
> > > > > > web2py framework to edit the app details such as the version,
> > > > > > dependencies, app name, which could be included in the app_conf.yml
> > > > > > file [?]. This would make things a lot easier when you want to
> > > > > > retrieve the details of an app or when you want to subscribe it, so
> > > > > > this file will hold everything needed.
>
> > > > > > Notice, it will always follow "convention over configuration". If
> > > > > > there is no conf file, version "1.0" could be assumed, the folder 
> > > > > > name
> > > > > > becomes the "app name".
>
> > > > > > Massimo, is there any already existant file to keep this data? is 
> > > > > > this
> > > > > > a good idea?
>
> > > > > > On May 14, 4:26 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > > > > 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

Reply via email to