It’s been a long time coming, but to ensure that you know that we are very active, we thought we dust off the blog and give you a brief update on the state of affairs regarding the project.
Before we do, we want to send out a huge thanks to the community and their support. It’s been great to see the increased twitter and mailing list activity. We love hearing from TideSDK’s users, old and new, and appreciate any feedback to help us make TideSDK more useful and easier to use.
Over the last month, TideSDK has been downloaded over 4,800 times, we’ve doubled our twitter following and have gotten great questions and engagement on our mailing list. We also appreciate those that have dropped by our IRC channel to ask questions or offer support.
(partial snapshot of recent buzz around “tidesdk” via Social Buzz)
Further, we want to thank Software in the Public Interest (SPI) and its board members for taking us under their wings, as you may know by way of our twitter and mailing list updates. From the onset of the project, it has been in the plans to turn TideSDK into a non-profit organization. The reasons are straight forward - we want to ensure TideSDK’s long-term viability and support by enabling the additional support channels that SPI provides.
Through the efforts of our fearless project lead, David Pratt (fairwinds), we were also able to secure our own Stack Overflow tag to help users quickly surface relevant questions and solutions regarding the project. We are trying to address questions as they come up, but hope that the community at-large will be able to chip in with tips, tricks and questions alike.
This brings us to the current state of things and some more juicy bits. Part of the reason the blog got a bit dusty is that our team members have been working feverishly on the next release (v1.3.0) and have been largely limited to 140 character activity aside from the occasional mailing list entry. We are aiming for a release in a couple of days, but here’s how we anticipate the next releases will pan out:
|1.3.0||Completed||• Modern OS Support (Ubuntu 12.x, Lion, Mountain Lion, Windows 8)
• Moving away from legacy code
|1.3.1||Completed||• Proxy fix: For the Windows port of TideSDK, proxy settings (on IE settings) are autodetected by the SDK but are not used properly when executing an HTTP request.|
|1.4.0||In Progress||• Updated language packages (PHP, Python, Ruby)
• Upgraded webkit lib to enable access to latest HTML5, CSS3 and WebGL features
• TideBuilder, a replacement for Titanium Developer, to help you easily set up and package TideSDK projects
The goal is to put out a well tested, stable and up-to-date SDK that will enable you to tap into the advances in the different technologies and help you easily create cross platform apps with the skills you already have.
Beyond the 1.4.0 release we have exciting ideas for TideSDK, some of them involving NodeJS and NPM. You’ll hear more about that as we flesh out the details.
We have a great, global team in place right now, but are always looking for help. If you want to beta test the next release and help us identify bugs, are great at writing tutorials, or have C++ or other language knowledge, we’d be excited to talk to you.
If any company is interested in sponsoring or able/willing to donate any hardware to this non-profit project, please don’t hesitate to contact us at firstname.lastname@example.org.
Lastly, we just want to reiterate some of the ways you can keep in touch with us - we hope to hear from you:
David Pratt (fairwinds) has also posted a more detailed update on the mailing list, make sure to check it out and comment if you want additional information.
Thanks, TideSDK Team