Adding to my last post:
Notwithstanding the various obstacles I mentioned in my previous
post: another way we can encourage healthy developer contribution/
involvement is to make katieplayer extensible. We can do this by:
1. In the relatively near term: making katieplayer Apple Scriptable
(some will argue this is not extensibility, strictly speaking...but
you know what I mean). The Cocoa version of katieplayer will be
scriptable. We'll start small and expand the scripting dictionary as
the app grows. (As I recall, both Scott and Travis inquired about
katieplayer and AppleScript in earlier discussions).
2. In the longer term: create an open plugin architecture for
katieplayer. I like to think katieplayer as media player which
happens to have a DAISY focus. Media players and open plugin
architecture go together well.
Joe
On Mar 17, 2006, at 8:40 PM, Travis Siegel wrote:
I also believe in doing it right the first time. Only in this
case, I ask you one question.
If you were deaf blind, and had to use braille to access your
computer, would you want vo type feedback, or would you want
information that was in addition to what vo gives out, and thus
nearly completely useless to you as a deaf blind user? I'm not deaf
blind, but I know what my answer would be.
And as for working separately instead of together, talk to apple,
katie player, folks, and various share/freeware authors about how
I've offered to work with them or indeed tried to go to work for
them to make the programs accessible/more usable. Put that
together with the fact that I'm still working alone, then you tell
me why it doesn't happen.
On Mar 17, 2006, at 3:40 PM, Cheryl Homiak wrote:
I don't believe in doing quick put-ups. I believe in doing it
right in the first place. The fact that people on this list
continually ignore suggestions to work with the brltty team and
want to work on their own is puzzling and disappointing to me.
--
Cheryl
"Where your treasure is,
there will your heart be also".
