From arne at arnebrasseur.net  Sun Jul  1 06:26:12 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Sun, 01 Jul 2007 12:26:12 +0200
Subject: [Nitro] Daily tarball
Message-ID: <46878144.9040305@arnebrasseur.net>

I went ahead and set up daily tarball creation.

More info at:

http://www.arnebrasseur.net/2007/07/01/the-daily-nitro/en/

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From john at oxyliquit.de  Sun Jul  1 10:50:10 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 01 Jul 2007 17:50:10 +0300
Subject: [Nitro] Daily tarball
In-Reply-To: <46878144.9040305@arnebrasseur.net>
References: <46878144.9040305@arnebrasseur.net>
Message-ID: <op.tusjhwjwxegpx6@jo.local>

Hi,

> I went ahead and set up daily tarball creation.

interesting idea.  :)

Jo


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From Jimmy.Jazz at gmx.net  Tue Jul  3 11:47:20 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Tue, 03 Jul 2007 17:47:20 +0200
Subject: [Nitro] nitro 0.50: first encounter
Message-ID: <468A6F88.5090107@gmx.net>

Hello list,

I'm trying nitro 0.50 and it is working great. I didn't have the problem
i described in a precedent post anymore. The source is even more
readable and the syntax and the organization of nitro internals are more
powerful than ever. In other words, i have try it and i'm convinced :)

Also, i have found out some "minor" strangeness. I'm not quite used to
work with nitro so I hope they are only false positives or simply (and
that is what I think) i'm not in the pink ;)

If I'm in the wrong mailing list to expose my issues and to ask for
help, just let me know where i have to post them and please, sorry for
the noise.

1. Collisions

For instance, if I name a class Menubar with a lowercase 'b' in the
skin.rb file and its associated render method contains a <div
class="menubar">, the template <Menubar></Menubar> won't render anymore
until the class name is renamed MenuBar with a uppercase 'B'. Also, the
page will be always well rendered if <div class="menubar"> is declared
inside the htmlx template file.

To illustrate the issue:

-declare a class Menubar or MenuBar in your skin.rb file: (of course,
the word menubar was used like an example)

class Menu(Bb)ar < Raw::Element
  def render
    %{   
      <div class="menubar">
        #{content}
      </div>
      <hr />
    }
  end
end

-render the Menubar/MenuBar in the template like that,

<Page>
  <MenuBar>
    <render href="menubar" />
  </MenuBar>
</Page>

The above will work, the following not:

<Page>
  <Menubar>
    <render href="menubar" />
  </Menubar>
</Page>

Otherwise, if the style definition <div class="..."> is instead declared
in menubar.htmlx  and not in the class itself:

<div class="menubar">
<ul>
    <li class="browse_category">Choisissez une Cat?gorie:</li>
       
    <?r @labels.each do |label| ?>
        <?r if menuitem_active_on?(label.to_href) ?>
        <li class="active" id="current" title="Cette page">#{label}</li>
      <?r else ?>
        <li><a href="#{label.to_href}" accesskey="#{label.access_key}"
title="#{label.hint}">#{label}</a></li>
      <?r end ?>
  <?r end ?>
</ul>
</div>
<hr />

the page is then rendered correctly, whatever upper or lowercase 'b' you
will use in the class name.

2. Question: how does #{content :method} really work ?

That is the kind of stupid question i have but i really didn't get it to
work and didn't understand how it interacts with templates. Perhaps,
some better incantations could help me :)

3. Annotation and elements

I have tried to use an annotation to link a controller to an element. In
fact, :element_namespace gives me something related to
SomeClass::Controller:yy instead of Raw::Element::yy

Also, i certainly misunderstood the annotation stuff ;)

An example to illustrate the behavior:

class Blog::Controller

  ann :self, :element_namespace => Post

doesn't return an error and is linked to Blog::Controller::Post. I think
that is wrong ( it should be Raw::Element::Post)

In opposite,

ann :self, :element_namespace => BlogPage

returns an exception,

DEBUG: File './app/controller/blog.rb' is modified
 INFO: #<NameError: uninitialized constant Blog::Controller::BlogPage>

(The class BlogPage is declared in the app/skin/blogPage.rb file and
belongs to the Raw::Element superclass, so ann should link the class
Blog to Raw::Element::BlogPage instead)

4. Just to mention it

You need to press Ctrl-C twice to stop webrick

 INFO: Stoping Webrick adapter.
 INFO: Og uses the Mysql store.
Database "aSite" dropped
 INFO: Dropped database 'aSite'
 INFO: Database 'aSite' not found!
 INFO: Created database 'aSite'
DEBUG: Og manageable classes: []
DEBUG: SELECT * FROM ogcategory
ERROR: DB error Table 'aSite.ogcategory' doesn't exist, [SELECT * FROM
ogcategory]
ERROR:
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
`query'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
`query_statement'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:554:in
`query'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:367:in
`find'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:316:in
`all'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/manager.rb:118:in
`with_store'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:315:in
`all'
./conf/debug.rb:37:in `init_og'
./conf/debug.rb:22:in `setup_og'
./conf/debug.rb:31:in `setup'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:152:in
`read_configuration_file'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:180:in
`configure'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:97:in
`start'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro.rb:73:in
`start'
app.rb:31
 INFO: Starting Webrick adapter on 0.0.0.0:9000
 INFO: Press Ctrl-C to shutdown; Run with --help for options.
 INFO: Stoping Webrick adapter.


5. That is a bit Greek (Chinese?) to me

Some messages are really hard to understand and to debug and make the
source look fragile. That can be very frustrating especially if the
method are part of ruby language (e.g. each).

DEBUG: Rendering '/blog/post'
DEBUG: Compiling 'post' super-method
DEBUG: Compiling 'post' view sub-method [format: html]
--------
undefined method `each' for nil:NilClass
  (eval):3:in `post___html___view'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in
`send'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in
`method_missing'

6. Helper required

When i need an helper for a class,

include MenuHelper

i have to declare explicitly the pathname for the helper in the file
were include is called,

require "#{File.dirname(__FILE__)}/../helper/menu"

Also, isn't app/helper the default directory for the helpers ?

7. miscellaneous

I often get the following message on the screen. What is wrong with the
arguments ? I don't use it.

--------
wrong number of arguments (1 for 0)
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in
`index'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in
`send'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in
`index___super'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/render.rb:79:in
`send'
 
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/render.rb:79:in
`render'


@George

Here, we are far away from a heatwave . The local temperature is only
16?C and it is raining. ;)


Thx for you help,

Jj


-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070703/8cb85e4c/attachment.html 

From arne at arnebrasseur.net  Tue Jul  3 13:38:17 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Tue, 03 Jul 2007 19:38:17 +0200
Subject: [Nitro] nitro 0.50: first encounter
In-Reply-To: <468A6F88.5090107@gmx.net>
References: <468A6F88.5090107@gmx.net>
Message-ID: <468A8989.8020707@arnebrasseur.net>

Jimmy Jazz schreef:
> If I'm in the wrong mailing list to expose my issues and to ask for 
> help, just let me know where i have to post them and please, sorry for 
> the noise.
Jimmy, you are very much in the right place. Thank you for trying out 
Nitro, just post all your questions, problems or thoughts here. We can 
use the feedback.

For your current issues, I will have a look and get back to you.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From arne at arnebrasseur.net  Tue Jul  3 15:23:54 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Tue, 03 Jul 2007 21:23:54 +0200
Subject: [Nitro] nitro 0.50: first encounter
In-Reply-To: <468A6F88.5090107@gmx.net>
References: <468A6F88.5090107@gmx.net>
Message-ID: <468AA24A.3000204@arnebrasseur.net>

Jimmy Jazz schreef:
> 1. Collisions
>
> For instance, if I name a class Menubar with a lowercase 'b' in the 
> skin.rb file and its associated render method contains a <div 
> class="menubar">, the template <Menubar></Menubar> won't render 
> anymore until the class name is renamed MenuBar with a uppercase 'B'. 
> Also, the page will be always well rendered if <div class="menubar"> 
> is declared inside the htmlx template file.
>
> To illustrate the issue.....
It looks to me like you're mixing up two different things.

An Element is defined in a class, which corresponds with an XML tag 
(class Menubar and <Menubar>). To access any content within the XML tags 
you use the content method.
<Menubar>
   <p>some random content</p>
</Menubar>

class Menubar
  def render
    # here content has the value "<p>some random content</p>"
    # do with it whatever you like
  def
end

The other thing is the special tag <render href="something" />, which is 
converted by the TemplateFilter (the last filter in the html pipeline) 
to the ruby code
render "something"

which is a method in Raw::Controller that renders a certain action on a 
certain controller. So render "menubar" will render the menubar action 
on the current controller, and that way the menubar.htmlx template gets 
rendered. (Hope you're still with me.)

What puzzles me is that according to the rdoc, a template file in the 
Element template_root gets converted to an Element class. I can't find 
this functionality in the code. Also what's the Element template_root? 
only Template has a template_root setting.
This could be what causes your name clash, I couldn't reproduce it.

G, if you're there, please enlighten me.

> 2. Question: how does #{content :method} really work ?
with #{content :element_id} you can access the content of sub-elements.
<Page>
  <Menubar id="menu1">content related to menu1</Menubar>
</Page>

class Page
  def render
    #content(:menu1) == "content related to menu1"
  end
end
> 3. Annotation and elements
...
> class Blog::Controller
>
>   ann :self, :element_namespace => Post
>
> doesn't return an error and is linked to Blog::Controller::Post. I 
> think that is wrong ( it should be Raw::Element::Post)
>
>
> ann :self, :element_namespace => BlogPage
>
> returns an exception,  :  uninitialized constant 
> Blog::Controller::BlogPage
>
This looks simply a ruby thing. Remember a classname in ruby is just a 
constant that has an instance of Class asigned to it. When you write 
Post ruby will look up the constant Post in the current namespace. It 
will also look in some other places like top-level, I don't remember the 
details exactly. There's some discussion about the way constants are 
looked up anyway, IIRC it might change in ruby 1.9/2.0.

Anyway, Nitro can't do much magic here (except by using const_missing 
perhaps). If you write BlogPage and ruby can't find that constant, 
you're out of luck.
> 4. Just to mention it
>
> You need to press Ctrl-C twice to stop webrick
Not sure what to say here, anyone?
>
> 5. That is a bit Greek (Chinese?) to me
>
> Some messages are really hard to understand and to debug and make the 
> source look fragile. That can be very frustrating especially if the 
> method are part of ruby language (e.g. each).
>
> DEBUG: Rendering '/blog/post'
> DEBUG: Compiling 'post' super-method
> DEBUG: Compiling 'post' view sub-method [format: html]
> --------
> undefined method `each' for nil:NilClass
>   (eval):3:in `post___html___view'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in 
> `send'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in 
> `method_missing'
This basically looks like you've called nil#each in a template. The 
post__html__view method is generated by nitro, it renders the post 
action with the html format. It basically is a ruby version of your 
template.

Perhaps the __view methods could be wrapped in a begin/rescue for nicer 
error reporting. Also a possibility is defining methods on nil to do 
error reporting, e.g. nil#each : You had a nil where you weren't 
expected it, you probably wanted an instance of Enumerable, like Array. 
Rails does this, probably because many who are new to ruby go to rails 
and get confused by ruby stuff. (for the record, I'm not suggesting this 
should be done, but it's a possibility.)
>
> 6. Helper required
.....
> Also, isn't app/helper the default directory for the helpers ?
>
As far as I know there's no such thing as a 'default helper dir' in 
Nitro. I'm guessing, but G isn't a fan of the term 'helper'.
> 7. miscellaneous
>
> I often get the following message on the screen. What is wrong with 
> the arguments ? I don't use it.
>
> --------
> wrong number of arguments (1 for 0)
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in 
> `index'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in 
> `send'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in 
> `index___super'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/render.rb:79:in 
> `send'
>   
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/controller/render.rb:79:in 
> `render'
>
I have seen this also, would have to take a closer look. Could this be a 
bug?


I hope this already helps somewhat. Keep posting whatever you have.

One tiny suggesting, if you could make a post for every subject that 
would make it easier for people to reply or to follow a thread.

a bientot,
(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From john at oxyliquit.de  Tue Jul  3 15:29:35 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 03 Jul 2007 22:29:35 +0300
Subject: [Nitro] nitro 0.50: first encounter
In-Reply-To: <468A6F88.5090107@gmx.net>
References: <468A6F88.5090107@gmx.net>
Message-ID: <op.tuwlq5kpxegpx6@jo.local>

Hi,

> If I'm in the wrong mailing list to expose my issues and to ask for
> help, just let me know where i have to post them and please, sorry for
> the noise.

you are quite right here, and up front:  I _really_ like the way your
post looks like.  It's informative, high amount of descriptions and
event code to replicate.  Many thanks for that.

> 1. Collisions

Not sure what's going on here, I'm hoping Arne can reproduce that.

[22:16]  <arne_b> wait a sec, have to try something
[22:18]  <arne_b> mmm can't reproduce the name clash

> 2. Question: how does #{content :method} really work ?

All I know is:  it's supposedly used for rendering 'sub elements'
inside of an element.  I also know that it is a hash (which makes
multiple same-named sub-elements impossible).

In my early days of Nitro I have looked at these and shoved them
away as too complex for my little mind to grasp.

> 3. Annotation and elements

> Also, i certainly misunderstood the annotation stuff ;)

Yes you do.  :P

> An example to illustrate the behavior:
>
> class Blog::Controller
>
>   ann :self, :element_namespace => Post
>
> doesn't return an error and is linked to Blog::Controller::Post. I think
> that is wrong ( it should be Raw::Element::Post)

In the contrary, normal Ruby rules apply.  So, the constant
`Post` will be looked up:  first Blog::Controller::Post, then
Blog::Post, then Post.  Same applies to BlogPage, so the error isn't
really surprising.  If you want absolute the 'correct' constant, use
`::Raw::Element::BlogPage`.  There's no magic going on here, it's
really just plain ruby lookup rules, annotations have nothing to do
with that.

Annotations are a system to 'tag information to a symbol'.
`ann :self, :foo => :bar` adds merges the hash `{:foo => :bar}` into
the information which is available on the symol :self.
Too confusing?

Just think of annotations as a way of saving/retrieving information.


> 4. Just to mention it
>
> You need to press Ctrl-C twice to stop webrick

Yes, quite normal, Webrick just is that way, for a better experience
use mongrel.  :P


> 5. That is a bit Greek (Chinese?) to me
>
> Some messages are really hard to understand and to debug and make the
> source look fragile. That can be very frustrating especially if the
> method are part of ruby language (e.g. each).

> undefined method `each' for nil:NilClass
>   (eval):3:in `post___html___view'

Yes, I agree that this should probably better point to the template
(I assume that's where the error comes from).  Perfect error reporting
is one of the hardest things in a web-framework, really, especially
with templates.
I hope that George when he comes back can come up with a scheme where
he can pinpoint the error better.

> 6. Helper required
>
> When i need an helper for a class,
>
> include MenuHelper
>
> i have to declare explicitly the pathname for the helper in the file
> were include is called,
>
> require "#{File.dirname(__FILE__)}/../helper/menu"
>
> Also, isn't app/helper the default directory for the helpers ?

That always depends on your load path, if you need to explicitly
require paths or not.  For debug purposes, look into the global `$:`.
As the `helper :menu, :stack` method has been deprecated (removed?)
by George in this release, normal ruby rules apply and no special
path is searched/added by default. (I think.)

> 7. miscellaneous
>
> I often get the following message on the screen. What is wrong with the
> arguments ? I don't use it.
>
> --------
> wrong number of arguments (1 for 0)
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/compiler.rb:65:in
> `index'

Looks evil and like a bug, /me cries for George.

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From Jimmy.Jazz at gmx.net  Wed Jul  4 13:19:23 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Wed, 04 Jul 2007 19:19:23 +0200
Subject: [Nitro] app.port isn't always read when something goes wrong during
	setup
Message-ID: <468BD69B.3000105@gmx.net>

Hello,

Also, i'm hunting. Stop me if i'm to wild :)

That is not quite a nitro bug but could be annoying.

A server is already using port 9000 and you planned to run nitro on the
port 9002 in the same time by modifying app.port = 9002 in debug.rb. But
the nitro web server failed to connect to the database (bad password for
example). You will get:


$ ../nitro/bin/nitro
 INFO: Og uses the Mysql store.
mysqladmin: connect to server at '' failed
error: 'Access denied for user 'root'@'localhost' (using password: YES)'
 INFO: Dropped database 'aTest'
ERROR: Access denied for user 'root'@'localhost' (using password: YES)
 INFO: Starting Webrick adapter on 0.0.0.0:9000
 INFO: Press Ctrl-C to shutdown; Run with --help for options.
/usr/lib64/ruby/1.8/webrick/utils.rb:73:in `initialize': Address already
in use - bind(2) (Errno::EADDRINUSE)
        from /usr/lib64/ruby/1.8/webrick/utils.rb:73:in `new'
        from /usr/lib64/ruby/1.8/webrick/utils.rb:73:in `create_listeners'
        from /usr/lib64/ruby/1.8/webrick/utils.rb:70:in `each'
        from /usr/lib64/ruby/1.8/webrick/utils.rb:70:in `create_listeners'
        from /usr/lib64/ruby/1.8/webrick/server.rb:75:in `listen'
        from /usr/lib64/ruby/1.8/webrick/server.rb:63:in `initialize'
        from /usr/lib64/ruby/1.8/webrick/httpserver.rb:24:in `initialize'
        from
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/adapter/webrick.rb:55:in
`new'
        from
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/adapter/webrick.rb:55:in
`start'
        from
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:122:in
`start'
        from app.rb:14


The server won't use the port 9002 anymore but the default one (port
9000) instead.

The other peculiar behavior is when you stop the server (port=9002) with
Ctrl-C, nitro restarts automatically with port=9000.

$ ../nitro/bin/nitro
 INFO: Og uses the Mysql store.
Database "aTest" dropped
 INFO: Dropped database 'aTest'
 INFO: Database 'aTest' not found!
 INFO: Created database 'aTest'
DEBUG: Og manageable classes: [Menubar, Navigation]
DEBUG: CREATE TABLE ognavigation (`oid` CHAR(22) PRIMARY KEY, `title`
text, `url` text, `position` integer)
 INFO: Created table 'ognavigation'.
DEBUG: SELECT * FROM ognavigation LIMIT 1
DEBUG: SELECT * FROM ognavigation LIMIT 1
DEBUG: CREATE TABLE ogmenubar (`oid` CHAR(22) PRIMARY KEY, `title` text,
`url` text, `position` integer, `access_key` text, `hint` text)
 INFO: Created table 'ogmenubar'.
DEBUG: SELECT * FROM ogmenubar LIMIT 1
DEBUG: SELECT * FROM ogmenubar LIMIT 1
DEBUG: SELECT * FROM ogmenubar ORDER BY position ASC
 INFO: Initializing Database
DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
`hint`, `oid`) VALUES ('Accueil', 1, 'a', '/index', 'Page d\'accueil du
site', 'b-zWZKkJ8r3kvGabpumjG5')
DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
`hint`, `oid`) VALUES ('Communaut?', 2, 'c', '/blog/index', 'Les amis du
penguin', 'b-F_2ukJ8r3kvGabpumjG5')
DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
`hint`, `oid`) VALUES ('Magazine', 3, 'm', '/wiki/index', 'A la
d?couverte du penguin', 'b-Ghx4kJ8r3kvGabpumjG5')
DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
`hint`, `oid`) VALUES ('Contact', 4, 'o', '/contact', 'Pour en savoir
plus sur nous', 'b-GoWokJ8r3kvGabpumjG5')
 INFO: Starting Webrick adapter on 0.0.0.0:9002
 INFO: Press Ctrl-C to shutdown; Run with --help for options.
 INFO: Stoping Webrick adapter.
 INFO: Og uses the Mysql store.
Database "aTest" dropped
 INFO: Dropped database 'aTest'
 INFO: Database 'aTest' not found!
 INFO: Created database 'aTest'
DEBUG: Og manageable classes: []
DEBUG: SELECT * FROM ogmenubar ORDER BY position ASC
ERROR: DB error Table 'aTest.ogmenubar' doesn't exist, [SELECT * FROM
ogmenubar ORDER BY position ASC]
ERROR:
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
`query'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
`query_statement'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:554:in
`query'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:367:in
`find'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:316:in
`all'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/manager.rb:118:in
`with_store'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:315:in
`all'
./conf/debug.rb:34:in `init_og'
./conf/debug.rb:19:in `setup_og'
./conf/debug.rb:28:in `setup'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:152:in
`read_configuration_file'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:180:in
`configure'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:97:in
`start'
/home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro.rb:73:in
`start'
app.rb:16
 INFO: Starting Webrick adapter on 0.0.0.0:9000
 INFO: Press Ctrl-C to shutdown; Run with --help for options.
 INFO: Stoping Webrick adapter.


Jj
-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070704/557f0a01/attachment.html 

From george.moschovitis at gmail.com  Wed Jul  4 14:33:23 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Wed, 4 Jul 2007 21:33:23 +0300
Subject: [Nitro] app.port isn't always read when something goes wrong
	during setup
In-Reply-To: <468BD69B.3000105@gmx.net>
References: <468BD69B.3000105@gmx.net>
Message-ID: <afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>

Hm,, #1 seems like a "bug".

I cannot understand #2, why does the server restart?

-g.

On 7/4/07, Jimmy Jazz <Jimmy.Jazz at gmx.net> wrote:
>
>  Hello,
>
> Also, i'm hunting. Stop me if i'm to wild :)
>
> That is not quite a nitro bug but could be annoying.
>
> A server is already using port 9000 and you planned to run nitro on the
> port 9002 in the same time by modifying app.port = 9002 in debug.rb. But
> the nitro web server failed to connect to the database (bad password for
> example). You will get:
>
>
> $ ../nitro/bin/nitro
>  INFO: Og uses the Mysql store.
> mysqladmin: connect to server at '' failed
> error: 'Access denied for user 'root'@'localhost' (using password: YES)'
>  INFO: Dropped database 'aTest'
> ERROR: Access denied for user 'root'@'localhost' (using password: YES)
>  INFO: Starting Webrick adapter on 0.0.0.0:9000
>  INFO: Press Ctrl-C to shutdown; Run with --help for options.
> /usr/lib64/ruby/1.8/webrick/utils.rb:73:in `initialize': Address already
> in use - bind(2) (Errno::EADDRINUSE)
>         from /usr/lib64/ruby/1.8/webrick/utils.rb:73:in `new'
>         from /usr/lib64/ruby/1.8/webrick/utils.rb:73:in `create_listeners'
>         from /usr/lib64/ruby/1.8/webrick/utils.rb:70:in `each'
>         from /usr/lib64/ruby/1.8/webrick/utils.rb:70:in `create_listeners'
>         from /usr/lib64/ruby/1.8/webrick/server.rb:75:in `listen'
>         from /usr/lib64/ruby/1.8/webrick/server.rb:63:in `initialize'
>         from /usr/lib64/ruby/1.8/webrick/httpserver.rb:24:in `initialize'
>         from
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/adapter/webrick.rb:55:in
> `new'
>         from
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../raw/lib/raw/adapter/webrick.rb:55:in
> `start'
>         from
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:122:in
> `start'
>         from app.rb:14
>
>
> The server won't use the port 9002 anymore but the default one (port 9000)
> instead.
>
> The other peculiar behavior is when you stop the server (port=9002) with
> Ctrl-C, nitro restarts automatically with port=9000.
>
> $ ../nitro/bin/nitro
>  INFO: Og uses the Mysql store.
> Database "aTest" dropped
>  INFO: Dropped database 'aTest'
>  INFO: Database 'aTest' not found!
>  INFO: Created database 'aTest'
> DEBUG: Og manageable classes: [Menubar, Navigation]
> DEBUG: CREATE TABLE ognavigation (`oid` CHAR(22) PRIMARY KEY, `title`
> text, `url` text, `position` integer)
>  INFO: Created table 'ognavigation'.
> DEBUG: SELECT * FROM ognavigation LIMIT 1
> DEBUG: SELECT * FROM ognavigation LIMIT 1
> DEBUG: CREATE TABLE ogmenubar (`oid` CHAR(22) PRIMARY KEY, `title` text,
> `url` text, `position` integer, `access_key` text, `hint` text)
>  INFO: Created table 'ogmenubar'.
> DEBUG: SELECT * FROM ogmenubar LIMIT 1
> DEBUG: SELECT * FROM ogmenubar LIMIT 1
> DEBUG: SELECT * FROM ogmenubar ORDER BY position ASC
>  INFO: Initializing Database
> DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
> `hint`, `oid`) VALUES ('Accueil', 1, 'a', '/index', 'Page d\'accueil du
> site', 'b-zWZKkJ8r3kvGabpumjG5')
> DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
> `hint`, `oid`) VALUES ('Communaut?', 2, 'c', '/blog/index', 'Les amis du
> penguin', 'b-F_2ukJ8r3kvGabpumjG5')
> DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
> `hint`, `oid`) VALUES ('Magazine', 3, 'm', '/wiki/index', 'A la d?couverte
> du penguin', 'b-Ghx4kJ8r3kvGabpumjG5')
> DEBUG: INSERT INTO ogmenubar (`title`, `position`, `access_key`, `url`,
> `hint`, `oid`) VALUES ('Contact', 4, 'o', '/contact', 'Pour en savoir plus
> sur nous', 'b-GoWokJ8r3kvGabpumjG5')
>  INFO: Starting Webrick adapter on 0.0.0.0:9002
>  INFO: Press Ctrl-C to shutdown; Run with --help for options.
>  INFO: Stoping Webrick adapter.
>  INFO: Og uses the Mysql store.
> Database "aTest" dropped
>  INFO: Dropped database 'aTest'
>  INFO: Database 'aTest' not found!
>  INFO: Created database 'aTest'
> DEBUG: Og manageable classes: []
> DEBUG: SELECT * FROM ogmenubar ORDER BY position ASC
> ERROR: DB error Table 'aTest.ogmenubar' doesn't exist, [SELECT * FROM
> ogmenubar ORDER BY position ASC]
> ERROR:
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
> `query'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/adapter/mysql.rb:122:in
> `query_statement'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:554:in
> `query'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/store/sql.rb:367:in
> `find'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:316:in
> `all'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/manager.rb:118:in
> `with_store'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:315:in
> `all'
> ./conf/debug.rb:34:in `init_og'
> ./conf/debug.rb:19:in `setup_og'
> ./conf/debug.rb:28:in `setup'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:152:in
> `read_configuration_file'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:180:in
> `configure'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro/application.rb:97:in
> `start'
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../nitro/lib/nitro.rb:73:in
> `start'
> app.rb:16
>  INFO: Starting Webrick adapter on 0.0.0.0:9000
>  INFO: Press Ctrl-C to shutdown; Run with --help for options.
>  INFO: Stoping Webrick adapter.
>
>
> Jj
> --
>
>             |\      _,,,---,,_
>       ZZZzz /,`.-'`'    -.  ;-;;,_
>            |,4-  ) )-,_. ,\ (  `'-'
>           '---''(_/--'  `-'\_)
>
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070704/efb3becd/attachment-0001.html 

From Jimmy.Jazz at gmx.net  Wed Jul  4 17:42:21 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Wed, 04 Jul 2007 23:42:21 +0200
Subject: [Nitro] nitro 0.50: first encounter
In-Reply-To: <468AA24A.3000204@arnebrasseur.net>
References: <468A6F88.5090107@gmx.net> <468AA24A.3000204@arnebrasseur.net>
Message-ID: <468C143D.7030904@gmx.net>

Arne Brasseur a ?crit :
>
> I hope this already helps somewhat. Keep posting whatever you have.
>
> One tiny suggesting, if you could make a post for every subject that
> would make it easier for people to reply or to follow a thread.
>
> a bientot,
> (ab)
>
I agree with you: one post for one subject will be easier for me too :)

a bientot

Jj

-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070704/ab23d7da/attachment.html 

From Jimmy.Jazz at gmx.net  Wed Jul  4 18:11:09 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Thu, 05 Jul 2007 00:11:09 +0200
Subject: [Nitro] nitro 0.50: first encounter
In-Reply-To: <op.tuwlq5kpxegpx6@jo.local>
References: <468A6F88.5090107@gmx.net> <op.tuwlq5kpxegpx6@jo.local>
Message-ID: <468C1AFD.2000705@gmx.net>

Jonathan Buch a ?crit :
>> 1. Collisions
> 
> Not sure what's going on here, I'm hoping Arne can reproduce that.
> 
> [22:16]  <arne_b> wait a sec, have to try something
> [22:18]  <arne_b> mmm can't reproduce the name clash

Also, I sent to both of you a hopefully functional example.

>> 2. Question: how does #{content :method} really work ?
> 
> All I know is:  it's supposedly used for rendering 'sub elements'
> inside of an element.  I also know that it is a hash (which makes
> multiple same-named sub-elements impossible).
> 
> In my early days of Nitro I have looked at these and shoved them
> away as too complex for my little mind to grasp.
> 

:)

>> 3. Annotation and elements
> 
>> Also, i certainly misunderstood the annotation stuff ;)
> 
> Yes you do.  :P
> 
>> An example to illustrate the behavior:
>>
>> class Blog::Controller
>>
>>   ann :self, :element_namespace => Post
>>
>> doesn't return an error and is linked to Blog::Controller::Post. I think
>> that is wrong ( it should be Raw::Element::Post)
> 
> In the contrary, normal Ruby rules apply.  So, the constant
> `Post` will be looked up:  first Blog::Controller::Post, then
> Blog::Post, then Post.  Same applies to BlogPage, so the error isn't
> really surprising.  If you want absolute the 'correct' constant, use
> `::Raw::Element::BlogPage`.  There's no magic going on here, it's
> really just plain ruby lookup rules, annotations have nothing to do
> with that.
> 
> Annotations are a system to 'tag information to a symbol'.
> `ann :self, :foo => :bar` adds merges the hash `{:foo => :bar}` into
> the information which is available on the symol :self.
> Too confusing?
> 
> Just think of annotations as a way of saving/retrieving information.

I have be wrong to believe that :element_namespace (like the name could
have suggest) would help me to associate a Controller like
Blog::Controller to a particular Element Class like Raw::Element::BlogPage.

> Yes, quite normal, Webrick just is that way, for a better experience
> use mongrel.  :P
> 
As soon as i will be more productive :P
> 
>> 5. That is a bit Greek (Chinese?) to me
>>
>> Some messages are really hard to understand and to debug and make the
>> source look fragile. That can be very frustrating especially if the
>> method are part of ruby language (e.g. each).
> 
>> undefined method `each' for nil:NilClass
>>   (eval):3:in `post___html___view'
> 
> Yes, I agree that this should probably better point to the template
> (I assume that's where the error comes from).  Perfect error reporting
> is one of the hardest things in a web-framework, really, especially
> with templates.
> I hope that George when he comes back can come up with a scheme where
> he can pinpoint the error better.
> 
I'm sure he will :)

Thank you for your explanation

Jj

-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)



From Jimmy.Jazz at gmx.net  Thu Jul  5 05:55:15 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Thu, 05 Jul 2007 11:55:15 +0200
Subject: [Nitro] app.port isn't always read when something goes wrong
 during setup
In-Reply-To: <afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
References: <468BD69B.3000105@gmx.net>
	<afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
Message-ID: <468CC003.20609@gmx.net>

George Moschovitis a ?crit :

> I cannot understand #2, why does the server restart?

I do nothing special just Crtl-C

Jj

-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


From arne at arnebrasseur.net  Thu Jul  5 15:10:00 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Thu, 05 Jul 2007 21:10:00 +0200
Subject: [Nitro] [Fwd: About the Menubar collision (follow-up)]
Message-ID: <468D4208.2030106@arnebrasseur.net>

I'm taking this on-list, I suppose nobody really minds.

I investigated your example a bit, the problem isn't with the <render 
"menubar" />, it's with you Menubar og model. In fact this is documented 
behaviour :P

raw/compiler/filter/elements.rb

      # Try to use Controller::xxx
      # gmosx, THINK: this looks a bit dangerous to me!
     
      begin
        # gmosx, FIXME: Class.by_name also returns top level
        # classes, how can we fix this?

        klass = constant("#{controller}::#{name}")
        puts "Searching element #{name} as #{controller}::#{name} => 
#{klass}"      # I added this
      rescue
        # drink it!
      end

This outputs:
Searching element Menubar as Home::Controller::Menubar => Menubar

So this indeed returns the top-level class. The constant method is from 
facets. It looks to me it doesn't work like one would suspect...


(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An embedded message was scrubbed...
From: Jimmy Jazz <Jimmy.Jazz at gmx.net>
Subject: About the Menubar collision (follow-up)
Date: Wed, 04 Jul 2007 20:28:47 +0200
Size: 34787
Url: http://rubyforge.org/pipermail/nitro-general/attachments/20070705/ad3bb1d3/attachment-0001.mht 

From arne at arnebrasseur.net  Thu Jul  5 15:19:48 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Thu, 05 Jul 2007 21:19:48 +0200
Subject: [Nitro] [Fwd: About the Menubar collision (follow-up)]
In-Reply-To: <468D4208.2030106@arnebrasseur.net>
References: <468D4208.2030106@arnebrasseur.net>
Message-ID: <468D4454.7090608@arnebrasseur.net>

Oh and George, if you wan't to see the webrick restarting in action, 
just run the app.

(ab)

Arne Brasseur schreef:
> I'm taking this on-list, I suppose nobody really minds.
>
> I investigated your example a bit, the problem isn't with the <render 
> "menubar" />, it's with you Menubar og model. In fact this is 
> documented behaviour :P
>
> raw/compiler/filter/elements.rb
>
>      # Try to use Controller::xxx
>      # gmosx, THINK: this looks a bit dangerous to me!
>          begin
>        # gmosx, FIXME: Class.by_name also returns top level
>        # classes, how can we fix this?
>
>        klass = constant("#{controller}::#{name}")
>        puts "Searching element #{name} as #{controller}::#{name} => 
> #{klass}"      # I added this
>      rescue
>        # drink it!
>      end
>
> This outputs:
> Searching element Menubar as Home::Controller::Menubar => Menubar
>
> So this indeed returns the top-level class. The constant method is 
> from facets. It looks to me it doesn't work like one would suspect...
>
>
> (ab)
>
>
> ------------------------------------------------------------------------
>
> Onderwerp:
> About the Menubar collision (follow-up)
> Van:
> Jimmy Jazz <Jimmy.Jazz at gmx.net>
> Datum:
> Wed, 04 Jul 2007 20:28:47 +0200
> Aan:
> Arne Brasseur <arne at arnebrasseur.net>, Jonathan Buch <john at oxyliquit.de>
>
> Aan:
> Arne Brasseur <arne at arnebrasseur.net>, Jonathan Buch <john at oxyliquit.de>
> CC:
> george.moschovitis at gmail.com
>
>
> Hello devs,
>
> Sorry, I sent you the code directly without sending it to the mailing 
> list, but i don't know if it is allowed to send binary files to the 
> list (zip file). Anyway, it would be great to be able to send ruby 
> codes and examples to a ftp server available to the devs. Also, here 
> is an example of a "working" nitro project that will show you what 
> will happened and how i have proceed. I have certainly mishandled 
> nitro or ruby (ruby (as well nitro) is a new language/framework to me 
> :) but other people could certainly have the same feeling about how I 
> write it. Indeed, the fact that nitro hides a lot of the ruby 
> mechanism - we don't need explicitly initialize() or new() - make me 
> feel a bit uncomfortable especially because i'm in the learning stage ;)
>
> After running nitro, you will see (i hope) an orange menu bar to the 
> left (change the password and the name of the database to your 
> convenience)
>
> The files that end with a minus '-' are buggy. Just rename them and 
> they will show you the issue quite well. The "rendering" will just 
> disappear.
>
> Are both classes Menubar in navigation.rb (a model) and Menubar in 
> skin.rb (an element) belonging to the same superclass that could 
> explain the collision ? Why that choice was made ?
>
> There are two other problems i have discovered, but probably just 
> related to the fact that nitro doesn't find all the gem and ruby 
> codes. Uncomment them to see the errors.
>
> # validate_length :title, :range => 2..128, :msg => 'argh'
>
> doesn't work. Nitro complains about a missing 'validations' method
>
> $ ../nitro/bin/nitro
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../og/lib/og/model.rb:664:in 
> `method_missing': undefined local variable or method `validations' for 
> Navigation:Class (NameError)
>         from 
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../glue/lib/glue/validation.rb:432:in 
> `define_validation'
>         from 
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../glue/lib/glue/validation.rb:298:in 
> `validate_length'
>         from 
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../glue/lib/glue/validation.rb:297:in 
> `each'
>         from 
> /home/lilo/workspace/repo.nitroproject.org/script/lib/../../glue/lib/glue/validation.rb:297:in 
> `validate_length'
>         from ./app/model/navigation.rb:12
>         from 
> /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in 
> `gem_original_require'
>         from 
> /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
>         from app.rb:10
>
>
> and
>
> # is Orderable
>
> doesn't work either. Nitro complains this time about an undefined 
> method 'basename' that belongs to a standard ruby library.
>
> $ ../nitro/bin/nitro
> /usr/lib64/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:96:in 
> `is': undefined method `basename' for :Orderable:Symbol (NoMethodError)
>         from 
> /usr/lib64/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:94:in 
> `each'
>         from 
> /usr/lib64/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:94:in 
> `is'
>         from ./app/model/navigation.rb:29
>         from 
> /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in 
> `gem_original_require'
>         from 
> /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
>         from app.rb:10
>
> Thank you for you help,
>
> Jj
>
> -- 
>             |\      _,,,---,,_
>       ZZZzz /,`.-'`'    -.  ;-;;,_
>            |,4-  ) )-,_. ,\ (  `'-'
>           '---''(_/--'  `-'\_)
>
> *
> *
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general


-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070705/a155ec82/attachment.html 

From john at oxyliquit.de  Fri Jul  6 02:06:22 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 06 Jul 2007 09:06:22 +0300
Subject: [Nitro] app.port isn't always read when something goes wrong
	during setup
In-Reply-To: <afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
References: <468BD69B.3000105@gmx.net>
	<afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
Message-ID: <op.tuzk0605xegpx6@jo.local>

Hi,

> Hm,, #1 seems like a "bug".
>
> I cannot understand #2, why does the server restart?

Some 'rescue Object' somewhere?

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Fri Jul  6 02:06:22 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 06 Jul 2007 09:06:22 +0300
Subject: [Nitro] [Fwd: About the Menubar collision (follow-up)]
In-Reply-To: <468D4454.7090608@arnebrasseur.net>
References: <468D4208.2030106@arnebrasseur.net>
	<468D4454.7090608@arnebrasseur.net>
Message-ID: <op.tu04kf15xegpx6@jo.local>

Hi,

> I'm taking this on-list, I suppose nobody really minds.

Nope, on list is fine.  Jimmy:  zip files are ok here (until you hit a
limit, in which case the mailing list will send you a mail back that
you hit that limit), and the list is so low volume, that it really
doesn't hurt.  :)

> So this indeed returns the top-level class. The constant method is from  
> facets. It looks to me it doesn't work like one would suspect...

Hi, yes, the constant method looks up the given path from the current
position (unless you prefix it with ::), that's what the code and the
comment tells me.  The test-cases on the other hand displays more.

class TCKernel < Test::Unit::TestCase

     def test_constant
       c = "Test::Unit::TestCase"
       assert_equal( ::Test::Unit::TestCase, constant(c) )

It seems, like with just writing without the :: it'll look it up too,
meaning you can't control that it looks up the `Object` as well.
Well, on the other hand, normal ruby lookup works like that too, first
look in current, then go all the way back to Object.

So, better be careful where you put and name your classes.  :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From Jimmy.Jazz at gmx.net  Fri Jul  6 17:15:09 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Fri, 06 Jul 2007 23:15:09 +0200
Subject: [Nitro] accessing children within an  element
Message-ID: <468EB0DD.8020309@gmx.net>

Hello,

I took some time to discover why it was not possible to access a child
content from within an element :)

The instance variable @_children should have been declared as a class
variable @@_children. Otherwise you will lose what you have filled in
after calling the method add_child in
raw/lib/raw/compiler/filter/elements/element.rb.

Also, i'm a bit confused about how to use it.

If you write something like,

<Page>
<Box id="mybox">
  Jack
</Box>
</Page>

and you declare a class Box

Class Page
Class Box < Raw::Element
  %{
    <div id="mylayout">
     Oh Jack ...
    </div>
  }
end
end

the layout mylayout of the class Box  will be completely ignored if you
call the child "mybox" directly

def render
  #{content :mybox}
end

otherwise the layout will be used when you access the whole page like that:

def render
  #{content}
end

That could be really confusing for anyone and it can be also hard to
decide where to declare css layouts for an element in the class, the
render or the htmlx file. :(

Jj
-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070706/af7c8fb4/attachment.html 

From aurelianocalvo at yahoo.com.ar  Sat Jul  7 13:47:21 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Sat, 7 Jul 2007 14:47:21 -0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
Message-ID: <1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>

With Jo's help at IRC I've been able to set up nitro and start the
blog using sqlite3 as the data store. But when I go to the admin link
to create a new post I get an exception in the log and a "white screen
of death" in my browser.

What I did:
Go to http://localhost:9000/admin/og/create/Post and created a new post.

Exception in the log (with some context):
DEBUG: INSERT INTO ogpost (oid, author, title, access_time,
category_oid, update_time, body, create_time) VALUES
('copIeGllar3j0Iaa-JKF1G', 'aure', 'Blog test', NULL,
'bkpeKaljqr3lLJaa-JKF1G', '2007-07-07 14:36:12', 'This is a blog
test', '2007-07-07 14:36:12')
ERROR: Error while handling '/admin/og/save'
ERROR: undefined method `unsaved?' for nil:NilClass
  (eval):25:in `add_tag'
  /home/aure/nitro/script/lib/../../og/lib/og/collection.rb:258:in `send'
  /home/aure/nitro/script/lib/../../og/lib/og/collection.rb:258:in
`save_building_members'
  /home/aure/nitro/script/lib/../../og/lib/og/collection.rb:257:in `each'
  /home/aure/nitro/script/lib/../../og/lib/og/collection.rb:257:in
`save_building_members'
  /home/aure/nitro/script/lib/../../og/lib/og/model.rb:179:in
`save_building_collections'
  /home/aure/nitro/script/lib/../../og/lib/og/model.rb:176:in `each'
  /home/aure/nitro/script/lib/../../og/lib/og/model.rb:176:in
`save_building_collections'
  /home/aure/nitro/script/lib/../../og/lib/og/store.rb:98:in `save'
  /home/aure/nitro/script/lib/../../og/lib/og/model.rb:20:in `save'
  /home/aure/nitro/script/lib/../../og/lib/og/manager.rb:118:in `with_store'
  /home/aure/nitro/script/lib/../../og/lib/og/model.rb:19:in `save'
  /home/aure/nitro/script/lib/../../nitro/lib/nitro/part/admin/og/controller.rb:101:in
`save'
  (eval):4:in `call'
  (eval):4:in `save'
  (eval):4:in `call'
  (eval):4:in `save'
  (eval):3:in `call'
  (eval):3:in `save'
  /home/aure/nitro/script/lib/../../raw/lib/raw/compiler.rb:65:in `send'
  /home/aure/nitro/script/lib/../../raw/lib/raw/compiler.rb:65:in `save___super'
  /home/aure/nitro/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in
`send'
  /home/aure/nitro/script/lib/../../raw/lib/raw/controller/publishable.rb:36:in
`method_missing'
  /home/aure/nitro/script/lib/../../raw/lib/raw/adapter.rb:69:in `send'
  /home/aure/nitro/script/lib/../../raw/lib/raw/adapter.rb:69:in
`handle_context'
  /home/aure/nitro/script/lib/../../raw/lib/raw/adapter/webrick.rb:134:in
`do_POST'
  /usr/lib/ruby/1.8/webrick/httpservlet/abstract.rb:35:in `__send__'
  /usr/lib/ruby/1.8/webrick/httpservlet/abstract.rb:35:in `service'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
  /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
  /home/aure/nitro/script/lib/../../raw/lib/raw/adapter/webrick.rb:57:in `start'
  /home/aure/nitro/script/lib/../../nitro/lib/nitro/application.rb:123:in
`start'
  app.rb:22
  LOGGED FROM: /home/aure/nitro/script/lib/../../raw/lib/raw/adapter.rb:83:in
`handle_context'

From john at oxyliquit.de  Sat Jul  7 14:05:30 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sat, 07 Jul 2007 21:05:30 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
Message-ID: <op.tu3wiukvxegpx6@jo.local>

Hi,

> With Jo's help at IRC I've been able to set up nitro and start the
> blog using sqlite3 as the data store. But when I go to the admin link
> to create a new post I get an exception in the log and a "white screen
> of death" in my browser.
>
> What I did:
> Go to http://localhost:9000/admin/og/create/Post and created a new post.

Small bug in joins_many (or, rather the code calling it, but anyway).

George, please pull (there's also one more patch concerning the pager).

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Sat Jul  7 14:13:38 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sat, 7 Jul 2007 21:13:38 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <op.tu3wiukvxegpx6@jo.local>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<op.tu3wiukvxegpx6@jo.local>
Message-ID: <afd80b540707071113t5e778c68v498bc5a6955fe752@mail.gmail.com>

>
> Small bug in joins_many (or, rather the code calling it, but anyway).
> George, please pull (there's also one more patch concerning the pager).
>

Ok, thanks will do!

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070707/97108479/attachment.html 

From john at oxyliquit.de  Sat Jul  7 14:14:33 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sat, 07 Jul 2007 21:14:33 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <op.tu3wiukvxegpx6@jo.local>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<op.tu3wiukvxegpx6@jo.local>
Message-ID: <op.tu3wyjv2xegpx6@jo.local>

Hi,

> George, please pull (there's also one more patch concerning the pager).

I messed up, pager patch is non-existant, I didn't pull that patch
 from G yet, he fixed it already.  :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Sat Jul  7 14:15:54 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sat, 7 Jul 2007 21:15:54 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <op.tu3wyjv2xegpx6@jo.local>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<op.tu3wiukvxegpx6@jo.local> <op.tu3wyjv2xegpx6@jo.local>
Message-ID: <afd80b540707071115l2b3bd7f3v5fe46c4a8e8d304d@mail.gmail.com>

>
> I messed up, pager patch is non-existant, I didn't pull that patch
> from G yet, he fixed it already.  :P


;-)



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070707/7dc44154/attachment.html 

From aurelianocalvo at yahoo.com.ar  Sat Jul  7 14:19:35 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Sat, 7 Jul 2007 15:19:35 -0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <afd80b540707071113t5e778c68v498bc5a6955fe752@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<op.tu3wiukvxegpx6@jo.local>
	<afd80b540707071113t5e778c68v498bc5a6955fe752@mail.gmail.com>
Message-ID: <1340963a0707071119g67719517q4231cb6713ae6f6a@mail.gmail.com>

> > Small bug in joins_many (or, rather the code calling it, but anyway).
> > George, please pull (there's also one more patch concerning the pager).
> >
>
> Ok, thanks will do!
>
> -g.

I've pulled the patch from Jonathan's repository and it worked great
on my copy :-D.
Thank you very much,
Aureliano.

From george.moschovitis at gmail.com  Sat Jul  7 14:19:46 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sat, 7 Jul 2007 21:19:46 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
Message-ID: <afd80b540707071119h3809b003t6eca68f906384dc8@mail.gmail.com>

>
> With Jo's help at IRC I've been able to set up nitro and start the
> blog using sqlite3 as the data store. But when I go to the admin link
>

let me know if jonathans patch fixes this.

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070707/0c8a4f80/attachment.html 

From Jimmy.Jazz at gmx.net  Sat Jul  7 17:16:40 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Sat, 07 Jul 2007 23:16:40 +0200
Subject: [Nitro] app.port isn't always read when something goes wrong
 during setup
In-Reply-To: <afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
References: <468BD69B.3000105@gmx.net>
	<afd80b540707041133wfc99652i3719a143bb24bc88@mail.gmail.com>
Message-ID: <469002B8.8040800@gmx.net>

George Moschovitis a ?crit :
> Hm,, #1 seems like a "bug".
> 
> I cannot understand #2, why does the server restart?
> 
> -g.

Sorry, my mistake. I have defined an instance
application=Application.new followed by a application.start and used the
nitro helper nitro.start too.

I Hope you didn't lose too much time to find out what the problem could be.

Don't be too hard with me, the error was also in the example i sent to
you. I'm still learning nitro :)


Jj


-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


From aurelianocalvo at yahoo.com.ar  Sat Jul  7 20:48:36 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Sat, 7 Jul 2007 21:48:36 -0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <afd80b540707071119h3809b003t6eca68f906384dc8@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<afd80b540707071119h3809b003t6eca68f906384dc8@mail.gmail.com>
Message-ID: <1340963a0707071748p73255585h244ef87d591805e3@mail.gmail.com>

> > With Jo's help at IRC I've been able to set up nitro and start the
> > blog using sqlite3 as the data store. But when I go to the admin link
> >
>
> let me know if jonathans patch fixes this.

Yes, Jonathan's patch fixes this (in my PC).

From aurelianocalvo at yahoo.com.ar  Sun Jul  8 00:31:55 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Sun, 8 Jul 2007 01:31:55 -0300
Subject: [Nitro] Running specs
Message-ID: <1340963a0707072131h6d444c40n85862500dbb8621f@mail.gmail.com>

I'm trying to run the automated tests for nitro but I'm not being successfull.

When I run "rake test/nitro" or "rake test/raw" or "rake test/og" I
get the following error:
/home/aure/nitro/script/lib/spec.rb:18: uninitialized constant
Spec::VERSION (NameError)
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require'
        from ./script/lib/spec.rb:15
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require'
        from /home/aure/nitro/raw/spec/view/pager.rb:1

I have the latest nitro development version, and I can run my own
specs outside nitro with no problems.

I also get messages like:
Running controller/caching...             [   0 specs -   0 failed ]

That look suspicious. All of them share " 0 specs -   0 failed ". What
should I do to run the automated nitro tests?

Aureliano.

From john at oxyliquit.de  Sun Jul  8 02:07:23 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 08 Jul 2007 09:07:23 +0300
Subject: [Nitro] Running specs
In-Reply-To: <1340963a0707072131h6d444c40n85862500dbb8621f@mail.gmail.com>
References: <1340963a0707072131h6d444c40n85862500dbb8621f@mail.gmail.com>
Message-ID: <op.tu4tylm4xegpx6@jo.local>

Hi,

> I'm trying to run the automated tests for nitro but I'm not being  
> successfull.
>
> When I run "rake test/nitro" or "rake test/raw" or "rake test/og" I
> get the following error:
> /home/aure/nitro/script/lib/spec.rb:18: uninitialized constant
> Spec::VERSION (NameError)

It's `rake test:raw` not `rake test/raw`.

> I have the latest nitro development version, and I can run my own
> specs outside nitro with no problems.
>
> I also get messages like:
> Running controller/caching...             [   0 specs -   0 failed ]
>
> That look suspicious. All of them share " 0 specs -   0 failed ". What
> should I do to run the automated nitro tests?

Nitro requires the newest RSpec, might that be the problem?

When it says '0 specs' like that, some precondition failed, basically
it can't run the spec at all.  You'll get the errors at then end, when
all specs ran through.

You can also access single specs by doing
`rake test:raw:controller:caching`.  (It's just the path to the file).

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From arne at arnebrasseur.net  Sun Jul  8 08:07:32 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Sun, 08 Jul 2007 14:07:32 +0200
Subject: [Nitro] Client morpher testcase
Message-ID: <4690D384.7040102@arnebrasseur.net>

Hi,

I'm doing some more spec work. There is a testcase for a client morpher 
that apparently reacts to a client attribute and cooperates with an 
ajax_update method. No trace however of the morpher or the method.

What do I do? Throw out the testcase or not?

I'm guessing the morpher got thrown out because it caused a dependency 
on a specific javascript lib. Is this correct?

kind regards,
(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From john at oxyliquit.de  Sun Jul  8 08:54:49 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 08 Jul 2007 15:54:49 +0300
Subject: [Nitro] Blog explodes -> newby needs help
In-Reply-To: <afd80b540707071115l2b3bd7f3v5fe46c4a8e8d304d@mail.gmail.com>
References: <1340963a0707071045y4d53966fvfe6ea191321a4e81@mail.gmail.com>
	<1340963a0707071047q67965697o87b9199aa0fbe93e@mail.gmail.com>
	<op.tu3wiukvxegpx6@jo.local> <op.tu3wyjv2xegpx6@jo.local>
	<afd80b540707071115l2b3bd7f3v5fe46c4a8e8d304d@mail.gmail.com>
Message-ID: <op.tu5ctnvmxegpx6@jo.local>

Hi,

>> I messed up, pager patch is non-existant, I didn't pull that patch
>> from G yet, he fixed it already.  :P
>
>
> ;-)

uploaded spec update to cope with your latest changes there :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From aurelianocalvo at yahoo.com.ar  Sun Jul  8 09:18:48 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Sun, 8 Jul 2007 10:18:48 -0300
Subject: [Nitro] Running specs
In-Reply-To: <op.tu4tylm4xegpx6@jo.local>
References: <1340963a0707072131h6d444c40n85862500dbb8621f@mail.gmail.com>
	<op.tu4tylm4xegpx6@jo.local>
Message-ID: <1340963a0707080618l587a2a1k22eac7dac791b23f@mail.gmail.com>

> > I'm trying to run the automated tests for nitro but I'm not being
> > successfull.
> >
> > When I run "rake test/nitro" or "rake test/raw" or "rake test/og" I
> > get the following error:
> > /home/aure/nitro/script/lib/spec.rb:18: uninitialized constant
> > Spec::VERSION (NameError)

I've found the error:
My ruby include path included the /home/aure/nitro/script/lib folder.
When 'spec.rb' required 'spec' it required itself instead of the gem.

> It's `rake test:raw` not `rake test/raw`.

Ups! my mistake.

> When it says '0 specs' like that, some precondition failed, basically
> it can't run the spec at all.  You'll get the errors at then end, when
> all specs ran through.

> You can also access single specs by doing
> `rake test:raw:controller:caching`.  (It's just the path to the file).

Right now it's working :-D.

$ rake test:raw:controller:caching
(in /home/aure/nitro)
Please install systemu for better-looking results
Running caching...         [   2 specs - all passed ]
2 examples, 0 failures

No failing examples, let's add some tests!

From george.moschovitis at gmail.com  Sun Jul  8 11:24:56 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sun, 8 Jul 2007 18:24:56 +0300
Subject: [Nitro] Client morpher testcase
In-Reply-To: <4690D384.7040102@arnebrasseur.net>
References: <4690D384.7040102@arnebrasseur.net>
Message-ID: <afd80b540707080824o5c11cefbs1997d9acbd09ecd9@mail.gmail.com>

Ignore this,

the proposed method to do javascript special fx is to use Jquery. The old
scriptaculous morphers are deprecated.
JQuery is more flexible, elegant and powerful.

-g.

On 7/8/07, Arne Brasseur <arne at arnebrasseur.net> wrote:
>
> Hi,
>
> I'm doing some more spec work. There is a testcase for a client morpher
> that apparently reacts to a client attribute and cooperates with an
> ajax_update method. No trace however of the morpher or the method.
>
> What do I do? Throw out the testcase or not?
>
> I'm guessing the morpher got thrown out because it caused a dependency
> on a specific javascript lib. Is this correct?
>
> kind regards,
> (ab)
>
> --
> Arne Brasseur
> http://www.arnebrasseur.net
> arne at arnebrasseur.net
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070708/a03ff652/attachment.html 

From john at oxyliquit.de  Sun Jul  8 11:26:47 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 08 Jul 2007 18:26:47 +0300
Subject: [Nitro] Client morpher testcase
In-Reply-To: <afd80b540707080824o5c11cefbs1997d9acbd09ecd9@mail.gmail.com>
References: <4690D384.7040102@arnebrasseur.net>
	<afd80b540707080824o5c11cefbs1997d9acbd09ecd9@mail.gmail.com>
Message-ID: <op.tu5juxhwxegpx6@jo.local>

Hi,

> Ignore this,
>
> the proposed method to do javascript special fx is to use Jquery. The  
> old scriptaculous morphers are deprecated.
> JQuery is more flexible, elegant and powerful.

no, please don't ignore, eradicate.  ;)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Sun Jul  8 11:29:22 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sun, 8 Jul 2007 18:29:22 +0300
Subject: [Nitro] Client morpher testcase
In-Reply-To: <op.tu5juxhwxegpx6@jo.local>
References: <4690D384.7040102@arnebrasseur.net>
	<afd80b540707080824o5c11cefbs1997d9acbd09ecd9@mail.gmail.com>
	<op.tu5juxhwxegpx6@jo.local>
Message-ID: <afd80b540707080829n617cfd6bl4fc2787ed0b6408b@mail.gmail.com>

>
> no, please don't ignore, eradicate.  ;)
>

right!

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070708/876c9e54/attachment.html 

From george.moschovitis at gmail.com  Sun Jul  8 14:52:09 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sun, 8 Jul 2007 21:52:09 +0300
Subject: [Nitro] ATOM dump
Message-ID: <afd80b540707081152y2fdce5e5m63aabe8049d82eb0@mail.gmail.com>

Dear devs,

Nitro contains a utility that automatically converts objects and collections
to atom feeds. You can find the code at:

lib/raw/util/atom.rb

the problem is that this code does not always work. To be more specific,
sometimes it does not generate valid atom code. I think there must be a
problem with encoding of the content field or something. I would like to ask
someone on this list to have a look at this and possibly help with a patch
or fix.

thanks in advance,
-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070708/0f35587a/attachment.html 

From Jimmy.Jazz at gmx.net  Sun Jul  8 15:35:12 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Sun, 08 Jul 2007 21:35:12 +0200
Subject: [Nitro] about rake test
Message-ID: <46913C70.4010102@gmx.net>

Hello,

Also, rake context test won't work until I added require
"facets/more/ann" in og/lib/og/relation/has_many.rb. Perhaps it is a
simple oblivion or i sadly corrupt my nitro installation :).

* cgi/cookie doesn't work either and complains about a bad timestamp
that doesn't use the http1.1 format.

ExitStatus:
#<Process::Status: pid=16046,exited(0)>
StdOut:
.F.

1)
ArgumentError in 'Raw::Cookie should report expire timestamp in the
format used by HTTP/1.1 (rfc2616)'
invalid value for Integer: "08"
/home/lilo/workspace/repo.nitroproject.org/raw/spec/cgi/cookie.rb:26:in
`Integer'
/home/lilo/workspace/repo.nitroproject.org/raw/spec/cgi/cookie.rb:26:
/usr/lib64/ruby/1.8/timeout.rb:48:in `timeout'
/home/lilo/workspace/repo.nitroproject.org/raw/spec/cgi/cookie.rb:6:

* controller returns a warning about

./raw/lib/raw/compiler.rb:58: warning: multiple values for a block
parameter (0 for 1)
        from ./raw/lib/raw/controller/publishable.rb:36



Jj



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070708/9a86ede7/attachment.html 

From john at oxyliquit.de  Sun Jul  8 16:15:03 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 08 Jul 2007 23:15:03 +0300
Subject: [Nitro] about rake test
In-Reply-To: <46913C70.4010102@gmx.net>
References: <46913C70.4010102@gmx.net>
Message-ID: <op.tu5w7dacxegpx6@jo.local>

Hi,

Aurelianito reported the same on IRC.  :)

> Also, rake context test won't work until I added require  
> "facets/more/ann" in og/lib/og/relation/has_many.rb. Perhaps it is a  
> simple oblivion or i sadly corrupt my nitro installation :).

No, that issue is only existant while testing (because it is more
'independend').  Nothing wrong with your repo at all, just a glitch,
it'll not hinder any application you do.

> * cgi/cookie doesn't work either and complains about a bad timestamp  
> that doesn't use the http1.1 format.

Yeah, but I know nothing about cookies, someone more proficient has
to have a look at that.  If you know what it should deliver, could
you propose a spec or code change to make the spec go green?

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From arne at arnebrasseur.net  Sun Jul  8 18:11:59 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Mon, 09 Jul 2007 00:11:59 +0200
Subject: [Nitro] about rake test
In-Reply-To: <op.tu5w7dacxegpx6@jo.local>
References: <46913C70.4010102@gmx.net> <op.tu5w7dacxegpx6@jo.local>
Message-ID: <4691612F.2030205@arnebrasseur.net>

Jonathan Buch schreef:
>> * cgi/cookie doesn't work either and complains about a bad timestamp  
>> that doesn't use the http1.1 format.
>>     
>
> Yeah, but I know nothing about cookies, someone more proficient has
> to have a look at that.  If you know what it should deliver, could
> you propose a spec or code change to make the spec go green?
>   
I will fix this (since I broke it :), the problem is that Integer() 
considers the number to be octal when it starts with a zero, and 8 isn't 
valid in octal. Leading zeroes need to be stripped off first.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070709/0d23229a/attachment.html 

From aurelianocalvo at yahoo.com.ar  Sun Jul  8 23:45:26 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Mon, 9 Jul 2007 00:45:26 -0300
Subject: [Nitro] is Orderable weird exception
Message-ID: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>

I'm trying to use the Orderable mix in and I'm getting a weird error:

/usr/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:96:in
`is': undefined method `basename' for :Orderable:Symbol
(NoMethodError)
	from /usr/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:94:in
`each'
	from /usr/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:94:in
`is'
	from ./spec/model/helper/../../../app/model/question.rb:4

class Question
  attr_accessor :text, String
  belongs_to :survey
  is Orderable, :scope => :survey # this is the offending line
end

Any ideas?

Aureliano.

From john at oxyliquit.de  Mon Jul  9 01:08:27 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Mon, 09 Jul 2007 08:08:27 +0300
Subject: [Nitro] is Orderable weird exception
In-Reply-To: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
References: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
Message-ID: <op.tu6lwdltxegpx6@jo.local>

Hi,

> I'm trying to use the Orderable mix in and I'm getting a weird error:
>
> /usr/lib/ruby/gems/1.8/gems/facets-1.8.54/lib/facets/more/paramix.rb:96:in
> `is': undefined method `basename' for :Orderable:Symbol

like before and like I explained already, Orderable as class can
not be found so Og does some magic.
Require the right file (og/model/orderable.rb) and it'll go away.

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From aurelianocalvo at yahoo.com.ar  Mon Jul  9 08:23:50 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Mon, 9 Jul 2007 09:23:50 -0300
Subject: [Nitro] is Orderable weird exception
In-Reply-To: <op.tu6lwdltxegpx6@jo.local>
References: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
	<op.tu6lwdltxegpx6@jo.local>
Message-ID: <1340963a0707090523j60de7613va9a8636fe3265534@mail.gmail.com>

> like before and like I explained already, Orderable as class can
> not be found so Og does some magic.
> Require the right file (og/model/orderable.rb) and it'll go away.

I've required the right file and this error went away but orderable is
not working :(.
It creates the position row in the database but it does not fill it.

Models:
class Question
  attr_accessor :text, String
  belongs_to :survey
  is Orderable, :scope => :survey
end

class Survey
  attr_accessor :name, String
  has_many :questions , :list => true, :order => 'position DESC'
end

Offending spec:

describe Question, "new" do

  before( :all ) do
    @your_car = Survey.create_with( :name => "your car")
  end

  it "positions should be set" do
    @like_your_car = Question.create_with( :text => "Do you like your car?")
    @your_car.questions << like_your_car
    @your_car_color = Question.create_with( :text => "What is the
color of your car?")
    @your_car.questions << your_car_color

    @like_your_car.position.should == 1 # position == null both here
and in the database.
    @your_car_color.position.should == 2
  end

  after( :each ) do
    Question.delete_all
  end

  after( :all ) do
    Survey.delete_all
  end
end

From aurelianocalvo at yahoo.com.ar  Mon Jul  9 09:31:32 2007
From: aurelianocalvo at yahoo.com.ar (Aureliano Calvo)
Date: Mon, 9 Jul 2007 10:31:32 -0300
Subject: [Nitro] is Orderable weird exception
In-Reply-To: <1340963a0707090523j60de7613va9a8636fe3265534@mail.gmail.com>
References: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
	<op.tu6lwdltxegpx6@jo.local>
	<1340963a0707090523j60de7613va9a8636fe3265534@mail.gmail.com>
Message-ID: <1340963a0707090631m5853c1easf629da16d84de76f@mail.gmail.com>

Debugging a little I've found that the code defined with before
:og_insert does not run when an entity is inserted (at least on the
test I did here). It makes the following code unreachable:

#Line 64 og/lib/og/model/orderable.rb
  before :og_insert do
    add_to_bottom()
  end

Because of it, the position is not set on insertion :(.

How can I fix it?

> Orderable is not working :(.
> It creates the position row in the database but it does not fill it.
>
> Models:
> class Question
>   attr_accessor :text, String
>   belongs_to :survey
>   is Orderable, :scope => :survey
> end
>
> class Survey
>   attr_accessor :name, String
>   has_many :questions , :list => true, :order => 'position DESC'
> end
>
> Offending spec:
>
> describe Question, "new" do
>
>   before( :all ) do
>     @your_car = Survey.create_with( :name => "your car")
>   end
>
>   it "positions should be set" do
>     @like_your_car = Question.create_with( :text => "Do you like your car?")
>     @your_car.questions << like_your_car
>     @your_car_color = Question.create_with( :text => "What is the
> color of your car?")
>     @your_car.questions << your_car_color
>
>     @like_your_car.position.should == 1 # position == null both here
> and in the database.
>     @your_car_color.position.should == 2
>   end
>
>   after( :each ) do
>     Question.delete_all
>   end
>
>   after( :all ) do
>     Survey.delete_all
>   end
> end
>

From john at oxyliquit.de  Mon Jul  9 09:44:00 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Mon, 09 Jul 2007 16:44:00 +0300
Subject: [Nitro] is Orderable weird exception
In-Reply-To: <1340963a0707090631m5853c1easf629da16d84de76f@mail.gmail.com>
References: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
	<op.tu6lwdltxegpx6@jo.local>
	<1340963a0707090523j60de7613va9a8636fe3265534@mail.gmail.com>
	<1340963a0707090631m5853c1easf629da16d84de76f@mail.gmail.com>
Message-ID: <op.tu69q2d0xegpx6@jo.local>

Hi,

> Debugging a little I've found that the code defined with before
> :og_insert does not run when an entity is inserted (at least on the
> test I did here). It makes the following code unreachable:
>
> #Line 64 og/lib/og/model/orderable.rb
>   before :og_insert do
>     add_to_bottom()
>   end
>
> Because of it, the position is not set on insertion :(.
>
> How can I fix it?

Aspects.

George:  could you _PLEASE_ have a look at that.  I just can't grok
that area.  Pretty please with sugar on top?

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From Jimmy.Jazz at gmx.net  Mon Jul  9 09:49:21 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Mon, 09 Jul 2007 15:49:21 +0200
Subject: [Nitro] about rake test
In-Reply-To: <4691612F.2030205@arnebrasseur.net>
References: <46913C70.4010102@gmx.net> <op.tu5w7dacxegpx6@jo.local>
	<4691612F.2030205@arnebrasseur.net>
Message-ID: <46923CE1.7050404@gmx.net>

Arne Brasseur a ?crit :
> Jonathan Buch schreef:
>>> * cgi/cookie doesn't work either and complains about a bad timestamp  
>>> that doesn't use the http1.1 format.
>>>     
>>
>> Yeah, but I know nothing about cookies, someone more proficient has
>> to have a look at that.  If you know what it should deliver, could
>> you propose a spec or code change to make the spec go green?
>>   
> I will fix this (since I broke it :), the problem is that Integer()
> considers the number to be octal when it starts with a zero, and 8
> isn't valid in octal. Leading zeroes need to be stripped off first.
>
> (ab)
>
> -- 
> Arne Brasseur
> http://www.arnebrasseur.net
> arne at arnebrasseur.net
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general

I'm not able to create specs ( howtos somewhere ?) but i can fight easy
bugs :)

 ([1-9]\d{2}) would do the trick

also that's probably not what you expect ;)

Jj



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070709/c56bc5fb/attachment.html 

From george.moschovitis at gmail.com  Mon Jul  9 12:07:21 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Mon, 9 Jul 2007 19:07:21 +0300
Subject: [Nitro] is Orderable weird exception
In-Reply-To: <op.tu69q2d0xegpx6@jo.local>
References: <1340963a0707082045v2708f8blb2b6bdad90bed08a@mail.gmail.com>
	<op.tu6lwdltxegpx6@jo.local>
	<1340963a0707090523j60de7613va9a8636fe3265534@mail.gmail.com>
	<1340963a0707090631m5853c1easf629da16d84de76f@mail.gmail.com>
	<op.tu69q2d0xegpx6@jo.local>
Message-ID: <afd80b540707090907j646d932eg86403556daf6293@mail.gmail.com>

>
> Aspects.
> George:  could you _PLEASE_ have a look at that.  I just can't grok
> that area.  Pretty please with sugar on top?
>

Ok, I will investigate this!

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070709/fc5bb102/attachment.html 

From Jimmy.Jazz at gmx.net  Mon Jul  9 14:19:45 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Mon, 09 Jul 2007 20:19:45 +0200
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
Message-ID: <46927C41.90907@gmx.net>

Hello,

I don't see how to mix static and dynamic aspect of nitro in an easy way.

I would like to use some nitro functionalities like in tc_element.rb:

class Box < Raw::Element
  def open
    %|<div style="color: #@color">|
  end

  def close
    "</div>"
  end
end

but Nitro seems to ignore @color wherever you declare it (controller,
template, <?r ?>, %{}, etc.). Any advice ?

I don't want to be careless. Nitro looks nice but it is finally far more
complicated to use as it looks like at first, mostly because there
aren't usable examples available to beginners. Please, don't make it to
elitist :( I'm really feeling i'm using the hard way, not to mention
nitro is using facets too.

@George: It is like deciphering the Rosetta stone to understand Egyptian
hieroglyphs writing. Easy for one who can read Greek but harder to the
other ;)

Also, nobody react to my proposal to redefine the @_children instance
variable into a class variable. I was able to access a child element
like that. Was it so silly ?


gs
-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070709/2b7eebeb/attachment.html 

From arne at arnebrasseur.net  Mon Jul  9 15:53:50 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Mon, 09 Jul 2007 21:53:50 +0200
Subject: [Nitro] how to initialize @color and make it visible into the
 template?
In-Reply-To: <46927C41.90907@gmx.net>
References: <46927C41.90907@gmx.net>
Message-ID: <4692924E.7030104@arnebrasseur.net>

Jimmy Jazz schreef:
...
> but Nitro seems to ignore @color wherever you declare it (controller, 
> template, <?r ?>, %{}, etc.). Any advice ?
Just do like this in your template: <Box color="#e3f" />.

The thing with templates that confused me in the beginning also is that 
they are rendered only once, the first time a page is loaded. So if you 
evaluate code in an element the result should always be the same, or 
generate template code.

So if you want to access instance variables set in a controller, you 
need to generate code to do that, and not do it directly.

> I don't want to be careless. Nitro looks nice but it is finally far 
> more complicated to use as it looks like at first, mostly because 
> there aren't usable examples available to beginners. Please, don't 
> make it to elitist :( I'm really feeling i'm using the hard way, not 
> to mention nitro is using facets too.
>
> @George: It is like deciphering the Rosetta stone to understand 
> Egyptian hieroglyphs writing. Easy for one who can read Greek but 
> harder to the other ;)
Well I started out here crying for documentation, but G tought it better 
to prepare 0.50 first. I still plan to start the effort of a proper 
manual, but in the meantime I'm converting tests to specs because it has 
to be done before 0.50 can be released. Also I'm quite new to Nitro 
myself, still learning as I experiment and read the sources.

I feel your pain Jimmy, it's not easy for a newbie to get up to speed 
with Nitro quickly. I'm pretty sure this will change over time, but as 
it stands things move slow. G is very busy with other stuff, and this 
also forms a bottleneck. Several questions can only adequately be 
answered by him.

But if anyone wants to contribute... most welcome. Feel free to convert 
unittests to specs, write documentation or hang out on the ML and IRC 
and help people out.

If you look at the rubyforge stats there is quite a bit of interest in 
this project, but I imagine many people struggle with it and eventually 
move on. That's just... sad, so... anyone?
>
> Also, nobody react to my proposal to redefine the @_children instance 
> variable into a class variable. I was able to access a child element 
> like that. Was it so silly ?
That way you wouldn't be able to use the same element more than once in 
a template, every instance would share the same children. I don't think 
this is what we want.

On a related note, I do have a patch in my repo 
(http://darcs.arnebrasseur.net/glycerin) that uses a facets dictionary 
to store the children. It's like a hash but with ordering, so you know 
in what order child elements occur.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From wyhaines at gmail.com  Mon Jul  9 16:08:45 2007
From: wyhaines at gmail.com (Kirk Haines)
Date: Mon, 9 Jul 2007 13:08:45 -0700
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <4692924E.7030104@arnebrasseur.net>
References: <46927C41.90907@gmx.net> <4692924E.7030104@arnebrasseur.net>
Message-ID: <f4cd26df0707091308m6e8d7e04g7adb49d339702312@mail.gmail.com>

On 7/9/07, Arne Brasseur <arne at arnebrasseur.net> wrote:
> Jimmy Jazz schreef:
> ...
> > but Nitro seems to ignore @color wherever you declare it (controller,
> > template, <?r ?>, %{}, etc.). Any advice ?
> Just do like this in your template: <Box color="#e3f" />.
>
> The thing with templates that confused me in the beginning also is that
> they are rendered only once, the first time a page is loaded. So if you
> evaluate code in an element the result should always be the same, or
> generate template code.
>
> So if you want to access instance variables set in a controller, you
> need to generate code to do that, and not do it directly.

I've read this a couple of times, but I think I still need it
explained to me a bit more, because I am not quite sure I understand.

Let's say I have something....an online community site of some sort.
I want to have a little box in one corner of the page that shows the
time and date, whether the user has any new messages in their mailbox,
and some other stuff that may change regularly.

To be nice and modular, I want to have something like this in my page template:

<InfoBox foo="bar" blah="snog" whatever="snow white" />

InfoBox is that thing with all that information.

Now, in InfoBox's template, are you saying that all the content has to
be generated programatically, because that template will only ever be
rendered once, so I can't just dynamically include data generated a
method call into it?  Or do I misunderstand you?


Kirk Haines

From arne at arnebrasseur.net  Mon Jul  9 16:36:10 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Mon, 09 Jul 2007 22:36:10 +0200
Subject: [Nitro] how to initialize @color and make it visible into the
 template?
In-Reply-To: <f4cd26df0707091308m6e8d7e04g7adb49d339702312@mail.gmail.com>
References: <46927C41.90907@gmx.net> <4692924E.7030104@arnebrasseur.net>
	<f4cd26df0707091308m6e8d7e04g7adb49d339702312@mail.gmail.com>
Message-ID: <46929C3A.3060906@arnebrasseur.net>

Kirk Haines schreef:
>> So if you want to access instance variables set in a controller, you
>> need to generate code to do that, and not do it directly.
>>     
>
> I've read this a couple of times, but I think I still need it
> explained to me a bit more, because I am not quite sure I understand.
>
> Let's say I have something....an online community site of some sort.
> I want to have a little box in one corner of the page that shows the
> time and date, whether the user has any new messages in their mailbox,
> and some other stuff that may change regularly.
>
> To be nice and modular, I want to have something like this in my page template:
>
> <InfoBox foo="bar" blah="snog" whatever="snow white" />
>
> InfoBox is that thing with all that information.
>
> Now, in InfoBox's template, are you saying that all the content has to
> be generated programatically, because that template will only ever be
> rendered once, so I can't just dynamically include data generated a
> method call into it?  Or do I misunderstand you?
>   
I will give an example. Suppose your InfoBox depends on a user, if you 
want to write this in your template:

<InfoBox user="@u" />

Then you have to do something like this to make it work

class InfoBox
  def render
    "<div class="infobox">Unread messages : \#{#{@user}.unread_messages}"
  end
end

The first time the page gets rendered an InfoBox instance is created, 
and the instance variable @user is set to the string "@u". The render 
method is called yielding:

    "<div class="infobox">Unread messages : #{@user.unread_messages}"

This becomes part of your compiled template, which utilizes the @user 
var set in your controller. Note how the outer interpolation is escaped 
: \#{

This is what I came up with, and I think it's messy, but it works. 
Having talked about it a bit on IRC with Manveru and Jonathan I get the 
impression this is not the primary usecase. You can also use it to 
rewrite the part of your template inside the tag. Looked at it this way 
you can add custom preprocessing to whatever is inside 
<Element>...</Element>. Manveru called it 'Aspect oriented programming 
for templates'. It 'wraps' a piece of your template, doing stuff with it.

For the InfoBox usecase, judging from the blog example I'd say G prefers 
to use <?include href="infobox" ?> which just reminds me too much of 
rails partials, but even worse. Elements seem so nice and clean for this 
on first sight, but the fact that they're rendered only once makes it 
cumbersome. Maybe we need another compiler filter for 'dynamic' elements?

This is one of the things where I'm very curious myself what their 
primary intended use is. Maybe G or manv or Jo or someone else could 
give more good examples of their usefulness, including what to do with 
the @_children.

One idea I had was to declare 'widgets' with besides the render method 
also have a css and a javascript method. the outer Page element joins 
all the css and javascript together and puts it in the header, creating 
reusable components (sort of).

Any other wild ideas? Insights?

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070709/c5d761f4/attachment.html 

From george.moschovitis at gmail.com  Tue Jul 10 01:33:37 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 08:33:37 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <46927C41.90907@gmx.net>
References: <46927C41.90907@gmx.net>
Message-ID: <afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>

>
> class Box < Raw::Element
>   def open
>     %|<div style="color: #@color">|
>   end
>
>   def close
>     "</div>"
>   end
> end
>


Elements are evaluated at "compile time" ie when the page is loaded for the
first time. However, you can  achieve dynamic effects, let me give you an
example:

class Box < Raw::Element
   def render
      %{
      <div style="color: \#{@color}">
        #{content}
      </div>
      }
   end
end

then use it like this:

<?r
colors = [ "#ff0", "#f00", "#00f", #"0ff" ]
?>
<h1>Dynamic boxes</h1>

<Box color="colors[rand(colors.size)]">
   This box is randomly colored ;-)
</Box>


-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/254efba8/attachment.html 

From george.moschovitis at gmail.com  Tue Jul 10 01:38:34 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 08:38:34 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
Message-ID: <afd80b540707092238w55c2e90fka17feae3358ce628@mail.gmail.com>

>
>       <div style="color: \#{@color}">
>

Please note I am using \#{} instead of @{} !

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/a1b9b88e/attachment.html 

From george.moschovitis at gmail.com  Tue Jul 10 01:40:27 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 08:40:27 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <4692924E.7030104@arnebrasseur.net>
References: <46927C41.90907@gmx.net> <4692924E.7030104@arnebrasseur.net>
Message-ID: <afd80b540707092240x1739d89cua35073a9450baf84@mail.gmail.com>

>
> On a related note, I do have a patch in my repo
> (http://darcs.arnebrasseur.net/glycerin) that uses a facets dictionary
> to store the children. It's like a hash but with ordering, so you know
> in what order child elements occur.
>

Nice idea, just fixed this in  my code too.

-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/fee05772/attachment.html 

From john at oxyliquit.de  Tue Jul 10 02:32:38 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 10 Jul 2007 09:32:38 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <46927C41.90907@gmx.net>
References: <46927C41.90907@gmx.net>
Message-ID: <op.tu8kdo0axegpx6@jo.local>

Hi,

(late, my internet died at home..)

> I don't see how to mix static and dynamic aspect of nitro in an easy way.
>
> I would like to use some nitro functionalities like in tc_element.rb:
>
> class Box < Raw::Element
>   def open
>     %|<div style="color: #@color">|
>   end
> end
>
> but Nitro seems to ignore @color wherever you declare it (controller,
> template, <?r ?>, %{}, etc.). Any advice ?

I'm unsure what %|| means, but I'm guessing that it means "" (double
quotes).  "#{@color}" in this context means, the instance variable
@color from the _Box_ instance.  Depending on where you defined that
variable (probably in your controller), you have to get the instance
variable from the _Controller_ instance.

So, what you want is to get the @color variable resolved in the
controller scope (which is also the template scope).

You do that by escaping.   "\#{@color}", this saves the string
"#{@color}" back to the template, which then gets normally executed
like you had written #{@color} in the template.

I's just a matter of scope here.

> I don't want to be careless. Nitro looks nice but it is finally far more
> complicated to use as it looks like at first, mostly because there
> aren't usable examples available to beginners. Please, don't make it to
> elitist :( I'm really feeling i'm using the hard way, not to mention
> nitro is using facets too.

Well, we aren't actually working on making Nitro elitist.  ;)  It's just
that very few people are working on making it less elitist (meaning docs,
tutorials, examples).
This is a cycle, no people no docs, no docs no people.  Which also means,
anybody can help break that cycle, simply by writing down your own
experience, like a small tutorial on what you find important to know
as a beginner.
The second is, fast development cycle means docs are out of date fast,
so, few people to keep them up to date, which means bad docs, which also
creates problems for beginners.  So, we need more stable people who
constantly update docs.  Hard, very.
I'm far beyond the beginner levels sadly and can't really forsee what
beginners need, but at least I try to help.  :)

> @George: It is like deciphering the Rosetta stone to understand Egyptian
> hieroglyphs writing. Easy for one who can read Greek but harder to the
> other ;)
>
> Also, nobody react to my proposal to redefine the @_children instance
> variable into a class variable. I was able to access a child element
> like that. Was it so silly ?

Well, class variables are like $globals, just with a different scope.
That means, those are shared over all instances, if you change it in
one, it changes for all.  This might work when there are no threads
involved, but will fail with more than one concurrent thread.

Note, I don't know anything about the @_children instance variable,
so I can't say something about that.

Everything in Ruby or any other programming language is a matter
of scope, try to think 'where does this variable appear, where
am I now, can I access this variable from the current scope?'.
If the variable can't be accessed from the current scope, there's
two possibilities, bring the foreign scope to the current one,
or bring the 'execution' of the variable to the foreign scope.

Hope that helps,

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Tue Jul 10 02:37:53 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 10 Jul 2007 09:37:53 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
Message-ID: <op.tu8kpfsrxegpx6@jo.local>

Hi,

>       <div style="color: \#{@color}">
> <?r colors = [ "#ff0", "#f00", "#00f", #"0ff" ] ?>
> <Box color="colors[rand(colors.size)]">

are you sure?  `colors[rand(colors.size)]` will have to be eval'ed
somewhere, where is that done?  Either magic or one has to do that
in the Element oneselve (probably with a binding to the controller
scope again).

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Tue Jul 10 02:39:29 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 10 Jul 2007 09:39:29 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <afd80b540707092240x1739d89cua35073a9450baf84@mail.gmail.com>
References: <46927C41.90907@gmx.net> <4692924E.7030104@arnebrasseur.net>
	<afd80b540707092240x1739d89cua35073a9450baf84@mail.gmail.com>
Message-ID: <op.tu8kr3izxegpx6@jo.local>

Hi,

>> On a related note, I do have a patch in my repo
>> (http://darcs.arnebrasseur.net/glycerin) that uses a facets dictionary
>> to store the children. It's like a hash but with ordering, so you know
>> in what order child elements occur.
>>
>
> Nice idea, just fixed this in  my code too.

then either of you has to eradicate his patch and pull the other one
to not create conflicts. :)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Tue Jul 10 02:39:49 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 09:39:49 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <op.tu8kpfsrxegpx6@jo.local>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
	<op.tu8kpfsrxegpx6@jo.local>
Message-ID: <afd80b540707092339w8c0e0f3yfdc3fc017ef08d47@mail.gmail.com>

the element will generate this code:

<div style="color: #{colors[rand(colors.size)]}">...</div>

which does what you want.

-g.

On 7/10/07, Jonathan Buch <john at oxyliquit.de> wrote:
>
> Hi,
>
> >       <div style="color: \#{@color}">
> > <?r colors = [ "#ff0", "#f00", "#00f", #"0ff" ] ?>
> > <Box color="colors[rand(colors.size)]">
>
> are you sure?  `colors[rand(colors.size)]` will have to be eval'ed
> somewhere, where is that done?  Either magic or one has to do that
> in the Element oneselve (probably with a binding to the controller
> scope again).
>
> Jo
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/9e9a3ae3/attachment-0001.html 

From john at oxyliquit.de  Tue Jul 10 02:44:36 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 10 Jul 2007 09:44:36 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <afd80b540707092339w8c0e0f3yfdc3fc017ef08d47@mail.gmail.com>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
	<op.tu8kpfsrxegpx6@jo.local>
	<afd80b540707092339w8c0e0f3yfdc3fc017ef08d47@mail.gmail.com>
Message-ID: <op.tu8k0mdsxegpx6@jo.local>

Hi,

>> >       <div style="color: \#{@color}">

> the element will generate this code:
>
> <div style="color: #{colors[rand(colors.size)]}">...</div>

I don't think it does, I think it would be more like

>> >       <div style="color: \#{#{@color}}">

to paste the text correctly back to the template.  And no, I don't
really find it that visually pleasing.  :P

>> > <?r colors = [ "#ff0", "#f00", "#00f", #"0ff" ] ?>
>> > <Box color="colors[rand(colors.size)]">

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Tue Jul 10 02:55:55 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 09:55:55 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <op.tu8k0mdsxegpx6@jo.local>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
	<op.tu8kpfsrxegpx6@jo.local>
	<afd80b540707092339w8c0e0f3yfdc3fc017ef08d47@mail.gmail.com>
	<op.tu8k0mdsxegpx6@jo.local>
Message-ID: <afd80b540707092355l50a35513y837c96222ea1ad29@mail.gmail.com>

>
> >> >       <div style="color: \#{#{@color}}">
>

hmm, thats what happens when you try to anwser emails before breakfast ;-)
you are right.

we could abstract this by means of a helper method 'var', like this:

<div style="color: #{val(:color)}">

where

def var(sym)
  %|\#{#{instance_variable_get("@#{sym}")}}|
end
(i hope the above is right, still no breakfast ;-) )

any good name suggestions for the 'var' helper method?


-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/73e284b8/attachment.html 

From george.moschovitis at gmail.com  Tue Jul 10 02:57:25 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 09:57:25 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <afd80b540707092355l50a35513y837c96222ea1ad29@mail.gmail.com>
References: <46927C41.90907@gmx.net>
	<afd80b540707092233n16ae0061l2b450f5479f962d8@mail.gmail.com>
	<op.tu8kpfsrxegpx6@jo.local>
	<afd80b540707092339w8c0e0f3yfdc3fc017ef08d47@mail.gmail.com>
	<op.tu8k0mdsxegpx6@jo.local>
	<afd80b540707092355l50a35513y837c96222ea1ad29@mail.gmail.com>
Message-ID: <afd80b540707092357i454509a1mc72fe42636367061@mail.gmail.com>

>
>
> <div style="color: #{val(:color)}">
>

even nicer:

<div style="color: #{var :color}">

but we need a better name for 'var'

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/0f3f063b/attachment.html 

From john at oxyliquit.de  Tue Jul 10 12:19:00 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 10 Jul 2007 19:19:00 +0300
Subject: [Nitro] Current Oxyliquit repo status
Message-ID: <op.tu8980yrxegpx6@jo.local>

Hi,

news from my repo[1].  I pushed a bunch of patches from my own repo.
All are only cleanup or bugfix patches.  Some of them add 'expected'
behaviour, some just remove minor glitches.

They are mostly extracted from my 'uber different' working repo, I
hope didn't screw up porting them.  None are really earth-shattering,
but the sheer amount worries me a little.

I hope Arne and George (or really anyone) can have a look at them
before George pulls them to the final repo.

Jo

[1] http://oxywtf.de/~john/darcs_repos/glycerin

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Tue Jul 10 14:42:03 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 21:42:03 +0300
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <op.tu8980yrxegpx6@jo.local>
References: <op.tu8980yrxegpx6@jo.local>
Message-ID: <afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>

Thanks for the report! ;-)

-g.

On 7/10/07, Jonathan Buch <john at oxyliquit.de> wrote:
>
> Hi,
>
> news from my repo[1].  I pushed a bunch of patches from my own repo.
> All are only cleanup or bugfix patches.  Some of them add 'expected'
> behaviour, some just remove minor glitches.
>
> They are mostly extracted from my 'uber different' working repo, I
> hope didn't screw up porting them.  None are really earth-shattering,
> but the sheer amount worries me a little.
>
> I hope Arne and George (or really anyone) can have a look at them
> before George pulls them to the final repo.
>
> Jo
>
> [1] http://oxywtf.de/~john/darcs_repos/glycerin
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/6cd51cc3/attachment.html 

From arne at arnebrasseur.net  Tue Jul 10 15:23:43 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Tue, 10 Jul 2007 21:23:43 +0200
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>
References: <op.tu8980yrxegpx6@jo.local>
	<afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>
Message-ID: <4693DCBF.4030500@arnebrasseur.net>

I will have a look, probably over the weekend. Here's my report, please 
apply or reject and explain.

Thx,
(ab)

Sun Jul  8 13:41:30 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Converted request testcase, deleted adapter/tc_webrick stub

Sun Jul  8 13:46:49 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Deleted test/adapter/raw_post1.bin

Sun Jul  8 13:54:49 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * In og specs : setup->before, added og_teardown

Sun Jul  8 14:37:59 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Converted mounter (4 pass) and compiler (1 fails)

Sun Jul  8 14:40:22 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Minor cosmetics (style convention)

Mon Jul  9 18:47:08 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Fixed cookie spec, see ML 08-07-07

Mon Jul  9 18:54:53 CEST 2007  Arne Brasseur <arne at arnebrasseur.net>
  * Fix endless loop in error handling


George Moschovitis schreef:
> Thanks for the report! ;-)
>
> -g.
>
> On 7/10/07, *Jonathan Buch* <john at oxyliquit.de 
> <mailto:john at oxyliquit.de>> wrote:
>
>     Hi,
>
>     news from my repo[1].  I pushed a bunch of patches from my own repo.
>     All are only cleanup or bugfix patches.  Some of them add 'expected'
>     behaviour, some just remove minor glitches.
>
>     They are mostly extracted from my 'uber different' working repo, I
>     hope didn't screw up porting them.  None are really earth-shattering,
>     but the sheer amount worries me a little.
>
>     I hope Arne and George (or really anyone) can have a look at them
>     before George pulls them to the final repo.
>
>     Jo
>
>     [1] http://oxywtf.de/~john/darcs_repos/glycerin
>     <http://oxywtf.de/%7Ejohn/darcs_repos/glycerin>
>
>     --
>     Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>     _______________________________________________
>     Nitro-general mailing list
>     Nitro-general at rubyforge.org <mailto:Nitro-general at rubyforge.org>
>     http://rubyforge.org/mailman/listinfo/nitro-general
>
>
>
>
> -- 
> http://phidz.com
> http://blog.gmosx.com
> http://cull.gr
> http://www.joy.gr
> http://nitroproject.org
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general


-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/c73757b9/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patches_20070710ab.patch
Url: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/c73757b9/attachment-0001.pl 

From george.moschovitis at gmail.com  Tue Jul 10 15:40:10 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 10 Jul 2007 22:40:10 +0300
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <4693DCBF.4030500@arnebrasseur.net>
References: <op.tu8980yrxegpx6@jo.local>
	<afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>
	<4693DCBF.4030500@arnebrasseur.net>
Message-ID: <afd80b540707101240s489790d2hfc4c890a295ebae1@mail.gmail.com>

please, remind me the url of your repo.

-g.

On 7/10/07, Arne Brasseur <arne at arnebrasseur.net> wrote:
>
>  I will have a look, probably over the weekend. Here's my report, please
> apply or reject and explain.
>
> Thx,
> (ab)
>
> Sun Jul  8 13:41:30 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Converted request testcase, deleted adapter/tc_webrick stub
>
> Sun Jul  8 13:46:49 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Deleted test/adapter/raw_post1.bin
>
> Sun Jul  8 13:54:49 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * In og specs : setup->before, added og_teardown
>
> Sun Jul  8 14:37:59 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Converted mounter (4 pass) and compiler (1 fails)
>
> Sun Jul  8 14:40:22 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Minor cosmetics (style convention)
>
> Mon Jul  9 18:47:08 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Fixed cookie spec, see ML 08-07-07
>
> Mon Jul  9 18:54:53 CEST 2007  Arne Brasseur <arne at arnebrasseur.net><arne at arnebrasseur.net>
>   * Fix endless loop in error handling
>
>
> George Moschovitis schreef:
>
> Thanks for the report! ;-)
>
> -g.
>
> On 7/10/07, Jonathan Buch <john at oxyliquit.de> wrote:
> >
> > Hi,
> >
> > news from my repo[1].  I pushed a bunch of patches from my own repo.
> > All are only cleanup or bugfix patches.  Some of them add 'expected'
> > behaviour, some just remove minor glitches.
> >
> > They are mostly extracted from my 'uber different' working repo, I
> > hope didn't screw up porting them.  None are really earth-shattering,
> > but the sheer amount worries me a little.
> >
> > I hope Arne and George (or really anyone) can have a look at them
> > before George pulls them to the final repo.
> >
> > Jo
> >
> > [1] http://oxywtf.de/~john/darcs_repos/glycerin<http://oxywtf.de/%7Ejohn/darcs_repos/glycerin>
> >
> > --
> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> > _______________________________________________
> > Nitro-general mailing list
> > Nitro-general at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/nitro-general
> >
>
>
>
> --
> http://phidz.com
> http://blog.gmosx.com
> http://cull.gr
> http://www.joy.gr
> http://nitroproject.org
>
> ------------------------------
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.orghttp://rubyforge.org/mailman/listinfo/nitro-general
>
>
>
> --
> Arne Brasseur
> http://www.arnebrasseur.netarne at arnebrasseur.net
>
>
>
> New patches:
>
> [Converted request testcase, deleted adapter/tc_webrick stub
> Arne Brasseur <arne at arnebrasseur.net>**20070708114130] {
> adddir ./raw/spec/context
> move ./raw/test/nitro/cgi/tc_request.rb ./raw/spec/context/request.rb
> hunk ./raw/spec/context/request.rb 1
> -require File.join(File.dirname(__FILE__), '..', 'CONFIG.rb')
> +require "script/lib/spec"
> hunk ./raw/spec/context/request.rb 3
> -require 'test/unit'
> +require "raw/context/request"
> hunk ./raw/spec/context/request.rb 5
> -require 'nitro/cgi/request'
> -
> -class TC_Request < Test::Unit::TestCase # :nodoc: all
> -  class DummyRequest
> -    include Nitro::Request
> -
> -    def initialize
> -      @headers = {}
> -      @params = {}
> +module Raw
> +  describe Request do
> +    class DummyRequest
> +      include Request
> +
> +      def initialize
> +        @headers = {}
> +        @post_params = @get_params = {}
> +      end
> hunk ./raw/spec/context/request.rb 15
> -  end
> hunk ./raw/spec/context/request.rb 16
> -  def test_all
> -    req = DummyRequest.new
> +    before do
> +      @req = DummyRequest.new
> +    end
> hunk ./raw/spec/context/request.rb 20
> -    req.headers['HTTP_HOST'] = 'www.nitroproject.org'
> -    assert_equal 'nitroproject.org', req.domain
> -    assert_equal 'www', req.subdomains.first
> -
> -    req.headers['HTTP_HOST'] = 'www.nitroproject.co.uk'
> -    assert_equal 'nitroproject.co.uk', req.domain(2)
> +    it "should split the hostname into domain / subdomains" do
> +      @req.headers['HTTP_HOST'] = 'www.nitroproject.org'
> hunk ./raw/spec/context/request.rb 23
> -    req.headers['HTTP_X_REQUESTED_WITH'] = 'XMLHttpRequest'
> -    assert req.xhr?
> +      @req.domain.should == "nitroproject.org"
> +      @req.subdomains.first.should == "www"
> +    end
> hunk ./raw/spec/context/request.rb 27
> -    req.headers['REQUEST_METHOD'] = 'POST'
> -
> -    req.headers['CONTENT_TYPE'] = 'application/x-yaml'
> -    assert req.yaml_post?
> -
> -    req.instance_variable_set '@post_format', nil
> -    req.headers['CONTENT_TYPE'] = 'text/xml'
> -    assert req.xml_post?
> -
> -    req['test'] = 'hello'
> -    assert req['test']
> -    assert_equal 'hello', req['test']
> -    assert req.has?('test')
> +    it "should support different top level domain lengths" do
> +      @req.headers['HTTP_HOST'] = 'www.nitroproject.co.uk'
> +      @req.domain(2).should == "nitroproject.co.uk"
> +    end
> +
> +    it "should set the xhr? predicate if requested with XMLHttpRequest"
> do
> +      @req.headers['HTTP_X_REQUESTED_WITH'] = 'XMLHttpRequest'
> +      @req.xhr?.should == true
> +    end
> +
> +    it "should find out that it's a POST with content type
> application/x-yaml and report this via Request#yaml_post? " do
> +      @req.headers['REQUEST_METHOD'] = 'POST'
> +      @req.headers['CONTENT_TYPE'] = 'application/x-yaml'
> +      @req.yaml_post?.should == true
> +    end
> +
> +    it "should find out that it's a POST with content type text/xml and
> report this via Request#xml_post? " do
> +      @req.headers['REQUEST_METHOD'] = 'POST'
> +      @req.headers['CONTENT_TYPE'] = 'text/xml'
> +      @req.xml_post?.should == true
> +    end
> +
> +    it "should behave like a hash with #[], #[]= and #has?" do
> +      @req.headers['REQUEST_METHOD'] = 'GET'
> +      @req['test'] = 'hello'
> +      @req['test'].should_not be_nil
> +      @req['test'].should == "hello"
> +      @req.has?('test').should == true
> hunk ./raw/spec/context/request.rb 56
> -    assert !req.has?('phantom')
> +      @req.has?('phantom').should == false
> hunk ./raw/spec/context/request.rb 58
> -    req['bug'] = nil
> -    assert !req.has?('bug')
> -  end
> +      @req['bug'] = nil
> +      @req.has?('bug').should == true
> +    end
> hunk ./raw/spec/context/request.rb 62
> -  def test_local_net?
> -    req = DummyRequest.new
> +    it "should recognize IP addresses intended for private use" do
> +      local_ips = ["192.168.1.1", "192.168.20.1", "192.168.99.1", "
> 192.168.200.1", "192.168.21.245", "192.168.90.34", "192.168.254.254", "
> 172.16.1.1", "172.18.1.1", "172.31.254.1", "172.21.1.254", "10.16.1.1", "
> 10.0.1.1", "10.254.1.254", "10.192.1.192", "10.254.254.254", "10.10.10.10
> "]
> +      local_ips.map { |ip| @req.local_net?(ip) }.all?.should == true
> +    end
> hunk ./raw/spec/context/request.rb 67
> -    local_ips = ["192.168.1.1", "192.168.20.1", "192.168.99.1", "
> 192.168.200.1", "192.168.21.245", "192.168.90.34", "192.168.254.254", "
> 172.16.1.1", "172.18.1.1", "172.31.254.1", "172.21.1.254", "10.16.1.1", "
> 10.0.1.1", "10.254.1.254", "10.192.1.192", "10.254.254.254", "10.10.10.10
> "]
> +    it "should recognize public IP addresses" do
> +      not_local_ips = ["191.168.1.1", "192.169.20.1", "193.168.254.254",
> "172.15.1.1", "171.18.1.1", "172.32.0.0", "173.21.1.254", "11.16.1.1", "
> 66.249.93.104", "72.14.221.104", "66.102.9.104", "17.254.3.183", "
> 207.46.250.119", "207.46.130.108", "207.68.160.190", "65.54.240.126", "
> 213.199.144.151", "65.55.238.126"]
> +
> hunk ./raw/spec/context/request.rb 71
> -    not_local_ips = ["191.168.1.1", "192.169.20.1", "193.168.254.254", "
> 172.15.1.1", "171.18.1.1", "172.32.0.0", "173.21.1.254", "11.16.1.1", "
> 66.249.93.104", "72.14.221.104", "66.102.9.104", "17.254.3.183", "
> 207.46.250.119", "207.46.130.108", "207.68.160.190", "65.54.240.126", "
> 213.199.144.151", "65.55.238.126"]
> +      not_local_ips.map { |ip| ! @req.local_net?(ip) }.all?.should ==
> true
> +    end
> hunk ./raw/spec/context/request.rb 74
> -    assert_equal true, local_ips.map { |ip| req.local_net?(ip) }.all?
> -    assert_equal true, not_local_ips.map { |ip| req.local_net?(ip)
> }.all?{|v|!v}
> +    after do
> +      @req = nil
> +    end
> hunk ./raw/test/nitro/adapter/tc_webrick.rb 1
> -require File.join(File.dirname(__FILE__), '..', 'CONFIG.rb')
> -
> -require 'test/unit'
> -require 'ostruct'
> -
> -require 'glue'
> -require 'nitro'
> -require 'nitro/adapter/webrick'
> -
> -class TC_AdaptersWebrick < Test::Unit::TestCase # :nodoc: all
> -  include Nitro
> -
> -  def test_adaptor
> -  end
> -
> -end
> rmfile ./raw/test/nitro/adapter/tc_webrick.rb
> }
>
> [Deleted test/adapter/raw_post1.bin
> Arne Brasseur <arne at arnebrasseur.net>**20070708114649] {
> hunk ./raw/test/nitro/adapter/raw_post1.bin 1
> ------------------------------277124474474241471962886717
> -Content-Disposition: form-data; name="title"
> -
> -dsadsad
> ------------------------------277124474474241471962886717
> -Content-Disposition: form-data; name="file"; filename="nitro.png"
> -Content-Type: image/png
> -
> -?PNG
> rmfile ./raw/test/nitro/adapter/raw_post1.bin
> rmdir ./raw/test/nitro/adapter
> }
>
> [In of specs : setup->before, added og_teardown
> Arne Brasseur <arne at arnebrasseur.net>**20070708115449] {
> hunk ./og/spec/accumulator.rb 8
> -  setup do
> +  before do
> hunk ./og/spec/accumulator.rb 89
> +  after do
> +    og_teardown(@store)
> +  end
> +
> hunk ./og/spec/adapter_quoted_column.rb 7
> -  setup do
> +  before do
> hunk ./og/spec/adapter_quoted_column.rb 65
> +  after do
> +    og_teardown(@store)
> +  end
> hunk ./og/spec/aggregations_calculations.rb 8
> -  setup do
> +  before do
> hunk ./og/spec/aggregations_calculations.rb 44
> +
> +  after do
> +    og_teardown(@store)
> +  end
> hunk ./og/spec/model/revisable.rb 60
> +
> +  after do
> +    og_teardown(@store)
> +  end
> }
>
> [Converted mounter (4 pass) and compiler (1 fails)
> Arne Brasseur <arne at arnebrasseur.net>**20070708123759] {
> move ./raw/test/nitro/compiler/tc_compiler.rb ./raw/spec/compiler.rb
> move ./raw/test/nitro/dispatcher/tc_mounter.rb
> ./raw/spec/dispatcher/mounter.rb
> rmdir ./raw/test/nitro/cgi
> rmdir ./raw/test/nitro/dispatcher
> hunk ./raw/lib/raw/compiler/filter/template.rb 1
> +require "facets/more/settings"
> +
> hunk ./raw/lib/raw/dispatcher.rb 8
> +require "raw/controller/publishable"
> +
> hunk ./raw/spec/compiler.rb 1
> -require File.join(File.dirname(__FILE__), '..', 'CONFIG.rb')
> +require "script/lib/spec"
> hunk ./raw/spec/compiler.rb 3
> -require 'test/unit'
> +require "raw/controller"
> hunk ./raw/spec/compiler.rb 5
> -require 'nitro/test/testcase'
> +#FIXME : This is a verbatim conversion from Test::Unit, it no longer runs
> +#FIXME : Add more specs to document how the compiler works
> hunk ./raw/spec/compiler.rb 8
> -require 'nitro'
> -require 'nitro/test/context'
> +module Raw
> +  describe Compiler do
> +    class TestController < Controller
> +      def test(arg1, arg2); end
> +    end
> hunk ./raw/spec/compiler.rb 14
> -class TC_Compiler < Test::Unit::TestCase
> -  class TestController < Nitro::Controller
> -    def test(arg1, arg2); end
> -  end
> +    before do
> +      Server.map['/'] = TestController
> +      reset_context()
> +    end
> hunk ./raw/spec/compiler.rb 19
> -  def setup
> -    Server.map['/'] = TestController
> -    reset_context()
> -  end
> +    it "should raise nothing when no param specified" do
> +
> +      lambda do
> +        process(:uri => '/test/two')
> +      end.should_not raise_error(Exception=nil, message=nil)
> hunk ./raw/spec/compiler.rb 25
> -  def test_no_param_specified
> -    assert_nothing_raised do
> -      process(:uri => '/test/two')
> hunk ./raw/spec/compiler.rb 26
> +
> hunk ./raw/spec/dispatcher/mounter.rb 1
> -require File.join(File.dirname(__FILE__), "..", "CONFIG.rb")
> +require "script/lib/spec"
> hunk ./raw/spec/dispatcher/mounter.rb 3
> -require "test/unit"
> +require "raw/dispatcher"
> hunk ./raw/spec/dispatcher/mounter.rb 5
> -require "nitro/dispatcher"
> +module Nitro
> +  STANDARD_FORMATS=[]
> hunk ./raw/spec/dispatcher/mounter.rb 8
> -class TC_DispatcherMounter < Test::Unit::TestCase # :nodoc: all
> -
> -  include Nitro
> -
> -  class RootController
> -  end
> -
> -  class LinkController
> -  end
> -
> -  class LinkCommentController
> -  end
> -
> -  class UserController
> +  def Nitro.proto_path
> +    ''
> hunk ./raw/spec/dispatcher/mounter.rb 11
> +end
> +
> +module Raw
> +  describe Dispatcher::Mounter do
> +    RootController = Class.new
> +    LinkController = Class.new
> +    LinkCommentController = Class.new
> +    UserController = Class.new
> +
> hunk ./raw/spec/dispatcher/mounter.rb 21
> -  def setup
> -    @d = Dispatcher.new
> -  end
> +    before do
> +      @d = Dispatcher.new
> +    end
> hunk ./raw/spec/dispatcher/mounter.rb 25
> -  def teardown
> -    @d = nil
> -  end
> +    after do
> +      @d = nil
> +    end
> hunk ./raw/spec/dispatcher/mounter.rb 29
> -  def test_mount
> -    @d.root = RootController
> -    assert_equal RootController, @d["/"]
> +    it "should mount '/' with #root=" do
> +      @d.root = RootController
> +      @d["/"].should == RootController
> +    end
> hunk ./raw/spec/dispatcher/mounter.rb 34
> -    @d.root.links = LinkController
> -    assert_equal LinkController, @d["/links"]
> -    assert_equal RootController, LinkController.ann(:self, :parent)
> +    it "should mount at a path based on the method name" do
> +      @d.root = RootController
> +      @d.root.links = LinkController
> +      @d["/links"].should == LinkController
> +    end
> hunk ./raw/spec/dispatcher/mounter.rb 40
> -    @d.root.links.comments = LinkCommentController
> -    assert_equal LinkCommentController, @d["/links/comments"]
> -    assert_equal LinkController, LinkCommentController.ann(:self,
> :parent)
> +    it "should store the parent controller as an annotation on the child"
> do
> +      @d.root = RootController
> +      @d.root.links = LinkController
> +      LinkController.ann(:self, :parent).should == RootController
> hunk ./raw/spec/dispatcher/mounter.rb 45
> -    @d.root.users = UserController
> -    assert_equal UserController, @d["/users"]
> -  end
> +      @d.root.links.comments = LinkCommentController
> +      @d["/links/comments"].should == LinkCommentController
> +      LinkCommentController.ann(:self, :parent).should == LinkController
> +    end
> +
> +    it "should allow multiple paths at the same level" do
> +      @d.root = RootController
> +      @d.root.links = LinkController
> +      @d.root.users = UserController
> +      @d["/users"].should == UserController
> +      @d["/links"].should == LinkController
> +    end
> hunk ./raw/spec/dispatcher/mounter.rb 58
> +  end
> }
>
> [Minor cosmetics (style convention)
> Arne Brasseur <arne at arnebrasseur.net>**20070708124022] {
> hunk ./raw/spec/context.rb 2
> -require 'ostruct'
> +require "ostruct"
> hunk ./raw/spec/context.rb 4
> -require 'raw'
> +require "raw"
> }
>
> [Fixed cookie spec, see ML 08-07-07
> Arne Brasseur <arne at arnebrasseur.net>**20070709164708] {
> hunk ./raw/spec/cgi/cookie.rb 26
> -        wkday, day, month, year, hour, minute = $1, Integer($2), $3,
> Integer($4), Integer($5), Integer($6)
> +        wkday, day, month  = $1, $2.to_i, $3
> +        year, hour, minute = $4.to_i, $5.to_i, $6.to_i
> +
> }
>
> [Fix endless loop in error handling
> Arne Brasseur <arne at arnebrasseur.net>**20070709165453] {
> hunk ./raw/lib/raw/controller/render.rb 218
> -  #--
> -  # gmosx, TODO: add check for infinite loops here.
> -  #++
> -
> +  # ---
> +  # Return if already handling an error, to avoid endless loop
> +  # +++
> +
> hunk ./raw/lib/raw/controller/render.rb 223
> +    return if @context.status >= 400 && @context.status <= 599
> +
> }
>
> Context:
>
> [[og] better error reportin in joins_many + nil-bugfix
> Jonathan Buch <jo at helloit.fi>**20070707180158]
> [Fixed forced Og bug [rmela].
> George Moschovitis <george.moschovitis at gmail.com>**20070704080541]
> [Fixed pager helper. test for ancestors.include? Og::Model.
> George Moschovitis <george.moschovitis at gmail.com>**20070702091037]
> [Glycerin script for the blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070702084425]
> [Moved some files around.
> George Moschovitis <george.moschovitis at gmail.com>**20070702084404]
> [Fixed IfMorpher, def self.key;"each";end -> def self.key;"if";end
> Arne Brasseur <arne at arnebrasseur.net>**20070630100213]
> [Raw::Pager spec fixup, green
> Jonathan Buch <jo at helloit.fi>**20070628193214]
> [Brainless test-to-spec : controller/aspects, view/pager
> Arne Brasseur <arne at arnebrasseur.net>**20070627211336]
> [Typo: ribust -> robust
> Arne Brasseur <arne at arnebrasseur.net>**20070627172742]
> [Mark mysql error as error, not info.
> George Moschovitis <george.moschovitis at gmail.com>**20070627122029]
> [Small improvements in the blog example. Added glycerin.rb helper script.
> :w
> George Moschovitis <george.moschovitis at gmail.com>**20070627121854]
> [Written skeleton of doc/RELEASES for the upcoming version. Lists the more
> important changes. Still under construction.
> George Moschovitis <george.moschovitis at gmail.com>**20070627105358]
> [Minor cleanup.
> George Moschovitis <george.moschovitis at gmail.com>**20070627085900]
> [Minor changes to make example easier to run. [arne]
> George Moschovitis <george.moschovitis at gmail.com>**20070627071122]
> [Check if template exists, else use app/template. Fixes WSOD problem in
> blog [james_b].
> George Moschovitis <george.moschovitis at gmail.com>**20070626112108]
> [Improved blog example, added auto syndication and export to JSON. More
> fault tolerant ATOM exporter.
> George Moschovitis <george.moschovitis at gmail.com>**20070626111745]
> [Updated CHANGELOG.
> George Moschovitis <george.moschovitis at gmail.com>**20070626104045]
> [Use nitro/part/xx instead of part/xx [james_b].
> George Moschovitis <george.moschovitis at gmail.com>**20070625080218]
> [Fix glycerin.rb, remove gen from load path, add load path for part/admin
> Jonathan Buch <jo at helloit.fi>**20070624065430]
> [Og.manager must be non-nil in nitro/application.rb
> Jonathan Buch <jo at helloit.fi>**20070624063940]
> [Make webfile spec runnable, prepare for better tests
> Jonathan Buch <jo at helloit.fi>**20070623151311]
> [Fix bug in compiler, George please check, controller spec fixes
> Jonathan Buch <jo at helloit.fi>**20070623122207]
> [Converted webfile test
> Arne Brasseur <arne at arnebrasseur.net>**20070623124119]
> [Changed og/spec/helper to work with script/lib/
> Arne Brasseur <arne at arnebrasseur.net>**20070623115719]
> [Updated aspects spec to new lib/spec location
> Arne Brasseur <arne at arnebrasseur.net>**20070623101651]
> [Converted from test to spec, adapted to new script/lib/spec location
> Arne Brasseur <arne at arnebrasseur.net>**20070623100913
>  cookie; controller; context converted
> ]
> [Put helpers in script/lib
> Arne Brasseur <arne at arnebrasseur.net>**20070623100727]
> [Bring specs up to date with cgi.rb changes
> Jonathan Buch <jo at helloit.fi>**20070623071053]
> [Fill uuid_polymorphic with a non-implemented spec
> Jonathan Buch <jo at helloit.fi>**20070623070306]
> [Don't allow xxx.yyy structured parameters, only xxx[yyy]
> George Moschovitis <george.moschovitis at gmail.com>**20070621070657]
> [Make nitro aspects spec pass, George please recheck
> Jonathan Buch <jo at helloit.fi>**20070620204258]
> [Fix rest of Raw specs, all specs green
> Jonathan Buch <jo at helloit.fi>**20070620202559]
> [Fix cgi spec + fix cgi
> Jonathan Buch <jo at helloit.fi>**20070620195601]
> [Some minor stuff
> George Moschovitis <george.moschovitis at gmail.com>**20070620073240]
> [Added more blog files, added caching in blog example, better error
> reporting  in mysql driver.
> George Moschovitis <george.moschovitis at gmail.com>**20070620072747]
> [Work on the new blog example. Cleanup in the proto dir.
> George Moschovitis <george.moschovitis at gmail.com>**20070619095017]
> [Removed old blog example files, the proto app uses the new Nitro logo.
> George Moschovitis <george.moschovitis at gmail.com>**20070618231044]
> [Converted tc_cgi to spec/cgi, 19 specs - 6 fail
> Arne Brasseur <arne at arnebrasseur.net>**20070619172652]
> [Hack fixed an annoying problem in the compiler. Check out the comments
> for some details. Updated hello example.
> George Moschovitis <george.moschovitis at gmail.com>**20070618145716]
> [remove setup/db.rb and make spec/relation.rb pass
> Jonathan Buch <jo at helloit.fi>**20070617153442]
> [split spec for store, make them pass
> Jonathan Buch <jo at helloit.fi>**20070617152228]
> [Make :evolve :full to add needed columns in orderable
> Jonathan Buch <jo at helloit.fi>**20070617150610]
> [Fix single-inheritance + spec
> Jonathan Buch <jo at helloit.fi>**20070617145600]
> [@thread_safe was always set to `true`, insert a `raise` in manager when
> with_store will yield nil
> Jonathan Buch <jo at helloit.fi>**20070617145447]
> [Remove test directory
> Jonathan Buch <jo at helloit.fi>**20070617145351]
> [Rest of the specs converted, many failing though
> Jonathan Buch <jo at helloit.fi>**20070617143019]
> [Many more specs
> Jonathan Buch <jo at helloit.fi>**20070617135845]
> [Updated CONTRIBUTORS
> George Moschovitis <george.moschovitis at gmail.com>**20070614102316]
> [Converted tc_caching to spec/controller/caching
> Arne Brasseur <arne at arnebrasseur.net>**20070617172146]
> [Made structure of spec/ dir resemble raw/
> Arne Brasseur <arne at arnebrasseur.net>**20070617162248]
> [Converted Raw specs to new infrastructure/syntax
> Arne Brasseur <arne at arnebrasseur.net>**20070617155611]
> [Converted exisiting Nitro specs to new syntax/infrastructure
> Arne Brasseur <arne at arnebrasseur.net>**20070617155440]
> [Changed include Raw::TableHelper to Raw::Mixin::TableHelper in
> glue/builder/xml
> Arne Brasseur <arne at arnebrasseur.net>**20070617154515]
> [Added require 'facets/core/module/is' in raw.rb
> Arne Brasseur <arne at arnebrasseur.net>**20070617154348]
> [Fixed rake for specs in subdirs
> Arne Brasseur <arne at arnebrasseur.net>**20070617154132]
> [Run individual tests with rake test:project:filename
> Arne Brasseur <arne at arnebrasseur.net>**20070617153352]
> [Added glue loadpath in script/helper/spec
> Arne Brasseur <arne at arnebrasseur.net>**20070617135920]
> [Created script/helper/spec, to be included in specs, sets up loadpath,
> loads rSpec
> Arne Brasseur <arne at arnebrasseur.net>**20070617122742]
> [Revamp join.rb spec, fix bug in postgresql returning text pks when
> inserting
> Jonathan Buch <jo at helloit.fi>**20070617115049]
> [Fix Ez specs
> Jonathan Buch <jo at helloit.fi>**20070617105547]
> [join, types, has_one_create_on_insert specs, join failing horribly why?
> Jonathan Buch <jo at helloit.fi>**20070616142922]
> [build, camel case, delete all, ez, finder, has many  specs, property =>
> attr_acc
> Jonathan Buch <jo at helloit.fi>**20070616140009]
> [aggregation sepcs, accumulation specs, cacheable specs
> Jonathan Buch <jo at helloit.fi>**20070616125239
>  cacheable fails horrible, because `after_enchant` of cacheable seems not
>  to be called.  This also tries to unify cacheable spec.
> ]
> [Revise Optimistic Locking spec, failing because Aspects `pre` fails
> somehow
> Jonathan Buch <jo at helloit.fi>**20070616120206]
> [Automatic translation of all specs to new RSpec version
> Jonathan Buch <jo at helloit.fi>**20070616114845]
> [Fix hierarchical spec + fix bug in hierarchical
> Jonathan Buch <jo at helloit.fi>**20070616114727]
> [accumulator spec translated
> Jonathan Buch <jo at helloit.fi>**20070616114654]
> [Fix psql insert bug
> Jonathan Buch <jo at helloit.fi>**20070616114600]
> [Rough translations of the Model folder to specs
> Jonathan Buch <jo at helloit.fi>**20070616110311]
> [Rake test/spec basic setup, ported from ramaze
> Arne Brasseur <arne at arnebrasseur.net>**20070616103820]
> [Bring Spec configuration to newest version
> Jonathan Buch <jo at helloit.fi>**20070616095855]
> [Moved apply/build/cleanup/ctabs from script to rake_tasks, added rakefile
> Arne Brasseur <arne at arnebrasseur.net>**20070615124258]
> [Minor stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070614090659]
> [Fixed Part.require
> Arne Brasseur <arne at arnebrasseur dot net>**20070613081240]
> [Improved transaction support in Mysql, applied psql fix to the sqlite
> adapter aswell.
> George Moschovitis <george.moschovitis at gmail.com>**20070606140618]
> [Transaction save psql store
> Jonathan Buch <jo at helloit.fi>**20070606063257]
> [Fixed --webrick option [arne].
> George Moschovitis <george.moschovitis at gmail.com>**20070529212659]
> [Added some missing files.
> George Moschovitis <george.moschovitis at gmail.com>**20070528170049]
> [Allow arbitrary joins_many relations
> Brian Davis <brian.william.davis at gmail.com>**20070520095013
>
>  Appends the relation name to the end of named many_to_many and joins_many
> relations, allowing multiple distinct joins_many relations with the same
> component classes.
> ]
> [Fixes in script adapter to make compatible with caching, allows for
> efficient, behind-the-scenes caching.
> George Moschovitis <george.moschovitis at gmail.com>**20070522103413]
> [more fault tolerant controler/model enchant code.
> George Moschovitis <george.moschovitis at gmail.com>**20070521220808]
> [Minor stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070520154602]
> [Added cool new asset filter.
> George Moschovitis <george.moschovitis at gmail.com>**20070520104852]
> [Many small fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070520104822]
> [bugfix, integer oids werent saved correctly anymore
> Jonathan Buch <jo at helloit.fi>**20070429075956]
> [small fix in refers_to, wasn't saving self correctly.
> Jonathan Buch <jo at helloit.fi>**20070429075049]
> [Startup speed patch, removes many unnecessary calls to ann()
> Jonathan Buch <jo at helloit.fi>**20070429074053
>  See thread:
> http://rubyforge.org/pipermail/nitro-general/2007-April/007605.html
> ]
> [small glue format validation fix
> Jonathan Buch <jo at helloit.fi>**20070429071907
>  This removes the nil checking from validate_format, should use
>  validate_value for that.  Also don't use .source on the regex.
> ]
> [make aggregations and :include work together
> Jonathan Buch <jo at helloit.fi>**20070430104747]
> [Throw ValidationError on save.
> George Moschovitis <george.moschovitis at gmail.com>**20070419104542]
> [Fixed nasty request.uri bug in the Mongrel adapter.
> George Moschovitis <george.moschovitis at gmail.com>**20070416174017]
> [table_create_tbody_fix
> rmela at robmela.com**20070331221914
>  If Og started but no Og objects method would throw an exception which was
> not handled.
> ]
> [More fixes in join and taggable.
> George Moschovitis <george.moschovitis at gmail.com>**20070415172345]
> [Some changes in proto
> George Moschovitis <george.moschovitis at gmail.com>**20070413071437]
> [Hack fixed join/joins_many code to work with custom primary keys.
> George Moschovitis <george.moschovitis at gmail.com>**20070413071347]
> [More flexible code in elements.
> George Moschovitis <george.moschovitis at gmail.com>**20070411080241]
> [Fixed updated field in atom serialization.
> George Moschovitis <george.moschovitis at gmail.com>**20070411080112]
> [Added tag cleanup code in taggable, added initial code for Taggable spec.
> George Moschovitis <george.moschovitis at gmail.com>**20070409071712]
> [Improve localization system, made it work with the latest nitro. Added
> insert_filter method to easily manipulate each Format's template_filter
> pipeline, working LocalizationFilter.
> George Moschovitis <george.moschovitis at gmail.com>**20070407105006]
> [Small fixes in taggable.
> George Moschovitis <george.moschovitis at gmail.com>**20070407084219]
> [Made Og collections enumerable, better title in automatic autom
> syndication, request.full_uri and more...
> George Moschovitis <george.moschovitis at gmail.com>**20070405093807]
> [Fixed nasty bug in --port_offset setting that kept cluster configurations
> from working correctly.
> George Moschovitis <george.moschovitis at gmail.com>**20070403170023]
> [More fixes to make polymorphic relations work. The implementation is a
> piece of crap :(
> George Moschovitis <george.moschovitis at gmail.com>**20070401094904]
> [Some cleanup in Og polymorphic relations, now works with :polymorphic =>
> true (along with the old version (, Object)). Added spec. Also fixed a nasty
> oid on insert bug.
> George Moschovitis <george.moschovitis at gmail.com>**20070331214542]
> [Fix mysql quote of nil values.
> George Moschovitis <george.moschovitis at gmail.com>**20070328111637]
> [Made custom_pk.rb spec pass [jonathan].
> George Moschovitis <george.moschovitis at gmail.com>**20070328102915]
> [Fix conflict in helper
> George Moschovitis <george.moschovitis at gmail.com>**20070328101205]
> [POLS when using Og::VarChar()
> Jonathan Buch <jo at helloit.fi>**20070327061024
>  * add new annotation :sql_type so VarChar doesn't have to use :sql
>   attr_accessor :name, VarChar(20), :unique => true
>   works now
>  * added annotation :null, so NotNull also doesn't use :sql
>  * 3 :control => :none in Revisable
>  * use glycerin setup script in spec/helper.rb instead of path unshift to
> Og
>  * make join-table creation less noisy
> ]
> [More fixes to make general primary keys work, fixed insert bug
> [jonathan].
> George Moschovitis <george.moschovitis at gmail.com>**20070327224835]
> [Quote primary key in og_delete.
> George Moschovitis <george.moschovitis at gmail.com>**20070327210121]
> [HelloWorld_Should_Always_Work
> rmela**20050117145850]
> [Handle xml/yaml/json post data, some cleanups in cgi.rb (many more to
> come).
> George Moschovitis <george.moschovitis at gmail.com>**20070327194110]
> [More fixes to support arbitraty promary keys (and UUID in particular).
> George Moschovitis <george.moschovitis at gmail.com>**20070326114037]
> [Fix and #store as #get_store aliaas.
> George Moschovitis <george.moschovitis at gmail.com>**20070326100204]
> [<< helper for manager, useful for writing db change scripts.
> George Moschovitis <george.moschovitis at gmail.com>**20070326100038]
> [Initial version of the UUID mixin.
> George Moschovitis <george.moschovitis at gmail.com>**20070326100003]
> [Some changes to Og to prepare for UUID support.
> George Moschovitis <george.moschovitis at gmail.com>**20070326095900]
> [sql.rb changes
> Jonathan Buch <jo at helloit.fi>**20070320104410
>  * remove duplicated write_attrs
>  * made write_attr_boolean return 'f' instead of NULL
>  * fix require in tc_timestamped
>  * add :extra_condition to .find (for use with set_find_options())
>   i.e. set_find_options(:extra_condition => 'time_deleted IS NULL')
>  * fix validate_format
> ]
> [Pad nice parameter in dispatcher.
> George Moschovitis <george.moschovitis at gmail.com>**20070323204529]
> [Implemented CSSFormat for dynamically generated css files. Adapted output
> caching to make more reusable.
> George Moschovitis <george.moschovitis at gmail.com>**20070320222239]
> [Moved ormsupport from facets to og/util/inflect. better organization of
> the og dir.
> George Moschovitis <george.moschovitis at gmail.com>**20070320094108]
> [Minor fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070319190835]
> [fixes: compartmentalizing fixture classes - 6/63
> Judson Lester <nyarly at gmail.com>**20070319080512]
> [Fixes for new API
> Judson Lester <nyarly at gmail.com>**20070318031650]
> [Cleaned up sti.rb, moved into model, better interface. Moved unmanageable
> into model (and into Og::mixin)
> George Moschovitis <george.moschovitis at gmail.com>**20070317165215]
> [Cleaned up og/model.rb a little bit.
> George Moschovitis <george.moschovitis at gmail.com>**20070317162317]
> [Unified many_to_many and joins_many specs
> Judson Lester <nyarly at gmail.com>**20070313234146
>  Until there's a useful distinction between m2m and jm, I can't see a
> reason to maintain seperate spec files
> ]
> [Og::Exception
> Judson Lester <nyarly at gmail.com>**20070313224726
>  Added Og::Exception to og.rb and Og::Deleted to store.  Added a spec on
> Model for Og::Deleted's use, and
>  added code to SqlStore to fulfill it.
> ]
> [validation: uniques really work
> Judson Lester <nyarly at gmail.com>**20070314212512
>  Worth noting: the sense of the block to Validation::add_validation has
> been reversed.  It makes more sense
>  to me to return "true" if the validation passes.
>
>  Also, I realize now that I have no idea what "validate_related" is
> supposed to do.
> ]
> [validation: unique nulls and numbers
> Judson Lester <nyarly at gmail.com>**20070314205044]
> [validation: fixed null value unique colision
> Judson Lester <nyarly at gmail.com>**20070314204037
>  As it was, two null values both counted as unique.  As I understand it,
> that's wrong, in a SQL sense.
>  If you want that behavior, add a validate_value as well.
>  Also exposed by this fix: null values come back as empty strings.
>  Correct behavior?
> ]
> [Minor stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070316114101]
> [Misc fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070314204706]
> [quote column
> Guilherme Antoniolo <antoniolo at gmail.com>**20070314172025]
> [store: fixes 1
> Judson Lester <nyarly at gmail.com>**20070314185220]
> [Converted more service formats.
> George Moschovitis <george.moschovitis at gmail.com>**20070313101306]
> [Validation fix
> Judson Lester <nyarly at gmail.com>**20070312224433
>  Not sure how, but "Validation::add_validation" got changed to "
> self.class.add_validation" which is incorrect.
> ]
> [respect user defined :foreign_key annotation
> Jonathan Buch <jo at helloit.fi>**20070313081503]
> [Fix in admin part, refactored code in 'service' formats, made more
> flexible.
> George Moschovitis <george.moschovitis at gmail.com>**20070312180410]
> [Fixed nasty cache cleanup bug.
> George Moschovitis <george.moschovitis at gmail.com>**20070311103449]
> [Cookie expires, use -rubygems in nitro and more.
> George Moschovitis <george.moschovitis at gmail.com>**20070311102657]
> [Fix stupid Application error that forced the Webrick adapter.
> George Moschovitis <george.moschovitis at gmail.com>**20070310171958]
> [Call redirects on POST method (+ spec)
> George Moschovitis <george.moschovitis at gmail.com>**20070310093821]
> [Updated CONTRIBUTORS.
> George Moschovitis <george.moschovitis at gmail.com>**20070310080222]
> [many_to_many spec
> Brian Davis <brian.william.davis at gmail.com>**20070309233521
>  Added a spec outlining proper multiple many_to_many relation behavior.
> Currently, this spec fails and fails hard.
> ]
> [Fix in util/markup.rb + spec.
> George Moschovitis <george.moschovitis at gmail.com>**20070309124538]
> [Minor changes to the validation patch.
> George Moschovitis <george.moschovitis at gmail.com>**20070309110137]
> [spec: cleanup, add validations
> Judson Lester <nyarly at gmail.com>**20070309024700]
> [ New implementation of Og Validations, unfinished.
> George Moschovitis <george.moschovitis at gmail.com>**20070308164651]
> [spec: merge with Og changes
> Judson Lester <nyarly at gmail.com>**20070308021223]
> [spec: store specifications split out
> Judson Lester <nyarly at gmail.com>**20070308015556
>  Interestingly enough, there are 5 failures out of 35 specs.
> ]
> [sql: Accounting for custom primary keys in PSQL
> Judson Lester <nyarly at gmail.com>**20070306095837]
> [sql: cleanup OGTABLE + specs work better
> Judson Lester <nyarly at gmail.com>**20070306015638]
> [sql: cleanup - OGTABLE & oids
> Judson Lester <nyarly at gmail.com>**20070306012512]
> [Slightly improved Validation::Errors.
> George Moschovitis <george.moschovitis at gmail.com>**20070308122857]
> [Added tidy helper. It seems to fuckup some htmls though.
> George Moschovitis <george.moschovitis at gmail.com>**20070308122103]
> [Simple ATOM dumper/loader.
> George Moschovitis <george.moschovitis at gmail.com>**20070308122032]
> [Added temp_dir option in application, optimized updated!/touched! in
> Timestamped.
> George Moschovitis <george.moschovitis at gmail.com>**20070307201235]
> [Improvements to the generated RDoc.
> George Moschovitis <george.moschovitis at gmail.com>**20070306150611]
> [Some fixes in Og test cases. Many more are needed.
> George Moschovitis <george.moschovitis at gmail.com>**20070306114103]
> [Fix in encode_uri
> George Moschovitis <george.moschovitis at gmail.com>**20070306112833]
> [Cleverly use Ruby's autoload to make the code more flexible.
> George Moschovitis <george.moschovitis at gmail.com>**20070306094200]
> [sql: removing psql comment
> Judson Lester <nyarly at gmail.com>**20070306013102]
> [sql: postgres and threadsafe oids
> Judson Lester <nyarly at gmail.com>**20070306012957]
> [spec: resolved some existing specs
> Judson Lester <nyarly at gmail.com>**20070304071444
>  Switched spec/store.rb and spec/sti_relation.rb over to isolated
> specifications.
>  As a result, discovered a couple of bugs in store.sql.
> ]
> [spec: Isolated specifications, silenced psql
> Judson Lester <nyarly at gmail.com>**20070303085152]
> [spec: adding spec-helper
> Judson Lester <nyarly at gmail.com>**20070303014330
>  The first of several patches to add specs to Og.  Specifically trying to
> isolate spefications from each other, and
>  break them down into small chunks.
> ]
> [Minor.
> George Moschovitis <george.moschovitis at gmail.com>**20070305073132]
> [The reloader detects element include file changes.
> George Moschovitis <george.moschovitis at gmail.com>**20070304205121]
> [Misc fixes and updates.
> George Moschovitis <george.moschovitis at gmail.com>**20070304204733]
> [Ensure log/.temp dirs extis, create temp files (like pids) in .temp, dont
> start a state server by default (made this an command line option
> --stateserver). Used the CookieSessionStore instead.
> George Moschovitis <george.moschovitis at gmail.com>**20070303180413]
> [Much better implementation of CookieSessionStore. Sends a separate cookie
> for the client.
> George Moschovitis <george.moschovitis at gmail.com>**20070303170319]
> [Reimplemented DrbStore. By looking to the drbstore source it is easy to
> convert the rest of the stores.
> George Moschovitis <george.moschovitis at gmail.com>**20070303085841]
> [Fixed reloader.
> George Moschovitis <george.moschovitis at gmail.com>**20070303085305]
> [Implemented hybrid JSON/Marshal CookieSessionStore, partly readable at
> the client (!!!!!!!). A-M-A-Z-I-N-G.
> George Moschovitis <george.moschovitis at gmail.com>**20070302222151]
> [Added experimental JSONCookieSessionStore, don't use yet.
> George Moschovitis <george.moschovitis at gmail.com>**20070302140252]
> [Improved new sessions implementation, re-added memory store.
> George Moschovitis <george.moschovitis at gmail.com>**20070302135407]
> [Totaly reimplementation of session system. Also introduced a new cookie
> based session store (will be the default).
> George Moschovitis <george.moschovitis at gmail.com>**20070302114529]
> [request[] accepts symbols as keys.
> George Moschovitis <george.moschovitis at gmail.com>**20070301114609]
> [Misc fixes
> George Moschovitis <george.moschovitis at gmail.com>**20070301114529]
> [STI Relations again
> Judson Lester <nyarly at gmail.com>**20070228201315]
> [Misc fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070228074617]
> [Cool changes: the dispatcher mounter handles models, the old model
> scaffold code is now just a mixin, simplified the blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070227203420]
> [Added again to og/spec dir.
> George Moschovitis <george.moschovitis at gmail.com>**20070227191037]
> [Further cleaned up the directory structure of the raw ad og projects.
> George Moschovitis <george.moschovitis at gmail.com>**20070227190957]
> [Misc Og stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070227111912]
> [sti reference
> Judson Lester <nyarly at gmail.com>**20070227103047
>  References from STI child classes now point across to other entities,
> including other STI children.
>  There's two questionable lines in Relation::enchant that strike me as
> ugly - but the refactoring to
>  make them unnecessary would be quite serious for a mere aesthetic point
> ]
> [sti-relations: failing spec
> Judson Lester <nyarly at gmail.com>**20070227020622
>  Added a spec for a feature that I want: for relationships of STI children
> to function properly.
>  Moreoever, I'd like for relationships to STI children to function
> properly as well.  Right now the
>  spec fails, which means I'm allowed to write some code!
> ]
> [More Og cleanup and fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070227110806]
> [Renamed Og::Entity to Og::Model, to be more consistent with the rest of
> Nitro and easier for newcomers with AR / MVC experience.
> George Moschovitis <george.moschovitis at gmail.com>**20070227105616]
> [with_store fixes
> Judson Lester <nyarly at gmail.com>**20070226213256
>  Added some explicit local variables to account for the with_store blocks.
>  SHould write some spec for
>  this...  Or at least update tests.
>
>  Oh, and cleaned up some of the STI comment-outs
> ]
> [Some cleanups, removed more glue files.
> George Moschovitis <george.moschovitis at gmail.com>**20070226123929]
> [Reimplemented Og's multithreaded strategy, should also fix the reported
> memory leak. [jonathan]
> George Moschovitis <george.moschovitis at gmail.com>**20070226110315]
> [Misc fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070225194136]
> [Created sti.rb
> Judson Lester <nyarly at gmail.com>**20070224231100]
> [STI Refactoring
> Judson Lester <nyarly at gmail.com>**20070224230929
>  Moving schema inheritance conditionals into the SchemaInheritance module
> ]
> [questionable-sti
> Judson Lester <nyarly at gmail.com>**20070222190520]
> [Converted all refs from Nitro to Raw. (Big patch ;-))
> George Moschovitis <george.moschovitis at gmail.com>**20070225115142]
> [Moved raw/lib/nitro to raw/lib/raw
> George Moschovitis <george.moschovitis at gmail.com>**20070225105824]
> [Moved glue dirs to nitro/mixin and og/mixn, use Nitro::Mixin and
> Og::Mixin namespaces.
> George Moschovitis <george.moschovitis at gmail.com>**20070225105440]
> [Use debug/info/error as shortcuts for debugger, cleaner code and allows
> for customization. Response keeps the output buffer, added some info text
> when running the console (nitro console)
> George Moschovitis <george.moschovitis at gmail.com>**20070224212830]
> [Worked a bit more on the blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070224191429]
> [At last, #render uses encode_uri, so does caching. The sweeper reuses the
> Caching code and has a better interface. POLS rules ;-)
> George Moschovitis <george.moschovitis at gmail.com>**20070224102731]
> [nitro command pass over unrecognized parameters to the application.
> George Moschovitis <george.moschovitis at gmail.com>**20070224093901]
> [Added simple rdoc script, minor cleanup to improve rdocs. a lot more is
> needed.
> George Moschovitis <george.moschovitis at gmail.com>**20070223215539]
> [Fix in attr utils.
> George Moschovitis <george.moschovitis at gmail.com>**20070223195942]
> [Make spec output more readable.
> George Moschovitis <george.moschovitis at gmail.com>**20070223102419]
> [Rearanged some docs.
> George Moschovitis <george.moschovitis at gmail.com>**20070223101248]
> [Aspects preserver arity, this fixes a nasty encode_uri bug, added
> encode_uri spec.
> George Moschovitis <george.moschovitis at gmail.com>**20070223100555]
> [Cleaned up argument/env parsing and nitro command. Script/Console adapter
> works again.
> George Moschovitis <george.moschovitis at gmail.com>**20070222205615]
> [state.rb use facets/daemonize.
> George Moschovitis <george.moschovitis at gmail.com>**20070222145031]
> [Use application instead of server everywhere.
> George Moschovitis <george.moschovitis at gmail.com>**20070222144803]
> [Worked more on aspects, still not happy with it.
> George Moschovitis <george.moschovitis at gmail.com>**20070222140104]
> [Minor
> George Moschovitis <george.moschovitis at gmail.com>**20070222121517]
> [Aspects apply to local methods if no target is provided, fixed some small
> bugs.
> George Moschovitis <george.moschovitis at gmail.com>**20070222121322]
> [Added nitro specs, simple spec for aspects. Fixed nasty aspects bug, the
> block is instance_evaled now.
> George Moschovitis <george.moschovitis at gmail.com>**20070222113445]
> [Introduced spec dir. First spec (Publishable) helps identify a faster
> implementation of action_methods.
> George Moschovitis <george.moschovitis at gmail.com>**20070222103352]
> [Fixing postgresql
> Judson Lester <nyarly at gmail.com>**20070221100539]
> [Moved appserver to nitro, renamed to application.
> George Moschovitis <george.moschovitis at gmail.com>**20070221212957]
> [Fix in flash.
> George Moschovitis <george.moschovitis at gmail.com>**20070221202512]
> [Make aspects more flexible, fixed action_methods, improved format
> callbacks.
> George Moschovitis <george.moschovitis at gmail.com>**20070221172955]
> [Converted the codebase to use the new safer (and more elegant, though
> slightly slower) aspects implementation.
> George Moschovitis <george.moschovitis at gmail.com>**20070221122616]
> [Changed many "property"s to "attr_accessor"s for consistency.
> George Moschovitis <george.moschovitis at gmail.com>**20070221083245]
> [Important fix in dispatcher, added RSS format.
> George Moschovitis <george.moschovitis at gmail.com>**20070220153918]
> [Removed simple example. Caching check ann(:action, :cache) annotation.
> George Moschovitis <george.moschovitis at gmail.com>**20070220123112]
> [Removed runner.rb, add argument parsing to server, temp solution.
> George Moschovitis <george.moschovitis at gmail.com>**20070220112630]
> [More cleanup, removed some obsolete code.
> George Moschovitis <george.moschovitis at gmail.com>**20070219210048]
> [Mailer works again, added MailTemplate. Needs some more cleanup though.
> George Moschovitis <george.moschovitis at gmail.com>**20070219201817]
> [Some temp hack fixes. Moved mailer from glue to nitro.
> George Moschovitis <george.moschovitis at gmail.com>**20070219185629]
> [Converted mongrel adapter to latest.
> George Moschovitis <george.moschovitis at gmail.com>**20070219180130]
> [Refactored some more common code to adapter.rb
> George Moschovitis <george.moschovitis at gmail.com>**20070219175323]
> [Separated Context from Render (at last).
> George Moschovitis <george.moschovitis at gmail.com>**20070219173055]
> [Reorganized some files, cleanup.
> George Moschovitis <george.moschovitis at gmail.com>**20070219164826]
> [Misc fixes and small improvements, trying to make cull.gr run again.
> George Moschovitis <george.moschovitis at gmail.com>**20070219152031]
> [Mongrel adapter works again, cleaned up webrick and mongrel adapters,
> more to come.
> George Moschovitis <george.moschovitis at gmail.com>**20070218213433]
> [New super simple output caching system and some source files
> reorganization.
> George Moschovitis <george.moschovitis at gmail.com>**20070218205255]
> [Use ___super instead of ___control.
> George Moschovitis <george.moschovitis at gmail.com>**20070218172628]
> [Minor fixes to make it run with latest facets. The source code extraction
> on error was buggy, so I removed it for the moment, better implementation is
> comming.
> George Moschovitis <george.moschovitis at gmail.com>**20070218112949]
> [Some fixes to make compatible with facets 1.8.49 and daemonized support
> using the facets daemonized method to get rid of one more dependency.
> George Moschovitis <george.moschovitis at gmail.com>**20070218111351]
> [Removed old prototype/scriptaculous helpers and morphers.
> George Moschovitis <george.moschovitis at gmail.com>**20070218101117]
> [Renamed gen to raw
> George Moschovitis <george.moschovitis at gmail.com>**20070218100113]
> [New implementation of source extraction from errors.
> George Moschovitis <george.moschovitis at gmail.com>**20070216213800]
> [Small reloader optimisation.
> George Moschovitis <george.moschovitis at gmail.com>**20070216100510]
> [Misc stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070216093053]
> [Introduced new reloader: elegant, orthogonal to the  dispatcher, monitors
> include files and just works ;-)
> George Moschovitis <george.moschovitis at gmail.com>**20070216091347]
> [Organized new Nitro directory.
> George Moschovitis <george.moschovitis at gmail.com>**20070215122253]
> [Introduced new nitro directory. A super-framework that integrates gen, og
> and facets.
> George Moschovitis <george.moschovitis at gmail.com>**20070215114034]
> [Renamed nitro dir to gen.
> George Moschovitis <george.moschovitis at gmail.com>**20070215113953]
> [Moved glycerin into script
> George Moschovitis <george.moschovitis at gmail.com>**20070215112139]
> [Removed service.rb will be replaced by Nitro's new implicit web service
> capabilities.
> George Moschovitis <george.moschovitis at gmail.com>**20070215104516]
> [Removed buggy squeeze filter and misc stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070215102211]
> [Organized context related files in the context directory for better
> source code structure.
> George Moschovitis <george.moschovitis at gmail.com>**20070215092131]
> [Improved format system, now defines filter_templat and
> before_action/after_action for extra delivery. new implementation of auto
> serialization to atom/json etc... under construction.
> George Moschovitis <george.moschovitis at gmail.com>**20070214182218]
> [Added some more filters.
> George Moschovitis <george.moschovitis at gmail.com>**20070214165937]
> [Simple example that demonstrates how Nitro can be used like php for quick
> and dirty web apps.
> George Moschovitis <george.moschovitis at gmail.com>**20070214163135]
> [Initial test for auto json, ignore.
> George Moschovitis <george.moschovitis at gmail.com>**20070214163112]
> [Set correct content_type for formats.
> George Moschovitis <george.moschovitis at gmail.com>**20070214143238]
> [Reintroduced the hello world example.
> George Moschovitis <george.moschovitis at gmail.com>**20070214093958]
> [Improved blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070214093938]
> [Fix in aspects, and some improvemnts in the blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070214093905]
> [Support action with parameters, support template override, fixes to make
> admin part work again.
> George Moschovitis <george.moschovitis at gmail.com>**20070213133102]
> [Minor.
> George Moschovitis <george.moschovitis at gmail.com>**20070213124013]
> [Moved action/template checkers to publishable, some fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070213123604]
> [Minor
> George Moschovitis <george.moschovitis at gmail.com>**20070213113501]
> [Change in request.path calculation, fix in dispatcher.
> George Moschovitis <george.moschovitis at gmail.com>**20070213081419]
> [Minor.
> George Moschovitis <george.moschovitis at gmail.com>**20070213071906]
> [Added some skin files to the new blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070213071806]
> [Addded Judson's STI patch. [judson]
> George Moschovitis <george.moschovitis at gmail.com>**20070213071717]
> [Added elements filter (slightly improved from old version), worked on the
> new blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070212230931]
> [Added some more files from the new example, under construction.
> George Moschovitis <george.moschovitis at gmail.com>**20070212143319]
> [Adapted proto dir.
> George Moschovitis <george.moschovitis at gmail.com>**20070212141755]
> [Reimplemented / cleaned up morpher to make compatible with the new
> system.
> George Moschovitis <george.moschovitis at gmail.com>**20070212141116]
> [Use Compiler Filters as instances (more flexible, canuse custom version
> of the filters).
> George Moschovitis <george.moschovitis at gmail.com>**20070212123128]
> [Cleanup and Cookie helper.
> George Moschovitis <george.moschovitis at gmail.com>**20070212104536]
> [Improved format, dispatcher, converted some more of the old compiler
> filters.
> George Moschovitis <george.moschovitis at gmail.com>**20070211200630]
> [New Compiler filter architecture.
> George Moschovitis <george.moschovitis at gmail.com>**20070211172527]
> [Resource Representation Formats (allow for customized handling of
> resources, in progress)
> George Moschovitis <george.moschovitis at gmail.com>**20070211172434]
> [Added new blog example.
> George Moschovitis <george.moschovitis at gmail.com>**20070211172405]
> [Big changes (in progress). Removed all old examples. Introduced brand new
> Compiler architecture. Clean efficient code and initiali support for REST.
> George Moschovitis <george.moschovitis at gmail.com>**20070211172242]
> [Use the old hacky autoreload code in the new dispatcher. Will have to
> revisit this hack later.
> George Moschovitis <george.moschovitis at gmail.com>**20070210130725]
> [Use consistently URI instead of URL throughout hte source code.
> George Moschovitis <george.moschovitis at gmail.com>**20070210125452]
> [Misc fixes to make code work with latest changes.
> George Moschovitis <george.moschovitis at gmail.com>**20070210122747]
> [Optimized cookie to_s.
> George Moschovitis <george.moschovitis at gmail.com>**20070210114028]
> [Use facets/settings instead of glue/configuration.
> George Moschovitis <george.moschovitis at gmail.com>**20070209101458]
> [Started refactoring the nitro adapters, initial changes in
> webrick/mongrel.
> George Moschovitis <george.moschovitis at gmail.com>**20070208222404]
> [Renamed caching to cache.
> George Moschovitis <george.moschovitis at gmail.com>**20070208182229]
> [Minor fixes.
> George Moschovitis <george.moschovitis at gmail.com>**20070208180613]
> [New implementation of AppServer, do not use the crappy Runner class,
> improvements in Dispatcher/Router. Still under construction.
> George Moschovitis <george.moschovitis at gmail.com>**20070208111757]
> [Improved dispatcher, refactored dispatcher/mounter (now the preferred way
> to mount controllers).
> George Moschovitis <george.moschovitis at gmail.com>**20070207185157]
> [Introduced new implementation for Router, simplified.
> George Moschovitis <george.moschovitis at gmail.com>**20070206204508]
> [No cross-refs between Context/Server/Dispatcher.
> George Moschovitis <george.moschovitis at gmail.com>**20070206080104]
> [Enforced some consistency rules.
> George Moschovitis <george.moschovitis at gmail.com>**20070205225344]
> [Added coding conventions text.
> George Moschovitis <george.moschovitis at gmail.com>**20070205205845]
> [Minor.
> George Moschovitis <george.moschovitis at gmail.com>**20070205205808]
> [Introduced judson's eval-less version of sql.rb/mysql.rb. Needs fix in
> facets/more/aspects to work [judson].
> George Moschovitis <george.moschovitis at gmail.com>**20070205201027]
> [New tc_dispatcher.rb
> George Moschovitis <george.moschovitis at gmail.com>**20070204114558]
> [Removed unused emitter functionality from render.
> George Moschovitis <george.moschovitis at gmail.com>**20070204105203]
> [Use consistent require paths for Facets libraries.
> George Moschovitis <george.moschovitis at gmail.com>**20070203193118]
> [Minor
> George Moschovitis <george.moschovitis at gmail.com>**20070202224838]
> [Introduced brand new clean and restful dispatcher. In its early stages
> but seems to work. Better integration to come.
> George Moschovitis <george.moschovitis at gmail.com>**20070202224313]
> [Better proto dir.
> George Moschovitis <george.moschovitis at gmail.com>**20070202135708]
> [Render.redirect_on_empty == true by default, nitro automatically injects
> redirect_to_referer when the output buffer is empty!
> George Moschovitis <george.moschovitis at gmail.com>**20070202135414]
> [Improved proto dir, small fixes here and there.
> George Moschovitis <george.moschovitis at gmail.com>**20070202121359]
> [missed an inspect...
> Judson Lester <nyarly at gmail.com>**20070201235628]
> [evald string roundup
> Judson Lester <nyarly at gmail.com>**20070201234916
>  All of the eval_og_ methods have been pushed up into some mixed in
> modules that
>  get included into enchanted classes.  There may still be some orphaned
> methods etc,
>  but on the whole this looks a lot more manageable.
> ]
> [resolving repo pull
> Judson Lester <nyarly at gmail.com>**20070201204635]
> [Mixin_enchant_sketch
> Judson Lester <nyarly at gmail.com>**20070201015234
>  This is the beginnings of a change from eval'd strings for enchantment
> and mixins with
>  a smidge of dynamic code.  Honestly, there's plenty of eval'd strings in
> Facets, which
>  is out of the scope of this attempt
> ]
> [Fix in include_as_property.
> George Moschovitis <george.moschovitis at gmail.com>**20070201222701]
> [Moved attributeutils to nitro/util.
> George Moschovitis <george.moschovitis at gmail.com>**20070201180155]
> [Moved autoreload to nitro/util
> George Moschovitis <george.moschovitis at gmail.com>**20070201175601]
> [Removed glue/html.
> George Moschovitis <george.moschovitis at gmail.com>**20070201133616]
> [More fixes to make more examples run again.
> George Moschovitis <george.moschovitis at gmail.com>**20070201113941]
> [Some fixes to make more tests pass.
> George Moschovitis <george.moschovitis at gmail.com>**20070201102019]
> [Use daemons 1.0.4 [pistos]
> George Moschovitis <george.moschovitis at gmail.com>**20070131123211]
> [Minor.
> George Moschovitis <george.moschovitis at gmail.com>**20070131123051]
> [Update to make compatible with facets 1.8.8
> George Moschovitis <george.moschovitis at gmail.com>**20070131122951]
> [Removed gen project.
> George Moschovitis <george.moschovitis at gmail.com>**20070130213755]
> [Removed nitro/version.rb
> George Moschovitis <george.moschovitis at gmail.com>**20070130213303]
> [Added the --create myapp option to the nitro command.
> George Moschovitis <george.moschovitis at gmail.com>**20070130212817]
> [Bumped version, use >= for external dependencies in gemspec files.
> George Moschovitis <george.moschovitis at gmail.com>**20070130190409]
> [Small fix in mail.
> George Moschovitis <george.moschovitis at gmail.com>**20070130133455]
> [This is a BIG patch. Many many changes to make Nitro compatible with the
> latest version of Facets. The new annotation (and ann_attr.rb)
> implementation is used now. Not fully tested yet.
> George Moschovitis <george.moschovitis at gmail.com>**20070129175454]
> [Made encode_url much more flexible with some shortcuts: R(User, :login)
> == R(User::Controller, :login), user = User[1]; R(user, :delete) ==
> R(User::Controller, :delete, :oid, user.oid). Updated test case.
> George Moschovitis <george.moschovitis at gmail.com>**20070124235748]
> [Small changes on the previous patch.
> George Moschovitis <george.moschovitis at gmail.com>**20070124174909]
> [cache_pstore_v2
> lasso at lassoweb.se**20070123181625]
> [Added option to include a text file in an element template, useful to
> reuse .xinc templates inside elements.
> George Moschovitis <george.moschovitis at gmail.com>**20070123234701]
> [Show entity oids in admin screen.
> George Moschovitis <george.moschovitis at gmail.com>**20070117100117]
> [Use a flag to skip sweepers (hack implementation, rethink).
> George Moschovitis <george.moschovitis at gmail.com>**20070117100049]
> [Don't overwrite create_time when inserting a timestamped object.
> George Moschovitis <george.moschovitis at gmail.com>**20070115110125]
> [Fix in sql indices creation.
> George Moschovitis <george.moschovitis at gmail.com>**20070114234655]
> [proto fcgi.rb -> dispatch.fcgi
> Fabian Buch <fabian at fabian-buch.de>**20070111140200
>  and changed shebang to #!/usr/bin/env ruby
> ]
> [Minor stuff.
> George Moschovitis <george.moschovitis at gmail.com>**20070112085957]
> [f.attribute appends "_ctl" to the id. label now too [Malte]
> Jonathan Buch <john at oxyliquit.de>**20070111135608]
> [bumped 2006 to 2007, bumped version to 0.42.0
> George Moschovitis <george.moschovitis at gmail.com>**20070109090930]
> [logger fix, print argument error when $DBG
> Jonathan Buch <john at oxyliquit.de>**20070105125305
>  Also adds a testcase to tc controller params, thanks Kartesus.
>  Since any ArgumentError triggered the 'Wrong parameter count' error,
>  we better use $DBG to make the old error available when developing.
> ]
> [Moved call/answer in separate file, slightly improved.
> George Moschovitis <george.moschovitis at gmail.com>**20070102173659]
> [Removed old sanitize code + html tokenizer from glue directory.
> George Moschovitis <george.moschovitis at gmail.com>**20061231175707]
> [don't override sequence in psql adapter
> Jonathan Buch <john at oxyliquit.de>**20061229232529]
> [Make mysql escape a little safer (investigate this).
> George Moschovitis <george.moschovitis at gmail.com>**20061231150128]
> [Better rendering of checkbox control.
> George Moschovitis <george.moschovitis at gmail.com>**20061231150112]
> [Set content_type / charset in outgoing emails.
> George Moschovitis <george.moschovitis at gmail.com>**20061231150048]
> [Better error reporting in form attributes.
> George Moschovitis <george.moschovitis at gmail.com>**20061228174034]
> [Fix in compiler.
> George Moschovitis <george.moschovitis at gmail.com>**20061228174022]
> [Full error reporting in live mode.
> George Moschovitis <george.moschovitis at gmail.com>**20061228125612]
> [Added create_on_insert test case.
> George Moschovitis <george.moschovitis at gmail.com>**20061228112250]
> [Added option :create_on_insert in has_one relations, to automatically
> create the target class by default. For example:
> George Moschovitis <george.moschovitis at gmail.com>**20061228111740]
> [Convienience helper in scaffold, automatically enchants all entities.
> George Moschovitis <george.moschovitis at gmail.com>**20061228111706]
> [Updated TODO.
> George Moschovitis <george.moschovitis at gmail.com>**20061228111650]
> [Updated html_filter.
> George Moschovitis <george.moschovitis at gmail.com>**20061227214552]
> [some sti fixes, minor other stuff
> Jonathan Buch <john at oxyliquit.de>**20061227161104]
> [WITHOUT OIDS for psql, psql < 8.0 add oid column without that
> Jonathan Buch <john at oxyliquit.de>**20061227145633]
> [set force_boolean for populate_object (.assign) to true as default
> Jonathan Buch <john at oxyliquit.de>**20061213110710]
> [fix nasty sti bug
> Jonathan Buch <john at oxyliquit.de>**20061213110312
>  it wanted the 'ogtype' field always as the first field.  Fix to not rely
> on
>  that.
> ]
> [sqlite enhancements
> Jonathan Buch <john at oxyliquit.de>**20061213110215]
> [Fix for sql.rb create_field map to make it even more general
> Jonathan Buch <john at oxyliquit.de>**20061213105840
>  also some minor enhancements in tcs
> ]
> [split method_missing in entity.rb
> Jonathan Buch <john at oxyliquit.de>**20061209123335
>  move functionality to 2 extra methods, find_by_() and
> find_or_create_by_()
> ]
> [oracle fixes, resolve_limit_options works
> Jonathan Buch <john at oxyliquit.de>**20061208194811]
> [sql.rb split create_table, oracle fixes
> Jonathan Buch <john at oxyliquit.de>**20061208181706]
> [Fix some bugs that prevernted admin to work.
> George Moschovitis <george.moschovitis at gmail.com>**20061224122801]
> [Security: auto html_filter all string parameters in request.fill. Use a
> new whitelist based version fo html filtering.
> George Moschovitis <george.moschovitis at gmail.com>**20061224122639]
> [use ',' as tags separator by defautl as well.
> George Moschovitis <george.moschovitis at gmail.com>**20061222121519]
> [Dont pass resource uris to Nitro and don't try to handle Nitro uris with
> Webricks FileHandler.
> George Moschovitis <george.moschovitis at gmail.com>**20061220154108]
> [Made the Template transformation pluggable (and not added by default at
> the end of the transformation pipeline. This way alternative template
> engines may be used. [manveru]
> George Moschovitis <george.moschovitis at gmail.com>**20061220151314]
> [Moved markup.rb to util/markup.rb
> George Moschovitis <george.moschovitis at gmail.com>**20061220105332]
> [Removed old, unused scaffolding code.
> George Moschovitis <george.moschovitis at gmail.com>**20061220104601]
> [Moved spark and flare into example to cleanup the dir structure.
> George Moschovitis <george.moschovitis at gmail.com>**20061220101826]
> [Fixed a @params bug.
> George Moschovitis <george.moschovitis at gmail.com>**20061220101632]
> [Moved sanitize into nitro/utils.
> George Moschovitis <george.moschovitis at gmail.com>**20061220101609]
> [Fixed admin part sitepath bug [rayman].
> George Moschovitis <george.moschovitis at gmail.com>**20061220100514]
> [support :psql again as store... it's nicer to type and doesn't break the
> old tutorials/configs anymore
> manveru at weez-int.com**20061218160439]
> [Some more fixes to make get/post params work.
> George Moschovitis <george.moschovitis at gmail.com>**20061218112234]
> [Remove post/get params  fix.
> George Moschovitis <george.moschovitis at gmail.com>**20061218111227]
> [FeedHelper Atom with html content
> Fabian Buch <fabian at fabian-buch.de>**20061215110619
>  Atom can contain html, but only if marked as that. This patch sets
>  the markup type of content to be always html (doesn't hurt if non-markup
>  text is provided). With this change it looks much nicer in many
> FeedReaders.
>  ATTENTION: changes API: provide markuped content to FeedHelper, it makes
> no
>  sense that the FeedHelper calls the markup() method, since not everyone
>  uses RedCloth for his/her markup (e.g. Oxy uses BlueCloth).
> ]
> [Some changes to the error handling code to return correct status codes. I
> am not happy with this at the moment, anyone  can improve this?
> George Moschovitis <george.moschovitis at gmail.com>**20061218105923]
> [WebFile: use more useful controls
> Fabian Buch <fabian at fabian-buch.de>**20061214134538]
> [Fix in taggable to_s, separate to_s_safe method (move this to greek.rb ?)
> George Moschovitis <george.moschovitis at gmail.com>**20061213092136]
> [TAG 0.41.0
> George Moschovitis <george.moschovitis at gmail.com>**20061213092116]
> Patch bundle hash:
> fb29213773237c8e3e718bf6f19440cab671af0e
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070710/ce64f5fc/attachment-0001.html 

From john at oxyliquit.de  Wed Jul 11 01:20:55 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 11 Jul 2007 08:20:55 +0300
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <afd80b540707101240s489790d2hfc4c890a295ebae1@mail.gmail.com>
References: <op.tu8980yrxegpx6@jo.local>
	<afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>
	<4693DCBF.4030500@arnebrasseur.net>
	<afd80b540707101240s489790d2hfc4c890a295ebae1@mail.gmail.com>
Message-ID: <op.tvabssh3xegpx6@jo.local>

Hi.

> please, remind me the url of your repo.

his repo is http://darcs.arnebrasseur.net/glycerin

but the easiest is to do just:

$ cat _darcs/prefs/repos

which will show you all repos you interacted with.  If you use the
bash autocomplete for darcs you are even able to use `darcs pull <tab>`
to get to that list.

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Wed Jul 11 01:36:21 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Wed, 11 Jul 2007 08:36:21 +0300
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <op.tvabssh3xegpx6@jo.local>
References: <op.tu8980yrxegpx6@jo.local>
	<afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>
	<4693DCBF.4030500@arnebrasseur.net>
	<afd80b540707101240s489790d2hfc4c890a295ebae1@mail.gmail.com>
	<op.tvabssh3xegpx6@jo.local>
Message-ID: <afd80b540707102236u5bfefa85v2802bca7968a4932@mail.gmail.com>

>
> bash autocomplete for darcs you are even able to use `darcs pull <tab>`
>

nice one!

-g.


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070711/137b1849/attachment.html 

From arne at arnebrasseur.net  Wed Jul 11 03:43:36 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Wed, 11 Jul 2007 09:43:36 +0200
Subject: [Nitro] Current Oxyliquit repo status
In-Reply-To: <op.tvabssh3xegpx6@jo.local>
References: <op.tu8980yrxegpx6@jo.local>	<afd80b540707101142pa4d4fbam75be8b75c046b558@mail.gmail.com>	<4693DCBF.4030500@arnebrasseur.net>	<afd80b540707101240s489790d2hfc4c890a295ebae1@mail.gmail.com>
	<op.tvabssh3xegpx6@jo.local>
Message-ID: <46948A28.1010400@arnebrasseur.net>

Jonathan Buch schreef:
> his repo is http://darcs.arnebrasseur.net/glycerin
>   
Note that I didn't send the element-children-as-dictionary patch, don't 
pull that one if you already did it yourself. I will unpull mine and 
pull yours.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From george.moschovitis at gmail.com  Wed Jul 11 05:57:27 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Wed, 11 Jul 2007 12:57:27 +0300
Subject: [Nitro] patches
Message-ID: <afd80b540707110257v4a202424ud821a1e83168154c@mail.gmail.com>

I did some quick testing of the patches with my apps. Everything seems to
run ok, so I added them to the repo. I will examine them in more detail in
the coming days.

thanks,
-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070711/37c7c510/attachment.html 

From john at oxyliquit.de  Wed Jul 11 06:13:36 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 11 Jul 2007 13:13:36 +0300
Subject: [Nitro] patches
In-Reply-To: <afd80b540707110257v4a202424ud821a1e83168154c@mail.gmail.com>
References: <afd80b540707110257v4a202424ud821a1e83168154c@mail.gmail.com>
Message-ID: <op.tvaoreilxegpx6@jo.local>

Hi,

> I did some quick testing of the patches with my apps. Everything seems to
> run ok, so I added them to the repo. I will examine them in more detail  
> in
> the coming days.

ayy!  Many thanks ^_^

Some of them just make life so much easier.  :P

Jo

From Jimmy.Jazz at gmx.net  Sun Jul 15 09:15:27 2007
From: Jimmy.Jazz at gmx.net (Jimmy Jazz)
Date: Sun, 15 Jul 2007 15:15:27 +0200
Subject: [Nitro] how to initialize @color and make it visible into the
 template?
In-Reply-To: <op.tu8kdo0axegpx6@jo.local>
References: <46927C41.90907@gmx.net> <op.tu8kdo0axegpx6@jo.local>
Message-ID: <469A1DEF.8080507@gmx.net>

Jonathan Buch a ?crit :

> 
> You do that by escaping.   "\#{@color}", this saves the string
> "#{@color}" back to the template, which then gets normally executed
> like you had written #{@color} in the template.
> 
> I's just a matter of scope here.

Indeed, that's made it. I made a mistake as I took the example from
tc_element.rb and spark as such. It is without the backslash. I'm now
able to use the variable within a <?r ?> or a controller.

> 
> Well, we aren't actually working on making Nitro elitist.  ;) 

I understand your point of view :)

Nitro offers many possibilities and does so much out of the sight of the
user, that is why i'm not always sure how to handle nitro. In my
opinion, the best documentation is the code itself. Also, the code is
quite technical and also difficult to understand (the number of modules
and files take a part of that difficulty) . I think it would be great to
just have a brief documentation that give us a view of nitro's internal,
like how the compilers, filters and dispatchers are working together and
why nitro is using annotations or settings for example.
George write a useful explanation how og works with nitro. Also he made
og so transparent that we could even not to know about it at all ;) The
same introduction about nitro would be great.

> that very few people are working on making it less elitist (meaning docs,
> tutorials, examples).
> This is a cycle, no people no docs, no docs no people.  Which also means,
> anybody can help break that cycle, simply by writing down your own
> experience, like a small tutorial on what you find important to know
> as a beginner.
I have followed nitro for a couple of month and i found it really
interesting to use. I'm sure George is on the right way to make nitro
popular and useful for geeks as well for noobs.
Also, the best gift you could give to a beginner, is perhaps a simple
model of a dynamic web site with just the minimum functionalities
(without javascript, ajax, etc) that nitro can give (and not what nitro
can hide ;). So he can understand how whole the thing interacts,
discover the power of nitro and share his experience with the community.
Contrary to spark or nitro blog, the model should just be composed of
"useful" and various bricks to illustrate nitro's functionalities. So
you won't need to write documentations up to date. The videos were a
good idea, but it is quite hard to follow. At any first difficulty, you
will lose the thread of the demonstration. Anyway, that is a good
promotion for nitro.

Before Nitro I was never interested in web development because i have
always found it too messy. As i discovered ruby my point of view has
radically changed. You are now able to build your own web pages in an
elegant and "easy" way. And that is what matters.

To write a tutorial you must know where to go and what is important to
know. I'm just illiterate in nitro "language" to do it now.
I hope i will soon be able to offer something useful and break the cycle
you described.

> The second is, fast development cycle means docs are out of date fast,
> so, few people to keep them up to date, which means bad docs, which also
> creates problems for beginners.  So, we need more stable people who
> constantly update docs.  Hard, very.
> I'm far beyond the beginner levels sadly and can't really forsee what
> beginners need, but at least I try to help.  :)
Anyway, you have done it really well. You take time to answer questions
even if like mine (sorry for that) they are not really relevant and
helpful.

> Everything in Ruby or any other programming language is a matter
> of scope, try to think 'where does this variable appear, where
> am I now, can I access this variable from the current scope?'.
> If the variable can't be accessed from the current scope, there's
> two possibilities, bring the foreign scope to the current one,
> or bring the 'execution' of the variable to the foreign scope.
> 
You have finally answered to your own interrogation about beginners: It
is a matter of scope and not only on the programming language level. One
question could be: How should a variable, an instance or a method be
accessed between the different files into a nitro application tree to
make a site dynamic with a MVC approach ?

Nitro gives us a lot of liberty and that is certainly what is the most
exciting but what actually makes it difficult to understand.It looks
certainly trivial to you because you are working with it and participate
in of its development, but not to us, beginners. It just like that: Do I
have the right information and how can I use it ? :).

Jj
-- 

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)






From george.moschovitis at gmail.com  Sun Jul 15 09:54:24 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sun, 15 Jul 2007 16:54:24 +0300
Subject: [Nitro] Nitro Week
Message-ID: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>

Dear devs,

I have allocated the coming week to work on Nitro. The goal is to make
0.50.0 ready for release. I would like to know, who can help me during this
week.
I will need:

- help with converting test cases to specs
- annotating the source code with useful comments.
- bug reports
- improving the RELEASES text for the new release.

I especially will need the help of Tom to fix some problems with Aspects and
try to get rid of Glue altogether. From tomorrow I will try to be online on
IRC so if you want to bring something to my attention you can join me there.

regards,
George.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070715/41581e87/attachment.html 

From arne at arnebrasseur.net  Sun Jul 15 10:36:16 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Sun, 15 Jul 2007 16:36:16 +0200
Subject: [Nitro] Nitro Week
In-Reply-To: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
Message-ID: <469A30E0.50501@arnebrasseur.net>

It's currently very busy here, but I might be able to help the second 
halve of the week.

(ab)

George Moschovitis schreef:
> Dear devs,
>
> I have allocated the coming week to work on Nitro. The goal is to make 
> 0.50.0 ready for release. I would like to know, who can help me during 
> this week.
> I will need:
>
> - help with converting test cases to specs
> - annotating the source code with useful comments.
> - bug reports
> - improving the RELEASES text for the new release.
>
> I especially will need the help of Tom to fix some problems with 
> Aspects and try to get rid of Glue altogether. From tomorrow I will 
> try to be online on IRC so if you want to bring something to my 
> attention you can join me there.
>
> regards,
> George.
>
> -- 
> http://phidz.com
> http://blog.gmosx.com
> http://cull.gr
> http://www.joy.gr
> http://nitroproject.org
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general


-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070715/74d9fd8a/attachment.html 

From john at oxyliquit.de  Sun Jul 15 12:21:48 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 15 Jul 2007 19:21:48 +0300
Subject: [Nitro] Nitro Week
In-Reply-To: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
Message-ID: <op.tvikwczixegpx6@jo.local>

Hi,

> I have allocated the coming week to work on Nitro. The goal is to make
> 0.50.0 ready for release. I would like to know, who can help me during this
> week.

great!

> - help with converting test cases to specs

I hope you can help arne with those, just convert crudely and let me clean
up after.  :P
(Of course, anyone is welcome to help here.  Surprise me.  :P)

> - annotating the source code with useful comments.
> - bug reports

Only one I'm having conceptual problems with:

OgModel#saved?

This is determined by asking if the primary key is not nil.  This works fine
as long as one uses autogenerated primary keys.  There's only one spec which
touches that issue, and that spec uses .insert to get around that.

The next piece of the puzzle is:  .create
In the current incarnation of .create it uses .insert to persist the object.
(This was a recent change from me, in the last 15 patches).  Before it used
.save which obviously breaks non-autogenerated pks.

Now, with .insert a different problem crops up, autosaving of relations +
.create blocks:

OgModel.create(:foo) do |o|
   o.some_attr = 'foo' # this is ok
   o.some_rel = some_obj # this saves `o` in the background
end

So, what happens essentially with my .insert patch for .create, it tries to
insert the object twice into the DB.  Once for autosaving, once in .create.

Aurelianito (on irc) cought that issue, I've never used .create with a block
so I'm grateful someone else does.

There's 2 ways we can take here, either create a 'persisted' flag on each
og object, or continue treating non-autogenerated pks as step-childs.

(I myself will just continue using my .insert patch as I don't use blocks
on .insert but many non standard pks.  But then again, my repo is quite
different anyhow.  :P)

So basically the issue here is the .saved? reacting on the 'wrong input'.
What are we gonna do?

> - improving the RELEASES text for the new release.

I honestly have no idea whatsoever what is new in this release... ^^;

> I especially will need the help of Tom to fix some problems with Aspects and
> try to get rid of Glue altogether.

Just got an idea for glue so you don't have to make a gem for it even if it
doesn't get removed:  just copy paste the glue parts in raw/nitro/og, just
for the gems.

Jo

-- 
Feel the love
http://pinkjuice.com/pics/ruby.png

From george.moschovitis at gmail.com  Mon Jul 16 02:35:07 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Mon, 16 Jul 2007 09:35:07 +0300
Subject: [Nitro] Nitro Week
In-Reply-To: <op.tvikwczixegpx6@jo.local>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
	<op.tvikwczixegpx6@jo.local>
Message-ID: <afd80b540707152335uaf18870i12eed34736fdda61@mail.gmail.com>

>
> OgModel#saved?
>
> This is determined by asking if the primary key is not nil.  This works
> fine
> as long as one uses autogenerated primary keys.  There's only one spec
> which
> touches that issue, and that spec uses .insert to get around that.



What is your proposal  ?


The next piece of the puzzle is:  .create
> In the current incarnation of .create it uses .insert to persist the
> object.
> (This was a recent change from me, in the last 15 patches).  Before it
> used
> .save which obviously breaks non-autogenerated pks.
>
> Now, with .insert a different problem crops up, autosaving of relations +
> .create blocks:
>
> OgModel.create(:foo) do |o|
>    o.some_attr = 'foo' # this is ok
>    o.some_rel = some_obj # this saves `o` in the background
> end
>
> So, what happens essentially with my .insert patch for .create, it tries
> to
> insert the object twice into the DB.  Once for autosaving, once in
> .create.
>
> Aurelianito (on irc) cought that issue, I've never used .create with a
> block
> so I'm grateful someone else does.
>
> There's 2 ways we can take here, either create a 'persisted' flag on each
> og object, or continue treating non-autogenerated pks as step-childs.
>
> (I myself will just continue using my .insert patch as I don't use blocks
> on .insert but many non standard pks.  But then again, my repo is quite
> different anyhow.  :P)
>
> So basically the issue here is the .saved? reacting on the 'wrong input'.
> What are we gonna do?


Hmm..this needs some thought...


>
> > I especially will need the help of Tom to fix some problems with Aspects
> and
> > try to get rid of Glue altogether.
>
> Just got an idea for glue so you don't have to make a gem for it even if
> it
> doesn't get removed:  just copy paste the glue parts in raw/nitro/og, just
> for the gems.
>

I think I will follow this tip.


BTW, I just talk we Tom. He proposed that we synchronize the release of
Nitro 0.50.0 with the release of Facets 2.0. I kind of agree. One of the
major features of 0.50.0 is that it catches up with the latest facets (1.8.0)
It would be not nice if one week after the release of Nitro, Facets jumped
again to a new version with a different structure. Plus it gives us some
more time.

I will postpone the Nitro week for a bit, but still I plan to work this week
on Nitro cleanup, bug fixing, and probably some new features (that I need
for my projects).

regards,
George.



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070716/a563a1f3/attachment.html 

From john at oxyliquit.de  Wed Jul 18 02:43:36 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 18 Jul 2007 09:43:36 +0300
Subject: [Nitro] how to initialize @color and make it visible into the
	template?
In-Reply-To: <469A1DEF.8080507@gmx.net>
References: <46927C41.90907@gmx.net> <op.tu8kdo0axegpx6@jo.local>
	<469A1DEF.8080507@gmx.net>
Message-ID: <op.tvnd8lgvxegpx6@jo.local>

Hi,

(sorry for the delay, I've gots teh work and your

> Indeed, that's made it. I made a mistake as I took the example from
> tc_element.rb and spark as such. It is without the backslash. I'm now
> able to use the variable within a <?r ?> or a controller.

I think G fixed that recently in spark (at least I have seen fixes
like that while I skimmed his patches).  Ah no, that might have been
in the documentation of Elements.. yes.. yes..

>> Well, we aren't actually working on making Nitro elitist.  ;)
>
> I understand your point of view :)
>
> Nitro offers many possibilities and does so much out of the sight of the
> user, that is why i'm not always sure how to handle nitro. In my
> opinion, the best documentation is the code itself.

I wouldn't exactly say 'best', in Nitro I never really had to look up that
much source, it used to 'just work' with whatever I did.  :P
That won't produce 'optimal' code as one misses out on some stuff, but
generally it makes fun and gets stuff done.  :P

With Og I have had more arguments with, even right now, I dive into Og
code at least twice a day to check for exact behaviour or to make bugfixes
or create new features.

> Also, the code is
> quite technical and also difficult to understand (the number of modules
> and files take a part of that difficulty) . I think it would be great to
> just have a brief documentation that give us a view of nitro's internal,
> like how the compilers, filters and dispatchers are working together and
> why nitro is using annotations or settings for example.

Learning a framework from the inside just takes time and practice, good
developer tools help greatly, 'find in project', big help.

> I have followed nitro for a couple of month and i found it really
> interesting to use. I'm sure George is on the right way to make nitro
> popular and useful for geeks as well for noobs.
> Also, the best gift you could give to a beginner, is perhaps a simple
> model of a dynamic web site with just the minimum functionalities
> (without javascript, ajax, etc) that nitro can give (and not what nitro
> can hide ;). So he can understand how whole the thing interacts,
> discover the power of nitro and share his experience with the community.
> Contrary to spark or nitro blog, the model should just be composed of
> "useful" and various bricks to illustrate nitro's functionalities. So
> you won't need to write documentations up to date.

Well, the plan of spark/flare is indeed to show off what nitro can be
used for.  The 'interesting conglomerat of functionality', I dunno if
it'd really be useful if the only purpose is to show off anything
Nitro can do.

> The videos were a
> good idea, but it is quite hard to follow. At any first difficulty, you
> will lose the thread of the demonstration. Anyway, that is a good
> promotion for nitro.

As always, if outdated it will cause users to 'hang in mid air'.  I
never tried to 'repeat' a screencast, as I find that kind of dumb and
repetitive.  :P  I use screencasts for 'how in general does that guy
do this kind of stuff', just looking for ideas.

> Before Nitro I was never interested in web development because i have
> always found it too messy. As i discovered ruby my point of view has
> radically changed. You are now able to build your own web pages in an
> elegant and "easy" way. And that is what matters.

Yay for Ruby.  ^_^

> To write a tutorial you must know where to go and what is important to
> know. I'm just illiterate in nitro "language" to do it now.
> I hope i will soon be able to offer something useful and break the cycle
> you described.

Take your time, there's no need to hurry.  :)

> Anyway, you have done it really well. You take time to answer questions
> even if like mine (sorry for that) they are not really relevant and
> helpful.

Uh, that is a mere matter of perspective, if you asked, you'll surely
find it helpful if I answer.  Somebody finding me helpful is all I
really crave for.  :P

> You have finally answered to your own interrogation about beginners: It
> is a matter of scope and not only on the programming language level. One
> question could be: How should a variable, an instance or a method be
> accessed between the different files into a nitro application tree to
> make a site dynamic with a MVC approach ?

I have a few graphs for Nitro here, describing part of the Nitro structure,
maybe I can dig those up and hand them to you.. (If I can find them.)
Making a graph of scopes for template/elements/controllers would fit right
there, I'll try to make that.

> Nitro gives us a lot of liberty and that is certainly what is the most
> exciting but what actually makes it difficult to understand.It looks
> certainly trivial to you because you are working with it and participate
> in of its development, but not to us, beginners. It just like that: Do I
> have the right information and how can I use it ? :).

Amen.  :)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Wed Jul 18 02:56:02 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 18 Jul 2007 09:56:02 +0300
Subject: [Nitro] Nitro Week
In-Reply-To: <afd80b540707152335uaf18870i12eed34736fdda61@mail.gmail.com>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
	<op.tvikwczixegpx6@jo.local>
	<afd80b540707152335uaf18870i12eed34736fdda61@mail.gmail.com>
Message-ID: <op.tvnevoooxegpx6@jo.local>

Hi,

> What is your proposal  ?

my proposal is that we both think about on how this can be resolved.  :)

>> So basically the issue here is the .saved? reacting on the 'wrong  
>> input'.
>> What are we gonna do?
>
> Hmm..this needs some thought...

Exactly.  :P

> BTW, I just talk we Tom. He proposed that we synchronize the release of
> Nitro 0.50.0 with the release of Facets 2.0. I kind of agree. One of the
> major features of 0.50.0 is that it catches up with the latest facets  
> (1.8.0)
> It would be not nice if one week after the release of Nitro, Facets  
> jumped again to a new version with a different structure. Plus it gives
> us some more time.

Yeah, this is a good point, we'd regret it if we didn't wait for facets
2.0.

> I will postpone the Nitro week for a bit, but still I plan to work this  
> week on Nitro cleanup, bug fixing, and probably some new features (that
> I need for my projects).

Yes, please do so.  :)  (remember the specs!  I know you don't like them,
but they _are_ useful ;) )

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Wed Jul 18 02:57:55 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Wed, 18 Jul 2007 09:57:55 +0300
Subject: [Nitro] Nitro Week
In-Reply-To: <op.tvnevoooxegpx6@jo.local>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
	<op.tvikwczixegpx6@jo.local>
	<afd80b540707152335uaf18870i12eed34736fdda61@mail.gmail.com>
	<op.tvnevoooxegpx6@jo.local>
Message-ID: <afd80b540707172357mbacfc17mb2daccd1255d0ed7@mail.gmail.com>

>
> Yes, please do so.  :)  (remember the specs!  I know you don't like them,
> but they _are_ useful ;) )


I like them ;-)

-g.



-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070718/a10cbef9/attachment.html 

From john at oxyliquit.de  Wed Jul 18 03:08:57 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 18 Jul 2007 10:08:57 +0300
Subject: [Nitro] Nitro Week
In-Reply-To: <afd80b540707172357mbacfc17mb2daccd1255d0ed7@mail.gmail.com>
References: <afd80b540707150654x13a820b8v3c8189cc36cbf15@mail.gmail.com>
	<op.tvikwczixegpx6@jo.local>
	<afd80b540707152335uaf18870i12eed34736fdda61@mail.gmail.com>
	<op.tvnevoooxegpx6@jo.local>
	<afd80b540707172357mbacfc17mb2daccd1255d0ed7@mail.gmail.com>
Message-ID: <op.tvnfg7spxegpx6@jo.local>

Hi,

>> Yes, please do so.  :)  (remember the specs!  I know you don't like  
>> them, but they _are_ useful ;) )
>
> I like them ;-)

So give em' some lovin'!  ^_-

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From arne at arnebrasseur.net  Wed Jul 18 03:51:07 2007
From: arne at arnebrasseur.net (arne at arnebrasseur.net)
Date: Wed, 18 Jul 2007 00:51:07 -0700 (PDT)
Subject: [Nitro] how to initialize @color and make it visible into the
 template?
In-Reply-To: <op.tvnd8lgvxegpx6@jo.local>
References: <46927C41.90907@gmx.net> <op.tu8kdo0axegpx6@jo.local>
	<469A1DEF.8080507@gmx.net> <op.tvnd8lgvxegpx6@jo.local>
Message-ID: <1610.87.64.194.170.1184745067.squirrel@webmail.arnebrasseur.net>

Jo said:
> Learning a framework from the inside just takes time and practice, good
> developer tools help greatly, 'find in project', big help.

Spending an hour or so to read the texinfo manual of find/grep can also be
time well spent.

> I have a few graphs for Nitro here, describing part of the Nitro
> structure,
> maybe I can dig those up and hand them to you.. (If I can find them.)
> Making a graph of scopes for template/elements/controllers would fit right
> there, I'll try to make that.

This kind of stuff would be really useful. Higher level documentation
doesn't get outdated so fast, and is especially helpful for people first
looking at the source.

> Amen.  :)

Amen ^_^

(ab)




From john at oxyliquit.de  Wed Jul 18 16:13:32 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 18 Jul 2007 23:13:32 +0300
Subject: [Nitro] Nitro Structure Graphics
Message-ID: <op.tvofsutaxegpx6@jo.local>

Hi,

as promised, slightly updated graphs from quite some time ago, they
were planned for a tutorial (or rather, a whole walkthrough) for which
I never got enough ideas as energy to write it.

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct1.png
Type: image/png
Size: 57929 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0008.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct3.png
Type: image/png
Size: 31011 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0009.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct5.png
Type: image/png
Size: 45334 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0010.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct8.png
Type: image/png
Size: 49718 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0011.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct6.png
Type: image/png
Size: 11535 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0012.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct2.png
Type: image/png
Size: 24367 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0013.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct4.png
Type: image/png
Size: 32858 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0014.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nitro_dirstruct7.png
Type: image/png
Size: 27848 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070718/e264e4ff/attachment-0015.png 

From william.full.moon at gmail.com  Wed Jul 18 23:02:04 2007
From: william.full.moon at gmail.com (* William)
Date: Thu, 19 Jul 2007 13:02:04 +1000
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvofsutaxegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
Message-ID: <021201c7c9b1$349b3610$0401a8c0@ghostgum>

Those are fantastic! 

-----Original Message-----
From: nitro-general-bounces at rubyforge.org
[mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Jonathan Buch
Sent: Thursday, 19 July 2007 06:14
To: nitro-general at rubyforge.org
Subject: [Nitro] Nitro Structure Graphics
Importance: Low

Hi,

as promised, slightly updated graphs from quite some time ago, they were
planned for a tutorial (or rather, a whole walkthrough) for which I never
got enough ideas as energy to write it.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.6/900 - Release Date: 14-Jul-2007
15:36
 


From george.moschovitis at gmail.com  Thu Jul 19 02:37:29 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Thu, 19 Jul 2007 09:37:29 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvofsutaxegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
Message-ID: <afd80b540707182337h1bf9abf5tb43f31626fef4c1e@mail.gmail.com>

These images are great...

Some minor remarks:

you don't have to extend from Nitro::Controller, ie no need for:

class MyController < Nitro::Controller
end

just

class MyController
end

does the trick.

Moreover, I would suggest that you use the cookie based session system
introduced in 0.50.0
So you don't need a session/state server any more...

Finaly your css files now reside in the tremplate dir, ie:

template/css/style.cssx

that typically gets rendered and cached in

public/css/style.css

you can use all Nitro templating features in a .cssx file (and typically in
.*X files)


thanks again for these great images,
-g.

On 7/18/07, Jonathan Buch <john at oxyliquit.de> wrote:
>
> Hi,
>
> as promised, slightly updated graphs from quite some time ago, they
> were planned for a tutorial (or rather, a whole walkthrough) for which
> I never got enough ideas as energy to write it.
>
> Jo
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>
>


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070719/0ad8ddd3/attachment.html 

From john at oxyliquit.de  Thu Jul 19 12:46:06 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Thu, 19 Jul 2007 19:46:06 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <021201c7c9b1$349b3610$0401a8c0@ghostgum>
References: <op.tvofsutaxegpx6@jo.local>
	<021201c7c9b1$349b3610$0401a8c0@ghostgum>
Message-ID: <op.tvp0u4a1xegpx6@jo.local>

Hi,

> Those are fantastic!

thank you very much!  Feel free to use/show around, sell them in your
garage sale.  :P  No really, I'm glad someone appriciates my near-non-
existant design skills which are fully exploited by this tool I used.  ;)
If they were actually useful, it'd be even better, someone's gotta
step up and write a Nitro book or something, if someone ever does she/he
can always ask me for graphs if needed.  :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Thu Jul 19 12:58:02 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Thu, 19 Jul 2007 19:58:02 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <afd80b540707182337h1bf9abf5tb43f31626fef4c1e@mail.gmail.com>
References: <op.tvofsutaxegpx6@jo.local>
	<afd80b540707182337h1bf9abf5tb43f31626fef4c1e@mail.gmail.com>
Message-ID: <op.tvp1e0wxxegpx6@jo.local>

Hi,

[Descriptions on how to make better use of Nitros current features]

> thanks again for these great images,

if the pictures actually get used instead of lying around on my
harddrive, I'd be inclined to update them to also incorporate new
features, but right now they'll just outdate again.  :P

But yeah, if you find them useful for anything at all, you have my
permission to do whatever.  :)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From arne at arnebrasseur.net  Thu Jul 19 13:30:37 2007
From: arne at arnebrasseur.net (arne at arnebrasseur.net)
Date: Thu, 19 Jul 2007 10:30:37 -0700 (PDT)
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvp0u4a1xegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
	<021201c7c9b1$349b3610$0401a8c0@ghostgum>
	<op.tvp0u4a1xegpx6@jo.local>
Message-ID: <49785.217.136.252.52.1184866237.squirrel@webmail.arnebrasseur.net>


> step up and write a Nitro book or something, if someone ever does she/he
> can always ask me for graphs if needed.  :P
>

Deal!

(ab)



From transfire at gmail.com  Thu Jul 19 18:27:56 2007
From: transfire at gmail.com (Trans)
Date: Thu, 19 Jul 2007 22:27:56 -0000
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvofsutaxegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
Message-ID: <1184884076.019854.111500@22g2000hsm.googlegroups.com>

Where does Raw fit in?

T.


From john at oxyliquit.de  Fri Jul 20 02:30:29 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 20 Jul 2007 09:30:29 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <1184884076.019854.111500@22g2000hsm.googlegroups.com>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
Message-ID: <op.tvq203oexegpx6@jo.local>

Hi,

> Where does Raw fit in?

Raw is the parts which drive the controllers, the templating and provides
the general runtime, views etc.  It is what most of the old nitro was.

nitro is the 'how a Nitro application is started' and provides additional
libraries (like the admin/ part, a mailer and Aspects (reminds me, why
aren't those in facets, as they look kinda like they'd belong there)).

Like I told G on irc, I dunno if it was worth throwing out glue and
yet creating enother dependency, but that's just me.  :)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From transfire at gmail.com  Fri Jul 20 12:59:06 2007
From: transfire at gmail.com (Trans)
Date: Fri, 20 Jul 2007 16:59:06 -0000
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvq203oexegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
Message-ID: <1184950746.443825.17280@o61g2000hsh.googlegroups.com>



On Jul 19, 11:30 pm, "Jonathan Buch" <j... at oxyliquit.de> wrote:
> Hi,
>
> > Where does Raw fit in?
>
> Raw is the parts which drive the controllers, the templating and provides
> the general runtime, views etc.  It is what most of the old nitro was.
>
> nitro is the 'how a Nitro application is started' and provides additional
> libraries (like the admin/ part, a mailer and Aspects (reminds me, why
> aren't those in facets, as they look kinda like they'd belong there)).
>
> Like I told G on irc, I dunno if it was worth throwing out glue and
> yet creating enother dependency, but that's just me.  :)

I just thought maybe it should be in the depictions somewhere. But
thanks for
the explanation. I agree with you, basically. I understand the how the
split is nice from a developers point of view, but I don't see why it
needs to be a package. If the package can't do anything on it's own,
then that makes no sense. So why not just have a raw/ subdirectory
under nitro/ instead? Or, maybe go the other way. Move all the stuff
currently in Nitro over to Raw and then have Nitro just be a meta-
package (like Rails is for it's Action* and Active* components).

Aspects is in Facets, btw. I think there's some differences between
Nitro's version and Facets' version though that have yet to be worked
out. Actually there a couple of libs like that. That's kind of a
outstanding issue. If we have a lib that is used by all of nitro (raw/
og) but is still specific to nitro (ie. not general enough for
Facets), where does it go? My feeling is that this indicates an red
flag -- That the lib should probably be re-examined to see if it can
in fact be be generalized. My bet is that it can, but if not, then I
think we make an exception and have two copies, one in Og and one in
Raw/Nitro. Otherwise, maybe Nitro really does need a little "Glue".

There is one other issue I need to bring up about dependencies. Facets
2.0 is a major overhaul. And a few things are being separated out to
make Facets a stronger, leaner package. First among them are all the
web related libs. I've moved those to a new project I'm pretty sure
will be called "Blow" (Block+Web), unless someone else has a much
better name. So Nitro will at least have this additional dependency
besides. Along with that there may be two more dependencies -- 1) I'm
debating whether to make all the CLI utilities a separate project, and
2) I'm creating a new project that houses English grammer and language
related libs, like inflect.rb. I guess this project will just be
called "English". There are a lot of advantages in having a separate
project for this kinds of thing which ultimately could lead to a very
strong library of natural language processing. If Nitro is still
insisting on pluralizing table names (something I always thought was a
waste of good cpu cycles personally), then that will be additional
required dependency.

T.


From george.moschovitis at gmail.com  Fri Jul 20 14:50:01 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Fri, 20 Jul 2007 21:50:01 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <1184950746.443825.17280@o61g2000hsh.googlegroups.com>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
	<1184950746.443825.17280@o61g2000hsh.googlegroups.com>
Message-ID: <afd80b540707201150u15a9fd02n5514bc15ee959d73@mail.gmail.com>

>
> under nitro/ instead? Or, maybe go the other way. Move all the stuff
> currently in Nitro over to Raw and then have Nitro just be a meta-
> package (like Rails is for it's Action* and Active* components).


Nitro is exactly that, a metapackage for Raw, Og, Glue


-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070720/809dbf9f/attachment.html 

From john at oxyliquit.de  Fri Jul 20 15:25:49 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 20 Jul 2007 22:25:49 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <afd80b540707201150u15a9fd02n5514bc15ee959d73@mail.gmail.com>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
	<1184950746.443825.17280@o61g2000hsh.googlegroups.com>
	<afd80b540707201150u15a9fd02n5514bc15ee959d73@mail.gmail.com>
Message-ID: <op.tvr18ab3xegpx6@jo.local>

Hi,

>> under nitro/ instead? Or, maybe go the other way. Move all the stuff
>> currently in Nitro over to Raw and then have Nitro just be a meta-
>> package (like Rails is for it's Action* and Active* components).
>
>
> Nitro is exactly that, a metapackage for Raw, Og, Glue

maybe doing it like with Glue?  Just don't create an extra package
for gems, just put it in the Gem for Raw.  Whatever.   :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Fri Jul 20 15:25:50 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 20 Jul 2007 22:25:50 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <1184950746.443825.17280@o61g2000hsh.googlegroups.com>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
	<1184950746.443825.17280@o61g2000hsh.googlegroups.com>
Message-ID: <op.tvr2wr2ixegpx6@jo.local>

Hi,

> Otherwise, maybe Nitro really does need a little "Glue".

yes, good points.  Feature creep isn't such a nice thing to have and
with so many different things within Facets a little harsh organization
can't hurt.

> There is one other issue I need to bring up about dependencies. Facets
> 2.0 is a major overhaul. And a few things are being separated out to
> make Facets a stronger, leaner package. First among them are all the
> web related libs. I've moved those to a new project I'm pretty sure
> will be called "Blow" (Block+Web), unless someone else has a much
> better name. So Nitro will at least have this additional dependency
> besides.

I honestly don't have the overview over the dependencies within Nitro
which lead to Facets...

But, I kinda like "Blow".  :)  Don't get too cought up in naming issues
I'm waiting for Nitro 0.49 which will go out very early after you
release Facets 2.0.  :)  At least I hope so, /me pokes G to work on
specs.  :P
/me pokes busy busy Arne too :P

> Along with that there may be two more dependencies -- 1) I'm
> debating whether to make all the CLI utilities a separate project, and
> 2) I'm creating a new project that houses English grammer and language
> related libs, like inflect.rb. I guess this project will just be
> called "English". There are a lot of advantages in having a separate
> project for this kinds of thing which ultimately could lead to a very
> strong library of natural language processing.

> If Nitro is still
> insisting on pluralizing table names (something I always thought was a
> waste of good cpu cycles personally), then that will be additional
> required dependency.

Og never pluralizes tables (and never did).  What it does use pluralize
for is for creating nice relation names.

class Forum
   has_many User
end

Forum#users

And no, I don't feel like we're wasting cycles here.  ;)  It's merely the
Og way, which makes it feel so good.  :)  (Those methods are generated at
boot time via eval, so no runtime wasting going on here.)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From transfire at gmail.com  Sat Jul 21 01:19:13 2007
From: transfire at gmail.com (Trans)
Date: Sat, 21 Jul 2007 05:19:13 -0000
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <op.tvr2wr2ixegpx6@jo.local>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
	<1184950746.443825.17280@o61g2000hsh.googlegroups.com>
	<op.tvr2wr2ixegpx6@jo.local>
Message-ID: <1184995153.046491.323800@w3g2000hsg.googlegroups.com>



On Jul 20, 12:25 pm, "Jonathan Buch" <j... at oxyliquit.de> wrote:
> Hi,
>
> > Otherwise, maybe Nitro really does need a little "Glue".
>
> yes, good points.  Feature creep isn't such a nice thing to have and
> with so many different things within Facets a little harsh organization
> can't hurt.
>
> I honestly don't have the overview over the dependencies within Nitro
> which lead to Facets...

Maybe we can make a list of those soon.

> But, I kinda like "Blow".  :)  Don't get too cought up in naming issues

You got it...

  http://blow.rubyforge.org/

On a side note, another Facets derivative...

  http://stick.rubyforge.org/

All I need now is a little triangle corner graphic that says "It came
from Facets" or something like that :)

> I'm waiting for Nitro 0.49 which will go out very early after you
> release Facets 2.0.  :)  At least I hope so, /me pokes G to work on
> specs.  :P
> /me pokes busy busy Arne too :P
>
> > Along with that there may be two more dependencies -- 1) I'm
> > debating whether to make all the CLI utilities a separate project, and
> > 2) I'm creating a new project that houses English grammer and language
> > related libs, like inflect.rb. I guess this project will just be
> > called "English". There are a lot of advantages in having a separate
> > project for this kinds of thing which ultimately could lead to a very
> > strong library of natural language processing.
> > If Nitro is still
> > insisting on pluralizing table names (something I always thought was a
> > waste of good cpu cycles personally), then that will be additional
> > required dependency.
>
> Og never pluralizes tables (and never did).  What it does use pluralize
> for is for creating nice relation names.

Hmmm... I think it did a long time ago. But maybe I just got it mixed
up with the relationship methods you mention below.

> class Forum
>    has_many User
> end
>
> Forum#users
>
> And no, I don't feel like we're wasting cycles here.  ;)  It's merely the
> Og way, which makes it feel so good.  :)  (Those methods are generated at
> boot time via eval, so no runtime wasting going on here.)

Ah, right. Well, either Og can depend on "English" or it can just copy
the inflect.rb file and distribute it with Og. The later means one
less dependency, the former provides other potential benefits for
Nitro users.

T.


From george.moschovitis at gmail.com  Sat Jul 21 02:33:34 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Sat, 21 Jul 2007 09:33:34 +0300
Subject: [Nitro] Nitro Structure Graphics
In-Reply-To: <1184995153.046491.323800@w3g2000hsg.googlegroups.com>
References: <op.tvofsutaxegpx6@jo.local>
	<1184884076.019854.111500@22g2000hsm.googlegroups.com>
	<op.tvq203oexegpx6@jo.local>
	<1184950746.443825.17280@o61g2000hsh.googlegroups.com>
	<op.tvr2wr2ixegpx6@jo.local>
	<1184995153.046491.323800@w3g2000hsg.googlegroups.com>
Message-ID: <afd80b540707202333k44848fai5df8b9e75f8cc78b@mail.gmail.com>

>
> Ah, right. Well, either Og can depend on "English" or it can just copy
> the inflect.rb file and distribute it with Og. The later means one
> less dependency, the former provides other potential benefits for
> Nitro users.
>


I don't have problems depending on things. The reason I want Glue removed is
due to the overlap
with Facets. I would like to remove Glue to promote Facets ;-) So I would
like to have Og depend
on English.

-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070721/dde36a47/attachment.html 

From rmela at rcn.com  Sat Jul 21 16:50:05 2007
From: rmela at rcn.com (Robert Mela)
Date: Sat, 21 Jul 2007 16:50:05 -0400
Subject: [Nitro] arrgghhhh
Message-ID: <46A2717D.4040803@rcn.com>

I remember the old Lint quizzes ( "What's wrong with this C program?") 
in Dr. Dobbs in the '90s.

So, in that spirit: What's wrong with this code?

    if defined?(Og) and Og.respond_to?(:manager)
      # THINK: don't allways force this.
      require "raw/model/enchant"
      for m in Og.manager.models
        m.send(:include, Enchant)
      end
    end

It's in application.rb from a fresh darcs get I did today.

I think I've reported & patched this one before -- or maybe it was a 
similar bug elsewhere...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rmela.vcf
Type: text/x-vcard
Size: 160 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070721/b6a5241c/attachment.vcf 

From john at oxyliquit.de  Sat Jul 21 18:55:35 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sun, 22 Jul 2007 01:55:35 +0300
Subject: [Nitro] arrgghhhh
In-Reply-To: <46A2717D.4040803@rcn.com>
References: <46A2717D.4040803@rcn.com>
Message-ID: <op.tvt7ax15xegpx6@jo.local>

Hi,

> I think I've reported & patched this one before -- or maybe it was a
> similar bug elsewhere...

please bear with us, the patch/report might have just been 'swallowed'
by everyday life.  Could you do Nitro a favour and just make a new
patch for it?  That'd be really nice.

Jo

-- 
Feel the love
http://pinkjuice.com/pics/ruby.png

From arne at arnebrasseur.net  Sun Jul 22 06:25:20 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Sun, 22 Jul 2007 12:25:20 +0200
Subject: [Nitro] arrgghhhh
In-Reply-To: <46A2717D.4040803@rcn.com>
References: <46A2717D.4040803@rcn.com>
Message-ID: <46A33090.1040202@arnebrasseur.net>

Something like

if defined?(Og) && Og.respond_to?(:manager) && Og.manager

?

(ab)

Robert Mela schreef:
> I remember the old Lint quizzes ( "What's wrong with this C program?") 
> in Dr. Dobbs in the '90s.
>
> So, in that spirit: What's wrong with this code?
>
>    if defined?(Og) and Og.respond_to?(:manager)
>      # THINK: don't allways force this.
>      require "raw/model/enchant"
>      for m in Og.manager.models
>        m.send(:include, Enchant)
>      end
>    end
>
> It's in application.rb from a fresh darcs get I did today.
>
> I think I've reported & patched this one before -- or maybe it was a 
> similar bug elsewhere...
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general


-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From arne at arnebrasseur.net  Mon Jul 23 16:17:08 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Mon, 23 Jul 2007 22:17:08 +0200
Subject: [Nitro] Markup spec
Message-ID: <46A50CC4.7080808@arnebrasseur.net>

I found a minute to merge the markup spec and markup testcase.

One test fails.

     # FIXME : This test is converted from TC, it fails
     #         The call to expand simply strips the html
     #         returning "Hello World!"
     #         Either fix the code or fix the spec

     it "should convert < and > to &lt; and &gt; with #expand" do
       @t.send(:expand, "<p>Hello World!</p>").
	should == "&lt;p&gt;Hello World!&lt;/p&gt;"
     end

I pushed it to http://darcs.arnebrasseur.net/glycerin.

There are 17 tc's left that need to be converted :

   nitro/raw/test/

   22009 tc_controller_params.rb
    2648 tc_dispatcher.rb
    1376 tc_element.rb
    1067 tc_flash.rb
     921 tc_helper.rb
    2991 tc_render.rb
    1814 tc_router.rb
     727 tc_server.rb
    1817 tc_session.rb
    1370 tc_template.rb

   nitro/raw/test/nitro/compiler:

   1349 tc_client_morpher.rb

   nitro/raw/test/nitro/helper:

   6468 tc_feed.rb
   2155 tc_navbar.rb
    623 tc_pager.rb
   3532 tc_table.rb
    624 tc_xhtml.rb

   nitro/raw/test/nitro/util:

   1834 tc_encode_url.rb

I included the filesize just in case (you never know) anybody likes to 
join he/she can get a feel of how much work each file is.

Converting a file is easy if you know a little bit Test::Unit and RSpec. 
Move the file to the spec/ tree, removing the tc_ prefix (use darcs mv).

Begin the file with
require "script/lib/spec"

require "raw/whatever/you're/testing"

TestCase  becomes  describe "..." do
test_something  becomes  it "..." do
assert_...  becomes  should ...

As soon as a spec runs it's ok, better if you can make it pass, but if 
you're not sure how to make it pass simply leave it like that. Jo will 
gladly look at it, and possibly pass it on to G.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net

From john at oxyliquit.de  Tue Jul 24 02:05:41 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Tue, 24 Jul 2007 09:05:41 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <46A50CC4.7080808@arnebrasseur.net>
References: <46A50CC4.7080808@arnebrasseur.net>
Message-ID: <op.tvygjrjlxegpx6@jo.local>

Hi,

> I found a minute to merge the markup spec and markup testcase.

yaaay!  ^_^  There should be more people visiting me on IRC, it
is the best place for me to encourage people to do work for me.  ;)

> One test fails.

Will have a look.

> There are 17 tc's left that need to be converted :

Now, that doesn't sound all too bad (except the params tc *g*).

> I included the filesize just in case (you never know) anybody likes to
> join he/she can get a feel of how much work each file is.

Yes, even if I feel my plea is futile, but please, step up and help Arne
to convert the last tcs.  :P

I'll do a few test runs on Og this weekend, to make a better green/red
ratio there too, now that I finally got George to really take a look
at Aspects (on IRC btw) (by constantly nagging him :P), things can go
forward again.  :)

Btw, G, why is the aspect initialization within Nitro, if it's Og specific?
If it's Og specific (it is protected by a defined?(Og) anyway), why
isn't it in Og?  Can it just go to Og.setup?  It essentially breaks Og
if you don't use Nitro, which is _bad_.

> As soon as a spec runs it's ok, better if you can make it pass, but if
> you're not sure how to make it pass simply leave it like that. Jo will
> gladly look at it, and possibly pass it on to G.

Indeed.  :)

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Tue Jul 24 02:35:27 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 24 Jul 2007 09:35:27 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <op.tvygjrjlxegpx6@jo.local>
References: <46A50CC4.7080808@arnebrasseur.net> <op.tvygjrjlxegpx6@jo.local>
Message-ID: <afd80b540707232335h1b0df78fkab4eb18df6440f62@mail.gmail.com>

>
> yaaay!  ^_^  There should be more people visiting me on IRC, it
> is the best place for me to encourage people to do work for me.  ;)


nice stragegy.

Btw, G, why is the aspect initialization within Nitro, if it's Og specific?
> If it's Og specific (it is protected by a defined?(Og) anyway), why
> isn't it in Og?  Can it just go to Og.setup?  It essentially breaks Og
> if you don't use Nitro, which is _bad_.


Interasting point! Never thought of that. Aspects are used both in Nitro and
Og.I thought I called the init code (if needed) in both
places.  I will recheck.

-g.

-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070724/f2208ce0/attachment.html 

From rob at robmela.com  Tue Jul 24 10:03:14 2007
From: rob at robmela.com (Robert Mela)
Date: Tue, 24 Jul 2007 10:03:14 -0400
Subject: [Nitro] Markup spec
In-Reply-To: <op.tvygjrjlxegpx6@jo.local>
References: <46A50CC4.7080808@arnebrasseur.net> <op.tvygjrjlxegpx6@jo.local>
Message-ID: <46A606A2.5030102@robmela.com>

Jonathan Buch wrote:
>
> Btw, G, why is the aspect initialization within Nitro, if it's Og specific?
> If it's Og specific (it is protected by a defined?(Og) anyway), why
> isn't it in Og?  Can it just go to Og.setup?  It essentially breaks Og
> if you don't use Nitro, which is _bad_.
>
>   
And vice-versa.  The protection wrapper in application.rb is itself an 
ugly workaround to permit Nitro to run w/o Og.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rob.vcf
Type: text/x-vcard
Size: 116 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/nitro-general/attachments/20070724/6f928338/attachment.vcf 

From william.full.moon at gmail.com  Tue Jul 24 10:24:25 2007
From: william.full.moon at gmail.com (* William)
Date: Wed, 25 Jul 2007 00:24:25 +1000
Subject: [Nitro] Markup spec
In-Reply-To: <46A50CC4.7080808@arnebrasseur.net>
References: <46A50CC4.7080808@arnebrasseur.net>
Message-ID: <00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>

Hi gang ...

I have been following the conversations -- Love what I see, I trust I'll get
some time to play later this quarter.

I have a comment on these recurrent "test" errors and "regression" errors
I've seen.  This was sparked by a similar conversation on total quality
management and that other TLA (three letter acronym) that Ruby folk love:

    DRY

    Do-not  Repeat Yourself

Testing seems (to me) to be the first place to Not Repeat.  

I am aware we have a test harness, etc.  One thing that I've always thought
is that the OO paradigm si a fertile ground for "responsible objects" --
Objects that take it upon themselves to sign a "pledge of personal
integrity".

I will avoid an essay -- I'll just make one (stress possible) possible
example for this.

Take the idea below ... (see Example-A, end)

When the class loads, it does the equivalent of a "Bootstrap self-test".  If
your PC and server's BIOS can benefit from this, why not our classes??!

There would be very few regression errors with an effective "self-check"
mechanism.

Give it some thought guys!

Aloha,
       ... Will

==============[ example A ]=========

    Class MyExample
	
	# all done -- establish "integrity"

    private
      def self_test_me( )
         #-- test some class stuff
            :
         #-- test instance stuff
           
           test = new MyExample
              :

      end #self_test_me  _____________

      self_test_me()

    end #_ MyExample __.__.__.__.__.__.__.__.__


-----Original Message-----
From: nitro-general-bounces at rubyforge.org
[mailto:nitro-general-bounces at rubyforge.org] On Behalf Of Arne Brasseur
Sent: Tuesday, 24 July 2007 06:17
To: General discussion about Nitro
Subject: [Nitro] Markup spec
Importance: Low

I found a minute to merge the markup spec and markup testcase.

One test fails.

     # FIXME : This test is converted from TC, it fails
     #         The call to expand simply strips the html
     #         returning "Hello World!"
     #         Either fix the code or fix the spec


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.16/914 - Release Date: 23-Jul-2007
19:45
 


From george.moschovitis at gmail.com  Tue Jul 24 10:56:09 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Tue, 24 Jul 2007 17:56:09 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <46A606A2.5030102@robmela.com>
References: <46A50CC4.7080808@arnebrasseur.net> <op.tvygjrjlxegpx6@jo.local>
	<46A606A2.5030102@robmela.com>
Message-ID: <afd80b540707240756m434f067fl5e96e8b553e39799@mail.gmail.com>

Btw,

the facets aspects implementation does not require the initialization step.
But it is not fully compatible with Nitro yet. I hope, when Tom finalizes
his design for facets 2.0 we can work together on this important issue.

-g.


On 7/24/07, Robert Mela <rob at robmela.com> wrote:
>
> Jonathan Buch wrote:
> >
> > Btw, G, why is the aspect initialization within Nitro, if it's Og
> specific?
> > If it's Og specific (it is protected by a defined?(Og) anyway), why
> > isn't it in Og?  Can it just go to Og.setup?  It essentially breaks Og
> > if you don't use Nitro, which is _bad_.
> >
> >
> And vice-versa.  The protection wrapper in application.rb is itself an
> ugly workaround to permit Nitro to run w/o Og.
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>
>


-- 
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070724/e523b178/attachment.html 

From transfire at gmail.com  Tue Jul 24 18:46:37 2007
From: transfire at gmail.com (Trans)
Date: Tue, 24 Jul 2007 22:46:37 -0000
Subject: [Nitro] Facets 2 website
Message-ID: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>

Facets 2 is getting closer and closer. I just put up a preliminary
(read beta) website for the new version. Appreciate any corrections,
improvements and/or suggestions (especially better blurbs).

  http://facets.rubyforge.org

Cheers,
T.


P.S. I know that the Wiki isn't working.


From arne at arnebrasseur.net  Wed Jul 25 03:50:19 2007
From: arne at arnebrasseur.net (arne at arnebrasseur.net)
Date: Wed, 25 Jul 2007 00:50:19 -0700 (PDT)
Subject: [Nitro] Facets 2 website
In-Reply-To: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
References: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
Message-ID: <1581.81.246.162.120.1185349819.squirrel@webmail.arnebrasseur.net>

Very nice!

Typo:
MORE is the equivalent if Ruby's Standard library
if -> of

(ab)

> Facets 2 is getting closer and closer. I just put up a preliminary
> (read beta) website for the new version. Appreciate any corrections,
> improvements and/or suggestions (especially better blurbs).
>
>   http://facets.rubyforge.org
>
> Cheers,
> T.
>
>
> P.S. I know that the Wiki isn't working.
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



From john at oxyliquit.de  Wed Jul 25 04:19:07 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 25 Jul 2007 11:19:07 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>
References: <46A50CC4.7080808@arnebrasseur.net>
	<00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>
Message-ID: <op.tv0fvripxegpx6@jo.local>

Hi,

> I have been following the conversations -- Love what I see, I trust I'll  
> get some time to play later this quarter.

that's great.  :)

> I have a comment on these recurrent "test" errors and "regression" errors
> I've seen.  This was sparked by a similar conversation on total quality
> management and that other TLA (three letter acronym) that Ruby folk love:
>
>     DRY

I really like your idea, but there is a _big_ hinderance for me there.  :)
Time.  Even the current startup is sub-optimal, with tests there'd have
to be a 'do test' switch which enables testing for those who do want to
run those.
Nitro/Og tests take around 15 minutes for me to run, I'd be crazy to
enable this.

IMO there isn't so much duplication going on in the tests as simply 'usage'
of facilities (at least in Og).  I don't have a recipe on how to make that
best, if I had a supercomputer at home I'd probably have that enabled
all the time and all would be well, but as I don't... :P

So, if people (I include myself here) would always test when they were
fiddling with something and before recording a patch, all would be in a
much better state.  This needs concentration of course.  :P
This goes of course most to George as he's simply the most productive
patcher, and I've just been patching Og tests/specs for years now.  :P

I'm not sure if integrated tests are so much better, that'd mean having
even bigger files, which is already a slight problem, and tests sometimes
can't be mapped to a single file (as with Og sql.rb).

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Wed Jul 25 04:19:07 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 25 Jul 2007 11:19:07 +0300
Subject: [Nitro] Facets 2 website
In-Reply-To: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
References: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
Message-ID: <op.tv0flzzlxegpx6@jo.local>

Hi,

> Facets 2 is getting closer and closer. I just put up a preliminary
> (read beta) website for the new version. Appreciate any corrections,
> improvements and/or suggestions (especially better blurbs).

only a few minor things:

* MORE is the equivalent _if_ Ruby's Standard library.
* In particluar, the web-related _lbs_
* Blow, the Units _systesm_
* few libs removed simply _becuase_ they _were't_

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Wed Jul 25 04:19:06 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 25 Jul 2007 11:19:06 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <afd80b540707232335h1b0df78fkab4eb18df6440f62@mail.gmail.com>
References: <46A50CC4.7080808@arnebrasseur.net> <op.tvygjrjlxegpx6@jo.local>
	<afd80b540707232335h1b0df78fkab4eb18df6440f62@mail.gmail.com>
Message-ID: <op.tvyx03f1xegpx6@jo.local>

Hi,

> Interasting point! Never thought of that. Aspects are used both in Nitro  
> and Og.  I thought I called the init code (if needed) in both places.
> I will recheck.

oh, that might be.... I'm not enitrely sure that it doesn't.  :)  I've
just seen it in Nitro though.

Thanks for checking though!

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From arne at arnebrasseur.net  Wed Jul 25 05:03:16 2007
From: arne at arnebrasseur.net (arne at arnebrasseur.net)
Date: Wed, 25 Jul 2007 02:03:16 -0700 (PDT)
Subject: [Nitro] Markup spec
In-Reply-To: <op.tv0fvripxegpx6@jo.local>
References: <46A50CC4.7080808@arnebrasseur.net>
	<00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>
	<op.tv0fvripxegpx6@jo.local>
Message-ID: <1680.81.246.162.120.1185354196.squirrel@webmail.arnebrasseur.net>

> So, if people (I include myself here) would always test when they were
> fiddling with something and before recording a patch, all would be in a
> much better state.  This needs concentration of course.  :P
> This goes of course most to George as he's simply the most productive
> patcher, and I've just been patching Og tests/specs for years now.  :P

I mentioned this before on IRC, but I'll say it again for the world to
hear. Once all the tests run I would really like it if patches would get
rejected automatically if they make the tests fail. They call it
continuous integration IIRC, and I'd be surprised if darcs didn't have a
hook for that.

One could also set up a seperate machine that runs the tests after each
new patch, and unpulls if it makes the tests fail.

Is it conceivable this would ever happen to the Nitro repo?

(ab)


From john at oxyliquit.de  Wed Jul 25 06:15:31 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Wed, 25 Jul 2007 13:15:31 +0300
Subject: [Nitro] Markup spec
In-Reply-To: <1680.81.246.162.120.1185354196.squirrel@webmail.arnebrasseur.net>
References: <46A50CC4.7080808@arnebrasseur.net>
	<00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>
	<op.tv0fvripxegpx6@jo.local>
	<1680.81.246.162.120.1185354196.squirrel@webmail.arnebrasseur.net>
Message-ID: <op.tv0mr5dgxegpx6@jo.local>

Hi,

> I mentioned this before on IRC, but I'll say it again for the world to
> hear. Once all the tests run I would really like it if patches would get
> rejected automatically if they make the tests fail. They call it
> continuous integration IIRC, and I'd be surprised if darcs didn't have a
> hook for that.
>
> One could also set up a seperate machine that runs the tests after each
> new patch, and unpulls if it makes the tests fail.
>
> Is it conceivable this would ever happen to the Nitro repo?

yes, darcs has support for test hooks.  This will only allow `darcs record`
if all the tests succeed.

It's rather easy to do:

$ cat _darcs/prefs/prefs
test rake test

That ensures for yourself that you're not sending faulty patches.
Continuous testing has to be done elsewhere.  (cron job on Gs computer?)

Soo.. that said, for me testing whole Nitro/Og takes around 15 minutes,
which is why I'd avoid doing that, it makes me cringe, walk away, hit
my head against a wall and is generally so unpleasent that I rather
make no patches at all.  Despite that, I do think that it is a good
idea to not make/allow faulty patches...

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From william.full.moon at gmail.com  Wed Jul 25 06:45:27 2007
From: william.full.moon at gmail.com (* William)
Date: Wed, 25 Jul 2007 20:45:27 +1000
Subject: [Nitro] self-test
In-Reply-To: <op.tv0fvripxegpx6@jo.local>
References: <46A50CC4.7080808@arnebrasseur.net>
	<00eb01c7cdfe$59ac9ba0$0401a8c0@ghostgum>
	<op.tv0fvripxegpx6@jo.local>
Message-ID: <000601c7cea8$ed740620$0401a8c0@ghostgum>

Good morning/ Good evening/ Good night.

Comments in-line.

-----Original Message-----
From: Jonathan Buch [mailto:john at oxyliquit.de] 
Sent: Wednesday, 25 July 2007 18:19


w>  I have a comment on these recurrent "test" errors and "regression" 
w>  ...
w>      DRY

j>  I really like your idea, but there is a _big_ hinderance for me 
j>  there.  :) Time.  Even the current startup is sub-optimal, 
j>  with tests there'd have to be a 'do test' switch which enables 
j>  testing for those who do want to run those.

Yes -- I appreciate this.  

The suggestion is more of a "challenge" to find an solution that is:

  -- Optimal
  -- Effective, and
  -- Efficient

On real operating systems (and probably Windows now) one might fork() a
self-test routine in parallel.  That would not impact the mainline
execution. ;-)

I am I saying that's a solution?  Not really.  I want to illustrate that
there 
Are ways to make it happen, by being ambitions.

j>  Nitro/Og tests take around 15 minutes for me to run, 
j>  I'd be crazy to enable this.

Yes, that too.  Why not consider some old-fashioned technology.  

When teletypes were unreliable, we needed to check the data.  

Here's an option.

j>  IMO there isn't so much duplication going on in the 
j>  tests as simply 'usage' of facilities (at least in Og).  

While that may or may not be the case -- Industry ready code finds
regression error all the time until someone takes action to stop it.

A simple idea is to "check" the code when it is patched.

I see an example from darcs in another post.

I was also wondering if a "check-sum" might be used to identify changed
classes, etc.  

So far a simple expression of the notion has defeated me.  ;)

As I say a challenge for the masses ::: Set forth (oops Ruby) and multiply.

/... Will.

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.16/914 - Release Date: 23-Jul-2007
19:45
 


From transfire at gmail.com  Wed Jul 25 07:12:31 2007
From: transfire at gmail.com (Trans)
Date: Wed, 25 Jul 2007 11:12:31 -0000
Subject: [Nitro] Facets 2 website
In-Reply-To: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
References: <1185317197.011851.141460@q75g2000hsh.googlegroups.com>
Message-ID: <1185361951.130222.247100@o61g2000hsh.googlegroups.com>

Thanks guys. I'll run a spell check on the site(s) today and get rid
of most of those typos.

I want to direct you to the Learn page, and click on the Quick API.
(If you click on the "MINI" star you'll get a "dialog" windowed
version.) This is a great little Facets reference, which works really
well if you add the link to your toolbar and change the link's
parameters to open up in a sidebar.

T.


From arne at arnebrasseur.net  Thu Jul 26 15:52:27 2007
From: arne at arnebrasseur.net (Arne Brasseur)
Date: Thu, 26 Jul 2007 21:52:27 +0200
Subject: [Nitro] Repo sync
Message-ID: <46A8FB7B.8080604@arnebrasseur.net>

Hi George,

I see you recently fixed the "infinite loop in error handler" problem. I 
had a patch in my repo that fixed this the 9th of July. I unpulled mine 
so they don't clash.

Could you please sync with my repo? I still have some four new patches 
there. If any of the patches seem unappropriate for the main repo please 
inform me, I'd be happy to unpull them.

Also regarding the error handling code, there could still be a (albeit 
rare) problem. Suppose the template for error 503 raises error 505 and 
vice versa (for example), then you still have an infinite loop. That's 
why my code checked if the current status code was in the range 400-599.

(ab)

-- 
Arne Brasseur
http://www.arnebrasseur.net
arne at arnebrasseur.net


From george.moschovitis at gmail.com  Fri Jul 27 03:52:42 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Fri, 27 Jul 2007 10:52:42 +0300
Subject: [Nitro] Repo sync
In-Reply-To: <46A8FB7B.8080604@arnebrasseur.net>
References: <46A8FB7B.8080604@arnebrasseur.net>
Message-ID: <afd80b540707270052g6b9b299bub0fd6324816ace19@mail.gmail.com>

please remind me your repo url again and I will do it.

thanks,
-g.

On 7/26/07, Arne Brasseur <arne at arnebrasseur.net> wrote:
>
> Hi George,
>
> I see you recently fixed the "infinite loop in error handler" problem. I
> had a patch in my repo that fixed this the 9th of July. I unpulled mine
> so they don't clash.
>
> Could you please sync with my repo? I still have some four new patches
> there. If any of the patches seem unappropriate for the main repo please
> inform me, I'd be happy to unpull them.
>
> Also regarding the error handling code, there could still be a (albeit
> rare) problem. Suppose the template for error 503 raises error 505 and
> vice versa (for example), then you still have an infinite loop. That's
> why my code checked if the current status code was in the range 400-599.
>
> (ab)
>
> --
> Arne Brasseur
> http://www.arnebrasseur.net
> arne at arnebrasseur.net
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://www.me.gr
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070727/dcdbf73d/attachment.html 

From arne at arnebrasseur.net  Fri Jul 27 03:58:11 2007
From: arne at arnebrasseur.net (arne at arnebrasseur.net)
Date: Fri, 27 Jul 2007 00:58:11 -0700 (PDT)
Subject: [Nitro] Repo sync
In-Reply-To: <afd80b540707270052g6b9b299bub0fd6324816ace19@mail.gmail.com>
References: <46A8FB7B.8080604@arnebrasseur.net>
	<afd80b540707270052g6b9b299bub0fd6324816ace19@mail.gmail.com>
Message-ID: <1211.81.245.162.39.1185523091.squirrel@webmail.arnebrasseur.net>

> please remind me your repo url again and I will do it.
>
> thanks,
> -g.

http://darcs.arnebrasseur.net/glycerin

Thank you!
(ab)



From john at oxyliquit.de  Fri Jul 27 07:10:21 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 27 Jul 2007 14:10:21 +0300
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
Message-ID: <op.tv4emormxegpx6@jo.local>

Hi,

thanks to Manveru I came across this:

http://rubypub.com/gem/nitro-0.41.0/

who feels fit 'n fresh enough to make a) documentation for Nitro and
b) pipe that back to the original in-code documentation.  ;)

No seriously, nice idea, but... what use is that when all changes
get lost on version-incrememts.  :P

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From george.moschovitis at gmail.com  Fri Jul 27 08:18:20 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Fri, 27 Jul 2007 15:18:20 +0300
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
In-Reply-To: <op.tv4emormxegpx6@jo.local>
References: <op.tv4emormxegpx6@jo.local>
Message-ID: <afd80b540707270518y2be46962x581df18501e12e2f@mail.gmail.com>

Nice!

-g.

-- 
http://www.me.gr
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070727/1470ab81/attachment.html 

From transfire at gmail.com  Fri Jul 27 08:54:06 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 12:54:06 -0000
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
In-Reply-To: <op.tv4emormxegpx6@jo.local>
References: <op.tv4emormxegpx6@jo.local>
Message-ID: <1185540846.169950.27370@d55g2000hsg.googlegroups.com>



On Jul 27, 4:10 am, "Jonathan Buch" <j... at oxyliquit.de> wrote:
> Hi,
>
> thanks to Manveru I came across this:
>
> http://rubypub.com/gem/nitro-0.41.0/
>
> who feels fit 'n fresh enough to make a) documentation for Nitro and
> b) pipe that back to the original in-code documentation.  ;)
>
> No seriously, nice idea, but... what use is that when all changes
> get lost on version-incrememts.  :P

That's a bout the third one of these thing I've seen in the last few
months. There's also,

  http://gemtacular.com/
  http://www.gemjack.com/

Though this is the first that seems to offer wiki-style doc editing.

The problem with the docs on these things is they make assumptions
about how documenting is done. Facets for instance is documented in
smaller pieces, not all in one -- which just makes a mess.

And you're right. What's the point of editing a wiki that will be
outdated tomorrow? Unless there some idea that docs should be kept in
separate directory like tests (and I read about a recent tool for
making this easier to do). But that seems crazy, I already keep
function tests in comments with the source. I know that's doesn't fly
for integration tests, but I really can imagine having to open another
file to document my code.... or am I missing something?

T.


From transfire at gmail.com  Fri Jul 27 10:24:30 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 14:24:30 -0000
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
In-Reply-To: <1185540846.169950.27370@d55g2000hsg.googlegroups.com>
References: <op.tv4emormxegpx6@jo.local>
	<1185540846.169950.27370@d55g2000hsg.googlegroups.com>
Message-ID: <1185546270.508087.53860@57g2000hsv.googlegroups.com>



On Jul 27, 5:54 am, Trans <transf... at gmail.com> wrote:

> for integration tests, but I really can imagine having to open another
> file to document my code.... or am I missing something?

s/cnt/can't/

T.


From transfire at gmail.com  Fri Jul 27 10:27:41 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 14:27:41 -0000
Subject: [Nitro] A better #is ?
Message-ID: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>

Maybe I hit one something... a slight variation on #is.

  class Module

    # Default append function is #include.
    def is(*modules)
      module.each do { |m|
        if m.respond_to?(:append_feature_function)
          send(m.append_feature_function,m)
        else
          include m
        end
      end
    end

  end

Example:

  module Foo
    def self.append_feature_function
      :extend
    end

    def x; "x"; end
  end

  class Bar
    is Foo
  end

  Bar.x  #=> "x"

Thoughts?

T.


From george.moschovitis at gmail.com  Fri Jul 27 10:32:54 2007
From: george.moschovitis at gmail.com (George Moschovitis)
Date: Fri, 27 Jul 2007 17:32:54 +0300
Subject: [Nitro] A better #is ?
In-Reply-To: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
Message-ID: <afd80b540707270732h4bc0650dh2a87cb54db98ca30@mail.gmail.com>

It looks cool, and I can't see any problems...

-g.

On 7/27/07, Trans <transfire at gmail.com> wrote:
>
> Maybe I hit one something... a slight variation on #is.
>
>   class Module
>
>     # Default append function is #include.
>     def is(*modules)
>       module.each do { |m|
>         if m.respond_to?(:append_feature_function)
>           send(m.append_feature_function,m)
>         else
>           include m
>         end
>       end
>     end
>
>   end
>
> Example:
>
>   module Foo
>     def self.append_feature_function
>       :extend
>     end
>
>     def x; "x"; end
>   end
>
>   class Bar
>     is Foo
>   end
>
>   Bar.x  #=> "x"
>
> Thoughts?
>
> T.
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://www.me.gr
http://phidz.com
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070727/9a13e461/attachment.html 

From john at oxyliquit.de  Fri Jul 27 10:35:12 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 27 Jul 2007 17:35:12 +0300
Subject: [Nitro] A better #is ?
In-Reply-To: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
Message-ID: <op.tv4n4yswxegpx6@jo.local>

Hi,

>   Bar.x  #=> "x"

Strikes me as redundand with class_extension, too much power for `is`?

I mean, you already have extend and include, having a hybrid by
inventing a lengthy `def self.append_feature_function` somehow isn't
so appealing to me.

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From transfire at gmail.com  Fri Jul 27 10:54:23 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 14:54:23 -0000
Subject: [Nitro] A better #is ?
In-Reply-To: <op.tv4n4yswxegpx6@jo.local>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
	<op.tv4n4yswxegpx6@jo.local>
Message-ID: <1185548063.557301.264320@w3g2000hsg.googlegroups.com>



On Jul 27, 7:35 am, "Jonathan Buch" <j... at oxyliquit.de> wrote:
> Hi,
>
> >   Bar.x  #=> "x"
>
> Strikes me as redundand with class_extension, too much power for `is`?

Not redundant, but #is could be made smart enough to recognize a
module that has a ClassMethods section and thus work as a suitable
alternative to class_extension. I kind of like that idea myself,
though I've always thought "ClassMethods" was a poor name choice.

I guess the debate is between the side that says, all modules should
be essentially equal and the method (include or extend) determines
it's use, vs. the side that says, the module should be a pure
encapsulation of functionality and thus dictate the terms of its own
use.

The things about implementing #is this way, it allows both options.
Use #include/#extend for the first, #is for the second.

> I mean, you already have extend and include, having a hybrid by
> inventing a lengthy `def self.append_feature_function` somehow isn't
> so appealing to me.

That's true. And actually one could use the callback:

  module Foo
    def append_feature(mod)
      mod.extend self
    end

    def x; "x"; end
  end

  class Bar
    is Foo
  end

  Bar.x  #=> "x"

However, that sort of misleads the programmer. #include is not
actually happening at all. In fact, one could never make that module
include even if they wanted too, without undefing append_feature.
Which is why I thought #is a good compromise. But perhaps there's a
bit more elegant solution using another callback?

T.


From transfire at gmail.com  Fri Jul 27 10:55:58 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 14:55:58 -0000
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
In-Reply-To: <1185546270.508087.53860@57g2000hsv.googlegroups.com>
References: <op.tv4emormxegpx6@jo.local>
	<1185540846.169950.27370@d55g2000hsg.googlegroups.com>
	<1185546270.508087.53860@57g2000hsv.googlegroups.com>
Message-ID: <1185548158.985393.268030@w3g2000hsg.googlegroups.com>



On Jul 27, 7:24 am, Trans <transf... at gmail.com> wrote:
> On Jul 27, 5:54 am, Trans <transf... at gmail.com> wrote:
>
> > for integration tests, but I really can imagine having to open another
> > file to document my code.... or am I missing something?
>
> s/cnt/can't/

OMG!

s/\/cnt\/can't\//\/can\/can't\//

;-)

T.


From john at oxyliquit.de  Fri Jul 27 10:59:30 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 27 Jul 2007 17:59:30 +0300
Subject: [Nitro] Nitro (or,
	any gem installables for that matter) documentation:
In-Reply-To: <1185548158.985393.268030@w3g2000hsg.googlegroups.com>
References: <op.tv4emormxegpx6@jo.local>
	<1185540846.169950.27370@d55g2000hsg.googlegroups.com>
	<1185546270.508087.53860@57g2000hsv.googlegroups.com>
	<1185548158.985393.268030@w3g2000hsg.googlegroups.com>
Message-ID: <op.tv4o9g0uxegpx6@jo.local>

Hi,

>> s/cnt/can't/
>
> OMG!
>
> s/\/cnt\/can't\//\/can\/can't\//

one of those days, huh?  ;D

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From john at oxyliquit.de  Fri Jul 27 12:55:46 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Fri, 27 Jul 2007 19:55:46 +0300
Subject: [Nitro] A better #is ?
In-Reply-To: <1185548063.557301.264320@w3g2000hsg.googlegroups.com>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
	<op.tv4n4yswxegpx6@jo.local>
	<1185548063.557301.264320@w3g2000hsg.googlegroups.com>
Message-ID: <op.tv4um8ryxegpx6@jo.local>

Hi,

> However, that sort of misleads the programmer. #include is not
> actually happening at all.

well, same here,

class MyClass
   is MyModule
end

I have absolutely no idea what is going on here, without first reading
the code (or documentation for that matter), if it does include, or
extend or does something completely different.

Now, that isn't necessarily a bad thing, all the end user will only ever
do `is FooBlah` and will happily use the facilities it provides.
What I'm not sure is if we need that kind of power in the backend,
do you have any 'bigger usecase' in mind?

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From transfire at gmail.com  Fri Jul 27 13:18:25 2007
From: transfire at gmail.com (Trans)
Date: Fri, 27 Jul 2007 17:18:25 -0000
Subject: [Nitro] A better #is ?
In-Reply-To: <op.tv4um8ryxegpx6@jo.local>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
	<op.tv4n4yswxegpx6@jo.local>
	<1185548063.557301.264320@w3g2000hsg.googlegroups.com>
	<op.tv4um8ryxegpx6@jo.local>
Message-ID: <1185556705.927956.124070@57g2000hsv.googlegroups.com>



On Jul 27, 9:55 am, "Jonathan Buch" <j... at oxyliquit.de> wrote:
> Hi,
>
> > However, that sort of misleads the programmer. #include is not
> > actually happening at all.
>
> well, same here,
>
> class MyClass
>    is MyModule
> end
>
> I have absolutely no idea what is going on here, without first reading
> the code (or documentation for that matter), if it does include, or
> extend or does something completely different.
>
> Now, that isn't necessarily a bad thing, all the end user will only ever
> do `is FooBlah` and will happily use the facilities it provides.
> What I'm not sure is if we need that kind of power in the backend,
> do you have any 'bigger usecase' in mind?

Well, the bigger picture that I see is due to the annoyance of the
smaller ones. I really hate having to know if a given module is
intended to be included or extended in order to give me the desired
functionality. I have to look it up! Take Forwardable for example. Do
you know how to use it? So to me, #is is actually better. I don't care
how is does what it does, just that it does it. If I need to care how,
then I can resort to include and extend. So that's the first thing.

Then there is ClassMethods/class_extension. I'm still not happy with
these, and I continue to seek a remedy. As of late I've decided that
the best course (short of a core-change) is a 3rd method beside
include and extend that would notice a ClassMethods section and act
accordingly. But that's actually beside the point. If we decide #is
should have this more versatile use, then it's easy enough to add this
third possibly to the mix.

I guess ultimately I'm asking to what extent do we prefer the
simplicity if is => include, vs the convenience a smart #is can bring
to the table.

T.


From john at oxyliquit.de  Sat Jul 28 15:20:53 2007
From: john at oxyliquit.de (Jonathan Buch)
Date: Sat, 28 Jul 2007 22:20:53 +0300
Subject: [Nitro] A better #is ?
In-Reply-To: <1185556705.927956.124070@57g2000hsv.googlegroups.com>
References: <1185546461.264957.264600@r34g2000hsd.googlegroups.com>
	<op.tv4n4yswxegpx6@jo.local>
	<1185548063.557301.264320@w3g2000hsg.googlegroups.com>
	<op.tv4um8ryxegpx6@jo.local>
	<1185556705.927956.124070@57g2000hsv.googlegroups.com>
Message-ID: <op.tv6v032cxegpx6@jo.local>

Hi,

> Well, the bigger picture that I see is due to the annoyance of the
> smaller ones. I really hate having to know if a given module is
> intended to be included or extended in order to give me the desired
> functionality.

late answer.   Had to think a while about this and I think you're right.
What one mostly cares about is 'getting functionality', not the way how
to get it.

Btw, I like class_methods, it's easy to use and does exactly what I
expect it to do without much thinking from my side necessary.  :P
So once again, thanks for showing us more 'facets of ruby'.  ^_^

Jo

-- 
Feel the love
http://pinkjuice.com/pics/ruby.png

From transfire at gmail.com  Tue Jul 31 16:39:10 2007
From: transfire at gmail.com (Trans)
Date: Tue, 31 Jul 2007 20:39:10 -0000
Subject: [Nitro] Facets SVN
Message-ID: <1185914350.423367.174310@o61g2000hsh.googlegroups.com>

Hi--

I just imported Facets into the Rubyforge subversion repository. You
should be able to get an anonymous checkout of the latest with:

  svn checkout svn://rubyforge.org/var/svn/facets/trunk facets/

Facets 2.0 is coming along nicely --still some things I'd like to get
cleaned up, but a release (beta?) is Real Soon Now(tm).

Btw, if you are interested in becoming a honest to goodness ruby spit-
shining Facets developer, let me know.

T.