cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: [RT] Cocoon Blocks
Date Sat, 29 Jun 2002 10:43:53 GMT
Tony Collen wrote:
> Stefano Mazzocchi wrote:
> <snip/>
> >Fire your comments and try to tear it appart: I'm pretty confident this
> >is really a big thing for Cocoon!
> >
> Pardon my ignorance, but what is the origin of the term "block"?  From
> what I read, its just a module, or a plugin... how about calling it a
> plugin or a module? :)  Seriously though, there was a mention of "new
> terminology" over on the big thread on Cocoon-Users, so perhaps calling
> block plugins or modules would be a little more descriptive?  Just some
> thoughts.  I look forward to wrapping my head around whatever they're
> called :)

Good point.

Blocks come from the microelectronic world where 'chuncks of logic' are
called blocks, just like there are blocks in the city and so on.

The alternative was to use 'brick' as in good old Lego sense.

I don't like plugin, because a plugin is something that you plug-in to
increase the functionality of a basic application. Example: Photoshop is
functional even without plugins, a naked Cocoon wouldn't do anything
without blocks.

Component is already taken from the avalon world and it's too
software-oriented (look at COM, DCOM, CORBA, COP and friends)

Module is admittedly a good suggestion.

Anyway, "block", like anything else in the RT is to be considered a
suggestion and I'm not married with anything there. So if there is
agreement we can change even the name.

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche

To unsubscribe, e-mail:
For additional commands, email:

View raw message