I would love to use something like this. 


On Feb 17, 2012, at 11:46 PM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote:

> In the past, I've been keeping longer, largely textual content in an
> external wiki system and pulling it out to appropriate locations on
> the main wesite by placing a little wiki components on the pages, so
> that I can update the data on the fly as needed. This strategy has
> worked out fairly well as I was able to use either Confluence or XWiki
> (they implement the same xmlrpc interface) as the back-end data
> systems, but it's still a bit clumsy for my taste. I realize properly
> versioning the content is a big task, but I'd be willing to let that
> go if in return I could make editing the content even simpler.
> 
> Ideally, I'd be able to edit the content in place. If I had the rights
> to do so, I'd get a little edit button (like most pages on tynamo.org
> for example but I could be targeting just sections of the page),
> otherwise I'd just see static content. The content would sit in the
> database of my choosing, but would be heavily cached. Even if all of
> these content snippets would be cached in memory, I wouldn't care
> since it'd still be a tiny sliver of all memory resources. Also while
> content doesn't change often, it's desirable that cache doesn't stay
> stale for too long.
> 
> I was evaluating the CKEditor component for a different purpose but I
> can see that it could fairly easily be used for this purpose as well.
> Implementing it as a mixin is a clever idea, only in this case you
> could attach it to any output component as well (or even any container
> such a div) and it'd make a unique key based on the page name and the
> component id for storing the content in the database. Of course, it'd
> have to create a whole form ui in place and be able to submit it.
> 
> It's not trivial to get all of the above done, but I think it's
> definitely doable. Does such a component & module already exist? If
> not, I could totally see running this as a GSoC project - I'm sure
> Apache is in this year as well and we (Tapestry) should request our
> slots. Anybody else up for a challenge?
> 
> Kalle
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to