Hi again.
I have added the fixes. I am not sure that they are all correct, as I
am quite a newbie.. They do however make it work :)
Feel free to remove what is not needed.
Hope it will help somebody someday - like it helped me..
Elad
-----UrsprÃngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 5. April 2005 13:26
An: [email protected]
Betreff: Re: AW: AW: Design note - Building a template mechanism
On Tue, 5 Apr 2005, Elad Messing wrote:
> I understand.
> So - I would very much like to learn the new implementation ! A demo site
> could be great !
>
> In Parallel - I am going through the example in the wiki and finding some
> errors in code. What do you think about me adding the fixes to make the
> example work by copy paste ? Is it needed ?
>
> Elad
>
your comments/fixes are welcome
:-)
> -----UrsprÎÎngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 5. April 2005 12:22
> An: [email protected]
> Betreff: Re: AW: Design note - Building a template mechanism
>
> On Tue, 5 Apr 2005, Elad Messing wrote:
>
> > Hello Stavros and all
> > Thanks for the reply. I think I understand the usage of it as you
> > explained in the "TemplateBasedWebSite" wiki page.
> > I also found the Othello example in the Scratchpad.
> >
> > Currently I am studying the wiki example, trying to build the same
> > in my environment.
> >
> > Do you think the wiki example is still valid today, or you would
> > have done this in a different way in Cocoon 2.1.7 ? This is actually
> > my question :)
> >
> > Thanks
> >
> > Elad
> >
>
> the idea described in wiki is the same, the impementation has changed
>
> (more features, cleaner code etc)
>
>
>
> >
> >
> > -----UrsprÎÂngliche Nachricht-----
> > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Gesendet: Dienstag, 5. April 2005 11:38
> > An: [email protected]
> > Betreff: Re: Design note - Building a template mechanism
> >
> >
> > hi elad
> >
> > i'm using this approach to create static web static web sites the goals are:
> > - yu have one layout file (.xhtml). then i get the content form
> > each request (requested web page) and put it inside this layout (now
> > i'm close to have pages (web requests) that make an exception and
> > use an alternative
> > layout)
> >
> > - you can define blocks with static content (html fragments) that
> > can be reused in any page
> >
> > - you can define your own elements that are translated to complex
> > html
> >
> > - there is a simple html 2 pdf transformation, so you are able to
> > server content pages as simple pdfs
> >
> > - you can change the theme for your site
> >
> > all this out of the box without to touch the sitemap.xmap
> >
> > there is a sample in cocoon sample /scratchpad called Othello than
> > demostrate all this but it's quite old
> >
> > i have a new version with many modification but i dont have found
> > time to make a pacth in bugzilla
> >
> > if you want i can pack my working directory with some demo site to
> > take a look
> >
> >
> > regards
> > -stavros
> > On Tue, 5 Apr 2005, Elad Messing wrote:
> >
> > > Hello All !
> > > I am now in the design phase of the web-application I am working on.
> > > The application will have a fixed structure - header, footer,
> > > content in the middle, and menu on the side - and I am looking for
> > > the
> > best
> > > practice to build this template mechanism in Cocoon.
> > >
> > > I have found in the wiki this page
> > > :http://wiki.apache.org/cocoon/TemplateBasedWebSite but - It is
> > > from
> > 10.2003
> > > - and mention working with version 2.0.4.
> > > I was wondering whether this is still a best practice or maybe a
> > > new better feature allows for another practice - which is better.
> > > (might be
> > that
> > > the Xinclude is involved ? Not sure)..
> > >
> > > Thanks in advance.
> > >
> > > Elad Messing
> > >
> > >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
