23 Mar
2009
23 Mar
'09
11:05 a.m.
On Mar 23, 2009, at 10:14 AM, Marius Dumitru Florea wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Ludovic Dubost wrote:
Regarding categories I'm not sure this should go in the rendering
module. I don't think it's the role of each macro to say in which
category it is. It's more a user thing, i.e. it's the code using
macros that should probably decide of categories. I'm not fully sure
of this but I think categories depend really on the use case and
should not be fixed and thus should be decided/set by the user of
macros. The user could be the wysiwyg editor itself for now or it
could be some other UI module (not sure which).
Since I'm not sure I'd like to know what others think.
Thanks
-Vincent
Vincent Massol a écrit :
For me it is to access the list of macros by a library first (with a
nice description)
In JV's mockups macros are grouped by category. See
http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HMacros
. I need a way to retrieve macros by category/library. On Mar 23, 2009, at 12:29 AM, Ludovic Dubost
wrote:
I can work on the Excel plugin. I just need to be told what to
change.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could
you
be more specific to see if it matches what Marius is working on?
Then it is
listing the available macros with a nice description.
I have the description. Now it is used as a tool tip for the macro
title
in the Edit Macro dialog. I know, it's hidden.
Then it is editing the parameters with a nice
description for each
parameter and eventually some types params (lists, etc..) and
controls
I have the parameter description and type. I don't have the list of
allowed values and the default value. The description is used as a
tool
tip for the input control (again, it's hidden). The type is used to
choose the input control. Currently I have this mapping:
boolean/java.lang.Boolean -> BooleanInput (a combo box with three
options: yes, no, unspecified)
java.lang.String -> TextInput
What other controls would you like to have Ludovic?
Regarding the library/macro/parameter description we need to update
the
UI design to take it into account. Maybe an information icon (like it
used to be in Curriki) near the library/macro/parameter would do. JV?
Thanks,
Marius
Re "macro libraries" not sure what this
is about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Yes it is having a section on the admin that lists the available
libraries and have a easy way to add a new one (it can be standard
XAR
import).
We should eventually be able to deactivate some libraries.
It should list libraries provided by the Wiki, by the XEM instance
and
natively (macros.vm or rendering macros)
Ludovic
Thanks
-Vincent
Also concerning 1.8.1 there are a few
features/bug fixes that we
need to
include as Curriki is depending on it and it won't be possible to
wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in
the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two
> reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be
> said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from
> 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9
> final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start
> the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to
> time
> but we'll advise people to switch to 2.x. I propose we keep
> support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the
> automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist
> putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/
> management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/
> Guillaume
> * Continue UI improvements (ex: new treeview, new search
> interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a
> new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs