jexus-devel Mailing List for Jexus
Brought to you by:
axonrg
Menu
▾
▴
jexus-devel — Discussion of development issues.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Ricardo G. <ax...@uk...> - 2004-05-26 12:29:21
|
Samuel Penn wrote: > Ricardo Gladwell said: > Another solution is just to use CML as the wrapper, and something > else for the content. For instance, you could embed XHTML within > the data portion if you wanted. XHTML 1.2 looks quite similar to > what you're suggesting for CML (nested section tags, no bold or > italics etc). I have to admit, I'm still not familiar with XHTML. I didn't realise they had added additional constructs, such as the section tag you highlighted. Interesting... another book to add to my reading list :) >>It would be, in effect, writing another word processor. Because of this, >>I'm unsure if this option is necessary. What would the Java client offer >>that, say, OpenOffice couldn't? > > Well, to reverse the question, how much of OO is actually needed? > All you need is support for some special tags (which needs to be > done in OO anyway), and basic text editing support. Good question. The only reason I suggest OO is that it seems to do a lot of what we want to do: export to a wide range of formats, including PDF, XML-based content syntax, seperation of content, layout and style. It has a plugin facility, it uses Java bindings. I'd be interested to know how we could insert yags tags into a document and process and display them all within OO.org. What do we need Jexus for?!? All we need is a webdav repository or XML database to store the content so it can be searched by other applications. Perhaps Jexus could merely be a database for OpenOffice text documents that is searchable and allows us to dynamically apply different styles to different documents? Kind regards... -- Ricardo Gladwell President, Free Roleplaying Community http://www.freeroleplay.org/ pre...@fr... |
|
From: Ricardo G. <ax...@uk...> - 2004-05-25 10:30:33
|
Samuel Penn wrote: > Currently, the Yagsbook Encyclopedia only supports Yagsbook XML > format, which in turns only supports Yags ruleset. It would be > nice if things were made more generic, to enable the support of > other document formats and other systems. I think allowing Yagsbook to support other rules systems would definitely widen its appeal, although how this would be achieved I have no idea. Perhaps, some method of generically assigning and describing traits? > Just to make things clear, it would work by the Encyclopedia class > have an add(ISource src) method to add an (already instantiated) > data source. The ISource interface defines a > (IEntry[])getAllEntries() method to getting all the entries out. > Each IEntry represents an individual XML document, giving access > to it via getter methods. > > I think this latter is the best way forward. I agree, some sort of generic mechanism for accessing the content would probably be best. > Would the CML format provide this sort of meta data? I need to flesh > out details about what I mean by TopicSet for instance (a concept I've > taken from NewsML) since currently it's all pretty much just in my head. Meta-data would probably be provided through RDF. -- Ricardo Gladwell President, Free Roleplaying Community http://www.freeroleplay.org/ pre...@fr... |
|
From: Ricardo G. <ax...@uk...> - 2004-05-25 10:17:58
|
Samuel Penn wrote: > On Monday 24 May 2004 14:30, Ricardo Gladwell wrote: >>Sorry about that, you can examine a (very rough) early sample of the >>proposed CML in our web CVS viewer here: >> >>http://cvs.sourceforge.net/viewcvs.py/jexus/net.sf.jexus.core/xml/sample.xml > > I started with <bold> tags, but being someone who writes the documents > by hand, I soon got bored and everything mutated to <b>, <i> and so on. > Actually, I have <s> and <e> (strong emphasis and emphasis) instead of > specific font styles. I'm of two minds whether or not to include styles such as even emphasis: after all, this is supposed to be a content-only format. It depends how much we can seperate style and >>Good point. There are three options here: >> >>1. Server-centric: Tolerate the loss of information when OpenOffice >>documents are "squeezed" into CML format. > > I'd be against this, especially in the case where game rules are being > stored. Consider an XML structure for a spell, or a beast. Both can get > very complex. You misunderstand, formats such as Yags would be unaffected by information loss. The information lost will be the style/layout information in the the OpenOffice document only. Yags data would be stored using an OO plugin and would not be affected. Given this, what is your opinion on this option now? >>2. Client-centric: We write a complex Java client, the server is just a >>WebDAV repository of CML files with a HTML admin front-end. The client >>imports content from other documents and exports content to other >>applications, and is responsible for all the transformations. Plugins are >>written for the client. Means writing complex client code. > > Complex, but has the advantage of being accessible wherever you are > online, especially if the Java is an applet or something similar. > Could be totally thin client. It would be, in effect, writing another word processor. Because of this, I'm unsure if this option is necessary. What would the Java client offer that, say, OpenOffice couldn't? >>3. OpenOffice-centric - as 2 except we make OpenOffice the default format >>and client. OpenOffice uses its own content.xml format that we can use. We >>can write add-ons to OpenOffice to use additional data-sets, i.e. for >>yagsbook, which are sent in the content.xml part of a OO file. Of course, >>this limits us to using OO only. > > Possibly straightforward, and other office programs (e.g. KWord) are moving > towards the OpenOffice file format, but don't know how portable such things > would be. Limits usage to thick clients. I have to admit, I'm coming round to this option more and more. The above wouldn't be so much of an issue: OpenOffice (or OO.org) would be the thick client and its already been written. You couldn't run it on your PDA but you could import content from your PDA into OO.org. OO.org already has its own content format, and it already seperates style and layout into seperate documents within a OO.org file (in three handy files: content.xml, style.xml and layout.xml :). In which case, Jexus just becomes a webdav storage facility with a web front-end. In fact, I'm not even sure what Jexus would be for: linkig content in a wiki like way? Dynamic publishing of content? >>Don't know if I can help with that: not familar with a Zaurus (what is it?) > > Linux based PDA, with mini-keyboard. Sounds dead nifty :) > I noticed Maven on your site, and I've spent some time looking at it. It > looks quite useful, and Iit's been added to the list of things I need to > investigate. I can't recommend Maven enough: its really revolutionary and time saving. > I'm wondering whether this discussion would be better on the Jexus > site, where it would be visible to people interested in the project. Good point: forwarding this onto the Jexus development mailing list as well :) I suggest we send discussion on this to both mailing lists, unless anyone objects? -- Ricardo Gladwell President, Free Roleplaying Community http://www.freeroleplay.org/ pre...@fr... |
