Re: Re: cfg.h (config layer 0 discussion)

Hi,

> >>     I'll try to explain. How menu system for GUI-based application may be
> >> created? By another structure that will copy config but with some tree?
> >> You may be very surprised but level 0 config already has all for GUI menu
> >> in it. Only thing it has not yet was formatting field (from main menu
> >> panel to drop-down menu, from drop-down menu to submenu, for separators
> >> between parts of drop-down menu, etc.). So that CONF_TYPE_GROUP at first
> >> was proposed as such formatting field (application-level type config
> >> item). Finally on "Alt" keypress or mouse event we can just run some
> >> function of GUI like display_menu(window,config) - it's enough and you
> >> don't have to make some deep changes to reformat menu - just reorder
> >> items of config in source or even in runtime. :)
> >>     Did you understand now?
> 
> >Hmm, so the point is to make it easy to nest groups (as subconfigs)
> >and add and remove items from them?
> 
> Yes. For nested groups and separators. :)

Hmm. Do we really need nested groups??
It adds extra complexity (recursive parsing instead of for()) to config
layers, with very small advantage.


A'rpi / Astral & ESP-team

--
Developer of MPlayer G2, the Movie Framework for all - http://www.MPlayerHQ.hu