Put hidden parameters from HippoEdit.config somewhere in Options dialog

Started by JJK, May 28, 2009, 09:13:34 AM

Previous topic - Next topic

JJK

Hello Alex

Would it be possible, even useful, to have those semi-hidden parameters inside HippoEdit.config somewhere in Options dialog,as "advanced settings" for example ?
I have already seen that kind of features in some software, but I don't remember what. It contains all hidden settings, used only by expert users, in a scrollable list with 2 columns, name in first, value in 2nd. Values are choosen also in lists when there is a set of possible values.

Perhaps my wish has no sense, but it is more handy to have sets of names and sets of values somewhere instead of in help or in the forum. ;)

Stefan

I would like this compromise between    "options without GUI counterpart"    and    "fiddle in XML settings files" too.

I see the sense behind hiding options in XML setting only,
it's quicker for the coder to add an option without thinking about
and do the work for an GUI counterpart (find space, find name and description,...)

But maybe an compromise could be to provide an simple text list of this options? (see picture below)
Just an code to read all options with current settings from config.xml, provide an list,  and store it back?
Stefan, HippoEDIT beta tester 
HippoEDIT - the editor programmers wants to code thyself when they are dreaming.        -Don't just edit. HippoEDIT!-

Arthur

I think Alex has that planned for a new HE branch (perhaps 1.5) of betas.

Expert Mode was seen some time ago as described in this thread: http://forum.hippoedit.com/index.php/topic,301.msg1205.html#msg1205

alex

Hi All,

yes, Expert mode was planned. The problem is that it is rather time consuming in my case to program UI for all this settings (read, save, change, options, help) etc.

Also I do not have "names" of the paramaters in runtime.

to JJK: something what you mean (control) called Object Instpector, if I am not mistaken, it is very comfortable to chnage properties there, but I do not have it and need to implement :/ Also because I do not have a textual form in runtime this is also small problem (I could get them, but this is also time). 

So, conclusion:
Idea is clear, good but time consuming. Because xml parameters are planned to be rare used by most of users, workaround to change them in xml directly for me is a good compromise now.
But I would keep this in mind and would add such inspector if I would have time, or it would become easier.

Best regards,
Alex.
HippoEDIT team
[url="http://www.hippoedit.com/"]http://www.hippoedit.com/[/url]

JJK


alex

Thanks JJK,

the vacation was perfect. Was in Denmark with family and friends fishing trout ;)
HippoEDIT team
[url="http://www.hippoedit.com/"]http://www.hippoedit.com/[/url]