I plan to create JSON-RPC service for all functions so you will be able
to create client for instance in python/wxwidgets. In web version every
entity (like database, widgets, forms, extension etc.) will have it's
own window (jqueryui dialog).

I want to start as we fix bugs that prevent to make a release 0.9.0.

On Wed, 14 Dec 2011 10:46:00 -0600
Jon Phillips <[email protected]> wrote:

> How can we move forward on this guys?
> 
> I would prefer we maintain current admin interface in stability mode,
> some bug fixes, etc, but then:
> 
> * start making other admin interfaces to edit aiki site
> 
> It would be great to have a more purely command mode, or the ways you
> guys propose.
> 
> Roger, I totally agree with the above.
> 
> We need to make editing an aiki site a joy for developers, and not a
> pain in the ass! :)
> 
> I actually was thinking up a way we could write bash scripts to pull
> out a widget into your favorite editor, edit it, and then when you
> hit save, it gets saved into the database. That would be cool, right?
> 
> Jon
> 
> On Fri, Nov 25, 2011 at 2:51 AM, Jon Phillips <[email protected]>
> wrote:
> 
> > 2011/10/29 Bassel Safadi <[email protected]>:
> > >
> > >
> > > 2011/10/29 Jakub Jankiewicz <[email protected]>
> > >>
> > >> Dnia 2011-10-29, o godz. 11:44:07
> > >> Roger Martín <[email protected]> napisał(a):
> > >>
> > >> > Thanks Jon,
> > >> > your feedback give me one idea:
> > >> >
> > >> >
> > >> > why must we store aiki admin widget in database?
> > >> > Now, aiki admin is 'stored' in create-insert.sql - in few
> > >> > words a beautiful mode for editing ;-)-- and during
> > >> > installation process inserted in database.
> > >> >
> > >> > We can create a array for admin widget, and change parse
> > >> > engine for search widget in database or in hard-coded array.
> > >> > It's not perfect solution but means:
> > >> > - it easier (compared with actual sql)  to maintain for
> > >> > aiki-devoleper: $admin["header"] = array (
> > >> >  "permissions=>".."
> > >> >  "normal_select" =>".."
> > >> >   "widget"=>"....code here....") ;
> > >> > You can edit admin in your ide, see results it in your browser
> > >> > and if crashs control-z, else 'bzr push'
> > >>
> > >> We can store admin panel in static files in the source code and
> > >> make create this sql file. So Developers will be editing static
> > >> files (admin.html admin.js admin.css) and Aiki Users will be
> > >> able to edit them from Admin.
> > >>
> > >
> > > or we can group widgets as apps in the database and make the
> > > admin panel
> > an
> > > app that get installed by default and can be removed as well.
> > > currently
> > all
> > > widgets have app id but that is not in use currently nor it show
> > > up in
> > the
> > > interface. but we can add a table for apps and make the users
> > > insert app
> > ids
> > > in widgets then apps can be shared with different sites in the
> > > same aiki installation
> >
> > I like the idea, that an app, or extension can be purely run from
> > disk in addition to storing in the database.
> >
> > I do think we need a solution to this APPS problem soon though, so
> > we can share features across aiki.
> >
> > Jon
> >
> > --
> > Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳
> > irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing)
> >
> 
> 
> 

-- 
Jakub Jankiewicz
twitter: @jcubic
www: http://jcubic.pl

_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help   : https://help.launchpad.net/ListHelp

Reply via email to