23 Apr
2007
23 Apr
'07
5:20 a.m.
I use it in my widgets, and if it was gone I would have to make a new page
for every widget to put the div tag back in. But if it was optional (e.g.
#style in seaside) I wouldn't care, or you could even get rid of it in the
base class and add a new derived class that has it and I will switch my
classes to inherit there. Actually I guess I could add the base class to my
own image if you just want to get rid of it.
From: Lukas Renggli <renggli(a)iam.unibe.ch>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: Magritte Mailing List <smallwiki(a)iam.unibe.ch>
Subject: Inquiry: Widgets
Date: Sun, 22 Apr 2007 21:35:20 +0200
Hi,
I would like to ask a question to the Pier users before doing a
change to the Pier widgets: Currently every widget has its own
hardcoded <div class="[custom_classes]" id="[custom_id]">
around
itself and it also emits a <h1>. I am currently building some new
sites and these <div> and <h1> tags rather hurt than help.
I wonder if we shouldn't get rid of those <div> and <h1> altogether?
I guess this is sort of a relict from SmallWiki where there were no
environments. Nowadays designers can add <div> (or other tags) around
a widget within the environment if necessary. There is no need to
write Smalltalk for that anymore.
Does that make sense?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Get a FREE Web site, company branded e-mail and more from Microsoft Office
Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/