The reason it is not combined into a single column is that a user who does not have HasManageNamespacePermission can still view this page and will still get the first column of information about the file lock. They will not get any buttons though.
I will look at clearing up ambiguities Monday when I implement UnitTest. John Davidson On 10/21/07, Jimmy Sieben <[EMAIL PROTECTED]> wrote: > Nice idea! > > I had 3 thoughts about the admin UI. > > 1) The status label and button captions could be a little clearer IMO. > Rather than "Is Unlocked"/"Is Locked", how about just > "Unlocked"/"Locked"? For the button captions, how about "Lock Topic" and > "Unlock Topic" instead of "Create Lock" and "Remove Lock"? > > 2) It occurred to me that the "File Lock Status" and "Change File Lock" > columns in the table will always be either: > > Is Unlocked | Create Lock or > Is Locked | Remote Lock > > This is really just a single state, so why not combine them into a > single column like this: > > "Locked - [Unlock Topic]" or "Unlocked - [Lock Topic]" > > Where [Unlock Topic] and [Lock Topic] represents a button with the given > caption. > > It's a minor change, but I think it would make the interface a little > cleaner. > > 3) What about a "Lock Topic"/"Unlock Topic" button right there in the > right border if the user has the proper rights. Is that easy to do? It > seems it would be nice to bubble that functionality up rather than > forcing the user to go into the lock management page and hunt down the > topic. > > Thoughts? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John > Davidson > Sent: Saturday, October 20, 2007 8:45 PM > To: FlexWiki Users Mailing List > Subject: [Flexwiki-users] File Locking Implementation > > This is mainly of interest to FlexWiki administrators in that they are > now able to lock individual topics, with only minimal, authorization > settings. The interface details and an explanation of the use of this > new feature are included in my blog at [1]. > > [1]: http://www.flexwiki.com/default.aspx/FlexWiki/JohnDavidsonBlog.html > > Note: that a similar implementation could be done for delete file > and/or delete namespace, if that is deemed desirable. > > John Davidson > > ------------------------------------------------------------------------ > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Flexwiki-users mailing list > Flexwiki-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flexwiki-users > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Flexwiki-users mailing list > Flexwiki-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flexwiki-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
