02.10.09 - 08:40am
This release is pre-alpha, and intended to get the product into the hands of early adopters in order to get feed back and bug reports. In order to focus our efforts on getting this release out, we have targeted only one device, the HTC Touch Pro. This has a number of user interface implications, including graphics designed for a 300 dpi screen, control layout intended for a vga screen and reliance on a hardware keyboard for text input.
You can install this on your HTC Touch Pro by navigating to the cab installer with your existing browser. This will download the cab file and kick off the installation process.
Alternatively you can download the cab file to your desktop and transfer it to your device via activesync. Once the cab file has been copied to you device, navigate to it using file explorer (on the device) and click on the cab file to launch the installer.
Please note, its been brought to our attention that some carriers are filtering web traffic to preclude downloading cab files. If this is the case with your carrier, you’ll either have to download to your desktop and transfer by activesync, or be connected by wifi if you download directly to the device.
Our focus to this point has been to have a working, usable browser. To get there in a hurry we have punted in a few places, and I’d like to point a couple of them out. First is the update mechanism (both for the browser itself and for extensions). After installing this release, you will not be offered updates automatically, so please stay tuned for follow up releases. Also, we have disabled plug-in support. This is one of our high priority items going forward. Finally, as I mentioned before, there is no soft keyboard support. On an HTC Touch Pro, you’ll have to slide out the keyboard to enter a url.
Besides the release, we marked another major milestone yesterday when the final patch to NSPR landed and we were able to build for Windows Mobile off Mozilla’s trunk for the first time ever. I say the first time because minimo was built from branches of both NSS and NSPR.
Over the last week and half there have been several blog posts and “news” articles floating around the internet about leaked Windows Mobile Fennec builds. This has been fairly entertaining to those of us working on the project for a couple reasons. First, the builds that these posts have pointed to are the builds that I pointed to on twitter. They were intended to be used by the developers working on the project (or anyone else willing to deal with really buggy software) to find bugs before we pushed anything out to the general public.
Also, the concept of secret, leaked builds flies in the face of how Mozilla operates. Our source code is out there for everyone to see. We have a bug reporting system that anyone can (and is encouraged to) access to file new bugs or track the progress of existing bugs. The majority of our discussion around the project is entirely public on irc, our wiki or our meetings and conference calls.
I have been working for Mozilla for 16 months now. At first its a bit of an adjustment to having everything you do or say out there in the public. But after overcoming that initial shock, its a point of pride. This project goes to extraordinary lengths to be open and transparent. If you are going to write about Mozilla, take advantage of that. Read our meeting minutes, hop on irc to ask a question or even dial into the weekly status meeting. Its all out there, just look.