But if one wanted to write for cross platform, using as much shared code as
possible while being able the "tweak"  the OSX version in places where a
Cocoa GUI widget or other feature offered a benefit to that version, it
would be good to know it could be done all inside RB.

Its all about having as many choices to fine tune apps for the particular OS
while maintaining as common a code base as possible.


On 20/2/07 05:54, "Ryan Dary" <[EMAIL PROTECTED]> wrote:

> It's easy... just use Cocoa.  What's the point of using RB if you're
> only gaining "Direct Access to Cocoa"?  Just use Cocoa.  If you know RB,
> the language barrier is small.  Cocoa is simple to learn, easy to use,
> and creates beautiful apps... on Mac only.
> 
> REALbasic is a cross-platform development environment.  It has it's own
> framework, and that is the way it should be.  Do you really want to code
> your projects twice or three times (linux?), then just code on each
> platform in C/C++/Obj-C/C# and be on your merry way.
> 
> - Ryan Dary
> 
> Daniel Stenning wrote:
>> Seth, 
>> 
>> As someone who clearly has detailed experience of both Cocoa and RB,  how
>> hard ( technically/architecturally )in your opinion would it be to bring out
>> a future version of RB that allowed ont to program DIRECTLY to the COCOA
>> API, bypassing the RB GUI frameworks ( and maybe non-gui)-  for those
>> programmers who only need to write OSX apps, but would prefer to use the RB
>> language and IDE ?
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
> 
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
> 

Regards,

Dan

_______________________________________________________
www.13flatFIVE.com
The C++ <> REALbasic code migration specialists


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to