Author Topic: Project properties as editors  (Read 5536 times)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Project properties as editors
« on: September 11, 2014, 09:59:33 pm »
Initial discussion has been started in this topic http://forums.codeblocks.org/index.php/topic,16708.0.html

I've started the extraction of the project properties dialog as an editor.
Here is a screen shot with the current state: http://cmpt.benbmp.org/codeblocks/screens/project_props_editors.png

What I've done:
1. Make the project properties dialog to be an editor
2. Make the build options dialog to be a tab in the project options
3. Add some apis to make sharing the is-modified state between different objects a bit easier

What needs to be done:
1. Make all controls in all tabs to affect the modified state of the editor
2. Remove all build options buttons that are scattered all over the UI
3. Extract and improve the Dependencies dialog
4. Add an API which will allow plugins to control the priority of the added panels in the project properties dialog
5. Lots of testing and bug fixing....

I'm starting this topic to see if this is something that will be an accepted change by developers and users.
So please post your feedback before it is not too late.
If there are people interested to help I can share a branch in my repo on github...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Project properties as editors
« Reply #1 on: September 23, 2014, 08:10:04 am »
How do you manage synchronisation? I.e. for now, as the dialogs are modal there can hardly be an interfering process. But with the options being an editor you could change it during a build for example...?! I could think of some more race conditions like that...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Project properties as editors
« Reply #2 on: September 23, 2014, 09:42:31 am »
I've not done anything yet, but I think it is possible to make the editors read only during build.
Also in the  current implementation nothing stops you to edit the settings during build (the project -> properties menu is not disabled)!
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re:
« Reply #3 on: September 23, 2014, 09:22:13 pm »
That's true, but if you press ok it get refused.maybe a similar corrupt is possible. However I just wanted to mention this doubt. I wouldn't mind if settings are presented litter that...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Project properties as editors
« Reply #4 on: September 23, 2014, 10:09:30 pm »
Thank you for mentioning it, I'll see what can be done to make it a bit safer in this regard.
About the settings: I don't think making the same change will add any benefits, because you cannot have multiple setting windows for the environment settings or the editor settings.
For now I think, I'll do the change only for the project options.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]