captain-steel / gitterclient

Windows Phone client for Gitter

GitterClient |

AppVeyor

Travis CI

This project is using :

• Windows Phone 8.1 (Store Apps)
• Web Authentication Broker
• MVVM Light
• Refit
• Splat
• Json.NET
• Reactive Extensions
• RectiveUI

DONE

• Getting the Authorization key
• Exchanging the Authorization key with the server to get the Token
• Getting the list of rooms
• Diplaying the rooms list
• Store the Token in the IsolatedStorage
• Created a UI to view the messages
• Send a message inside a room

TODO

• Disconnect user & revoke permissions

gitterclient's Issues

Send a message to a Room

Use Refit to create the appropriate method
See [Messages API(]https://developer.gitter.im/docs/messages-resource)

Open a Room (Channel) and see messages

Create a UI to enter in a Room (Channel) a see the message.
Use the Streaming API

Fix build errors on Travis CI

/home/travis/build/captain-steel/GitterClient/GitterClient/GitterClient.csproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WindowsXaml/v12.0/Microsoft.Windows.UI.Xaml.CSharp.targets, to import. Ignoring.
Project "/home/travis/build/captain-steel/GitterClient/GitterClient.sln" (default target(s)):
Target ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Target Build:
/home/travis/build/captain-steel/GitterClient/GitterClient/GitterClient.csproj: error : /home/travis/build/captain-steel/GitterClient/GitterClient/GitterClient.csproj: /home/travis/build/captain-steel/GitterClient/GitterClient/GitterClient.csproj could not import "$(MSBuildExtensionsPath)\Microsoft\WindowsXaml\v$(VisualStudioVersion)\Microsoft.Windows.UI.Xaml.CSharp.targets"
Task "MSBuild" execution -- FAILED
Done building target "Build" in project "/home/travis/build/captain-steel/GitterClient/GitterClient.sln".-- FAILED
Done building project "/home/travis/build/captain-steel/GitterClient/GitterClient.sln".-- FAILED

Build FAILED.

Don't use a ViewModel for AuthenticationPage

Resolve a bug when not using a ViewModel with the AuthenticationPage.
Actualy it works by clicking on a button 'Connect' which triggers a RelayCommand