Creating an Alternative Window for Social Extension

With all the attempts of loading text into a Gwibber Window epically failing, it was time to implement the backup plan my team and I came up with. Instead of using the Gwibber window provided by Gwibber developer Ken VanDine, we will just create and implement our own window that would do pretty much the same thing. The only difference would be that this window will only submit to the user's choice of Twitter or Facebook or both. If we have the time though we could probably implement all of the social networks that Gwibber supports, but for now Facebook and Twitter will have to do. To save us some time with creating a window to use, I found that MonoDevelop has a GUI designer for creating Gtk windows, so last night I spent a few hours messing around with the designer. It splits up the window class into a source code section and designer section. While you are designing the window in the GUI designer, it adds  the code to the source code side. If any action events need to be programmed, you can select an action event on the designer side and it will create a placeholder for it on the source code side. You can then add the code you want inside the event place holder. So far I have been able to create a window to look very similar to the Gwibber window, and it can load a current track and it will send to all the accounts that are configured in my Gwibber account. The next step is to allow the user to select which account they want to send it to, make the text editable and implement a character limit of 140 characters. This could serve to be a little bit of work, but it's doable.