[brailleblaster] Re: Some Thoughts
- From: Alex Jurgensen <asquared21@xxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Wed, 2 Feb 2011 08:44:57 -0800
Hi John,
Oh no!
It is one word?
I have to completely rewrite my source code now to reflect the changes.
Or we could always have "Brailleblaster" on Windows and Linux, and then
"Braille Blaster" on the Mac.
Besides that, I have been examining a very neat toolkit that allows BB on the
Mac to receive software updates just like Webkit, Adium, and many other
applications.
It won't work on Windows/Linux, but I think that it is still pretty cool.
In doing my research, I cam across a developer who was trying to port it to
Java code, so hopefully we can use this soon on all three OS's.
For the meantime, what do you all think if I include this in my mock up?
Regards,
Alex,
Alex Jurgensen,
VoiceOver Trainer,
Visit me on the web at: http://www.vipbc.org/
On 2011-02-02, at 12:19 AM, John J. Boyer wrote:
> I've read through all these messages, and I'm convinced we should stick
> with SWT. By the time BrailleBlaster is ready for use by anybody other
> than a developer the problems on the Mac may be resolved. We can add a
> little pressure to the Eclipse developers to help things along. The idea
> of using the SWT browser to present GUI content is interesting.
>
> The classpaths specified in the ant build.xml file go iknto the manifest
> of the BrailleBlaster jar file. This makes callinng BrailleBlaster very
> convenient on my flavor of Linux and on Windows. We could make different
> versions of BrailleBlaster for different distros, but I think that is
> something for the early adapters who use these distros to worry about.
> They will know their own flavors. And many of them won't care about the
> standard locations.
>
> Let's learn from Alex's experience in proting BrailleBlaster to the Mac.
> Concern about various Linux flavors at this time is a distraction.
>
> As for me, I'm concentrating on getting BrailleBlaster to work with at
> least generic embossers. Then I'll make a simple text editor using a
> GUI. the experience in doing this will be necessary to make the real
> GUI. The text editor will remain as a BrailleBlaster feature to be used
> by advanced users.
>
> Incidentally, BrailleBlaster is a single word. It should not have a
> space.
>
> John
>
> --
> John J. Boyer; President, Chief Software Developer
> Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
>
>
> ----- End forwarded message -----
>
> --
> John J. Boyer; President, Chief Software Developer
> Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
>
>
Other related posts:
