Hi David,
Thanks very much for your kind feedback. I'll continue to work away on the
things you have described. Some notes on a few of the to-do items:
> No color icon?!
Colour icons are available as a screenshot currently, but I thought it less
gruntwork to collectively decide on the design/arrangement/spacing etc of
the b&w icons first, then can just have the same spacing/design for the
colour icons. The colour icons for the launcher has already been made by
someone else (some nice 3d pacifiers) in the directory. I believe Michael
mentioned he could add in some lines in the compilation to specify colour
icon output, after the colour icons are spliced and ready.
> > -Addition of an autoscroll button, with increase (+) and decrease (-)
> > scroll speed on either side. Autoscroll has a play arrow like the arrow
> > that shows the tape direction on a cassette player so not confuse with
> > the 'forward' arrow icon.. Autoscroll play icon changes to a square
> > 'stop' icon while scrolling.
>
> Except... the [-]/[+] chevrons are too small to reach with a stylus.
Will do. Add in a few more pixels for width. Will try to shift things around
to make some more room for the extra pixel. I think the widths of the other
icons were 13 pixels.
> Ideally changes/updates to this should include the ability to stop the
> scrolling while the speed is changed. Another press of the play icon after
> changing speeds should resume the autoscroll option (speed had
> absolutely no
> effect on my Palm m505, speed was the same 'slow' or 'fast' with zero
> difference)
>
> Not OK. There was absolutely no speed difference after tapping on
> the [-] icon 10 times and then tapping on the [+] icon 20 times. Zero
> difference.
Will have to fix that.
> > 6. Prevent a power-off when autoscrolling, since will have no user input
> > for a minute or 2, which would normally cause device to shut off: OK.
>
> This is a problem, and is related to a bug in the autoscroll as
> found in your version of the viewer. If you set autoscroll on (play), and
> scroll to the bottom of a page, the page KEEPS SCROLLING to 100% over and
> over, causing a nice flicker, and wasting battery considerably and causing
> an annoying navigation problem.
>
> Solutions:
>
> - stop the 'play' of autoscroll when the following options are
> selected/hit:
>
> - ANYTHING on the scrollbar is touched.
> - The [-]/[+] is tapped
> - Home (house) icon and the two forward/back icons
> - Menu
> - Percentage indicator
> - Power button off/on should disable autoscroll.
>
> You can see this bug by setting autoscroll, then select 'Top' from
> the percentage indicator. EEP! Shouldn't do that.
Sure thing. Of the items in the list though, do you want to stop play when
you hit a [-] or [+], instead of being able to increase decrease speed as it
is playing?
Power off/on, will do.
Michael also recommended a stop autoscroll when hit the bottom of the page
(if the page doesn't have an autscroll=2.html like you suggest), which
sounds like a good idea. Sound good to you too?
> > 1. Hardkey/Gesture options to increase/decrease speed.
>
> Up/Down rocker is an intuitive selection here. Let's not try making
> things difficult.
Do you think it is better to override the omnipresent page up/down to always
do a increase/decrease autoscroll instead when autoscroll is on? Or to set
them as an option for a hardkey/gesture? Setting as an option in the list
for a hardkey/gesture is reusing the code that is already there, just added
to the bottom of the list, and allows user configuration of whether they
want them or not. Up/down rocker would not be much code either though.
After you mentioned this, I noticed that this is the behaviour in CSpotRun.
> > 2. Ability to choose to autoscroll upwards instead of downwards...does
> > anyone ever do this?
>
> Yes, advogato diaries are a perfect example of this.
Will do.
> Additionally, I'd suggest a new record_id, which when reached at the
> top/bottom/middle/whatever of a database, would 'autoscroll' into the next
> page. Basically if I build a page which has a faux tag like:
>
> AUTOSCROLL=2.html
>
> (from the 1.html page), and set autoscroll on, and this tag is
> reached (yes, as a record_id), it would then 'tap' on that invisible link
> and go to the next page. Just an idea.
Sounds reasonable. I can't put this in though. Perhaps Michael can comment
on this.
> > 3. Upper time limit on the prevent of power off without user input so
> > that can't accidently leave it running and wipe your PDA since it ran
> > out of juice.
>
> Make it selectable.
>
> [x] Stay on while autoscrolling
>
> ..when selected, should pop up an alert which says something like:
>
> 'This option will force your Palm device to stay ON forever, or
> until you hit the power button'
>
> When they disable autoscroll (which should remove the toolbar
> iconset also), the sleep value should be restored.
Sure thing. Seems like a fair way to handle it.
> You can also trap the low power event sent by the OS, which will
> drop a dialog in the way anyway. Simply stop scrolling while that
> dialog is
> in place (I don't think you have any other option, it's modal)
A very good idea. Both of these might slow pixel scrolling marginally, but
should be worth it.
> > -The rubber chicken in the 'About Plucker' form: smoothened up pixel
> > edges.
>
> Looks great. All of the changes you've made are really good. Let's
> shore up the autoscroll with the limits I've mentioned above, and
> see where
> we can implement as much code reuse as possible. The viewer is now 77k
> total, and that's quite large (though not 293k like "Them(tm)").
