M
murrayatuptowngallery
So many suggestions on how to and how NOT to do things, it gets
confusing.
I have been playing around with an application-specific calculator,
initially form-based, where users select parameters and it produces
output numbers in a table format, ideally small enough to fit in a
wallet.
I never got it to look the way I imagined, and someone threw me a
curve; make it work with webphone type displays.
So I thought, this could kill two birds with one stone...wallet size
and cell phone display size...
I'm not familiar with CSS yet.
The questions:
1) I can see a PDA having a stylus for mouse-like inputs. How do cell-
phone-based browsers make screen entries like moving sliders?
2) How many different screen size formats does one have to plan for,
and does one do that with alot of css statements about the end user,
or does each end user's device screen know how to make things fit (I
think 'no', but there must be a general solution).
3) I found that some slider applications (Tigra, for example), use
methods that allow input changes to be seen onscreen 'live' without
form-based submissions. THAT was a big improvement. I understand the
group of 'onchange' type commands...is there a way to 'refresh' on-the-
same-page results as the sliders are moved? A submit button is not
'live' enough.
Thank you
Murray
confusing.
I have been playing around with an application-specific calculator,
initially form-based, where users select parameters and it produces
output numbers in a table format, ideally small enough to fit in a
wallet.
I never got it to look the way I imagined, and someone threw me a
curve; make it work with webphone type displays.
So I thought, this could kill two birds with one stone...wallet size
and cell phone display size...
I'm not familiar with CSS yet.
The questions:
1) I can see a PDA having a stylus for mouse-like inputs. How do cell-
phone-based browsers make screen entries like moving sliders?
2) How many different screen size formats does one have to plan for,
and does one do that with alot of css statements about the end user,
or does each end user's device screen know how to make things fit (I
think 'no', but there must be a general solution).
3) I found that some slider applications (Tigra, for example), use
methods that allow input changes to be seen onscreen 'live' without
form-based submissions. THAT was a big improvement. I understand the
group of 'onchange' type commands...is there a way to 'refresh' on-the-
same-page results as the sliders are moved? A submit button is not
'live' enough.
Thank you
Murray