[lively-kernel] Code reorganization in Webwerkstatt - please check your js files
Marko.Roeder at student.hpi.uni-potsdam.de
Fri Oct 28 15:54:03 CEST 2011
Hi, all -
To be honest, I liked it the way it was before all of the changes ;-). It seems like we changed a lot in the last couple of days and some of those decisions appear to me as if they only had to be done because previous changes introduced new challenges and problems :-/.
I absolutely agree with Robert's statement, the (old) bootstap.js did/does a good job for loading modules and initializing the kernel. I therefor strongly opt for keeping the bootstap.js the only file that has to be included in the head of a world/xhtml-file and maybe following Keith idea of extracting the files to be load (to the head of the file or somewhere else).
Furthermore I had a problem with moving the "kernel" to kernel/core/CodeBase/... from the beginning because I could see that what the "codebase"/root was before (e.g. .../webwerkstatt/) does not include all the additional folders referencing modules, etc. (e.g. users, projects, ...).
I do not think that it is hard to extract the core files (for a release, a clean installation, a new project, ...) and we have done that preparing release zips, dumps, etc. So why not keep all those files in the (tree) structure we have had so far?
In addition to that I do not (yet) see what all the openness to several VCS will bring for the project, in other words: Why does LK suddenly have to not only "run" with SVN but with GIT, Bazar, and so on? Still the decision to use SVN was not only about the version control system to use but a deep technical decision that influenced a lot of the LK architecture. And to be honest, do you know one (or more) projects that do have/maintain/use more than one VCS?
So, these are my thoughts and I know, we are all working towards a good and practical way to do releases and how we can sync different branches/projects/installations that are based on Lively's "kernel". But maybe we should step back for a moment and look at what we have and what might be a reasonable, small step (or two, or three, ...) to reach this goal!
As always, questions, opinions and feedback are more than welcome...
More information about the lively-kernel