[Sputnik-list] blueprint
pierre pracht
pierre.pracht at gmail.com
Wed Feb 13 13:45:17 GMT+2 2008
Le 12 févr. 08 à 11:35, Yuri Takhteyev a écrit :
>> - Name custom part with id and recurrent use with class :
>> <div id="extra-content" class="last span-6 column">
>> - Let Blueprint/Sputnik build aggregate rule :
>> SEMANTIC_CLASS = [["#extra-content"="last span-6
>> column", ... ]]
>> <div id="extra-content">
>
> Not sure what you mean here.
See in attachment, I have in order :
- set class="span-6 colum" to put it in place
- add id="search" to attach some custom property in css
- strip of class="span-6 colum" by building them in SEMANTIC_CLASS
>> A module can be a good fit as you say it could be used in other
>> context.
>>
>> I would completing it :
>> - Custom font-size and vertical rhythm (test done see attachment)
>> - Color font border ... option
>> - Semantic class aggregation
>> - Simple concatenation first
>> - Property parsing and masking later
>
> Sounds good.
A prototype is done.
But I use Xavante with WSAPI. I need to relaunch it to see change. Is
there a development node ? I stuck in trying to use it with CGI.
>> It leads to a question (independent of extraction in a module)
>> How separate template from its own options ? (not site wide)
>
> What do you mean?
If a template use some parameters, user will first tweak parameters.
Ideally they need a custom form.
Currently, you get both in same field.
See other mail for reflexion on local meta-data.
>> Don't bother with semantic class nobody see (use) them.
>
> I understand the argument when designing a particular site. But it's
> a little different when making a wiki engine. Yes, people will see
> the classes and IDs - the downstream developers. My fear is that a
> new user will install it, look at the template, and say "what the hell
> is this?" On the other hand, <div id="logo"> is self-documenting.
I agree, with semantic class you get both :
>> <div id="logo">
>> SEMANTIC_CLASS = { ["#logo"] = {".span-4", ".column"}, }
But if the downstream developers want to change site layout, it need
to dive into configuration to find SEMANTIC_CLASS parameter.
First, when I have finish semantic class functionality, I was
thinking : What a heck, not very use-full.
Rapidly I saw were it pay of : You get all your layout parameter in
one place.
See above for reflexion on use of a custom form.
User will in order :
- Change common option : color, font, size, image ...
- And later dive into template
PS: I didn't understand how luarocks must be packaged
You would see in attachment :
a tar.gz of blueprint module :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blueprintcss.tar.gz
Type: application/x-gzip
Size: 4160 bytes
Desc: not available
Url : http://lists.luaforge.net/pipermail/sputnik-list/attachments/20080213/82095f1a/blueprintcss.tar.bin
-------------- next part --------------
a modified version of css.lua who add blueprint_css action :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: css.lua
Type: application/octet-stream
Size: 1074 bytes
Desc: not available
Url : http://lists.luaforge.net/pipermail/sputnik-list/attachments/20080213/82095f1a/css.obj
-------------- next part --------------
a css template who use it :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _blueprint_screen.lua
Type: application/octet-stream
Size: 1309 bytes
Desc: not available
Url : http://lists.luaforge.net/pipermail/sputnik-list/attachments/20080213/82095f1a/_blueprint_screen.obj
-------------- next part --------------
a other style sheet and an HTML template for test :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _blueprint_layout.lua
Type: application/octet-stream
Size: 1327 bytes
Desc: not available
Url : http://lists.luaforge.net/pipermail/sputnik-list/attachments/20080213/82095f1a/_blueprint_layout.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _templates.lua
Type: application/octet-stream
Size: 13770 bytes
Desc: not available
Url : http://lists.luaforge.net/pipermail/sputnik-list/attachments/20080213/82095f1a/_templates.obj
-------------- next part --------------
More information about the Sputnik-list
mailing list