Hi Sergiu, Guillaume, devs, Guillaume Lerouge wrote: I've had some problems here when I forgot to add users' rights to some documents that must have restricted access. Would it make sense to add some kind of information to the footer warning about the fact that a given document is freely readable or this or that right has been granted to a given group or a number of users? Thanks.

Hi Sergiu, On 5/31/09, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: Sounds good. Looks good to me. Could we see it live on incubator to provide additional feedback? I'd like to see the tag edition mechanism you're proposing in action to provide more feedback.

Vincent Massol wrote: I don't think this is a good idea. I've never seen any application giving tags more importance than the content itself (and considering that until recently tags were not displayed at all, putting them in the footer is already a big improvement).

You mean the "Show" menu?

Yes, that's what I meant. Hm, interesting you asked this. Actually this change was a step towards a larger reorganization of the UI, with the final goal of eliminating the edit mode completely. But more on this later. Yes, this means that the rights edit mode will be removed from the Edit menu and the edit mode panel. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Hello, see below Vincent Massol wrote: I like the proposal, it looks good / feels right. Of course we'll have more things to comment after we'll see it working and use it, so go for it! +1 Actually, does a user need / want to see the tags? or they're just a way to make machines understand what a document is about, with little effort from humans (which create the content) and little effort from machines which don't need to NLP content. I think a human user would rather know what a document is about from the title and first few lines. I don't think I would look for the tags if I had the actual content in front of my eyes. Maybe after reading, indeed.

Happy coding, Anca > >>> If not, then I think we should add a "View/Edit tags" entry in the >>> action menu, same as what we have for comments, attachments, etc >> You mean the "Show" menu? > > yes > >>>> 2. The "Created by ... on ..." information about the document will >>>> be >>>> displayed before "Last modified by...", under the document >>>> content, >>>> and >>>> not down in the page footer, where it seems ambiguous (seems to be >>>> referring to the whole wiki), nor in the Information tab. >>> +1 >>> >>>> 3. The "Information" tab becomes "Related documents", since it >>>> does >>>> not >>>> contain the tags and the creator anymore. The related documents >>>> are: >>>> * parent (editable in view mode by the same mechanism as the >>>> tags) >>>> * children >>>> * included documents >>>> * links and backlinks >>> +1 >>> >>>> 4. A new "Rights" tab is displayed for admins after "Related >>>> pages", >>>> basically providing the rights management UI. >>> +1 although I don't think it's just for admins. It should be to >>> anyone >>> having the rights to change the rights (ie edit rights). However it >>> should probably not be displayed in simple mode (only in advanced >>> mode). >> Yes, that's what I meant. >> >>> Does it mean anything for the edit panel? Does it mean edit mode >>> will >>> be only for editing the content, objects and class? Do we keep >>> both? >>> (same question for the history and tags/parent). >> Hm, interesting you asked this. Actually this change was a step >> towards >> a larger reorganization of the UI, with the final goal of >> eliminating >> the edit mode completely. But more on this later. >> >> Yes, this means that the rights edit mode will be removed from the >> Edit >> menu and the edit mode panel. >> -- >> Sergiu Dumitriu >> http://purl.org/net/sergiu/ > > Thanks > -Vincent

Hi Sergiu, On Tue, Jun 2, 2009 at 7:27 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: Sound exciting :-) I'm eager to learn more about this one. Btw, you might want to talk about it with JV since he worked on ideas to merge the inline + edit mode. I guess what you have in mind is an AJAXy edit-in-place where one or multiple editors show up instead of the textarea + input fields on a given page while the panels stay where they are... If we have a default template it would work with objects too.

Wonder what happens to XClass edition and used yet not-exposed XObject properties in such a scenario though... Food for thought for later I guess.