Hi Arno,
It's not necessary to "upload" the Web page. Just set the root
directory of the HTML pages in the xmlcResourcePath in the web.xml and
any newly added page will be picked up by the Preview servlet. The HTML
Developers can worked on their favorite tools with the HTML and preview
it instantly in the browser.
And this is not an idea, it's prototyped already in the new XMLC 2.2
Alpha 2. Check it out...
Again, the download URL is:
http://homepage.mac.com/taweili/XMLC.html
From the Preview in the README of the examples.
---
Preview Servlet
This servlet let you preview the static pages' XMLC output in a
browser.
Setup:
Add the directory of the static page root to 'docroot.dir' in the
build.properties and 'ant'
Running:
Start Tomcat using run-tomcat.sh and point your browser to
http://localhost:8080/xmlc/Preview/dyna/dyna01.html
and click on 'Jump to dyna/dyna02.html'
These HTML to be loaded is at 'res/dyna'
If you has setup docroot.dir pointing to your static page root, use
http://localhost:8080/xmlc/Preview/index.html
Assuming your starting page is named index.html and browser away.
---
David Li
---
"It spells Mac OS X but pronounces NeXTSTEP"
On Friday, Nov 29, 2002, at 18:24 Asia/Shanghai, Arno Schatz wrote:
Hi David,
that is really a good idea, your suggestion no. 3!
We could extend the servlet such that a html developer could upload a
html file and the servlet will run it through XMLC and show the
resulting page. That way even 3rd party html designer could easily
view their results. Even though this is not much more than using HTML
Kit on the desktop, is is probably much better accepted and easier to
use.
thanks for the idea,
Arno
David Li wrote:
Hi Arno,
I can understand you concern. I have worked with html developers in
many projects and it's difficult to tell html developers what's wrong
with their HTML page if it looks correct on screen. We mostly end up
turning off the warning in Tidy.
There are several solution to this problem and we could look at
each of them:
1. Have Tidy to ignore the invalid HTML and parse the rest.
This would be difficult. First, Tidy (consider the origin and the
name) is to make sure the HTML is correctly according to spec.
Second, how to differentiate an area to be "ignored" and an area to
be "correct" in the pages are difficult.
2. Make sure the HTML developers produce "correct" HTML.
Well, difficult as we all have experience. Ask them to read the Tidy
output would be difficult. Some of the warning are not really
necessary to be corrected like missing 'summary' on the table.
3. Let HTML developers inspects the XMLC output VISUALLY in a browser.
(shameless promotion of the new XMLC 2.2 dynamic loading features
here! Download it NOW!!!)
XMLC 2.2 enables the loading of HTML page into XMLC without being
compiled. Base on this feature, I have written a Preview servlet that
the Web developers can use to look at their pages and see in the
browser as how the pages would looked after being processed by XMLC.
I just put the Preview servlet on the XMLC 2.2's alpha release page.
The URL is:
http://homepage.mac.com/taweili/XMLC.html
The file name is called 'preview-example.tar.gz' and it only works
with XMLC 2.2 alpha.
David Li
---
"It spells Mac OS X but pronounces NeXTSTEP"
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 