We stated that mShell v3.0 will be released in the beginning of July, now it is beginning of July and you might ask where our release is. We are wrapping up the project but had to face quite some difficulties with implementing the compiler. Especially to solve the problem of application signing keeps us still up. Even though we cannot release it yet we are almost finished and hope to release it soon. Stay tuned.

We are planing to release the new version of mShell 3.0 beginning of July. It will include following features:

• Script compiler for standalone apps. Only self signed capabilities available though.
• New language feature: OOP.
• More standard modules like video, screen capture, image alpha blending.
• Bug fixes and some still secret features.

Hope I made you looking forward to this release.

Since the developer certificate of mShell expired people who tried to install it got a certificate error. I just updated the downloads here, with the new versions that will work.

We also found the bug with open signed NMIs which we also fixed. The updated NMI SDK can also be downloaded. 

When you Open Sign mShell 2.02 you get some capabilities that are not available with the self signed (standard) version. In this post I'll show you how to do this.

1. If you have an previous version installed on you phone. Uninstall it first.
   
2. Download mShell 2.02 or higher from here.
3. Go to the Open Signed web site: https://www.symbiansigned.com/app/page/public/openSignedOnline.do
4. On that site enter the IMEI of your phone. For the IMEI type on your phone: *#06#
5. Enter a valid email.
6. Select the mShell SIS file that you want to sign: mShell-S60-3rd-OS.sis for Nokia and mShell-UIQ3-OS.sis for UIQ phones.
7. Select all capabilities.
8. Enter the verification code and accept the agreement.
9. Now you will recieve a confirmation email, click the link and soon after that you'll recieve a second email with a download link. Download it.
10. Install the signed mShell SIS file on your phone.
11. (Optional) Register your copy of mShell.
    

We have just released mShell version 2.02 with the intention to provide you with several bug fixes and some enhancements. Enjoy!

Download it here.

Changelog v2.02:

• 2.02-1: Added net.iaps.
• 2.02-2: Fixed msg.open on UIQ3, adding file index.
• 2.02-3: Replaced infowing by airbit.
• 2.02-4: Replaced activation by registration.
• 2.02-5: Editor remembers last position for each file.
• 2.02-6: Pagewise scrolling in editor with left shift.
• 2.02-7: Improved handling of noneditable part of console text.
• 2.02-8: Added files.parse.
• 2.02-9: Added net.local, net.remote.
• 2.02-10: Created 3rd edition version with UID 0xe7e0cab7 for open signing.
  
• 2.02-11: Added inbox2m.m.
  
• 2.02-12: Increased number of literals per module to 64K.
  
• 2.02-13: Added value constructors to NMI.
  
• 2.02-14: Bug fixes.
  

The question remains when will we release version 3.0 that contains a compiler? We are currently working on it and hope to release as soon as possible a compiler and some major new features to mShell.

We'll release version 2.02 between the 14.4-18.4.08, we will enter the testing phase next week and hope to bring this version to you as soon as possible. We are also working on the version 3.0 that will contain many new features, including a m compiler!

What will be new in version 2.02:

• Several Buxfixe.
• No more activation required, optional registration.
• Minor functional enhancements (e.g. editor, gettings scripts from inbox).
• 3rd ed SIS suitable for Open Signing.
  

The web activation is available again. Note that this way of activating your mShell version works only for mShell and not for mVNC. This is because mShell is bound to the phone (trough the IMEI) and mVNC to the SIM card.

The activation will send you a signed SIS to the provided email, you can then install that SIS file on your phone.

Here you find the web activation. 

As of the 3.3.2008 mShell has found a new harbor: airbit AG Switzerland. When infowing changed hands end Christmas 2007, mShell was taken out of it and will now flurish under a new company called airbit. The founders consist of the core mShell team and we plan to take the product to a next level soon.

You'll hear more about us and what we envision for the future of mShell. 

We are moving our servers and will have a longer downtime from Saturday (1.3.08) to Sunday (2.3.08) of www.m.shell.net and the registering processes. Well try to keep it as short as possible!

Thanks for your understanding. 

Since a few weeks I have a Nokia E90. This great phone has an external screen at standard S60 3rd Ed resolution of 240x320 pixels and an internal screen with 800x284 canvas size.

What a pitty when I started some of my scripts written earlier for the Nokia N70. Many of them has been written with the typical S60 2nd Ed screen resolution in mind so the app screen "hangs" somewhere in the upper left corner when running on a bigger screen. Although the script worked fine I had to go trough the code and change all constant screen coordinates or sizes to relative coordinates and sizes. All the time I saved with the quick hack to assume a constant screen size and/or orientation where eated up with the boring and time consuming adaptions for screen res. independency.

When programming for mobile phones you should always aware that screen size can be different from device to device. Also the screen orientation can change while your programm is updating the screen.

Use graph.size() to get the current screen resolution. If you are using icons (from files) it's a good idea to produce the graphics for a virtual screen resolution which should be at least  two times higher than the current standard. Before drawing the icons you can scale it with graph.size(icon, scale) or graph.size(icon, w, h).

For many applications it is also sufficient to to put the graph module in scaled mode. 

Whatever method you like better, make your application screen resolution independent!