[
Lists Home |
Date Index |
Thread Index
]
:) What's the prize?
I am going to write about our closed source webapp, so if you are not
interested in that type of thing you do not need to read further.
On Nov 5, 2003, at 8:01 AM, Didier PH Martin wrote:
> Hi,
>
>
>
> As usual, in this list there is a lot of talk and very little walk.
> Here is a challenge I am proposing to the member of this list and
> particularly to the people who think great application can be done
> with a browser technology and W3C frameworks.
>
>
>
> Here it is:
>
> The goal is to get an XML document to be edited on the client, all
> validation performed on the client and the filled XML document
> returned to the server. Let’s start with a modest document as below.
> What is to be filled are the data content for each element. Simple no?
Not simple, but doable. I doubt many people would have the patience and
suffer the hacks necessary (not too many...), though.
If you have simple data to enter (i.e. using a form) it would not be
too hard to use MSIE's MSXML SOM to do client-side schema validation.
Article-type content is bit more difficult, but you can still use the
SOM to only allow valid content to be entered. We have found that
editors who are used to using styles in Word pick up using our editor
fastest. Designers/artists who do not understand CSS are the worst (we
usually won't take them as clients).
>
> So to recap:
>
> a) The XML document is associated with a stylesheet for
> rendition. All the element’s data content are empty.
We provide a ~wysiwyg~ view of the XML in editing, so it is better to
have some placeholder content in a new instance. I wrote ~wysiwyg~
because, of course, there is no true wysiwyg of content that is
separate from presentation. But users are familiar with MSWord style
editing so we try to provide something similar.
> The XML document is rendered in the browser using an XSLT stylesheet
> (you design and implement the stylesheet – rendition is opened)
yep. For us, a page can contain multiple content pieces. The edit view
is transformed to provide the L&F of the final rendered page, but the
content pieces are xsl:copy-of'd in their appropriate location in the
page layout. The XML L&F is handled with CSS, for example:
c\:article {
display:block
}
>
> b) The user enters the data and the XML data content is filled.
> The element Version has to be validated. Only 1.0 is allowed.
> Validation obviously is performed on the client side.
sure, even more, be able to add/manipulate validly (is that a word?).
>
> c) The XML document is returned to the server with all its data
> content filled
yep, also indexed by a search engine (Lucene)
>
>
>
> Here is the XML document:
>
> <demo>
>
> <version></version>
>
> <author>
>
> <name></name>
>
> <email></email>
>
> </author>
>
> <description></description>
>
> </demo>
For IE you need to have the XML start in a namespace, using a non-null
prefix, like:
<c:demo xmlns:c="boo">
>
>
>
> See, the XML document to be filled is simple. By the way, at first
> let’s not restrict that to a single browser.
Only IE for us on the client, until other browsers get a SOM. The
server is Linux and java.
> IE, Opera, Mozilla or others are fine. As long as the apps can do what
> is mentioned in this message and no “fat server” technology is used.
> The whole “fill the blanks” operation should occurs without constant
> connection with a server.
yep.
> Now let’s see how many can walk their talk
http://www.livestoryboard.com
and though not the latest, you can see screenshots here:
http://livestoryboard.com/Products/Screen_shots.html
best,
-Rob
>
>
>
> Cheers
>
> Didier PH Martin
>
> http://didier-martin.com
>
>
- References:
- Challenge
- From: "Didier PH Martin" <martind@netfolder.com>
|
