Re: [Bugs-r-devel] [R] R2WinBUGS and calling WinBUGS in Crossover MAC BETA

[Kenneth B. <kb...@tc...>]

OK - the plot thickens...

open Applications/CrossOver/WinBUGS14.app /par script.txt

does *not* work because Apple did not program its magical "open" command 
(which is designed to be the command-line equivalent of double-clicking 
an icon) to allow command-line arguments following the name of the program.

There is an open-x11 equivalent for opening X11 apps, and the lack of a 
command line seems to have made this almost unusable for many people.  I 
  found therefore that someone had written a version which allowed 
arguments:

http://xanana.ucsc.edu/Library/init/zsh/man/html/open-x11.html

but I could not find any equivalent for the plain "open".

A workaround would be to hard-wire the excecution of script.txt  into 
WinBUGS14.app itself, either through Mac OS/X or something in WinBUGS...

Ken



Gorjanc Gregor wrote:
> Rodney talked about wine - DarWINE, you talk about CrossOver. So, Mac
> "just knows" which emulator needs to be started. Sounds a bit magical. How
> is this done? We need to know, if we want to enable this in R2WinBUGS. 
> Additionally, what happens, if there are both DarWINE and CrossOver installed.
> 
> Kenneth & Rodney, can you also try to start {Win,Open}BUGS with script option 
> i.e.
> 
> open Applications/CrossOver/WinBUGS14.app /par script.txt
> 
> Thanks, Gregor
> 
> -----Original Message-----
> From: Kenneth Benoit [mailto:kb...@tc...]
> Sent: Wed 2006-12-13 07:09
> To: Rodney Sparapani
> Cc: Rodney Sparapani; Gorjanc Gregor; Ben Bolker; bug...@li...
> Subject: Re: [R] R2WinBUGS and calling WinBUGS in Crossover MAC BETA
>  
> Thanks Rodney, that so simple "mac" solution worked:
> 
> open Applications/CrossOver/WinBUGS14.app
> 
> starts Crossover and opens WinBUGS.  So if I can pass that argument to 
> R2WinBUGS then it seems like it should work!
> 
> Ken
> 
> 
> Rodney Sparapani wrote:
>> Ahha... 
>> Finally, something that I can answer.  If I'm at the terminal command 
>> prompt, and type:
>> open /Applications/OpenBUGS\ 2.2.0/winbugs.exe
>> then, first DarWINE starts, then XDarwin or whatever it is called, and then
>> OpenBUGS!!!
>>
>> The Fonz gives Richie motorcycle riding advice
>> Fonzie:  ... where a helmet and never smile!
>> Richie:  Why not?
>> Fonzie:  You get bugs in your teeth
>>
>>
>>
>> -----Original Message-----
>> From: Kenneth Benoit [mailto:kb...@tc...]
>> Sent: Tue 12/12/2006 4:42 PM
>> To: Rodney Sparapani
>> Cc: gre...@bf...; Ben Bolker; 
>> bug...@li...
>> Subject: Re: [R] R2WinBUGS and calling WinBUGS in Crossover MAC BETA
>>
>> Hi - That, plus the difficulty I encountered in getting Darwine to work
>> at all, led me to remove it and to install Crossover Mac Beta instead.
>> It works just great with WinBUGS 1.4, running it quickly and completely
>> *except* that first I have to start Crossover and then choose the
>> installed WinBUGS from the programs menu to start it.  (and then it pops
>> right up and runs fine!)
>>
>> So the only question seems to be: how to get it started from the command
>> line which R2WinBUGS can call??
>>
>> Ken
>>
>>
>> Rodney Sparapani wrote:
>>  >
>>  >> Rodney (can you please join to bugs-r development list) reported that he
>>  >> was able to start OpenBUGS under Intel Mac, but not WinBUGS. Maybe he
>>  >> can say more.
>>  > Hi Guys:
>>  >
>>  > Couldn't really follow the discussion.  But, WinBUGS does not work with
>>  > DarWINE, although, OpenBUGS does.  I'm using v. 0.9.21 DP, but this 
>> hasn't
>>  > changed going back to about v. 0.9.10 DP.  And, before
>>  > that OpenBUGS doesn't work either.
>>  > I've spent a lot of time trying to
>>  > figure it out, but it's madness.  WINE and R are written, more or less,
>>  > from the Linux standpoint.  Compiling R even on industry-standard
>>  > Solaris can be tricky and WINE on Solaris is virtually impossible.
>>  > Mac OS X adds its own wrinkles.  Many of the infrastucture that R 
>> requires
>>  > are already there, but often R chooses to install a slightly different
>>  > compiler and/or library and you are pulling out your hair trying to
>>  > figure out
>>  > what you are supposed to do and why.  Of course, a professional Mac
>>  > developer would figure this out in a couple of minutes, but we
>>  > statisticians
>>  > must suffer for our art :)
>>  >
>>  > And to add insult to injury, I tried to subscribe to the mailing list
>>  > on sourceforge, but I couldn't figure it out.  There is this obnoxious
>>  > adware that sourceforge employs that covers the search dialog.  No
>>  > matter what I did in Firefox 2.0, I couldn't get past it.
>>  >
>>  > Rodney
>