Skip to main content

TweetAwesome - A Twitter client developed in Silverlight

(GEEK ALERT : This post is for those who are interested in Microsoft Technologies, especially Silverlight).

A while ago I thought of developing my own Twitter client just for fun. And what better way to write it in than Silverlight. Because of the cross-domain policy restriction in Silverlight, I had to write a WCF service which carried the tweets payload. I decided to call this app TweetAwesome - a homage to my awesomeness and humility. :)

TweetAwesome uses TwitterVB as its Twitter API library and wears the Metro Theme for Silverlight. The application is also styled using Expression Blend (although I still don't fully know how to use it). As I don't have the infrastructure/money/time to host a WCF service, this app is just for enthusiasts. Here are some snapshots (sneak preview) of the application. (Click on the pictures to launch a full screen slideshow)
.

1. When TweetAwesome is used for the first time, the user is asked to allow TweetAwesome to access Twitter on its behalf


2. User signs in to Twitter and allows access, getting a PIN in return.


3. User enters the PIN in TweetAwesome and validates it.


4. User's timeline is being retrieved.


5. User's Timeline


6. User's Mentions


7. New Tweet Window


8. Reply Window


9. Retweet Window

This application is still under development and my plan is to add a host of features into it like URL shortening integration, Photo sharing integration. I will be posting the source code of this application soon. So keep any eye on the Downloads section.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Use AI to build your house!

When a new housing society emerges, residents inevitably create chat groups to connect and share information using various chat apps like WhatsApp and Telegram. In India, Telegram seems to be the favorite as it provides generous group limits, admin tools, among other features. These virtual communities become treasure troves of invaluable insights. But whatever app you use, there is always a problem of finding the right information at right time. Sure, the apps have a "Search" button, but they are pretty much limited to keyword search and are useless when you have to search through thousands of messages. I found myself in this situation when it was my turn to start on an interior design project for my home. Despite being part of a vibrant Telegram group, where countless residents had shared their experiences with various interior designers and companies, I struggled to unearth the pearls of wisdom buried within the chat's depths. I remembered that I could take advantage o

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con