Hi John, Testing your release on the Mac, without my app bundle does not work. I get the following errors: COPYRIGHT.txt getting-started.txt native LICENSE.txt helpDocs programData brailleblaster.jar lib Shelty-2:dist AlexJ$ java -jar brailleblaster.jar Exception in thread "main" java.lang.UnsatisfiedLinkError: /Users/AlexJ/Downloads/brailleblaster-0-1.2.0/dist/native/lib/liblouisutdml.so: no suitable image found. Did find: /Users/AlexJ/Downloads/brailleblaster-0-1.2.0/dist/native/lib/liblouisutdml.so: unknown file type, first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00 at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1823) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1699) at java.lang.Runtime.load0(Runtime.java:770) at java.lang.System.load(System.java:1020) at org.liblouis.liblouisutdml.loadLibrary(Unknown Source) at org.brailleblaster.BBIni.<init>(Unknown Source) at org.brailleblaster.BBIni.<clinit>(Unknown Source) at org.brailleblaster.Main.main(Unknown Source) Shelty-2:dist AlexJ$ Any ideas what I can do? Regards, Alex, On 2011-02-02, at 9:51 AM, John J. Boyer wrote: > Alex, > > I'm looking forward to seeing your moc-up. I always like looking at > source code. > > My release is a little strange. The swt.jar is for Windows, because that > is where I will test a GUI when there is one. I only use the command > line on Linux and don't have Gnome or anything else. The gtk and Windows > SWT jars have the same name swt.jar. I suppose the Mac one does also. > You will have to go to http://eclipse.org/swt > > I rather think that it doesn't matter whether the native libraries are > 32 or 64 bit, as long as the OS can run them. It shouldn't matter to the > JVM. > > John > > On Wed, Feb 02, 2011 at 09:26:12AM -0800, Alex Jurgensen wrote: >> Hi John, >> >> I didn't notice the ")". That should have been an underscore. >> >> The reason why I have built my app bundle is to firstly address my own >> workflow and secondly to do something that I feel can contribute to the >> project. >> >> I have a new mock up ready for submission. >> >> By the way, is the SWT library included in your release of BB for Linux? Do >> you have the Mac version? >> >> Regards, >> Alex, >> >> >> On 2011-02-02, at 9:19 AM, John J. Boyer wrote: >> >>> 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 >>> >>> >> > > -- > John J. Boyer; President, Chief Software Developer > Abilitiessoft, Inc. > http://www.abilitiessoft.com > Madison, Wisconsin USA > Developing software for people with disabilities > >