Hello,
Why all settings in environmentoptions.xml ? for example, New desktop settings added, its good think, But why all value in environmentoptions.xml ? My suggestion is different file for each setting grup. PackageEditor_***** can be separate xml file. So user (like me) when any conflict, just remove that file, and IDE create default values. At this style, I mean each settings in separated file, can copy settings to different os or user(s)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20151011/a2bc03f0/attachment.html>

Hello, Why all settings in environmentoptions.xml ? for example, New desktop settings added, its good think, But why all value in environmentoptions.xml ?

It was easier to implement and loading/saving only one file is faster. The IDE already loads 30+ configs every start and this costs some time. Loading the files contents and parsing the XML could be done in parallel.

What settings a user wants to move to another OS varies widely. Maybe implement a dialog, where the user can select what to export.

Mattias

yes, But how long get time? 1 second 5-10 second? need test. if conflict any settings, hard to find it. I'm talk about to lazarus user(s) ofcource this conflict problem on usually on svn

For cross compile. for exmple I'm on osx and make win and linux build. For some design and/or some test etc. I'm using virtualbox os and installed same fpc & lazarus (svn)
Keyboard maps. Editors colors, etc. Export/Import maybe helpful, but at this point need select which settings will export or import. On import need version check etc.

Mattias Gaertner wrote

What settings a user wants to move to another OS varies widely. Maybe implement a dialog, where the user can select what to export.

Yes, the export/import stuff needs attention.

The Desktop manager can now export/import all desktops or just one. All the settings belonging to a desktop are included.

The environment options dialog "General" page (former "Desktop") still has buttons for export/import but they are not usefull for anything. The set of options used makes no sense. I am planning to remove the buttons unless somebody has a better idea.

FreeMan, would you like to study this issue more and improve it?

Regards,
Juha

Little bit scare this :S
My project has finished and I want to change it with old one this week. My plan was last week but I found bug on tmemo,(if I'm not wrong its about qt showmodal & resize codes) I found it after 4 days. This high priority for me.
Anyway.

I need some help that, 'cos I'm no any idea about lazarus code, class etc.
- for export&import which file has in?
- is any help about for classes? (will be fast puzzle for me
- Have you any improve idea about that?
I'll try look at that, then I can say, I can do or not

Regards, Juha

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20151014/3f77b7a3/attachment.html>

FreeMan wrote

I need some help that, 'cos I'm no any idea about lazarus code, class etc. - for export&import which file has in? - is any help about for classes? (will be fast puzzle for me - Have you any improve idea about that?

Export and import use the same code that saves and loads environment options. You can look how export/import for desktops is done in the desktop manager.
You can also look at the obsolete code for buttons in "General" page in environment options window.

My only idea is to delete the export/import buttons from the "General" page.

I personally don't need more detailed export but I can commit such code if somebody implements it.
You must figure out how small portions of the settings you want, then divide the save/load code into smaller methods and then create a GUI for it. Easy piecy. :)

Juha