On 12/17/2010 06:10 AM, Casper Bang wrote:
Can we thus infer, that you are not convinced by Java's deeply rooted
philosophy of "write once, run anywhere" ...for UI-kits anyway?
Well, not for what I was saying :-) First, because I was talking of
Android, which is sure not Java from the UI point of view. But mainly
because the need for different UIs, which I don't see how could be
managed by any technology with a single design, arises from the fact
that differently sized devices exist for different purposes. I mean, a
tabled is not just a larger phone. Example: what I'm thinking for my
blueBill (I recall you, it's a tool for writing down bird observations
of the field) is that a birdwatcher would use it on the field for record
observations, listen to callls and quickly read fact sheets for the
identification; data would live shortly on the phone, as they would be
quickly transferred to another system for archival and further offline
elaboration. For all this, a regular phone of the size if a Droid, more
or less, is pretty good. Larger would mean more weight, more gear in
addition to binoculars or long lenses... not practical.
What would be interesting to see on a larger tablet, 10" wide? For
instance, a professional ornithologist in a capture station, when they
take birds, measure, mark with rings and then release them. This is done
in specific stations where you can use larger equipment (I believe they
now use regular laptops), and filling a detailed form with observations
would work much better with a larger screen and all the form in a single
display, rather than a step-by-step wizard. They could take many bird
photos (typically of details, such as feathers on the tail or the wings)
directly with the embedded camera, because they have the bird in their
hands, that' pretty close (OTOH a birdwatcher needs to use a
professional long lens). Note that it's not the matter of adding one or
two more fields or the capability of adding photos (that can live as
well in the basic version), rather the workflow of the operations which
is different and is best fit by another screen size. Even the lifecycle
of data would be different, as replacing a laptop an ornithologist will
likely want to have a rich database of archived data that he can recall
at any moment, in addition to have a data entry device.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
fabrizio.giud...@tidalwave.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
