View previous topic :: View next topic |
Author |
Message |
vida18 Agent
Joined: Sep 13, 2008 Posts: 10
|
|
Back to top |
|
|
pluby The Architect
Joined: Jun 16, 2003 Posts: 11949
|
Posted: Sat Sep 13, 2008 12:05 pm Post subject: |
|
NeoOffice 3.0 will use the same code that we have written and users have tested over the last 5 years: a combination of C, C++, Objective-C, and Java.
Patrick |
|
Back to top |
|
|
MacRat Sake Horner
Joined: Mar 02, 2006 Posts: 364 Location: Earth
|
Posted: Sat Sep 13, 2008 12:29 pm Post subject: |
|
You don't want to catch mono? |
|
Back to top |
|
|
ovvldc Captain Naiobi
Joined: Sep 13, 2004 Posts: 2352 Location: Zürich, CH
|
Posted: Sat Sep 13, 2008 12:43 pm Post subject: |
|
I understand there is some C# in the MS Office XML format translator but otherwise, this is not a language you can expect to see in Mac software a lot. In fact, I had no idea there was such a thing as Cocoa#....
Best wishes,
Oscar _________________ "What do you think of Western Civilization?"
"I think it would be a good idea!"
- Mohandas Karamchand Gandhi |
|
Back to top |
|
|
vida18 Agent
Joined: Sep 13, 2008 Posts: 10
|
Posted: Sun Sep 14, 2008 12:22 am Post subject: |
|
I forgot this link for CocoaSharp. |
|
Back to top |
|
|
OPENSTEP The One
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
|
Posted: Mon Sep 15, 2008 8:59 pm Post subject: |
|
It's also been my experience that mono on OS X has some quirks to it...in the time that we've been using it with odf-converter (alebit faceless) we've encountered a few times things that run fine on Linux builds need to have us tweak the VM/CLR parameters to function properly on Mac OS X...and rarely we have crashes. That's not to say that C# isn't a great language, though, but unfortunately a lot of technologies that it uses via WinForms and various .Net enabled libraries are still only available on Win32 and only supported through rudimentary Mono stuff. The Mono project has really been focused more on GTK# I think rather than doing a full clone of WinForms. I may be completely wrong on that as I haven't looked in depth at their support in over a year, however.
I don't think we'll be moving to any new frameworks as, logistically, we're really invested in Objective-C++ as our language of choice. It allows us to mix in Cocoa while still using the UNO C++ language binding for accessing services. Without the ability to tie into one of those language bindings, a lot of the development beyond VCL hacking becomes difficult, if not impossible.
ed |
|
Back to top |
|
|
|