Mathias Bauer wrote:
Joe Smith wrote:
Why does OOo not have a tool like Windows' regedit, or Mozilla's
about:config, or GConf's gconf-editor, where the OOo "registry" could be
searched and edited directly?
You can a lot of good XML editors to do so. This is even more
comfortable as "about:config", in most cases it also beats the Windows
registry editor.
That is surprising to me. From my limited understanding of OOo's
"registry" -- what is the right name? -- the XML form is quite different
from the functional content once all the individual data files are
merged. I would think a functional view, like OOo will 'see' when using
the database, would be needed.
What do you use to build and maintain the database? Wait, let me guess:
vi? Emacs? ;-)
IIRC XMLSpy was a quite capable editor in this regard.
Riiight. I'll let you ask them about open-sourcing that ;-)
I've not seen a FLOSS one that I wanted to use for more than 30s.
Look on the OOo configuration schema files: they *are* annotated.
Ahh, ok, I see now. Very nice[1]. I only ever looked at the .xcu files.
But isn't that another reason that a specialized tool is needed?
...
A quick look shows no requests, but it seems like an obvious benefit to me.
We are working hard on the requests already, there's no time to look for
"obvious benefits" that noone requested before. ;-)
Understood and thanks again for taking time to explain.
Would it be helpful to have a specific request on file, or a skeleton
project page, so someone with the skills to put something together could
have a good start?
<Joe
[1] $ locate -0 *.xcs | xargs -0 grep -l 'TextMode'
.../openoffice.org/share/registry/schema/org/openoffice/Office/Common.xcs:
<prop oor:name="TextMode" oor:type="xs:int">
<info>
<desc>
Specifies if glyph outlines are exported. They produce the
highest quality and it is the only possible way to create EPS
files that are CJK compliant. Not using glyphs will produce
smaller files, but it might lead to problems if not all fonts
are available during printing.
</desc>
<label>Export text using glyph outlines - always / never</label>
</info>
<constraints>
<enumeration oor:value="0">
<info>
<desc>Glyph outlines</desc>
</info>
</enumeration>
<enumeration oor:value="1">
<info>
<desc>No glyph outlines</desc>
</info>
</enumeration>
</constraints>
<value>0</value>
</prop>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
