- http://builds.appcelerator.com.s3.amazonaws.com/mobile/master/mobilesdk-1.8.0-20110513115704-win32.zip is the latest for windows at this moment. To install, just unzip it inside your Titanium SDK folder (this should be, in Windows, %ProgramData%\Titanium – in my case, this translates to C:\ProgramData\Titanium); The ZIP already has the required folder structure (mobilesdk\win32\[version]\etc..), so just unzip it there and everything will be fine.

If you are already using Titanium Studio, use the “Help” -> “Install Titanium SDK from URL” and paste the full URL to the ZIP file you have selected from the nightly builds. I prefer the method above, as this option, sometimes, doesn’t unzip the full contents of the updated SDK.

Appcelerator has made no official announcement on 1.8.0, so I have no idea what is new, but keep in mind: this is a beta release, and should not be used in production apps.

Here is the uploaded javascript header file, updated for Appcelerator’s Titanium Mobile version 1.5.1. This can be used with Eclipse+Aptana’s autocomplete, using the method described by James David Low a while back.

I haven’t tried it yet, I’m using notepad++ still, but I’ll give it a go ASAP!

More in ADT Magazine

Original post from Appcelerator’s developer blog:

Tonight, we pushed the latest 1.3 update to distribution servers. You should be getting an update notification inside Titanium Developer if you haven’t already. It’s been a little over 4 weeks since our last release. We had promised to get out 1.3 before the end of May and we’re a little earlier than expected.

The 1.3 release included over 120+ fixes for both Android and iPhone/iPad. The Android team won the most bug fixes in this release clocking in 63 bug fixes to iPhone’s 61. Go Android! For a full list of all the changes, please see the Change Log. Great job to Don, Bill and Marshall for all the hard work on Android. We still have a ways to go to where we want with Android but we’re iterating quickly now. We also have some very exciting Android features coming soon.

This release does have one major notable item worth talking about here (we detailed more of the specifics in the Change Log). With 1.3 and iPhone/iPad, we now are generating full source as part of the XCode project created at project setup. This change provides several benefits in terms of ensuring that we’re in continued compliance with Apple’s Terms of Service, making it easier for debugging or environmental issues we sometimes run into and making it easier to export a project to another machine (useful for agency/development partners).

The updated the Kitchen Sink distribution for 1.3 and it can be downloaded either from github or in a zip distribution. For 1.3, we’ve also started a basic Kitchen Sink for iPad.

What’s next?

As soon as we finish one release, we’ve already begun the next – in some cases before the final release is out the door. The next release is expected to be 1.4 and should be released to the community in June. For 1.4, we’ll continue to focus primarily on maintenance issues, API parity for Android and full API support for the upcoming iPhone 4.0 OS.

We’ll be pushing the first drop for the Blackberry SDK very soon now that 1.3 is out the door. Blackberry work has been progressing in parallel and we hope to release it within the next couple of weeks to Professional/Enterprise subscribers and Partners. We anticipate the full community release of Blackberry will be late Summer. If you’re not currently a subscription customer and would like to get access to Blackberry, please signup here.

Developer Site Updates

We’re making a number of major improvements to the Developer website and hope to release them in waves over the next month. Besides a number of nagging issues/bugs that have been reported, we’re also improving site search, introducing a new forum-based discussions and rolling out a new help desk for subscription customers.

Desktop Plans

Many have asked why Mobile releases faster than Desktop. This is a good question and let me address it. Desktop has been a slightly more mature product and has been adopted by some rather very large companies (as long as a ton of projects from tiny to large). We’re continuing to make substantial investments in Desktop and will be having a big update in the summer for Desktop.

Module SDK

Quite a number of developers have used the current iPhone Module SDK to extend Titanium. In 1.4, we’re planning on introducing the new Android Module SDK. We’re also hard at work on a new product we’re calling Marketplace that relates to modules for mobile, tablet and desktop. If you’re interested in extending Titanium with your own unique stuff, please let us know.

Tooling

We have some new significant updates to the Titanium tooling in the works – including debugger support. Expect a refresh of the current tooling with massive improvements in the early Summer timeframe.

Improved Documentation

We continue with each release to improve the API reference documentation. However, we know we’ve got a long way to go to better documentation. We’ve been working with a professional training company to produce our first set of programming guides and I’m pleased to say that we’ve almost finished the first new Getting Started Guide. The guide will be much more comprehensive and will be the first of many new Guides we’ll be producing over the next few months.

Training

We’re very close to launching a new comprehensive, professionally produced AppU video training series. Our plan is to release new video content every month much like we do software. The training will include not only on-demand video based courseware, but also guides and sample code. Stay tuned for more updates.

Community Growth

The last 4 months have been a whirlwind for the Appcelerator team and we’re very proud of our accomplishments and all of the great applications that are being built from all over the world. Nothing makes us more happy than to hear about all the cool applications that you’re building every day. Thank you for sharing them with us.

With all of this growth, comes challenges that we’re trying to meet. In the past 4 weeks, we’ve had numerous website outages as we hurried to upgrade our Amazon AWS infrastructure to handle the growth. We think we’re now ready for the next wave of growth from a infrastructure standpoint. We’ve also found more places where we could add high-availability and load-balancing as well as invested in better monitoring tools.

We’ve also welcomed four new developers to the Appcelerator team in the past 2 weeks – all of which came directly from our community and who are passionate about what we’re trying to accomplish. With this we hope to be able to continue to accelerate development and make Titanium the best product available.

Thank you so much for your support, your passion and your patience as we continue on our journey together.

Codestrong!
Jeff

Yes, not surprisingly, Novell’s MonoTouch is now supporting the iPad. Not a surprise, as they already supported the iPhone, and iPad is just an iPhone with a bigger screen. This means you can use your C# skills to create applications to for the whole iSomething ecosystem, without having to learn Objective-C or even ActionScript (the upcoming Flash CS5 will have a cross-compiler that targets the iPhone+iPad).

MonoTouch supports many of the iPhad gadgetry, including GPS and accelerometer, as well as bindings to the address book. The User Interface is built using the Apple’s Interface Builder, that ships with the iPhone SDK – this means that you also have all the controls native to the iPhone available for you app, including Pickers, Sliders, Buttons, etc, etc – the downside is: you can’t just recompile your Silverlight/WPF/Winforms .net application… you have to write the UI from scratch, which is not a big problem if you have logic and presentation truly separated. Also, the applications are statically compiled, instead of being compiled on demand by a JIT compiler inside the CLR – as a result of this some limitations, such as limited Generics support and no dynamic code generation, are present – more on this at http://monotouch.net/Documentation/Limitations

But, as with all things Apple-related, there’s a catch: None of this is free – to deploy your app you need to pay Apple; MonoTouch is not OpenSource, its a commercial product, prices start at $399. Also, you need to buy an Apple Mac Intel computer (10.5 or 10.6) to develop your applications.

Bryan Costanich wrote a nice introduction article about MonoTouch at InfoQ – read it here.

 The communication, available in Apple’s hotnews section (search for “Third party applications on the iPhone”) is the following:

“Let me just say it: We want native third party applications on the iPhone, and we plan to have an SDK in developers’ hands in February. We are excited about creating a vibrant third party developer community around the iPhone and enabling hundreds of new applications for our users. With our revolutionary multi-touch interface, powerful hardware and advanced software architecture, we believe we have created the best mobile platform ever for developers.

It will take until February to release an SDK because we’re trying to do two diametrically opposed things at once—provide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task. Some claim that viruses and malware are not a problem on mobile phones—this is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target.

Some companies are already taking action. Nokia, for example, is not allowing any applications to be loaded onto some of their newest phones unless they have a digital signature that can be traced back to a known developer. While this makes such a phone less than “totally open,” we believe it is a step in the right direction. We are working on an advanced system which will offer developers broad access to natively program the iPhone’s amazing software platform while at the same time protecting users from malicious programs.

We think a few months of patience now will be rewarded by many years of great third party applications running on safe and reliable iPhones.

Steve

P.S.: The SDK will also allow developers to create applications for iPod touch.”