thanks Micheal, thats sounds good.
My personal opinion is that all you valuable time should go on porting Moi straight to OSX (emulation systems dont do it for me), but then again I am only one user.

> My personal opinion is that all you valuable time should go
> on porting Moi straight to OSX (emulation systems dont do it for
> me), but then again I am only one user.

Hi yannada, the problem is that it is such a large amount of work that it is hard for me to schedule it.

Doing that would mean freezing MoI in its current state for about a year or so (possibly longer) while all my effort went to just that one project.

Choosing between that and adding a year's worth of modeling features to MoI, right now I have prioritized working on modeling features and adding new functionality instead of porting.

- Michael

I really don't see why everybody is so concerned with having Mac version. All of the new Mac's can run as PC anyway. And i think most people will upgrade to new systems before Michael could port Moi to Mac. And during that time, Moi's growth will suffer... I think it would be a big mistake to slow down development of the PC version. The best hope is to wait for someone to knock on Michael's door with a ported version in hand. This is what happened to McNeel, who always said they will not make a Mac version of Rhino...

jonah

hi Micheal, sorry i think you miss understood me.
What I meant, was if and when you spent time on Mac OSX it should be towards a native application support.
Anyway all I want to know is that Micheal is open to support other platforms like Mac.

<The best hope is to wait for someone to knock on Michael's door with a ported version in hand. This is what happened to McNeel, who always said they will not make a Mac version of Rhino...

Oh man I HOPE SO
I am one of the many Beta RhinoOSX testers and i must say it comes along well BUT Moi is ADDICTIVE.

It is true that modern macs can run pc apps but its kind of overkill installing gb's of windows for a couple of hundred mb's of apps that we may want to run on our macs.

It doesn't affect me so much as I still own more pc's than macs but that will soon change for me and all of my associates in the near future who have also made the choice to move to macs.

Either way I am still looking forward very much to the release of Moi.

Cheers

Mike R

Hi Mike - I definitely realize that for a Mac owner a native Mac version would be best.

But it is a huge amount of work for me to make that happen. I just simply do not have the time available to accomplish it...

I wish I could make MoI do everything that every person wanted, but I can't.

- Michael

Just a heads-up. I'm running the latest build of Parallels (5580) and moi displays fine in the split (quad) view. If I switch to a single view like TOP I get a white window. So as long as I stay in the quad view, everything is fine.

Thanks Paul, that's good to know, that's quite a bit of progress. Maybe it won't be too much longer until they have the final kinks worked out.

Please post here again if you see any more improvements.

- Michael

jbshorty: the problem about installing/using bootcamp on Mac or any virtualization solution like VMware or Parallels, is that you must install windows and own a windows licence to do that. Then, it's no more the same price at the end for the customer (MoI+Windows). And if I'm not wrong, the low end version of Vista are not compatible (from a license point of view) with the virtualization.

About the Mac release itself, a native release is always better, especially on graphic software like MoI. I also understand the Michael point of view. The development of Amapi on Mac was always a problem and was big "time eater" (Yes, I was from the Amapi Dev team). Even if the mac userbase is growing very fast, Michael will have more customers on PC and since he is alone, it's better for him to focus on one development.

I am confirming that MOI runs on Parallels for Mac build 5570 (in Leopard). Others may have already confirmed this, but I couldn't find any. So the Direct3D thing on a virtualized Mac is a non-issue as far as I can tell. It still isn't as good as a native app, but it does mean that those people who run a virtualized Window to run things like Rhino anyway (like me) will be able to rock MOI. Sweet.

FYI re: Windows licensing costs: our students get Windows for $30, which we require that they install on their mandatory Macbook Pro laptops. We haven't, yet, required Parallels, but that may be coming at some point.

_P

I stumble across that @ Rhino OSX Forum and it makes me wonder, would that be the case this MOI as well?


>eric_m
Seems like it could almost just be an easy port over from windows.



The time, effort and expertise required to produce a version of Rhino for the Mac may only be fully understood by a software programmer.

One of the biggest problems is that not everything in Windows has a OSX counterpart. Yes, the Rhino core complies pretty well under OSX, but anything GUI/interface (like toolbars, menus, mouse actions, dialogs ...) all have to be rewritten for the Mac OS.

In addition, RhinoScript for the PC uses Microsoft's Active Scripting technology. Because Microsoft does not provide Active Scripting for the Mac, RhinoScript is not available on the Mac platform. For Plug-ins to work on the Mac, they will require that their 3rd party libraries have Mac binaries available. If the providers for these libraries do not compile their code for the Mac, the plug-in will not be available on the Mac.

Here is a little fun trivia. Rhino was first born an AutoCAD plugin called AccuModel back about 1994. Because we did not have control over the ever changing AutoCAD video interface, Rhino development was moved to a stand alone Windows product. For the first five versions of Rhino, all we had on staff were Windows programmers. Then Marlin volunteered to help us out and the Mac alpha came on line. Rhino/Mac history is now in the making.

Hope this helps.
Mary Fugier
Robert McNeel Technical Support

Is MOI using the some Scripting technology as Rhino and if not which one? Is it available on the Mac platform?

Thanks in advance and sorry for all the questions, is just I am trying to understand (my name is dummy).

Hi yannada, MoI is also currently using Microsoft's Active Scripting mechanism to run its scripts.

Microsoft's Active Scripting system kind of provides an overall harness and the actual scripts are run by different scripting engines which can implement different scripting languages.

At some point in Rhino's development (I guess starting with v3?) they decided to only support the VBScript engine for Rhino scripts. One problem with this is that VBScript is a proprietary Microsoft language, as far as I know there are no portable implementations of a VBScript interpreter that can run that script code in a non-Microsoft environment. So that decision kind of caused an extra roadblock for porting Rhino.

For MoI, I have written all the scripts using the JavaScript language instead. JavaScript is an open standard language, and there are various different interpreters available that can run .js code on different operating systems.

So for MoI scripting language support itself is not such a big porting issue.

However, that does not mean that it will be easy to port MoI - it only means that there probably isn't an issue with this one specific thing.

There are still plenty of other issues that make it difficult to port MoI anytime soon aside from this.

- Michael

and it's not so difficult to found anywhere somebody for lend a Pc for some minutes ;)

>For MoI, I have written all the scripts using the JavaScript language...COOL

Thank for you prompt answer, learnig every day.