As an Assistant Professor, I'm teaching Symbian OS at the University of Applied Sciences in Hagenberg, Austria. My company "Mopius" is developing mobile software with a special focus on Symbian OS.
A Case-Study of Porting Widgets to S60
mopius | 11 October, 2007 21:29
 |
| The case study contains a description of the solved issues when porting the "Heise News"-widget to the S60 Web Runtime. |
Before this was published, an early beta had already been part of the S60 3rd Edition FP2 Beta-SDK for MIDP. This SDK supports the Web Run-Time environment for developing and testing widgets in the emulator, but does not include any further documentation.
Christian Kaar from the University of Applied Sciences in Hagenberg tested the new engine and tried to port several Apple Dashboard widgets to the S60 engine.
Even though Nokia has been a few days too fast for us with publishing their official documentation, his technical report is still very interesting to read. After an overview of widget technology, he included a case-study of porting two widgets, whereas the official documentation only points out the general issues.
You can download and read the technical report at symbianresources.com.
Browsing, Connectivity, S60 |
Next | 
Previous |
Comments (3) | 
Trackbacks (0)
Comments
Re: A Case-Study of Porting Widgets to S60
hartti | 14/10/2007, 21:24
Hi Andreas,Did you attend Phong's session on Web Runtime during the Forum Nokia Developer Day? What did you think?
Hartti
Re: A Case-Study of Porting Widgets to S60
mopius | 22/10/2007, 18:57
Hi Hartti,of course I attended the session at the FN Developer Day! It has been very interesting to see the Widgets in action. The examples have been helpful in understanding how development works - exactly the right difficulty level to see what's possible with this technology.
As a small suggestion - the hands-on part should probably be thought about once more. I guess it has somehow been a rather difficult situation for everyone, as neither Phong nor the attendants seemed to know what to do or how to do it.
A solution could be to distribute the required files well before the event, instead of through a memory stick in the pause before the session. I think not many had the resources when the hands-on part started, therefore couldn't do anything, which made it difficult for Phong as well...
-Andreas
Who am I?
Thinking about what mobile phones can do except messaging and voice calls is one of my main interests. At the department of Mobile Computing at the University of Applied Sciences in Hagenberg (Austria), I can work on those ideas every day by collaborating with students, researching and - well - thinking.
Calendar
Recently...
- Protect your Skis with your Phone!
- Mobile Surround Sound
- Automatically Calling Back Saves Money
- Abandon your Privacy
- Euro 2008? -> Table Soccer on your phone!
- Mobile Game Controllers: Problem Solved!
- Efficiency Boost - New Carbide.c++ Panic Lookup Plug-In
- ShakerRacer is now Open Source!
- 3D games and more – Java ME course materials available
- ShakerRacer: Real RC car controlled with the N95 acceleration sensor
Categories
Re: A Case-Study of Porting Widgets to S60
forum-mrkt | 12/10/2007, 19:59
One observation on wording. For years the term "mobile browsers" has denoted browser implementations that vary significantly from their desktop brethren. However, with the Web Browser for S60 the notion of one Web came to include mobile users and it raised the issue of whether or not prefixing something with the word "mobile" purely refers to the physical difference in location of the user or it also denotes a difference in technology.
There's likely not a unique answer to this, but your report certainly makes clear our point of same technology, different devices. To further emphasize that with the Web Browser for S60 and Web Run-Time there's one Web accessed by users in different environments using different types of devices, we adopted the notion of widgets for mobile users as opposed to using the ambiguous prefix of "mobile". We'll see where the terminology ends up in the future.
-Finn-