[Lazarus] New compiler options page "Additions and Overrides"

Martin lazarus at mfriebe.de
Mon Jun 10 23:59:43 CEST 2013


On 07/06/2013 23:40, Mattias Gaertner wrote:
> On Fri, 07 Jun 2013 21:23:46 +0100
> Martin <lazarus at mfriebe.de> wrote:
>> IMHO the "stored in" could be a "dropdown" (like
>> custow/ide-macro/outdir) in each row.
>> then the actual matrix, would have less disruptions.
...
>> Each "Target" would then appear only once. And the "stored in" would be
>> sorted (and thereby grouped) in each target block.
> The order does matter and putting an option in the wrong storage
> can have serious effects. For example if you accidentally put a session
> option into the project, you will break your team mates code.
> If you accidentally put a project option into the IDE you might break
> your other projects.
> IMO the storage and scope of an option must be made very clear to
> avoid such accidents.
>

I understand well the importance of the difference storage types, and 
even more to store an option in the correct place.

But I still thing it is too disrupting.

About the order: The order would be kept.
* Targets: abc
- Store IDE: Custom -Cr
- Store IDE: Custom -Cr
- Store lpi: Custom -Cr
- Store lps: Custom -Cr
* Targets: *
- Store IDE: Custom -Cr
- Store lpi: Custom -Cr
- Store lps: Custom -Cr

Within each target, the order would be kept.
Instead of using a "in matrix group/header", each storage group could 
have a color

If there where 3 radiobutton at the begin of each row

   I | L | L  |  M | M
   D | P | P  |  o | o
   E | I | S  |  d | d
     |   |    |  e | e
     |   |    |  1 | 2
   _______________
/ Targets: abc
| * | o | o | [x] | [ ] | Custom -Cr
| * | o | o | [x] | [ ] | Custom -Cr
| o | * | o | [ ] | [x] | Custom -Cr
| O | o | * | [x] | [x] | Custom -Cr

And each radio (column) had a different color, that would only show if the radio is set.
Changing the radio, will change the order. That could be deferred, until the user ends editing the TArget.

  
---------------------------
Then the next thing is "Target", maybe that could be more descriptive
"Apply to packages:"
"Apply to project [x], packages: '*'"
"Options for project [x] and packages: '*'"

With the storage as radio, if the grid is empty, an empty (dummy) "Target" could be displayed.

Since the name of that line contains the description, users may realize that they can set options for packages.


The "Target" header should allow right click, and offer a popup to add rows (idemacro, custum,...)





More information about the Lazarus mailing list