Overall process of using xopus

May 30 2008

  • 5 replies.
  • This question is not yet resolved.
  • This question was started by Michael Klemme.
  • Last post by Carl.
Michael Klemme
user
30 May, 14:49
Hallo!

I am new to xopus, planning to evaluate it for a real project.
I have seen the documentation and the demos, but I did not find an overall How To for setting up a new system.
This is what I think is needed:

* XML DTD and sample sources exist.
* Generate XSD matching DTD.
* Create an XSLT that converts the XML instance into a matching HTML instance (e.g. DIVs).
xopus attributes are added.
* Write a CSS to style this data on-screen
* Write a return handler that will accept the data back from the browser.
*Integrate all into the xopus canvas.

Would you agree that this is the right approach?

Grüße
Michael
Sjoerd
Xopus Team
30 May, 15:19
Yes, that sounds about right. Also see:
http://xopus.com/Documentation/Installation%20Guide/Getting%20Started.new
Michael Klemme
user
30 May, 19:08

XSL/CSS Generator

Thanks for your quick response!

Has now somebody already undertaken the task to generate the XSL and CSS needed from the DTD/XSD?
That would be a good starting point!
Sjoerd
Xopus Team
31 May, 18:34
No, but for an internal site we have a custom xml format (which can be edited in Xopus of course) from which the XSL, CSS *and* XSD are generated. If you stick to a small subset of XSD features, it's actually not that much work to do something like that.
Thomas Stahl
member
28 June, 14:45
>> we have a custom xml format from which the XSL, CSS *and* XSD are generated.

This sounds very interesting. Can you publish this system? It would be very helpful for all Xopus beginners (like me).
Carl
Xopus Team
30 June, 10:38
This system is quite integrated into the internal site, and given that it is integrated XSD and XSL and CSS, it is far from easy to read or understand.

We are a little apprehensive of publishing this system to people since it would not be a solution to their problem. This system is not a system to generate XSD and XSL, as it generates it on the fly, based on the custom XML format.

If you are new to Xopus it might be a better idea to take some time examining the Simple demo to see how Xopus handles and uses different files.

To find a solution to the problem you wish to solve using Xopus however, it is first necessary to take time to think about what structure of XML you actually need for that, and how this XML is best structured. For do's and don'ts you can take a look at the best practices pages in the documentation.

You would also be welcome to send your questions to us, so that we may help to find what you are looking for.

I would like to add that Xopus generally isn't a quick fix to a problem, it requires considerable thought and effort to get Xopus to do what you want it to do: to help users work with 'their information' rather than (your) XML.


React

HTML will be shown as HTML code.
Linebreaks and Links starting with http:// are automatically resolved