From: Frits J. <FJ...@uv...> - 2001-03-29 18:54:01
|
Sorry if I seemed offensive in my previous posting, and sorry to = everyone, if this gets to narrow for a mailinglist :) > -----Oprindelig meddelelse----- > Fra: Alain Fontaine [mailto:al...@va...] > Sendt: 29. marts 2001 20:39 > Til: php...@li... > Emne: RE: [Phpwebsite-developers] Template system (Smarty) >=20 >=20 > Hi there, >=20 > > -----Message d'origine----- > > De : php...@li... > >=20 > [mailto:php...@li...]De=20 > la part de > > Frits Jensen > > Envoy=E9 : jeudi 29 mars 2001 20:12 > > =C0 : 'php...@li...' > > Objet : SV: [Phpwebsite-developers] Template system (Smarty) > > > [cut] >=20 > [quote] > Totally agree! "This tarball works. U want more? Code!" > [/quote] >=20 > Okay, if we follow this direction, and that is what the main=20 > part of your > mail expresses, we will just hand out a text editor, the PHP=20 > source, the > mySQL source and a Linux distribution to the guy and say: This is > phpWebSite. Want more? Code!. Sorry - u couldnt get me more wrong. My concern was to make a finished product that came with upgrades, opposed to beta on beta with potential = for expansion. This would mean somewhat limited versions, but versions = where the user did not have to code. _Only_ if this wasn't enough for the user, = my staement was; Code! I want a complete and working system that can be = build on, not an ongoing beta - that's what I was trying to express. > Or even better, send them an E-mail with the URL's to php and=20 > mysql, and > tell them that this is all they need to have their portal=20 > site :). I agree > that this is ridiculus, but where I want get to is this: >=20 > It's all about finding the "right middle-way". >=20 > As far as I know, our target audience are people who don't really = feel > comfortable fiddling around in style sheets, HTML, let alone=20 > PHP code. I > guess, unless I am really mistaken, that we want phpWebSite=20 > to be a Portal > Application in the "Windows" sense, e.g. "point&click, setup.exe, > click-click" and there you have your own customized portal site. >=20 > In that sense, I definitely feel that a "theme editor" would be very > welcome. Don't forget that there will be many phpWebSite=20 > users that don't > even know HTML. Actually, the guy I am currently setting up=20 > phpWebSite for > is one of them. >=20 > Anyway, even if we don't include an editor, going the=20 > "templatized themes > definition" direction will probably prove to be much less of=20 > a hassle to > manage. Which of the following is better: >=20 > * 10 themes equals 10 directories, each having 15 files > or: > * 10 themes equals ONE directory, having 15 slightly more=20 > complex files >=20 Karsten just expressed MHO :) > The first possibility means 150 entities to manage, the=20 > second means 15 > entities. It's clear that both from a developer's point of=20 > view, AND from > the user's point of view, the second possibility is the way=20 > to go. In any > way, we will end up with an "easier to manage" factor equalling > approximately the number of themes. The more themes we have,=20 > the more the > second solution will become easier to manage/update. >=20 > I can somehow understand the points you make about including the = theme > editor (although I don't agree with all of them). However, I=20 > cannot agree > with you on the fact that it would be better to have the "10=20 > themes =3D=3D 10 > directories" structure. That is not dynamic, not manageable, and not > challenging. The last point is something we shouldn't forget:=20 > Most of us are > doing this because it is fun, and because we want to learn.=20 > If it weren't > for that, we could simply start creating static portal sites=20 > and keep our > lives busy updating them using Frontpage 2000. >=20 > No offense taken, and these are just my personal views on the=20 > matter :) >=20 > Alain :) >=20 >=20 >=20 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >=20 |