Squiggle 3.2 has been in Beta for several months now. Issues that were reported are all fixed. There will be no more revisions of Squiggle 3.2. The next version of Squiggle will be 3.3
In case you missed the previous announcement, Squiggle now has git repository. You can fork it and issue pull requests for bug fixes, implementing any of the suggested features or to implement any cool idea you have. This is your chance to mark your name in commit history of Squiggle 3.3. Read More...
Community has shown interest recently in contributing to SharePoint LogViewer therefore I’ve changed the source control to git. This means you can fork the project and issue pull requests now.
Looking forward to your contributions.
Read More...
At Hyves, we wanted to re-write a legacy web application in python Flask. I was in charge of setting up the boiler plate code that would be necessary to get a skeleton app, up and running.
For writing large application it is helpful to separate the concerns in different components and MVC pattern serves that purpose quite well. However Flask is a micro framework and doesn’t give you patterns or APIs to do MVC like application. You have to write all the code to make routing with controllers and actions work. Read More...
Squiggle 3.2 has finally reached the point where I can release it as beta version.
I will not be adding any more features to 3.2 until the final release. From this point onward only bugs will be fixed. I encourage you to download the beta and try out its different features.
Squiggle 3.2 has multiple extensibility points. You can write communication plugin, extension, authentication provider, message filter and message parser. I will blog about each of these in coming days.
You can find a complete list of features on the release page. Give it a try and if you find any bugs please report them on codeplex issue tracker. Read More...
Squiggle 3.2 has major changes in underlying communication layer. It is important that this release is tested longer before declared final therefore I’m announcing today the development release of Squiggle 3.2 to get the early feedback on bugs and issues.
Squiggle communication layer has been re-written to be platform agnostic. You can now write Squiggle client on Android, IOS, Mac and Linux by implementing the protocol using ZeroMQ and Protocol Buffers. You can also write extensions and plugins to add functionality to the client. Following are some of the features added in 3.2: Read More...
As promised the new feature of posting items that you need is now available on LetsDonateStuff.com.
Often people are reluctant in posting the items that they don’t need because they’re not sure if anyone will need them. Also it takes extra motivation to post something before someone actually asks for it. Therefore if there is something missing in your home that you could use second hand from someone who has spare lying around the house, then you can post it here. Read More...
This is just to update you guys about what is going on with Squiggle. Currently I’m working on version 3.2 as I write this. So far I’ve been working on re-writing the core communication components to enable writing of Squiggle client for other platforms easier i.e. Android, Linux, iOS, Mac, etc.
I don’t know if I’ll be adding more features to the actual client so there is no commitment there. However the communication core is going to be scalable and portable. In 3.2 release I also plan on adding extensibility points details of which I’ve not finalized yet. Maybe you’ll be able to download the client and then add voice chat feature or write your plugin to add support for custom applications e.g. games, screen sharing, e.t.c. Read More...
Squiggle used to be in SVN before and anyone who wanted to contribute a fix would have to upload a diff file as a patch. Yesterday I requested CodePlex to change my repository to Git and they were very quick in their response. Today Squiggle has been migrated to Git repository. This means you can now make pull requests and fork squiggle if you want.
For the last two days I’ve been working on adding OpenID support on LetsDonateStuff.com. There has been substantial amount of code change under the hood. For the end user it means they’re going to have a simpler experience for offering items.
Now when you go to offer item page, you have to login with your google, yahoo, etc account. The benefit of this is that you don’t have to specify your email and name multiple times if you offer multiple items. Also you now don’t have to click on the verification link in confirmation email. There is still a confirmation email sent to you on offering an item but it is only for letting you know that your item has been queued and also to give you that special link with which you can remove the offer. Read More...