Ok, changed mind after I about committed a separate path. So, I like how wordpress has a path for configurable things in wp-content. So, if we just move our current things we need on aiki to a subfolder like /assets/images/aiki and /assets/apps/aiki then we are covered.
Also, this will allow for versioning systems to manage these folders in different VCS like SVN, git, etc... Ok, I just committing the first changes, test on the packaging, etc....will do javascript last to make sure it works. We need some way to check the version of the aiki instance, and if not current version, have a block of code that runs updates... I like the way CCHOST did this by having some update_0_7_4() function which would compare the last version of aiki, with current and run any update functions during update... With this type of change, perfect instance where some paths change and could break some installations...bassel, how can we handle that? do you have a plan for this or is there a way? -- 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 : aikiframework.admins@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
