[Lazarus] Lazarus shortcuts conflict with windows shortcuts

Reinier Olislagers reinierolislagers at gmail.com
Wed Aug 15 14:37:11 CEST 2012


On 15-8-2012 14:05, Martin wrote:
> On 15/08/2012 12:40, Reinier Olislagers wrote:
>> I don't understand "The command-line isn't XML"? It can use the same
>> units to write the XML config as other existing code (just like
>> lazbuild).
> But it needs a separate reader, that writes data into the config object.
> 
> The XML reader already exists.
Ehm, ok, I'll take your word for it. I have the feeling we must be
misunderstanding each other.

>> Anyway, I'll shut up now - seems my suggestions were not well
>> received... which is no problem either, I'm busy delving into the depths
>> of documenting FPC's zipper classes right now anyway ;)
>>
> I don't see how the export solution is less helpful?
> you have an XML file (created once by the IDE):
> - contains koymapping only, interferes with noting else
> - any future IDE can read it. If formats are changed, old format are
> still supported.
Ehm yes, this is shifting backward compatibility to another layer... I
don't know if that is an actual advantage ;)

> *IF* the export exists, AND someone submits a patch, it would be
> possible to do "lazarus.exe --keymap=xmlfile.xml"
You mean it will then import/merge xmlfile.xml into the regular config
(overwriting existing settings or creating them depending on situation)?

Yes, that might be very helpful. As I said in an earlier post, I'll have
a look at what's available.

This import mechanism by itself need not be restricted to colors etc (a
GUI would be)... as long as
1. you devise a schema that takes into account the Laz xml filenames
(environmentoptions.xml, editoroptions.xml)=>fortunately that already
seems to be have been done in the Laz xml files themselves
2. mappings to deal with old versions if wanted
3. some strategy on how to deal with child objects (e.g. overwrite those
with same name?)
you could perhaps just dump all the XML as is, e.g. this for a corporate
install script:

<?xml version="1.0"?>
<CONFIG>
  <EnvironmentOptions>
    <Language ID="de"/>
  </EnvironmentOptions>
  <EditorOptions>
    <General>
      <Editor TabWidth="2" TabIndent="True"/>
    </General>
  </EditorOptions>
</CONFIG>

Added benefit: people can define their keymappings like that as well ;)

Having said that,
1. my XML-fu is almost nonexistent so please take all this with a pinch
of salt.
2. aren't there any tools that already provide such a "merge XML"
functionality?

Thanks,
Reinier




More information about the Lazarus mailing list