You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Kevin Menard <ni...@negativetwenty.net> on 2005/02/04 14:00:18 UTC
CMS Components [Was: Tapesty and CMS]
Hello Frederic,
Friday, February 4, 2005, 6:04:16 AM, you wrote:
> I'm looking for returns on experience on Content Management Systems
> using Tapesty.
Sorry for not directly answering you, but this question has finally
prompted to send mine out :-)
Would there be any value in having a common CMS API? It seems a fair
number of people here are working on CMSs and a lot of work gets
duplicated. I haven't had a ton of experience with CMSs, but the ones
I have all have this notion of a "block", which is a div or something
that renders for a particular piece of functionality. To me, this
screams out component.
I haven't been able to really think it all the way through yet. As
in, does it make sense to use (create) a higher level API or to just
use plain, old Tapestry components. In either case, it would be
pretty neat if CMS components could be developed and reused by others
in their own projects.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: New Tapestry Palette version available.
Posted by Jamie Orchard-Hays <ja...@dang.com>.
cool stuff like this might get me off of Intellij! :-D
----- Original Message -----
From: "Michael Henderson" <mh...@mac.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Tuesday, February 08, 2005 6:08 PM
Subject: New Tapestry Palette version available.
> Hi,
>
> A new version of the palette plugin is available, This version adds
> support for drag and drop creation of implicit component declarations and
> manual assignment of component ids during drag and drop.
>
> The custom property sheet also supports editing of implicit component
> bindings.
>
> The palette blog has more details:
>
> http://tapestrypalette.mjhenderson.com/C868201159/E411094788/index.html
>
> The code for manual assignment of component ids was provided by Alexey
> Romanchuk.
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
New Tapestry Palette version available.
Posted by Michael Henderson <mh...@mac.com>.
Hi,
A new version of the palette plugin is available, This version adds support for drag and drop creation of implicit component declarations and manual assignment of component ids during drag and drop.
The custom property sheet also supports editing of implicit component bindings.
The palette blog has more details:
http://tapestrypalette.mjhenderson.com/C868201159/E411094788/index.html
The code for manual assignment of component ids was provided by Alexey Romanchuk.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org