Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of douglass.doug@gmail.com
 designates 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=PXI9ZeeP/PqwopSUVlbzVzRf+vlksXUGKKAHo9pY8k2bhsRM77USia4624X+2gSxU9K4A8PCJXoI02K6dba1gCWO8j6CwrdvF91eDQrenVboWjmWe8S2b6K4TSaffC1XoWY11QUe8smPiY5S7cD9Aa9KsNrjLOFRDL/yYZRJTFo=
Message-ID: <3a9670a0608150630k65f623bfu47cb78dbcb5fd765@mail.gmail.com>
Date: Tue, 15 Aug 2006 07:30:44 -0600
From: "Doug Douglass" <douglass.doug@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Browser Based WYSIWYG Editors and Jackrabbit
In-Reply-To: <7987dae0608040842i1e045549saa90b8bed029dbbd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_207245_880845.1155648644542"
References: <214FF1B5E37DC84D9968F0F82FBB11256EFC16@AUGEXCH.ghsinc.com>
	 <7987dae0608040842i1e045549saa90b8bed029dbbd@mail.gmail.com>

------=_Part_207245_880845.1155648644542
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

As a different option, on a project a few years back we built a web-based
XML editor using chiba[1] to transform XML documents stored in a CMS
(Documentum) to XHTML forms via XForms. Since chiba does the transformation
server-side, performance was pretty good, completely cross-browser, and we
could add/change forms without having to redeploy the app as the XForm
templates were in the CMS too.

Note, the XML documents were a handful of very specific document types that
translated well to strongly-typed form input fields -- only a few places was
a user actually allowed to enter free-form text -- and the end users were
not "sophisticated" enough to be exposed directly to the XML, so a "general"
editor was not our first choice.

Whether any of the above is applicable to you depends on your use case.

HTH,
Doug

[1] http://chiba.sourceforge.net/

On 8/4/06, c <oneskiingfool@gmail.com> wrote:
>
> On 8/4/06, Darren Hartford <dhartford@ghsinc.com> wrote:
> >
> > Browser-based WYSIWYG and CMS - it sounds very much like you may be
> > looking for a full Web Content Management System where you edit pages.
> > If this sounds accurate, look at Magnolia CMS and Webgui to see if that
> > type of solution may be what you are looking for.
> >
> > -D
> >
> >
> To clarify.  Although I could be wrong, I don't really see it that way.  I
> look at what I'm trying to do as strictly a DMS.  The lines might be
> blurred
> a little because the online editor would probably save documents in HTML
> format, but I want them treated just like a 'regular' document as opposed
> to
> a 'web page'.... if that makes any sense.  But I will take another look at
> Magnolia.
>
>

------=_Part_207245_880845.1155648644542--