FYI, ...
Whatever, how can it be easy to configured?
sure by redesign / redefine the 'fold'. at least I need to redesign the IDE Options's frame.
redesign of the ide frame should be no problem. Open to any change needed. But imho thats last on the list.
Thanks you!
foldconfig:
I am still thinking about it, there are various options and considerations. Most important, what needs to be known by the HL, and what is markup.
I keep it simple in mind:
- Markup do know nothing, except the instructions (X,Y, etc.) of drawing.
- HL dictate what should be drawn by Markup, but it always depends on foldconfig.
- HL do know nothing of final/current value of foldconfig. (however, HL provides default foldconfig values.)
- HL knows specific language keyword (repeat,until,begin,while,do, etc.)
Whenever found specific keyword, HL just quickly provides "node" info without seeing what values are delivering from foldconfig.
So, neither HL nor Markup care about foldconfig. It is indirectly from user to user.
It is beautiful design of fold config.
That is why my markup is very simple: modular.! only 500lines. I think I will reduce the codes in future.
Since the HL needs to deliver the base info for the markup, it also needs some config for this. This means certain config will have to be present, even if the markup is not used at all. (this conflicts with keeping everything modular, but it can't be avoided)well it could have partly been avoided by ...
Hey, there are no conflicting. When HL providing nodes/infos, it is not a big job for HL, because everything has been done once foldconfig changed. And as usually, foldconfigs are not changed during user work with synedit.
Its not a big job for HL : provides the value looked up from foldconfig.
So, I think no worry for this aspect.
But that would cause far to much overhead, so imho not an option.
I agree, there are no benefit of additional-config-properties of current foldconfig.
We first need to look at how many modes are needed.
That means do decide if EVERY configurable keyword can have all options:
- colored and/or lined
- ignored/merged parent or child
merging does not make sense for all the keywords (there in no point in merge "repeat" with parent or child ever).
If Merging not applicable for few keyword, let's make it disabled (not configurable) for them.
Look at attachment of how to disabled.
If it was only your markup, then we could add 2 modes (outlineColor, outlineLine) and maybe that is the better idea for now.
Great! adding fmOutlineColor,fmOutlineLine is the best we can do for now.
These 2 modes, together with fmOutline, can easily be implemented into IDE options. see attachment of how to.
2) the difference between color and line is really none of the HLs business.
even HL will never care about these, but the HL is the only correct place to put them.
It is the reason of why there are combobox "languange" for configuring them. see attachment, noticeable as green.
Maybe you have more ideas?
I don't understand what is problem with current foldconfig?
I can't see any benefit of additional tags or enums.
I can't see any problem with current config's technique.
It is most probably caused by my stupid, I felt I may misunderstand of your ideas.
Can you further talk about these?
edit: +attachment.