This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Editing XML with HTML forms
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Editing XML with HTML forms
- From: "Robert Koberg" <rob at koberg dot com>
- Date: Tue, 23 Oct 2001 09:05:35 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
At the last place I was contracted to we used Interwoven. It does (or at
least similar to) what your tool does, but the problem was that our
non-technical editors could barely use it. And I think they spent more time
complaining about it.
I understand the reasons for a zero-client footprint, but I feel that the
non-technical end-user demands more.
I wouldn't mind continuing the debate offline, if you want?
best,
-Rob
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Paul Brown
> Sent: Tuesday, October 23, 2001 8:48 AM
> To: xsl-list@lists.mulberrytech.com
> Subject: RE: [xsl] Editing XML with HTML forms
>
>
> > [Robert Koberg]
> > This is the major problem... Server-side Java is nice
> > from uml point of view but it does not play out in
> > real-life...
>
> Wow. We should go have a rant/flame war in some more appropriate
> newsgroup... My perspective is exactly the opposite: server-side Java,
> especially where XML is involved, is the _only_ realistic option for
> production applications.
>
> This thread has actually seen a nice mix of different suggested solutions
> (Perl, libxml, msxml, JavaScript gymnastics etc.), and everything has its
> own unique and compellilng (based on circumstances) advantages.
> One of our
> design requirements was ZERO client-side footprint -- no Javascript, no
> Java, no DHTML, just a version of HTML that supports forms.
>
> Paul Brown
> FiveSight Technologies, Inc.
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list