[Lazarus] Apache CGI and dbugintf

[Leonardo M. Ramé]

Op 2010-10-21 16:07, Martin het geskryf:
> 
> then those items that where not user-modified, should follow future 
> changes to IDE defaults

The IDE already doesn't work like that, so why must this feature. Code
Templates being one example.


> As well as newly added default should automatically be available.
> - if of curse a user already defined "*.foo" then a newly added default 
> for that, does not need to be shown
> 
> The last bit may be hard to archive by using the "build in" names. But 
> it could work by using the extension itself as an ID
> 
> However several extensions are usually grouped. so you need to store 2 
> things.
> 
> group-info:
> - default groups stored given by ID
>    - only stored if caption, position/order or enabled/visible changed
> - user groups
> 
> then for each extension in which group it is:
> - extensions used in a default group are only stored in xml if they are 
> either:
>    - diasbled / or moved to another group.
> 
> e.g. if "*.pas" is not in the xml, it will be part of it's default group
> 
> If a new default group is added, for *.foo => but *.foo is already in a 
> user group, then the default group will be empty, and not displayed


Oh, but now we have to not only parse the XML file, we now need to compare
default and user-enabled file filters via name, id, extension etc... we
also need to parse the extensions to see if we should add new defaults or not.

Did I mention this will slow down the startup time of Lazarus even more?
Something that Michael pointed out should be avoided. So there goes the
idea of speeding up the process by merge the settings into an existing xml
file.



Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net:8080/fpgui/