[brailleblaster] Re: The Renaissance Framework
- From: Alex Jurgensen <asquared21@xxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Tue, 1 Feb 2011 17:45:28 -0800
Hi,
It most certainly is. It uses Webkit, the engine behind Safari and Google
Chrome.
I'm not saying that I am threatening to hold things back. In fact, if we went
the Renaissance root for the GUI on the Mac, I was willing to write all of that
code myself.
However, I just wanted to make sure we make the best choice before getting too
far into development.
On the bright side, I have figured out most of what is needed to have BB
self-update on the Mac.
Regards,
Alex,
On 2011-02-01, at 12:50 PM, Chris von See wrote:
> Alex, I'm just curious - do you find that the SWT browser control is
> accessible in the same way that a "regular" browser (Firefox, IE, Safari,
> Chrome, etc.) is? If the browser control is accessible, perhaps that's the
> way to go - build the framework using SWT and the UI content using HTML
> displayed in an SWT browser control.
>
> Just a thought...
>
>
> Cheers
> Chris
>
>
> On Feb 1, 2011, at 10:26 AM, Alex Jurgensen` wrote:
>
>> Hi,
>>
>> By the same reasoning, SWT fails on Mac OS X.
>>
>> Anyone who has used SWT based software knows that it is a nightmare.
>>
>> Using GNUStep allows the native controls to be drwan if I understand
>> it correctly.
>>
>> Eclipse is a good example of how SWT fails on Mac OS X. The
>> accessibility of SWT is so poor insider Eclipse that I had to do a lot
>> of digging around before I could even start using Eclipse.
>>
>> I also don't expect every user to have as much RAM as I did, and I was
>> experiancing RAM issues.
>>
>> What if we wrote the core of the program in C++ or C and did seperate
>> UIs for the different platforms?
>>
>> We oculd use C++ with Java wrappers and SWT on Linux and Windows and
>> Renaissance on Mac OS X.
>>
>> MVC would allow for this.
>>
>> Regards,
>> Alex,
>>
>>
>>
>> On 2/1/11, Michael Whapples <mwhapples@xxxxxxx> wrote:
>>> So from what I read it uses gnustep for the UI on linux and windows. While
>>> it hasn't been stated anywhere, I know from some of the initial discussions
>>> that why SWT was chosen is that the UI should be accessible to screen
>>> readers on any of the platforms supported without using additional access
>>> bridges (eg. the java access bridge). Therefore I think this makes
>>> renaissance fail to meet what is required, the accessibility on Linux is
>>> certainly suspect
>>> http://mail.gnome.org/archives/orca-list/2010-February/msg00063.html.
>>>
>>> Michael Whapples
>>> On 1 Feb 2011, at 15:26, Alex Jurgensen wrote:
>>>
>>>> Hi John and All,
>>>>
>>>> Here is what Wikipedia has to say about Renaissance.
>>>>
>>>> http://en.wikipedia.org/wiki/GNUstep_Renaissance
>>>>
>>>> Regards,
>>>> Alex,
>>>>
>>>>
>>>> Regards,
>>>> Alex,
>>>>
>>>>
>>>> On 2011-02-01, at 7:11 AM, John J. Boyer wrote:
>>>>
>>>>> Nope. This URL gives a page not found error.
>>>>>
>>>>> John
>>>>>
>>>>> On Tue, Feb 01, 2011 at 06:59:56AM -0800, Alex Jurgensen wrote:
>>>>>> Hi John,
>>>>>>
>>>>>> I believe that the URL is: http://www.renaissance.it/ .
>>>>>>
>>>>>> Regards,
>>>>>> Alex,
>>>>>>
>>>>>> On 2011-02-01, at 4:19 AM, John J. Boyer wrote:
>>>>>>
>>>>>>> Can you give us a URL for this Framework? I don't know if we want to
>>>>>>> switch from SWT at this point, since we have put a lot of effort into
>>>>>>> it. We also know it is accessible, but we aren't sure about
>>>>>>> Renaissance.
>>>>>>> What applications is it used in?
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On Tue, Feb 01, 2011 at 01:31:00AM -0800, Alex Jurgensen wrote:
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> There is a framework that I have been using for most of my native
>>>>>>>> applications UI's that I would like to share with you.
>>>>>>>>
>>>>>>>> It is called Renaissance and is based on the Openstep/Cocoa APIs.
>>>>>>>>
>>>>>>>> It is a lot like the SWT jars in functionality, but it allows the
>>>>>>>> underlying code to be written using Objective-C, C++ and/or C.
>>>>>>>>
>>>>>>>> I use it because it provides a very interesting autolayout engine that
>>>>>>>> makes it very easy to code user interfaces.
>>>>>>>>
>>>>>>>> Because it provides native controls, it should be accessible on all
>>>>>>>> three of the platforms that it runs on.
>>>>>>>>
>>>>>>>> I am throwing this out as an alternative to using SWT, since some of
>>>>>>>> the core libraries are already in natively compiled binaries and the
>>>>>>>> autolayout engine would probably be a big help to the person working
>>>>>>>> on the UI.
>>>>>>>>
>>>>>>>> Just my thoughts.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Alex,
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Alex A.AWEBSIGHT administrator
>> AWEBSIGHT web team
>> "Blindness is a gift, not a disability."
>> B.C unit
>> <ASquared21@xxxxxxxxx>
>> http://www.VisionMail.uni.cc/
>>
>
>
Other related posts:
