Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4253AA94.9080605@nada.kth.se>
Date: Wed, 06 Apr 2005 11:23:32 +0200
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] composition vs. inheritance in blocks
References: <42444CFF.4020807@yahoo.de> <42446062.8000404@nada.kth.se>
 <424529B7.2020409@yahoo.de> <4245512C.3000107@nada.kth.se>
 <4248F241.2050503@apache.org> <4249437A.80600@nada.kth.se>
 <424980CB.4030708@apache.org> <42499D1D.6000104@nada.kth.se>
 <4249ED2C.8060408@apache.org> <424A84B7.1000008@nada.kth.se>
 <424AD336.5090804@apache.org> <424B2C2A.7080305@nada.kth.se>
 <424BED74.5050701@apache.org> <424C1F61.3070006@nada.kth.se>
 <424CE96A.8010904@apache.org> <424D56B7.9030901@nada.kth.se>
 <424EB2EB.7070504@apache.org> <424FE7E2.2030407@nada.kth.se>
 <42539994.1050904@apache.org>
In-Reply-To: <42539994.1050904@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:

> Daniel Fagerstrom wrote:
>
>> I have given some examples of how a user could use some adapted form 
>> of MI to build applications based on a number of blocks, so I'm 
>> interested in your view about how to build blocks based applications.
>
>
> I can't add much to what Stefano already has said:
>
> "You install "Linotype2", is a real block and it requires "Linotype 
> Skin", "JCR Repository", "RDF TripleStore". The block manager goes to 
> the block library on cocoon.apache.org and finds a list of possible 
> blocks that implement those interfaces and that are known to be 
> compatible with the version of the block you are now installing."
>
>
> Except that not the BlocksManager but the BlockDeployer will install 
> blocks, that's the vision:
>
>  - reusability
>    --> skin can be used by more than one block)
>    --> develop functionality *once* and reuse it in many applications
>  - versioning
>  - development will become much easier because you can wire locally
>    available development blocks
>    e.g. I want to use the latest cForms block in *my* project I simply
>    point in the wiring.xml of *my* project to this block. There are
>    no difficult deployment cycles!
>
>
> And quoting Stefano a second time: "what is the best way to use those 
> features in order to achieve what I need". I don't know what will be 
> the best way to use all those features. When we have a working 
> prototype we will learn a lot and best practices will evolve.
>
Ok, so lets get to a working prototype. Still if we don't spend some 
thought on relevant use cases that comes up, the working prototype might 
be less relevant than it could be.

/Daniel