Plain Black, makers of WebGUI - Re: Config File Changes

Goto page «Previous Page 1 2 Next Page»

Config File Changes
User	JT
Date	8/28/2008 3:32 pm
Views	1506
Rating	1 Rate [ \| ]

Previous · Next
User	Message
JT	Date: 8/28/2008 3:32 pm · Subject: Config File Changes · Rating: 1 This morning at the WUC I announced a new admin bar, and as a result of the changes in that I announced that I'd have to make some config file changes. These are my planned changes. First, we can make the admin console pluggable. Here's how that would look in the config file. "adminConsole" : { "xxx" : { "label" : "", "url" : "", "group" : "3", "uiLevel" : 9, "icon" : "" }, "yyy" : { "label" : "", "url" : "", "group" : "12", "uiLevel" : 4, "icon" : "" } } Basically the admin console will be entirely configured from the config file, and WebGUI::AdminConsole will load it from there. Second, we'll replace the assets, utilityAssets, assetContainers, assetAddPrivileges, assetUiLevel, assetToolbarUiLevel, and asset field UI level directives with something like this: "assetCategories" : { "utilities" : { "label" : "Utilities", "uiLevel" : 7 }, "simple" : { "label" : "Simple", "uiLevel" : 9 "assets" : { "WebGUI::Asset::Wobject::Article" : { "addPrivilege" : "7", }, "WebGUI::Asset::Wobject::Layout" : { "addPrivilege" : "7", "isContainer" : 1, "toolbar" { "edit" : { "uiLevel" : 0 } } "tabs" : { "meta" : { "uiLevel" : 4 }, "advanced" : { "label" : "", "uiLevel" : 6 } }, "fields" : { "url" : { "uiLevel" : 7, "tab" : "security" }, "title" : { "uiLevel" : 1 }, "groupIdEdit" : { "tab" : "advanced" } } } } }, "intranet" : { "label" : "Intranet", "uiLevel" : 9 }, "shop" : : { "label" : "Shop", "uiLevel" : 4, "assets" : { "WebGUI::Asset::Sku::Product" : {}, } } }, In addition to replacing existing functionality, this will give us a few new abilities: Creating new tabs. Moving fields to another tab. UI Levels on tabs. New Content menu categories. What do you think?
Back to Top	Rate [ \| ]

martink	Date: 8/28/2008 3:40 pm · Subject: Re: Config File Changes · Rating: 0 jt@plainblack.com wrote: > What do you think? Methinks it's a great idea and that the wuc is probably the mostest fastest rfe list =) Martin
Back to Top	Rate [ \| ]

koen	Date: 8/28/2008 3:41 pm · Subject: Re: Config File Changes · Rating: 0 Would it be possible to split the configfile up into separate parts that can be included into eachother? Koen de Jonge - ProcoliX http://www.procolix.com Hosting - WebGUI - Virtualization
Back to Top	Rate [ \| ]

JT	Date: 8/28/2008 3:50 pm · Subject: Re: Config File Changes · Rating: 0 Thanks for hijacking my thread and not even bothering to answer the question I posed. =) > koen wrote: > Would it be possible to split the configfile up into separate parts > that can be included into eachother > I don't know the answer to that. I've thought about it in the past, but our config files write back to the file (upgrade scripts for example), which makes supporting this difficult at best.
Back to Top	Rate [ \| ]

koen	Date: 8/30/2008 7:27 am · Subject: Re: Config File Changes · Rating: 0 Thanks for hijacking my thread and not even bothering to answer the question I posed. =) Oh I'm sorry, I did the implicit default 'I agree' thing again. Add this above my question: 'I really like the idea, I think it's great. The only worries I have are being able to maintain a configfile that is that large, I allready have troubles maintaining the current ones.' Koen de Jonge - ProcoliX http://www.procolix.com Hosting - WebGUI - Virtualization
Back to Top	Rate [ \| ]

crythias	Date: 8/28/2008 7:29 pm · Subject: Re: Config File Changes · Rating: 0 I have a few problems... Nah, just KIDDING! I like it. Really, I do. I understand Koen's point about segmenting because, truly, this is going to be an unruly config file. You have already certain parts that have nothing to do with each other. I'm tempted to suggest WebGUI/etc/yourdomain.com.d/ consisting of: adminbar.conf connectdb.conf filelocations.conf spectreconnect.conf ldap.conf macros.conf pluginsandhandlers.conf or :) editme.conf (what you MUST change to make WebGUI even function) everythingelse.conf
Back to Top	Rate [ \| ]

JT	Date: 9/4/2008 1:56 pm · Subject: Re: Config File Changes · Rating: 0 other. I'm tempted to suggest WebGUI/etc/yourdomain.com.d/ I like this idea a lot. But there are a few problems I'll have to work out before I can even consider adopting something like this: We have to keep track of which file each parameter is read from so that when they're written back out they go to the right file. We have to somehow decide which file a new parameter gets written to. Makes searching more difficult because it may not be in the file you have open. Reading in multiple files is slower than reading in one big file.
Back to Top	Rate [ \| ]

pwrightson	Date: 8/29/2008 4:07 pm · Subject: Re: Config File Changes · Rating: 1 I like this a lot! I think it will allow flexibility to add new parameters in the future (eg. force SSL for certain operations). I am a little concerned about managing the deep trees that will be created. How about a config file editor in the Admin Console or in the WRE site set up? We could allow access to various sections using a mechanism similar to uiLevel. Same goes for the rest of the config file, with a very high uiLevel for things we do not want anyone to touch (WebGUI database parameters could be an example).
Back to Top	Rate [ \| ]

knowmad	Date: 9/3/2008 1:37 pm · Subject: Re: Config File Changes · Rating: 0 How about a config file editor in the Admin Console or in the WRE site set up? We could allow access to various sections using a mechanism similar to uiLevel. Same goes for the rest of the config file, with a very high uiLevel for things we do not want anyone to touch (WebGUI database parameters could be an example). I really like the idea of a web editor for the uiLevels. I could envision a page that showed all the possible settings with the ability to change the default uiLevel and a way to sort the entries by uiLevel or privilege name. As it is now, I have very little idea of what gets enabled from ui level 1 - 10. William ---- Knowmad Technologies http://www.knowmad.com
Back to Top	Rate [ \| ]

arjan	Date: 9/3/2008 5:30 pm · Subject: Re: Config File Changes · Rating: 1 As it is now, I have very little idea of what gets enabled from ui level 1 - 10. William Hi William, UI-levels are inherited from the definition like other properties are inherited. From asset (Asset.pm) for example: %properties = ( (...) isHidden=>{ tab=>"display", label=>$i18n->get(886), hoverHelp=>$i18n->get('886 description'), *uiLevel=>6,* fieldType=>'yesNo', defaultValue=>0, }, And then again from the definition in Wobject.pm, for example: displayTitle=>{ fieldType=>'yesNo', defaultValue=>1, tab=>"display", label=>$i18n->get(174), hoverHelp=>$i18n->get('174 description'), *uiLevel=>5* }, And ultimately from the Asset itself, such as from Article.pm for example: linkTitle=>{ tab=>"properties", fieldType=>'text', defaultValue=>undef, label=>$i18n->get(7), hoverHelp=>$i18n->get('link title description'), uiLevel=>3 }, Sometimes no uiLevel is given. I haven't checked this, but I guess there's a default of zero. Attached is an overview of default-UI-levels that Rogier made for internal use. It's not complete, but it gives you an impression, both of the default UI-levels and the UI-level we use by default. A dash - means it's not defined explicedly in the code. By the way: you say 1-10, but it's 0-9. If you override the UI-level value with something greater than 9, it's never shown, since you cannot assign (via the interface that is) a UI-level greater than 9 to a user. And finally, JT, can you tell me: I have difficulty to see if and how this [the config file changes] influences the ability to hide a standard-asset from the admin tab and show several prototypes that are dirived from it. Kind regards, Arjan Widlak United Knowledge Internet for the public sector www.unitedknowledge.nl Attached Files UI-levels_uitwerking.odt
Back to Top	Rate [ \| ]

WebGUI Dev > Config File Changes

Goto page «Previous Page 1 2 Next Page»

Config File Changes

Recent Discussions Color Key