On Wed, Dec 1, 2010 at 01:46, Thibaut DEVERAUX
<[email protected]>wrote:

> I love this feature !
>
> *Stage wisper, a bit of inspiration for further developments *:
>
> Will it be possible to use thoose streams as a global wiki's news stream ?
> Including comments, followed page modifications, goup exchanges, etc. Like
> in Buddypress for example.
> http://design-keys.org/activity/
> http://buddypress.org/community/activity/
>

Hi Thibaut,

Thanks for your message.
This User Status proposal is meant to be integrated with the existing
Activity Macro
http://extensions.xwiki.org/xwiki/bin/view/Extension/Activity+Macro
"The Activity Macro listens to the following: create, edit, delete events
for pages, comments, attachments and annotations."



> *
> *Going further, a few time ago during UX workshops we imagined an "all is
> manageable within the timeline" way of having regular user interacting with
> content.
> The use case is simple : it is to be used when the user want to see what is
> new today on the network and to comment the new content
> - see what new today on the timeline
> - interact with content staying into the timeline
> - continue reading what's new today on the timeline
> Here is the document :
> http://www.slideshare.net/thibautdeveraux/design-platform-v2-proposition ,
> going to "l'atelier" (in french sorry, it is a long time I'm supposed to
> make an english version of this concept with enhanced graphics for sharing,
> always need more time ^^)
> The limit of such system is the javascript amount a page can handle before
> becoming to slow. Yet it may give some inspiration.
>
> *
> About the UX of the proposition* :
>
> I like it, it sounds good as it is keeped simple.
>
> Maybe a few questions about details :
>
> 1/
> Is it necessary to add the yesterday, today, title between posts ?
> http://screencast.com/t/RJsu44z7bUSG
> There is already a "posted xx time ago" and the most immediatly usefull for
> the user may be more the last post he have read before than the day it was
> posted.
>

The information spawn over all the history and with
http://jira.xwiki.org/jira/browse/XE-748
we will be able to browse continuously through time.
Having Today, Yesterday,  dd MM is the best solution to separate content.
See http://incubator.myxwiki.org/xwiki/bin/view/Main/


>
> 2/
> Is there a special reason to have changed the order of the "send, privacy,
> references" icones that are used left to right on facebook, to right to
> left
> here ?
> Here : http://screencast.com/t/dhpNDfZ1
> Facebook : http://screencast.com/t/Gk2BhGld3
> There is no shame to use the same configuration. ^_^' Being like ergonomics
> users are used to is a good thing.
>

XWiki has the Vertical forms standard so it's normal to have the button
placed in the left, see
http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormVerticalUsage


>
> 3/
> Why is there "140" printed on the top right corner ?
> http://screencast.com/t/gOjv4WGe5VVQ
> Is it because messages are limited to 140 caracters ? I don't really
> understand why there should be such a limitation on wikis that can be used
> for project management, where people may have important things to share and
> explain ? Also, having text only small boxes is already limitating lengh of
> 90% of the messages people naturally enter.
>

This can be changed or remove.


>
> 4/
> Why is it always printed "changed status" ?
> http://screencast.com/t/cBqylv4X
> Is status notion is a concept that fit with all the use case of this
> feature
> ? For example what if people are not be thinking they are updating a
> status,
> yet are thinking they are sharing a message with the community ?
> Also, the act of seeing a small text right near an other user portrait let
> people know this is a message from this persone. This may be enough
> information, why specifing ?
> The only reason I see for specifing it, is when there is an usage for it.
> For example if this is a link to a specific context zone of the wiki where
> the action took place. it may be a groupe or the user profile.
>

Being part of the Activity Stream we need to have a separation between
actions, see
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ActivityStreamV31


>
> 5/
> About the way items are displayed in a page creation case :
> http://screencast.com/t/ue1Ogbd5gf
> Why changing the order of message items between a user message case and a
> page creation case ?
> http://screencast.com/t/oDJij00HEN
> I would let's the user read the flow in the same way for each item. Eye
> habits.
> Example : http://screencast.com/t/nxWatyS9g
>
>
The Activity Stream is page centric and this layout allow multiple entries
for a page location, see
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ActivityStreamV31/pageExpanded.png



> 6/
> Why adding again the information about the message type near the portrait ?
> It is already in text and, anyway, I'm not sure the user need it at all.
> http://screencast.com/t/9UdhOgB4uR7j
> http://screencast.com/t/ACMMR0S15Q
>
>
Icons are more representative than words. It's much more easy to scan for
icons than to read the text. That's why the message is duplicated: in order
to assure fast scanning but keep the accessibility and learnability.


>
> Here is a proposal that may be simpler. Of course it depends on the answers
> to my question because I can't know evrything about the specifications :
> http://screencast.com/t/DNq3MVwLU
>
> Have a nice day
>
> Thibaut DEVERAUX
> Tel : +33 (0)6 75 51 20 80
> [email protected]
> http://design-keys.org
> [email protected]
> http://bricks-studio.com
>
>
>
> 2010/11/30 Ecaterina Moraru (Valica) <[email protected]>
>
> > Hi,
> >
> > Please provide feedback for this User Status proposal:
> >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserStatusProposal
> >
> > Other references:
> > * Proposal Code:
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserStatusPrototype
> > * Mail [Investigation] User Statuses:
> > http://markmail.org/thread/65j5pc2ymmntujt3
> >
> > Thanks,
> > Caty
> > _______________________________________________
> > devs mailing list
> > [email protected]
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to