SV: [Phpwebsite-developers] Template system (Smarty)

[Frits J. <FJ...@uv...>]

Karsten (and onyone with interest);

> -----Oprindelig meddelelse-----
> Fra: Karsten Dambekalns [mailto:k.d...@fi...]
> Sendt: 29. marts 2001 20:39
> Til: php...@li...
> Emne: Re: [Phpwebsite-developers] Template system (Smarty)
> 
> 
> On Thu, Mar 29, 2001 at 08:11:52PM +0200, Frits Jensen wrote:
> 
> > I totally disagree, as having your themes this way would 
> make using good
> > third-party tools for editing CSS very complex, and the 
> whole structure more
> > complex from a designers point of view. One directory 
> containing one theme
> > makes sense for the user, increases ease of use, and is 
> open for the future
> > expansions. Pardon my tone =)
> 
> You are making a point here. Third-Party CSS editors would 
> get disturbed by
> placeholders in the CSS tenplate file. Hmmm....

I admit I do not code, but it just seems straight ahead for me to have
"real" CSS in its own file, and then whatever extra files a theme
unfortunetely have to have along in the same directory - messy, perhaps, but
sloppy, I should say no, as this is just playing by the given realities of
different systems interacting, and being prepered for whatever comes at the
same time.

> 
> > CSS'ing more versatile. Also there should be a referrer to 
> print and aural
> > versus monitor in the coding - I would like my pages to 
> print nicely. A
> > theme should consist of at least both one for monitor, and 
> one for print, to
> > be a complete theme.
> 
> That got my attention: Is there _any_ browser available, that _really_
> supports _any_ of the possibilities to format for printing? 
> Last time I
> looked at that issue, I was all too disappointed!
> 
> Or are you referring to this with a look in the future?

I suppose IE 5.5/Win is 100% print/monitor, but in general, I should think
one exciting thing of this project is 'doing it right' - so if for nothing
else, just for the sake - its only one line pr CSS-call, and does the
printing-CSS not exist, well no harm done, it'll get ignored, or
alternative, one could place an empty CSS for printing if one could not
bother.

> 
> But of course you are right. Maybe we should just do it 
> anyway, and see the
> browser makers implement it, just to satisfy the gazillion phpWebSite
> users... :-)

Jep =)

> 
> > There should be a certain logic to the tagging, so that we 
> do not end up
> > using 5 trillion individually named tags, one for each 
> plugin, option and
> > 'little thing i just coded'. Limit is the keyword. Without 
> having thought it
> > all the way through, I would say that it would be plenty 
> with 5 areas of
> > tagging. It could be something like:
> > 
> > leftbox.h1 =...
> > rightbox.h1 =...
> > article.h1 =...
> > special_big.h1 =...
> > special_small.h1 =...
> > top_bar.h1 =...
> > [...]
> > and so on...
> 
> Ok, I got that... Though you probably mean leftbox.h1 {...}
> 
> > leftbox_menu_padding.left =...
> > leftbox_menu_padding.right =...
> > leftbox_menu_padding.bottom =...
> > leftbox_menu_padding.top =...
> > leftbox_menu_padding.left =...
> > 
> > rightbox_menu_padding.left =...
> > rightbox_menu_padding.right =...
> > 
> > and so on...
> 
> What are those for? Or do you mean leftbox_menu { padding-left: ...
> padding-right:... } ?!?

lol - I was dumb enough to try and describe the mathematics, using imaginary
syntax.. Sorry, I can see it makes no sense. Perhaps this will: (no syntax
now, just describing how many 'tags' needed)

We have 5 areas:

leftbox
rightbox
main
special_big
special_small

Theese will each need all the usual stuff as 'h1 font size' for each 5, 'h2
font size' for each 5 and so on.

Second, I was trying to describe how some need padding, border, etc for all
four sides (Not just h1, but left padding, right padding, etc), marked
individually, and so on.

The main thing in my nonsense was that all there is to work with is one of
those 5 'subsets'; When coding, you could chose if your object belonged to
leftbox, rightbox, main, special_big, or special_small, and within this you
then could choose say 'h1'. I cannot remember the syntax but I will create a
complete set if u agree and understand..

When creating the CSS, u could then have individual looks for each of the 5
subsets. Typically all would be more or less the same, but as I tried to
explain; the system would be closed standard hereafter, but any needed
versatility would not be lost.

One extra subset for the top-bar would be needed.

> 
> > If I make any sense to anyone, I would take on the task of 
> creating a
> > _complete_ set of such names, so that that part of the 
> project was finito
> > and done with. 
> 
> Go ahead! Write something up and submit it to the list for 
> discussion. Any
> help is good help :-)

Thanks for the backup - I'll get to it - Only I am kinda new to all this
hacking, so please confirm that I am on solid ground here - I make the above
rules in a CSS where all is just black & white & Arial, and submit it on
this channel? Have u understood what I am trying to do, and would it be of
any use?

Thanks,
Frits

> 
> Regards,
> Karsten
> -- 
> fishfarm - Karsten Dambekalns
> Echternstr. 73 - 38100 Braunschweig
> 
> Tel. +49 531 1232902  mailto:k.d...@fi...
> Fax. +49 531 1232906  http://www.fishfarm.de/
> -----------------------------------------------------
>