Hi folks, In middle of studying for math final, I have decided to check out recent emails. And it seems that there are numerous messages that caught my attention, so naturally, I am writing this message to give my points on recent discussions: * WiFi card: Zach, you need to realize that, just because a WiFi works with a laptop does not mean that it will work with BrailleNote. The biggest factor that ultimately determines a hardware device working with a computer system, apart from hardware, is support of this device by the operating system - in other words, drivers. If there is no way for the operating system to know what to do with a device, then logically, this device is not supported. So, I am sorry to inform you that the card you've mentioned will not work with braillenote, since there is no message about CE drivers for this card. * SDK: Thanks Kevin for your explanations. I am sure some people would understand the following statement: Writing software is, in my opinion, the most amazing things about computers - allowing the users to tell the computer what they want it to do. However, writing the actual thing that allows users to write programs is, if I'm right, not an easy task. The developer of an SDK must come up with at least following programs: A. A program that allows programmers to write programs. Any text editor would do the job. However, some programs which relies on syntax and formatting of its code, such as C++ and Java and such, care must be taken to design an editor that is language-friendly e.g. keeping formatting straight, checking syntax, etc. B. Compiler/interpreter: A way of transforming human-readable code to machine language. Each CPU knows its own machine language. Special time must be spent on coming up with compiler(s) that will support multiple machine languages (called CPU architecture) - especially on BrailleNote family, which uses different CPU family per machine type - MIPS for Classic, ARM for PK and X-Scale for mPower. Also, the developer needs to consider what type of transformation is best: a compiler, which would transform the programming code into machine code instantly, or an interpreter, which runs programming code line by line. C. Reference manual: A way of telling programmers about different functions about a given software suite. Since KeySoft is complex software suite, the programmer needs to know which KeySoft function to employ when writing his or her own programs. For instance, my plan of a ultra scientific calculator program would need functions from KeyPlus and Nemeth translation function to work with complex mathematics task, such as unit conversion and symbols for calculus. Or a programmer who is planning to come up with a PDF converter needs to employ file translation function to convert PDF files to desired braille or text format and vice versa. Because of the complexity of the suite involved, there must be a clear reference documentation stating which function is best when writing certain type of programs. Some of the possibilities include: * Calculators: KeyPlus function, Nemeth and/or other countries' math symbol manipulator. * Document format converters: KeyWord, file translation function. * HTML email extension: keyMail, email reading/writing functions, HTML viewing mechanism from KeyWeb. And so forth. D. Debugger: A software cannot be released unless it is stable. There could be flaws with programming code that prevents a given software from running properly. This is where debuggers come in - this software shows exactly what's going on when a program is run, thereby allowing programmers to detect what's wrong with the malfunctioning software. And other components, if needed. Creating SDK (Software Development Kit) is not an easy task, especially for an embedded system like BrailleNote, which has strict hardware and operating system requirements. You need to understand that, just because we imagine software features does not mean it will "magically appear" at our fingertips - software engineering, particularly for devices like BrailleNote, requires careful programming, compiling, testing and retesting the software in question until it is stable enough to be used by mass populous. * KeySoft 8.0: The above portrait preety much explains why there are delays in keySoft release. Like I have emphasized, software programming is not an easy task. So please, can we have patience? I understand that some people are frustrated due to lck of communication from HumanWare, but let us think of this way: This lack of communication could be our own advantage as well as HW;s advantage: By giving us wait times, we can be more excited and anticipate more on future relases, and by having ample time, HW can release a KeySoft version that is stable. Hope the above message helps you. If it was too hard for you to understand, I apologize (I tried my best to explain it in simple terms). If you have any comments, feel free to contact me (if it is personal comments). Due to my math final on Tuesday, I wouldn't be able to answer all questions... sorry about that. Cheers, Joseph
___ Replies to this message will go directly to the sender. If your reply would be useful to the list, please send a copy to the list as well. To leave the BrailleNote list, send a blank message to [email protected] To view the list archives or change your preferences, visit http://list.humanware.com/mailman/listinfo/braillenote
