wirthaware / reactivehub Goto Github PK

This issue is to replace the API token/secret that is currently used by a combination which is specific to the ReactiveHUB.

As a user I want to be notified of a new message by sound effect.

• Sound effect can be turned on and off
• If multiple lists are already implemented, sound effects can be toggled per list

https://api.slack.com/

As a user I want to add more than one account per service, so I can maintain multiple identities with the same interface.

This includes:

• Showing which account received a message
• Choosing which account(s) should send/interact with a message

If the message source supports replying to a message, a reply function becomes available for the message
The button should be to the lower right of the message.
Borders currently indicate the rough position of the interaction buttons.

• Display the avatar of the sender of the message if possible
• If no avatar exists or the source does not support avatars, display a placeholder image
• The avatar is displayed in the rectangle which is to the left of the message

Share a message using the "Post"-Functionality provided by the message hub.
This way a message received on Twitter can be shared on Facebook and Google+.

The function should be in a menu containing advanced interaction options.
This menu should be accessible from the last button in the interaction area which is located at the bottom right corner of a message.

Share a message using the sharing functionality which is provided by the message source
The share button should be to the lower right of the message.
Borders currently indicate the rough position of the interaction buttons.

The bindings in the MessageListItem are made by standard WPF techniques.
They need to be corrected, so they use the ReactiveUI-Mechanism for bindings.

And everywhere where the service is displayed like settings, etc.

Like items for sources that support liking / favouriting, etc.
The button should be to the lower right of the message.
Borders currently indicate the rough position of the interaction buttons.

Block messages based on:

• Sender
• Keyword (e.g. Hashtag for Twitter)

(I know this title is confusing - I couldn't find a good one)

• Ability to create more than one list
• Rules can be specified to determine in which list a message is displayed

Examples:

• List A contains all messages with the Keyword "Blah"
• List B contains all messages sent from one of the following users {...}
• List C contains all messages not covered by previous rules.

Interesting, because Instagram is a stream of pictures instead of messages
(it could also be viewed as more than one stream since comments on a picture can be viewed as stream of messages too)

This Icon can be used for the official registered Twitter and Facebook apps

• Add Twitter library from ZCamp to project and refactor it
• Create Twitter-API access token
• Provide a way to read the dummy users timeline with automatic updates

Sources are no longer hard wired into the application, but loaded dynamically by discovering all available sources in the application folder. (using something like MEF)

Right now the messages are listed in the order they arrive (oldest first).
The most intuitive display method would be to display the messages in the order of their timestamps, most recent first.

A unified UI for sending messages and choosing where to send them to

Routing in ReactiveUI is not yet well documented and even the sample does not navigate between different views.

The first shot of the core UI should be a merged list of all received messages from all sources.

• Provide a way to configure parameters of the plugin like Username/Password.
  • The plugin specifies the settings it needs
  • The plugin specifies how the application should get the settings from the user
• Persist the configuration for each plugin
• Reload the configuration on startup