Nokia N-Series Internet Tablet Support

[GoogleCodeExporter]

Purpose of feature on this branch:

A client UI for the Nokia Internet Tablets running the MicroB user agent:
Nokia 770, N800, N810, N900

They all have 800x480 resolution in wide-screen format.

Proposition for feature implementation:

Would like to see buttons big enough for a fat finger tip, this would
require the screens in the UI be broken down more than just home, lights,
appliances...etc....it would have to be broken down by room under the
parent section.

A beautiful example of a UI for the N-Series is the Insteon software
'InterfaceGO':

http://www.interfacego.com/
http://www.interfacego.com/products/nk8.html

Original issue reported on code.google.com by brandtda...@gmail.com on 12 Apr 2010 at 7:13

[GoogleCodeExporter]

This would be interesting. We have to do it in a java script and be lightweight 
so as
not to burden the MicroB render engine. If we are looking at JQuery for an
implementation for the other themes, we would need to start looking at 
client/server
architecture in domus to accomplish this for themeing, maybe. Just a thought.

Original comment by bwsamuels@gmail.com on 13 Apr 2010 at 1:41

[GoogleCodeExporter]

Well, Does anybody care about this feature? I've got an android tablet now and 
will probably sell my n800.

Comments?

Original comment by bwsamuels@gmail.com on 14 Dec 2010 at 1:57

[GoogleCodeExporter]

I care about this feature in a generic sense meaning;

Mobile phones are great, but you have to think about tablets or touch screens 
that stay at home...people can't control their house if the touch screen left 
with the owner to work ;)

In order to have a bunch of strategically place tablets around the house they 
must be affordable. The N series are affordable at this point, some picture 
frames run linux could be hacked as a touchscreen....

I was playing with the Heyu Web Interface and the designer added a section to 
create device profiles in the application where you can specify height and 
width of page elements and save them to a user agent list. This makes it nice 
if you have a certain odd sized screen you want to display it on.

I support this ticket in a sense that we need to support more sizes/resolutions 
in general. If we just made a version that rendered well on the resolution of 
these older touch screens that would be fine...

Original comment by brandtda...@gmail.com on 14 Dec 2010 at 6:07

[GoogleCodeExporter]

Brandt,

The plethora of android devices are now cheaper than a used Nokia. You can get 
an Archos 28 for $99 list price or cheaper on sale and it runs Android 2.2. 
Nokia has bit the dust with Maemo and Symbian and is a minor device at this 
point.

Maybe a more simpler mobile web interface theme should be developed, but that 
is far as I would go with it.

Just my thouhts,

Brad

Original comment by bwsamuels@gmail.com on 17 Dec 2010 at 2:56

[GoogleCodeExporter]

2.8" screen is too small. I'm thinking of others here. I'm thinking of how to 
make home automation available to all. I'm thinking older people don't want no 
2.8" screen. The n800 is good because it has a fairly large screen for a very 
reasonable price ( $75 or less ). At least domus.Link should support lower 
resolutions like that.

I've come to realize that most people aren't going to be sitting in front of 
their computer when they want to control something, so wide mobile support is 
very important.

I think room by room organization is also very important. If a person wants to 
find a device from a list of anywhere up to 255 devices (for the x10 protocol) 
They are going to be presented with a very large list of items in domus.Link on 
their mobile device which would require a LOT of scrolling on a tiny screen! 
(no fun!) 

It is essential that we have separate screens per room so that scrolling is not 
required and all devices in a single room are presented up front.

-Brandt

Original comment by brandtda...@gmail.com on 17 Dec 2010 at 11:36

[GoogleCodeExporter]

I would agree the archos 28 may be a bit small. The 32 will be better and is 
about the size of an ipod touch. It's just the n800 is slow at 300mhz. The best 
solution is a generic mobile page that is slimmer for any mobile browser. We 
need to incorporate browser id and present different themes based on that. The 
config pages would not necessarily be neede for a mobile page as we would just 
need to present the controls for devices.

Brad

Original comment by bwsamuels@gmail.com on 19 Dec 2010 at 6:59

[GoogleCodeExporter]

I agree a generic "control only" mobile page that would be larger (easier to 
touch with a finger) would be perfect

I had already started working on something like this for domus.Link a while 
back but had put it down. Now that I finished school, I can pick this back up 
again. I hope to share this template and the HVAC code as well.

-Brandt

Original comment by brandtda...@gmail.com on 19 Dec 2010 at 8:07

[GoogleCodeExporter]

Just tested the 2.0beta7 on the NokiaN800 and it just doesn't play well. the 
JavasScript is just not right.

Original comment by bwsamuels@gmail.com on 24 Feb 2011 at 4:35

[GoogleCodeExporter]

New mobile web theme created from iWebKit5.04 solves this.

Original comment by bwsamuels@gmail.com on 27 Feb 2011 at 8:35

• Changed state: Started
• Added labels: Milestone-v2.0

[GoogleCodeExporter]

This issue was closed by revision r838.

Original comment by bwsamuels@gmail.com on 27 Feb 2011 at 9:19

• Changed state: Fixed