On 1/5/07, Vincent Massol <[email protected]> wrote:

First I want to say that I'm a little bit worried that we're doing this one or 2 days away from the beta 2 release. But Sergiu if you're committing to have it work flawlessly for before Monday I'm fine… ;-)

Now back to your proposal:

· Create page/blog/space/etc. Are you talking about the Create Panel or something else?

There will be in the future (b3) a "create" menu, replacing the create panel. Almost all desktop applications have a "New" entry in the menu. · +1 for the edit menu with no submenu

· Show: Do we need "attributes"? I would be for removing it.

It's not implemented yet, but I guess it should be visible only for advanced users. Simple users are interested in the content. · +1 for choosing the Simple or Advanced view setting in the user

profile. When the user registers, he'll specify what kind of user he is and then he can change it later by editing his profile.

Registration time = an option in the "Register" form?

· In simple mode the default editor should be the WYSIWYG editor. I guess this will override the default editor settings in the preferences.

The default editor will be either WYSIWYG or Inline (form edit), according to the page content. However, if the page contains advanced content (scripting), the wiki editor will be displayed, with an alert message warning that the page contains advanced content. · The rest is fine with me

Thanks

-Vincent

*From:* Sergiu Dumitriu [mailto:[email protected]] *Sent:* vendredi 5 janvier 2007 12:55 *To:* [email protected] *Subject:* [xwiki-dev] [vote] Menu for simple users

Hi all,

As http://jira.xwiki.org/jira/browse/XWIKI-562 says, the Beta2 will have two types of users, beginners and advanced. The difference is in the possible actions that the user has access to directly from the interface (all the functions can still be accessed from the right URL). We must decide which are these actions.

Here is my proposal: - create: - page - blog entry - space - edit: just the top button (no submenu) with the default editor. It will be possible to switch between the 3 available tabs: WYSIWYG, wiki and page access rights.

- show - comments - attachments - history - attributes (no code)

- print - pdf - preview

- delete - admins only

Switching to the "advanced" status: in the user profile (still looking for a better solution).

Waiting for your opinions.

Sergiu

-- You receive this message as a subscriber of the [email protected] list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Hi, This looks nice.. We are already using JTidy for the HTML -> XHTML conversion before we export to PDF. A good way to do this is indeed as an XWiki plugin. I would suggest 2 plugins: 1/ Importer It would be great if the importer have a generic part and a format specific part. We could use the base code as the code to import from other wiki formats. There is one case which is complex in importing is when you want to handle links. You might need to read multiple files to convert links from one format to another. For example if you have a set of HTML files with relative links you might want to convert them to wiki links. An importer framework which allows to handle this would be great. 2/ Validator/Cleaner It would be great to be able to use each part separately and have some options when calling it. Besides cross side scripting being able to allow/refuse tag lists would be great and also allow/refuse velocity and groovy I guess Vincent would like to see the plugin outside of the core, but I'll leave this to him. Ludovic Mac a écrit :

Hey there, I was thinking about building a XWiki plugin that will import (dynamically) another website, either whole or partial (A little XML parsing of it), besides reading the one page Plugin Doc Is there any thing else that I could use to help me speed up this development? Like XML parser/HtmlTidy or something that XWiki may already uses?

Also, While I am on this topic of html, since the Wiki will take Html/xml in the normal editing of the page. I would be willing to write a Validator that would strip out dangerious html (Cross site scripting,...) I have already done this in a filter for a "Sudo wiki" I was building from scratch, but would be willing to re-write it in a way that would be helpful to the project, if someone could point me in the right direction where this type of Class would fit in to the project.

Thanks,

Cant wait to see beta 2

------------------------------------------------------------------------

-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

-- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic