Uploaded image for project: 'Rave'
  1. Rave
  2. RAVE-831

Create awareness for IWC on workspace

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.18
    • Fix Version/s: None
    • Component/s: rave-portal
    • Labels:
      None

      Description

      Evaluation has indicated that the inter widget communication going on in the background is not noted by users.

      One possible solution would be to flash the frame of the receiving widgets in some color.
      Another option is to have some small icon flying from sender to receiver. The latter one should only occur for user-triggered IWC, however due to possible animation overload.

      1. rave-0-22.patch
        282 kB
        Olexiy Chudnovskyy
      2. screenshot.png
        92 kB
        Olexiy Chudnovskyy
      3. vsr-contacts.wgt
        50 kB
        Olexiy Chudnovskyy
      4. vsr-studentprojects.wgt
        49 kB
        Olexiy Chudnovskyy
      5. wookie-0-13-1.patch
        165 kB
        Olexiy Chudnovskyy

        Issue Links

          Activity

          Hide
          geerzo Chris Geer added a comment -

          IWC should be in the background. It would be up to the individual module designers to notify a user when it received a message.

          Show
          geerzo Chris Geer added a comment - IWC should be in the background. It would be up to the individual module designers to notify a user when it received a message.
          Hide
          calexey Olexiy Chudnovskyy added a comment -

          Hi, everyone,

          if someone is still interested in this issue, the OMELETTE research project [1] brought up several ideas on this problem. E.g., our research group [2] developed a mechanism to display and control IWC in a page [3]. For this purpose, the config.xml file of widgets is extended with descriptions of their publications and subscriptions. Possible message flows are then visualized with arrows. Furthermore, users can either block a single flow or completely isolate a widget (see screenshot).
          To use these features, one needs to extend both Wookie (0.13.1) and Rave (0.22) using the attached patches.

          Any feedback or comments are welcome!

          [1] http://www.ict-omelette.eu/home
          [2] http://vsr.informatik.tu-chemnitz.de/
          [3] http://vsr.informatik.tu-chemnitz.de/demo/iwc-control/

          Best Regards,
          Olexiy Chudnovskyy

          Show
          calexey Olexiy Chudnovskyy added a comment - Hi, everyone, if someone is still interested in this issue, the OMELETTE research project [1] brought up several ideas on this problem. E.g., our research group [2] developed a mechanism to display and control IWC in a page [3] . For this purpose, the config.xml file of widgets is extended with descriptions of their publications and subscriptions. Possible message flows are then visualized with arrows. Furthermore, users can either block a single flow or completely isolate a widget (see screenshot). To use these features, one needs to extend both Wookie (0.13.1) and Rave (0.22) using the attached patches. Any feedback or comments are welcome! [1] http://www.ict-omelette.eu/home [2] http://vsr.informatik.tu-chemnitz.de/ [3] http://vsr.informatik.tu-chemnitz.de/demo/iwc-control/ Best Regards, Olexiy Chudnovskyy
          Hide
          scottbw Scott Wilson added a comment -

          Thanks for this Olexiy, Can you create a corresponding issue in Wookie connected to this one, with the Wookie patch attached?

          In response to Chris's comment - user testing indicates that awareness of IWC is a problem for users.

          This is particularly of concern where the use of some widgets has additional consequences, such as widgets that communicate with enterprise systems, that incur a cost through use (such as SMS) or that initiate sharing outside of the portal (such as FB & Twitter widgets). However there is also a general usability issue in that users often don't know when one widget has updated the content of another.

          However, it should be up to the portal site owner whether to enable IWC highlighting.

          Show
          scottbw Scott Wilson added a comment - Thanks for this Olexiy, Can you create a corresponding issue in Wookie connected to this one, with the Wookie patch attached? In response to Chris's comment - user testing indicates that awareness of IWC is a problem for users. This is particularly of concern where the use of some widgets has additional consequences, such as widgets that communicate with enterprise systems, that incur a cost through use (such as SMS) or that initiate sharing outside of the portal (such as FB & Twitter widgets). However there is also a general usability issue in that users often don't know when one widget has updated the content of another. However, it should be up to the portal site owner whether to enable IWC highlighting.

            People

            • Assignee:
              Unassigned
              Reporter:
              javafrog Matthias Niederhausen
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development