Re: [pcgen-xml] Re: Expanded pcg proposal
- Eric Jarman wrote:
>I'd like to suggest the following:content.xml doesn't have any formatting information, so we would need to
>content.xml -- The outputsheet in OpenDocument format.
have content.xml & style.xml.
One cool thing about this is that making an output sheet for
content.xml/style.xml will be stupid easy, cause we can just write up
the sheet in open office, with the export tokens as the text (like |HP|
where hit points should be, since it stores it as xml)
>meta.xml -- timestamp, etc.because content.xml works the way it does, it's really just text
>settings.xml -- info related to the output sheet.
> paper size, which OS was used to generate content.xml, etc.
>mimetype -- the mimetype
>export.xml -- (optional) raw numbers to import into other programs
>META-INF/manifest.xml -- file list
>Pictures/* -- (optional) images included
>debug/* -- (optional) info for debugging character files
> could use config options to determine how much to save here
>debug/log.xml -- the log (section2) as suggested before
>debug/options.ini -- a copy of the pcgen options.ini file
>debug/outputsheet.xml -- a copy of the outputsheet used for content.xml
strings, the outputsheet is probably more going to be for style.xml, but
in principal, that's not a bad idea
>debug/data/* -- copies of the datasets loaded for the characterDeffinitely optional, but not a bad idea if someone turns on debug mode,
cause then we can see all of what is actually going on.
>PCGen/* -- actual info for the characterJust put this in customdata
>PCGen/pcg.xml -- (section1) data needed by pcgen to build the character.
>PCGen/equipment.lst -- custom equipment for the character
>PCGen/customdata/* -- (optional) lstfiles for any custom data generatedNot a bad idea storing custom lst in the pcg, it's always irritating
> by the lst editors used by this character.
when you load your character on another pcgen instance, and it's missing
the custom stuff you input for that char.
>PCGen/followers/* -- (optional) info for followers.Same as above for customdata
Not sure if I want to embed the xml, or whole xpcg files - so that they
can have their own export sheets in it. another way to deal with that
would be export.xml files in their directories, or making export.xml
tolerate more then one character in it. I suppose one could also export
*all* characters into content.xml/style.xml
>etc...I like it, but lets move debug into the program dir.
>Then any other directories for other programs.
>What do you think?
Just getting the built-in editors to work well has been an effort for a number of years now. I think that, if the code team were
to focus solely on the editors, they'd work on getting just the flat-file stuff working first before going towards the zipped
Paul W. King
OGL/PL/TM Chimp, Data Gibbon
From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of Edwin Holley
Sent: Wednesday, October 12, 2005 7:05 PM
Subject: RE: [pcgen-xml] Re: Expanded pcg proposal
Ok ... what about an editor for the data sets, which could support the zipped or unzipped data sets automatically.
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.14/130 - Release Date: 10/12/2005