[Sputnik-list] blueprint

[pierre pracht]

Le 14 févr. 08 à 20:19, Yuri Takhteyev a écrit :

> 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

Not found

> 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).

You must explain a bit your work flow.
I have made a new install
  - with luarocks for : luafilesystem, lualogging, wsapi ....
  - and a checkout of svn trunk as sputnik-trunk

So I have :
   /rocks
   /sputnik-svn/rocks

In my mind, It was clear that I can tell luarocks to look at both :
>> repositories = {
>>    "http://luarocks.luaforge.net/rocks",
>> --   "http://sputnik.freewisdom.org/rocks",
>>    "http://www.lua.inf.puc-rio.br/~mascarenhas/rocks",
>>    "/opt/sputnik2/sputnik-svn/rocks"
>> }
Nope...
I have take e few hours at searching...
ending attrying to  look in luarocks code ...

In-fine, I take an other way, making symbolic link.
It work, but  :
cd /opt/sputnik2/share/lua/5.1
ln -s  ln -s ../../../sputnik-svn/rocks/*/lua/* .

As you say over, serval rocks have a sputink dir
So I think that isn't the way to go.

> 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")

Explain !
Luarocks would handle the (base) path ? See above.

> 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.

Good

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

I would, but I need my new setup to work !
With "Sputnik on the Rocks" I wasn't able to use CGI

...wsapi/common.lua:177: bad argument #1 to 'match' (string expected,  
got nil)
stack traceback:
[C]: in function 'match'
...wsapi/common.lua:177: in function 'splitext'
...wsapi/common.lua:192: in function <...wsapi/common.lua:182>
(tail call): ?
...bin/wsapi.cgi:16: in function
(tail call): ?
[C]: in function 'xpcall'
...wsapi/common.lua:135: in function 'run_app'
...wsapi/common.lua:159: in function 'run'
...wsapi/cgi.lua:16: in function 'run'
...bin/wsapi.cgi:24: in main chunk
[C]: ?

May be an explanation :
I haven't : bin/wsapi
I have : bin/wsapi.cgi

Did I get the good version of wsapi ?
#  bin/luarocks list
wsapi
    cvs-1 (installed) - /opt/sputnik2/rocks/

In my previous install I take the xavante way.
But If I make some module, I need to use CGI. (installed thttpd)

> 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.

I need first to put it in good shape (1 week min)
Actual code is a mess, juste a proto to show that it would work.
But to work proprely I need to make a new setup with SCM and CGI.

> 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.

Yes this email.
If needed  in the mean time I can keep change in a git copy.

> 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.

I will, but maybe I will make a custom form for common parameters  
before.

- pierre