Hi Vincent,
On Tue, Nov 9, 2010 at 08:50, Vincent Massol <vincent(a)massol.net> wrote:
Hi Raluca,
On Nov 9, 2010, at 8:39 AM, Raluca Stavro wrote:
On Tue, Nov 9, 2010 at 9:05 AM, Vincent Massol
<vincent(a)massol.net>
wrote:
On Nov 9, 2010, at 7:46 AM, Raluca Stavro wrote:
> On Mon, Nov 8, 2010 at 6:27 PM, Ecaterina Moraru (Valica)
> <valicac(a)gmail.com> wrote:
>> On Mon, Nov 8, 2010 at 17:34, Raluca Stavro <raluca.morosan(a)xwiki.com
wrote:
>>>
>>>> Hello,
>>>>
>>>> I am working on
http://jira.xwiki.org/jira/browse/XE-741 and I would
>>>> need a final list of macro and parameter names. These would be the
>>>> current namings:
>>>>
>>>> Macro name:
>>>> * recentactivity
>>>> -> to be replaced with 'activity'
>>>>
>>>
>>> +1
>>>
>>> Parameter names:
>>>> * 'showRss' (boolean: false by default) - Whether to show
activity
>>>> rss links or not.
>>>> -> to be replaced with 'rss'
>>>>
>>>
>>> +1 for false, because the output does not reflect the content of the
>>> activity macro. We will make it default when this is fixed and we also
need
>>> to change the styling and position
for it when we finish to implement
the
>>> filters.
>>>
>>>
>>>> * 'showMinor' (boolean: false by default): - Whether to show
>>>> modifications that create minor versions or not.
>>>> -> to be replaced with 'minor'
>>>>
>>>
>>> from what I know the current implementation doesn't have this case
>>> implemented. Raluca are you gonna implement it? or we remove the
param?
>> It depends on the needs. Does everybody
think that this parameter is
>> needed? I tend to think that we don't need it anymore now that we have
>> so many filters.
>> I would be +1 to remove this parameter.
>
> We definitely need to *not* show minor by default and have the ability
for
users to see them if they need to. This is an important feature we have
and that we need to keep. We need it back before tomorrow to have it in XE
2.6 final as otherwise we'll have a feature regression from the previous
Recent Changes feature.
>
> Raluca why do you say: "I tend to think that we don't need it anymore
now that we have so many filters.". Do we have a filer that can be used to
not show minor modifications?
I was thinking about 'events' parameter.
Users can use this parameter
in order to increase the number of sub-entries to show, so this way
major versions would be displayed at one point. What is not clear for
me is the reason why we have to hide minor versions. Minor versions
could contain important changes, and hiding them by default would cut
part of the information.
The definition of "minor" is that it doesn't appear in any reporting by
default (recent activity, RSS feeds, email notifications, etc). I'll say it
differently; the user checks the "minor" box when he *doesn't want* that
his
change appears in reporting (usually because he's making small changes like
a typo fix).
So if you question this parameter you're questioning the need for the minor
modification feature itself. And I really don't think we should drop that
feature.
So I'd really be against removing this feature (hidden by default, can be
shown if needed) from the Recent Activity report.
Now I'm open to define where that toggle is located and how to activate it.
One issue I currently have with this is that when a comment gets added to a
page, the modification is considered a minor change. With the current Recent
Changes implementation, it means that the page that got the comment is NOT
displayed on the wiki homepage. It looks quite bad during a demo.
So either that needs to be fixed, or I'm in favor of showing minor edits by
default.