03.01.2013 Views

Chapter 1

Chapter 1

Chapter 1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 15.8<br />

The GUI used in the Psion PDAs was called Eikon (hence CEikAppUietc.). During early<br />

development of Symbian OS, Eikon was rewritten twice, but neither event had an impact on<br />

application engines – testimony to the effectiveness of the original architectural design. The<br />

first rewrite factored the GUI (originally titled HCIL) into CONE (a key item of GUI<br />

infrastructure and yet completely independent of any specific GUI) and Eikon. CONE<br />

survives to this day, but Eikon has been reworked, as different kinds of phones must be<br />

supported.<br />

As Psion and others produced new PDAs, ports of Eikon and the applications were made. In<br />

1997, Geofox released its Geofox One, with a 640 × 320 display and a track pad. Psion<br />

produced the netBook/Series 7 with a 640 × 480 color screen, and the Psion Revo with a<br />

480 × 160 display, with three-button toolbars.<br />

These ports showed that Eikon could scale to a different screen with only relatively minor<br />

modifications to itself and its applications. But they also show that even a minor change in<br />

screen size can make some software look odd, or prevent it from running altogether unless<br />

modified. The Battleships game's application view would look odd on a Psion netBook (lots<br />

of spare space above and below) and may not fit on a Revo at all.<br />

To get Java certification in 1998, Symbian OS needed (among other things), to be able to<br />

run GUI applications and applets written in Java – often ones originally targeted at a much<br />

larger device. Symbian did that by adding some more tweaks to Eikon and some support in<br />

the AWT implementation that links Java to Eikon. For instance, Symbian added scrolling<br />

menu panes, metaphors for emulating right-click, and scrolling app views. Although that<br />

meant that Java applications and applets could run without modification under Eikon, it did<br />

not guarantee a satisfactory experience with applications whose menus and views were too<br />

big to see all at once, and required contortions to produce frequently needed pointer<br />

gestures.<br />

So by the time Symbian split from Psion to become a mobile phone software vendor, it had<br />

became clear that different mobile phone manufacturers would have different requirements<br />

for which Eikon, however modified, would not be suitable.<br />

Replacing Eikon<br />

For some time, Symbian thought that each new device would have its own GUI that would<br />

replace Eikon altogether. The first opportunity to do this was during 1997 and early 1998,<br />

with the Ilium Accent produced by Philips Consumer Communications (never generally<br />

released).<br />

With a 640 × 200 display and no keyboard, the device parameters were radically different<br />

from those that drove Eikon, as shown below:<br />

The experience of the Ilium Accent showed clearly that Eikon could be replaced, but it also<br />

demonstrated the costs and the risks involved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!