Or maybe, move all system assets to /core and keep custom ones in /assets shorter the better....bassel?
Jon On Fri, Dec 24, 2010 at 1:19 PM, chovynz <[email protected]> wrote: > /core > /custom > ? > > On Fri, Dec 24, 2010 at 6:29 PM, rejon <[email protected]> wrote: > >> Public bug reported: >> >> We need to decide on a file structure that is indepedent of site- >> specific assets like assets/extensions and other ones like assets/images >> which currently has default images in it. >> >> Also, there is custom javascript in the /assets/javascript folder. >> >> I think we should make a decision. >> >> Possibly, /assets is the place for default assets: >> >> /assets >> /apps >> /images >> /extensions >> /javascript >> /uploads >> >> Then need something like: >> >> /custom >> /apps >> /images >> /extensions >> /javascript >> /uploads >> >> And keep those completely empty on an installation. We should even keep >> these except for a README in each, and then remove /assets/uploads from >> the current trunk of aiki. >> >> Any other suggestions? The more I've been working with aiki, realize >> that its weird. >> >> The other thought is we could put something like: >> >> /assets >> /apps/default >> /images/default >> /extensions/default >> /javascript/default >> /uploads/default >> >> For the current default aiki assets for these folders. >> >> Thoughts? I think we should move on this sooner rather than later, >> noticing that several installations have a mix of core and custom >> assets. It just makes keeping the core VS custom distinction harder to >> make real...let's keep it real :) >> >> ** Affects: aikiframework >> Importance: High >> Assignee: rejon (rejon) >> Status: Confirmed >> >> -- >> You received this bug notification because you are a member of Aiki >> Framework Developers, which is subscribed to aikiframework. >> https://bugs.launchpad.net/bugs/694026 >> >> Title: >> assets contains user files and core files >> > > > -- > Cheers > Chovynz > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/694026 > > Title: > assets contains user files and core files > -- Jon Phillips http://rejon.org/ http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (sf/global) +86.187.1003.9974 (china) +65.8330.5807 (singapore) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/694026 Title: assets contains user files and core files Status in Aiki Framework: Confirmed Bug description: We need to decide on a file structure that is indepedent of site-specific assets like assets/extensions and other ones like assets/images which currently has default images in it. Also, there is custom javascript in the /assets/javascript folder. I think we should make a decision. Possibly, /assets is the place for default assets: /assets /apps /images /extensions /javascript /uploads Then need something like: /custom /apps /images /extensions /javascript /uploads And keep those completely empty on an installation. We should even keep these except for a README in each, and then remove /assets/uploads from the current trunk of aiki. Any other suggestions? The more I've been working with aiki, realize that its weird. The other thought is we could put something like: /assets /apps/default /images/default /extensions/default /javascript/default /uploads/default For the current default aiki assets for these folders. Thoughts? I think we should move on this sooner rather than later, noticing that several installations have a mix of core and custom assets. It just makes keeping the core VS custom distinction harder to make real...let's keep it real :) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
