18 Jul
2014
18 Jul
'14
7:24 p.m.
Hi,
2014-07-18 18:47 GMT+02:00 Eduard Moraru <enygma2002(a)gmail.com>om>:
Hi Jeremie,
On Fri, Jul 18, 2014 at 5:58 PM, Jeremie BOUSQUET <
jeremie.bousquet(a)gmail.com> wrote:
you`d
to
I agree with you for livetable view, but I was trying to find more than 2
alternatives ;-)
There is no specific use-case for a "timeline" view in this case, except
that a timeline can be pretty, and fun (for the user, not so much for the
devs ...).
It would be, obviously, a pure UI gadget, and an UI customization
alternative for your dashboards for example.
Hello,
2014-07-18 16:32 GMT+02:00 Eduard Moraru <enygma2002(a)gmail.com>om>:
problems
Hi devs,
As part of the investigation on the Activity Stream Refactoring for the
6.2
> roadmap, I have written a couple of documents [1] on some of the
(specifically performance [2]) of the current implementation and also
tried
> to list various use cases [3] that a better AS implementation should
> support.
>
> I would like to ask you to:
> - help out in listing possible use cases [3] that I have missed or like AS
to support,
One use-case I thought about, but it's really nice-to-have IMO, could be allow choosing a specific "display" (or
"theme", or "displayer" ...) for
the macro results.
Possible displays or themes could be:
- default (the current one)
- livetable
- timeline ...
Obviously, granularity of details could not be the same depending on the
chosen theme, but it would be ok if maximum details are show in the
"default" (current) view.
And you could provide custom ones if needed.
It's maybe overkill, compared to duplicating the macro to an as_timeline
or
as_livetable macro ...
Interesting as a nice-to-have feature.
Do you have any particular actual use case for such a feature in mind? What
would be the benefit of displaying the events in a different view? I find
the livetable view not very useful.
Also, having a custom display would basically mean rewriting the macro
completely, since the macro is 95% UI. Perhaps the only functionality that
you would reuse would be indeed the filtering (through macro parameters),
though that too would be fairly easy to replicate.
The only use-case I can see for keeping 1 macro, maybe, would be that you
could easily customize it (when included in a dashboard for example), by
just editing it inline and choosing a different value for the "theme"
parameter.
It's slightly more user-friendly than having to include another macro. In
fact it would be easier in wiki mode than in wysiwyg in this case.
But, to start with, providing an alternate macro for a timeline view could
do the trick.[OFF] I have some hopes to provide a simile timeline extension
some day ... but still never found time to do it.[/OFF]
Thanks for the quick reply so far. Keep them coming! :)
-Eduard
http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62
http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62…
http://design.xwiki.org/xwiki/bin/view/Proposal/AcitvityStreamRefactoring62…
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
- offer
your opinion on my current findings [1] and/or
- share your thoughts on where should we go with the new implementation
of
AS.
Thanks,
Eduard
----------
[1]
[2]
[3]
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs