Good logic...put this in that plan on the wiki :) Rock on!

Jon

On Sun, Jan 29, 2012 at 8:34 PM, Jakub Jankiewicz <[email protected]> wrote:
>
>
> On Sun, 29 Jan 2012 19:19:34 +0800
> Jon Phillips <[email protected]> wrote:
>
>> On Sun, Jan 29, 2012 at 7:11 PM, Jakub Jankiewicz <[email protected]>
>> wrote:
>> >
>> >
>> > On Sun, 29 Jan 2012 12:58:35 +0800
>> > Jon Phillips <[email protected]> wrote:
>> >
>> >> Bassel, please help us! Don't fight us! Still Aiki has so many
>> >> features kept in your brain, and that is not good.
>> >>
>> >> http://aikiframework.org/wiki/Apps
>> >>
>> >> I agree with Jakub, image_viewer.php needs this:
>> >>
>> >> 1.) move image_viewer.php to image_viewer/image_viewer.php
>> >
>> > image_viewer.php should be in extensions folder and can be in Aiki
>> > by default. And image viewer should accessed from widget. like other
>> > stuff, there should not be exceptions like this in Aiki.
>>
>> The reason that files should be in folders is for version control. Its
>> easier to use git submodule or svn:externals when files are in
>> folders, and it keeps things tidy is the point. This is necessary for
>> assets to live in real production environments. Make sense?
>>
>> I was thinking about moving the assets to /sites/default/assets so we
>> could have /sites/somesite.com/assets, but think this puts too much
>> complexity in for now, and users can define this. However, we should
>> keep aiki as a good citizen in its assets department. The
>> /assets/images/*.* that ship with aiki should also be in a folder so
>> they aren't overwritten by local installations, and yes, this also has
>> impact if using bazaar and/or git to control revisions on a site. Make
>> sense?
>>
>> >
>> > There should be not bare php files in Aiki except
>> > update/install/aiki tools. Aiki sites and user may use them if they
>> > want but Aiki should be clean.
>>
>> But, aren't you saying update/install/aikitools are exceptions? Where
>> should they live then?
>
> I mean that they can be /assets/ folder but everything that can be
> called from Aiki should be in Aiki.
>
> Take GNU Emacs for example everything is written in Emacs Lisp but there
> are exceptions that are written in C because they can't be put in
> elisp.
>
>>
>> >
>> > Maybe instead of Apps we should have generic packages so extension
>> > could be installed like apps from Admin Panel and remove as well. Or
>> > extension will be an app, but simply with one file in it (in most
>> > cases).
>>
>> Sure, I think we should look at the html5 packaging of chrome and
>> mozilla to see how we can be compatible honestly. Longer term, I want
>> to see aiki become more self-contained. With the cool html5 features,
>> we could actually make aiki its own html5 package! But, that will
>> require a lot of work, but is my devious plan for aiki ;)
>
> If Aiki itself will be a package that package manager could not be in
> Aiki because, Aiki will bring files that will need to be put into
> aiki_apps_files table before database is created.
>
> And other thing that aiki_apps should store tables names in database
> itself, so when app bring new table it could be removed when along with
> app but there should be two function like in apt-get - remove/purge -
> purge will remove database table along with all the data that was
> created by an app, but interface should not expose this two functions
> only ask if user want to remove all data that was created by an app and
> with big warring message that he/she will lose all the data.
>
> So database for app will be
>
> aiki_apps 1-------N aiki_widgets
>   1   1
>   |    \
>   |     +---------N aiki_apps_tables
>   N
> aiki_app_files
>
>
>>
>> <snip />
>>
>> Jon
>>
>
> --
> Jakub Jankiewicz
> twitter: @jcubic
> www: http://jcubic.pl



-- 
Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon
+1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing)

_______________________________________________
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