[brailleblaster] Re: Some Thoughts
- From: "Sina Bahram" <sbahram@xxxxxxxxx>
- To: <brailleblaster@xxxxxxxxxxxxx>
- Date: Wed, 2 Feb 2011 13:06:48 -0500
Complexity now costs less and saves nightmares later. Complexity for
complexity's sake is bad, but I don't believe that something as
essential as resource bundles in any way classifies.
Take care,
Sina
-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
Sent: Wednesday, February 02, 2011 12:20 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Some Thoughts
More. I looked at the mock-up. That was one reason that I thought it was
time toemphasize that BrailleBlaster is one word.
I'm not familiar with app bundles, but I can't help wondering if this is
all more complicated than it needs to be. For testing, why can't you
just run BrailleBlaster as it is to see what errors you get.
A trivial matter but I noticed the directory name X86)64 Could you
replace the right parenthesis with an underscore? My Linux shell doesn't
like it.
John
On Wed, Feb 02, 2011 at 08:52:17AM -0800, Alex Jurgensen wrote:
> Hi,
>
> I suppose that the Mac issues should be resolved in any case. This would help
> the Mac community as a whole.
>
> I've built my boot loader now, but I can't test it yet.
>
> Did you get a chance to look at my mock up yet?
>
> What do you think of it?
>
> 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
> >
> >
>
--
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:
