as far as to why, i think wicket will easy allow us to build some very cool features. like in the page if you put {calendar id="blah"} you can easily have a calendar component in your wiki page. there are other wikis that offer this, but wicket wiki will offer this in a much simpler fashion because of wicket's component oriented nature. that means anyone who knows wicket will be able to easily write plugins.
i would love to have a WikiMarkupPanel that i can drop into any app i write and get the wiki formatting as well as any plugins working right away.
-Igor
On 3/10/06,
Christophe Lombart <[EMAIL PROTECTED]> wrote:
Last comment : why to build a wiki or cms application here. It is the
wicket goal ?
If I understand, the wicket main target is to provide a very nice web
framework.
Why not to work with another team which is more focusing on CMS/ECM problem ?
There so many open source projects in java. This is certainly the big
issue compare to other plateform like Zope. That causes small
communities. So, why to create another wiki system (or CMS, ECM or
...) ?
Christophe
On 3/10/06, Christophe Lombart <[EMAIL PROTECTED]> wrote:
> JCR is very simple.
> Classic RDBMS ( and its SQL) doesn't match correctly to content based
> application.
> With a JCR based repo, you have automatically support for versionning,
> indexing, full text & prop search, node type, .... Futhermore, JCR
> spec is not very difficult to understand. If you can use JDBC, you can
> use JCR.
>
> Now, that's clear JCR becomes the standard and will replace JDBC for
> managing content based application. Unfortunately, JCR is low level
> (like JDBC). The graffito team is building the first OCM tools
> (Object/content mapping tools). It is still on dev.
> see this Graffito project on :
> http://incubator.apache.org/graffito/jcr-mapping/index.html
>
> Again, before taking a decision, take the time to review the JCR spec.
>
> Christophe
>
>
> On 3/10/06, Igor Vaynberg <[EMAIL PROTECTED] > wrote:
> > how about focusing on something simple. write a wiki with a simple database
> > backend. then migrate it to use a repo and add all the bells and whistles.
> >
> > -Igor
> >
> >
> >
> > On 3/10/06, Riyad Kalla <[EMAIL PROTECTED]> wrote:
> > >
> > > I understand that goal, I just don't know how they achieve that... for
> > example, storing an enormous blob of XML in a database or a file certainly
> > meets the requirement of "not caring where it's stored", but gives you a
> > less than stellar data store to work with (in a DB).
> > >
> > > As a Java developer I feel it's my right to develop a new content
> > framework so as to avoid reading the JCR spec more closely :)
> > >
> > >
> > > Eelco Hillenius wrote:
> > > I think the idea behind JCR is that it doesn't care about where with
> > > what format it is stored.
> > >
> > > Eelco
> > >
> > > On 3/10/06, Riyad Kalla
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Christophe,
> > > From what I've seen on jackrabbit it dumps out an entire file in XML
> > format
> > > and all the examples I can find have it confirued to run from a file data
> > > store, not a DB. I had one friend comment that if you config it to dump to
> > a
> > >
> > > DB, it simply dumps the giant XML file into a single table, but I find
> > this
> > > hard to believe.
> > >
> > > Do you have any experience with it?
> > >
> > > Christophe Lombart wrote:
> > > On 3/10/06, Joe Toth
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >
> > > Any ideas for a content repository? Graffito and Jack Rabbit look
> > > interesting, but I hope they aren't projects stuck in XML hell.
> > >
> > >
> > >
> > > JCR is a must. Graffito is currently based on a DB schema and we are
> > >
> > > migrating to JCR (Java Content Repository) spec. Graffito is not only a
> > > repo. it is a full ECM plateform - Sorry it will be a full ECM plateform
> > > based on Spring :-). it offers a common foundation for all kind of content
> > >
> > > application. I think it should be nice to build wicket web apps on the top
> > > of Graffito. Christophe
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> > language
> > >
> > > that extends applications into web and mobile media. Attend the live
> > webcast
> > > and join the prime developer group breaking into this new coding
> > territory!
> > >
> > >
> > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
> > > _______________________________________________
> > > Wicket-develop mailing list
> > > [email protected]
> > >
> > >
> > https://lists.sourceforge.net/lists/listinfo/wicket-develop
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> > language
> > > that extends applications into web and mobile media. Attend the live
> > webcast
> > >
> > > and join the prime developer group breaking into this new coding
> > territory!
> > >
> > >
> > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
> > > _______________________________________________
> > > Wicket-develop mailing list
> > > [email protected]
> > >
> > >
> > https://lists.sourceforge.net/lists/listinfo/wicket-develop
> > >
> > >
> > >
> >
> >
>
>
> --
> Best regards,
>
> Christophe
>
--
Best regards,
Christophe
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
