From: Jason C. <cam...@xp...> - 2001-03-26 15:08:36
|
I'm working on the new block code but if we're changing the theme system, which I and others things we should, I don't want to commit stuff to CVS that will need to be recoded for the new theme system. I think we need to get on IRC and have a developers meeting soon to decide what we want to get done with the project before anything else gets added to the core code base. We as the developers need to decide what we want to do with the database first and then work from there. I've heard talk about changing the structure of the tables and what not, if thats going to happen and be in the core code I say we have a meeting SOON and decide on it and get that done first, when thats completed we can add/modify other parts of the system around the new model and maybe get a modular system started. I don't want to write or commit code that will need to be rewritten if the whole system changes. Anyone else feel this way? Jason Campbell Xplozive Media Technologies www.xplozivemedia.com phpWebSite Developer > On Sun, Mar 25, 2001 at 03:30:41PM -0500, Todd Owen wrote: > >> Jason, you're right about the .xlay files. I was looking at their >> .tmpl files, which are html. > > HTML templates seem to be the best solution right now. I wrote an email > to jason Campbell (and forwarded it to Brian later), but dind't get any > response until now. I will elaborate on my ideas in details later. But > again: HTML templates (combined with (PEAR:)Cache) are the way to go, > IMHO. > > The use of XML to to the basic placement of blocks might make sense. > But someone is working on arbritrary block positioning right now, > right? So lets see what the results are, before jumping on the XML > wagon just because it is cool. > > Regards, > Karsten > -- > Why do we have to hide from the police, daddy? > Because we use emacs, son. They use vi. > ----------------------------- > mailto:k.d...@tu... w³: http://www.k-fish.de/ > gpg: http://www.k-fish.de/mykeys.gpg |