On Mon, Dec 20, 2010 at 15:32, Jerome Velociter
<jerome(a)xwiki.com> wrote:
On Thu, Dec 16, 2010 at 8:18 AM, Marius Dumitru
Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Hi Thibaut,
On 12/15/2010 01:34 AM, Thibaut Camberlin wrote:
> Hi,
>
> On Wed, Dec 8, 2010 at 9:22 AM, Marius Dumitru Florea<
> mariusdumitru.florea(a)xwiki.com> wrote:
>
>> On 12/07/2010 03:40 PM, Ecaterina Moraru (Valica) wrote:
>>> On Fri, Dec 3, 2010 at 18:13, Sergiu Dumitriu<sergiu(a)xwiki.com>
wrote:
>>>
>>>> On 12/02/2010 10:21 PM, Vincent Massol wrote:
>>>>>
>>>>> On Dec 2, 2010, at 10:47 AM, Jerome Velociter wrote:
>>>>>
>>>>>> On Thu, Dec 2, 2010 at 8:47 AM, Marius Dumitru Florea
>>>>>> <mariusdumitru.florea(a)xwiki.com> wrote:
>>>>>>> Hi Caty,
>>>>>>>
>>>>>>> On 11/30/2010 10:02 PM, Ecaterina Moraru (Valica) wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>
>>>>>>>> Please provide feedback for this User Status proposal:
>>>>>>>>
>>>>
>>
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserStatusProposal
>>>>>>>
>>>>>>> You used a rich text area in your proposal. Are you planning
to
use
>> the
>>>>>>> WYSIWYG editor for entering the status message?
>>>>>>
>>>>>> If we are going to develop a completion mechanism for references,
it
>>>>>> should be developed in
the WYSIWYG in my opinion, and probably be
>>>>>> available as a standard feature of it.
>>>>>
>>>>> Actually it should also be available in the wiki editor IMO (that
would
>>>> be soooo great :)).
>>>>>
>>>>> The syntax proposed by Caty in the screenshots can be wiki syntax.
It's
>>>> very easy to add a
"user" prefix for links that would be used like
this:
>>>>>
>>>>> [[user:<username>]]
>>>>
>>>>
>>> @Jerome: Sure Jerome, wording is the easiest part.
>>>
>>> @Vincent: It was discussed in the past mails that the Activity will
>>> integrate page, users, application events so that's why is placed
here.
>>> If User Status is disabled, the
Activity Macro will remain unchanged,
>>> otherwise they combine.
>>>
>>
>>> @Marius, @Vincent, @Sergiu: we could have this auto-complete feature
>> inside
>>> Wiki, WYSIWYG. The syntax proposed was inspired by the WYSIWYG and the
>> macro
>>> editing done by Marius. The implementation problems | difficulties
needs
>> to
>>> be discussed with Marius, because I don't know much about WYSIWYG
>>> limitations.
>>
>> Do we need a rich text area for the user status?
>>
>> The WYSIWYG editor can be easily configured to display only the rich
>> text area and its JavaScript API exposes most of the features that are
>> normally available on the tool bar or the menu bar. Integrating the
>> WYSIWYG editor with the user status feature shouldn't pose any
problems.
>> And image/link/macro autocomplete is
definitely something that I'd like
>> to implement for the WYSIWYG editor.
>>
>
> Two remarks concerning autocomplete feature:
> * IMO syntax "[[user:" is too complex for a normal user. Autocomplete
should
be
triggered with pattern without the "[[" meaning only "user:"
> * If WYSIWYG already has the needed API, this is great. My only concern
is
> that using the WYSIWYG does make loading time
longer. Currently, loading
a
> page in WYSIWYG mode takes a significant
amount of time (that is also
why
most of
us prefer wiki mode under some circumstances) that would not be
acceptable for a home page.
This is true. Note that I'm not necessarily for using the WYSIWYG
editor, that's why I asked if we really need a rich text area for the
status. On the other hand, the WYSIWYG editor code is not the only one
that slows down the edit page. In my tests (
http://lists.xwiki.org/pipermail/devs/2010-October/020308.html ) the
editor alone loaded even in 1.3s . SmartClient and some other JavaScript
extensions (some which are not event used in edit mode) add a
significant amount of time. We need to improve the page loading speed.
Getting rid of smartclient would be a first good step towards this.
We need for that to finish and push the work done on a new explorer :
http://incubator.myxwiki.org/xwiki/bin/view/Sandbox/SpaceTree
I think this will be integrated when someone will start working on the
Selective Export feature. And this is planned for the XE3.0.