Tarjei Huse wrote: > > The css tag is not special, but yes, correct. > > One question here, is it better to refer to a .css file than adding the > whole css setup to a pageelement and downloading it with each document? > Just curious.
That depends on how widely dispersed your development team is, I guess. Since I'm a lone developer (and a long way from hoooooome[0]) I generally use files for library-type stuff. Unless you can use CVS, putting stuff in snippets is going to be easier if you are developing with a group & changes are somewhat frequent. > > Midgard currently doesn't have read access controls (which is going to > > be addressed as sooen as the scripting backend stabilizes), but > > group-based read controls are easily implemented by active checking (in > > Hmm. just a small request: before you start with the scriping backend, how > about tagging a 1.4.2 release and saying that the scriping will come in > 1.5? To have something stable for a while would be a Good Thing. :) No issues on that, but since all development for the scripting backend happens in separate directories, they'll not cross over anyway. There will be a new (from scratch) php4 extension, and the scripting stuff (in the 'scriptor' directory doesn't touch mod_midgard and midgard-lib. The scripting layer will rely on midgard-lib features for a while but will gradually start replacing them with scripted equivalents until midgard-lib can be phased out for that effort; as soon as the scripting layer is featureful enough, mod_midgard will gradually start using its features until that too doesn't rely on midgard-lib anymore, at which point it will be obsolete. mod_midgard-scripting will be a different branch, like mod_midgard-preparser is now. As for a time line for all of this, Alexander has indicated that the scripting layer, plus some examples, should be available somewhere this week or early next week, and the php4 extension should see early alpha just before xmas. No timeline yet for mod_midgard-scripting; we want to gain some experience with the scripting layer before we start redesigning mod_midgard. > > You can still use file-based images if you want to (my site does, but > > it's addmittedly a very simple site). The Midgard-native way of doing > > images is through attachments. Page-bound attachments are served > > automatically, for others (images bound to articles, for example) > > you'll need to implement a little script to serve them out. NAdmin > > includes such a script. > > Please note that static subdirs and images will not work if you have an > active root page. Unless you use the static page trick, or mmp with MidgardFavorFiles set to On. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
