[Sputnik-list] blueprint

[Yuri Takhteyev]

Great, I'll test this in the evening.  For now here are a few suggestions:

1. There is a script in my svn repository that you can use to package
rocks: scripts/make_a_rock.sh  Also, I would create your own
repository, which is really a web directory with rocks and a simple
"manifest" file (see http://sputnik.freewisdom.org/rocks/manifest).
At some points all rocks should be featured in the main repository,
but for experimental versions I think it really helps to have your own
directory.

2. I would make this into two rocks: "blueprintcss" (everything not
sputnik-specific) and "sputnik-blueprint".  Note that
sputnik-blueprint should reproduce sputnik's folder hiearchy:

sputnik-blueprint/lua/sputnik/actions/blueprint_css.lua
sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_templates.lua
sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_css_screen.lua
sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_css_layout.lua

This way those files will be available as if they were a part of
"sputnik" package: require("sputnik.actions.blueprint_css")

For now, let's keep this as a "plugin" that could be added on top of
"standard" sputnik: I promised people that the current version would
be feature-frozen until it's tested, documented and properly released.
 I want to at least _try_ to keep this promise. :)  For the next
iteration we can think if some of it would better be integrated into
the core.  This means that let's assume for now that the plugin will
add files and nodes rather than override existing ones.  E.g., instead
of replacing _templates, let's add _blueprint_templates and tell the
user to set DEFAULT_TEMPLATE_SET in _config.

If small changes are necessary for the current sputnik, I'll make
them, but please send them as a patch against SVN if possible.

3. You should email the Kepler list about the generic blueprint
library.   I think it's an interesting idea and it's may be useful for
Lua-based web stuff beyond Sputnik.  And we might get good
suggestions.

4. If you have a google account, I can add you to the sputnik-wiki
project (http://code.google.com/p/sputnik-wiki/) so that you could
check the files into SVN.

5. Any hope for documentation?  One possibility would be to start a
page at http://sputnik.freewisdom.org/en/BlueprintCSS.  Don't worry
about English grammar - we'll fix it up later.

- yuri

On Thu, Feb 14, 2008 at 8:04 AM, pierre pracht <pierre.pracht at gmail.com> wrote:
>
>
> Le 14 févr. 08 à 09:57, Yuri Takhteyev a écrit :
>
> I can see where this is going, but for some reason I am getting an
> error when I replace by _templates with your version.  I got rid of
> the error by getting rid of NAV_BAR,
>
> My bad, I have change get_nav_bar action in wiki.lua
> Sorry for the mess, I just packed them in hurry to illustrate my answer.
> I would take a look at the way you pack rocks.
> And takes file from svn as base install, so I can easily build patch.
> Is there some particular recommendation on :
>   svn / rocks / sputnik / sputnik-xxx ?
> I really need to get It right, actually I was trying to integrate :
> http://dnevnikeklektika.com/uni-form/
> (Rq: a choice for JavaScript library ?)
>
> I would finish blueprint later as without form handling, It isn't very
> useful.
>
> but the the layout doesn't quite look right.
>
>
> Rq : It miss the IE style Sheet, be care if you use it.
>
>  Next time can you attach a screen shot so that I know
> what I should expect to see?
>
> Done, but there is nothing new.
> Interesting parts are in _blueprint_screen :
>  - You can change site and column size of grid
>  - You set a base typography with a corect handling of line spacing
>  - You can change typography of base element :  h1={ 3 },
>  - Or of your own style ["#menu, #submenu"]={ 1.5   ,2 },
>    - It's a very strong point of blueprint,
>      this code give you easy customization of it. (btw need to be finished)
>  - Semantic class : let you use blue print class
>     without putting them in your template.
>
> All of this could be completed with class dedicated to color (_color)
> Have you a naming scheme for it ? :
>   tonic dominant secondary shade ...
>   ex : ["#menu"] = { ".tonic", ".bg_dominate_shade_5" },
>
> In the end we could imagine a dedicated form to help user in those
> customization.
>
> Also installation instructions...  BTW, if you want to see how I
> handle page defaults, look for the modules inside
> sputnik.node_defaults.  If you adjust your _blueprint_screen.lua and
> _blueprint_layout.lua this way, you can just tell people to copy those
> files to sputnik/node_defaults and the pages will appear when
> requested.  (the same will work for _templates, but only if the users
> deletes wiki-data/_templates
>
> Good !
> In a way, it answer to my question on staked storage.
> At first I have think that all file were copied at first run.
> I missed corresponding lines in versium/smart/repository.
> As excuse I would say I only start to grasp how sputnik work.
>
> PS : I would answer to the other mail later, it would take some time to put
> it in a mindful shape.
> Your right "we are on the same page". I missed some point on versium /
> versium.smart
>
> - pierre
>
> Screenshot :
>
>
>
> A tar.gz of blueprint (to unpack in rocks directory) :
>
>
> A modified version of css.lua who add blueprint_css action :
>
>
> A modified version of wiki.lua who add if_notlast helper at get_nav_bar
> action :
>
>
> A modified version of _templates, this one need to bee put in node_defaults,
> wiki-data/_templates need to bee removed :
>
>
> A css template who use blueprint rock module :
>
>
> A css template who custom rules (not blueprint) :
>
>
> Two previous need :
>   - to be drop in node_defaults
>   - to be seen by seen by rocks/manifest
>
> , ['sputnik.node_defaults._blueprint_layout']={'sputnik/8.01.01-0'}
> , ['sputnik.node_defaults._blueprint_screen']={'sputnik/8.01.01-0'}
>   - to be referenced in _config
>
>
> STYLESHEETS = {
>   NICE_URL.."_blueprint_screen.css",
>   NICE_URL.."_blueprint_layout.css",
> }
>
>
>

-- 
http://sputnik.freewisdom.org/