From: nescivi ()
Date: May 18, 2008
Subject:
Re: Building Sclang Executable on OS X (leopard or
Hiho,
On 5/17/08, blackrain wrote:
> Hi Marije,
> Sorry I missed your post.
>
> We could do this in OSXPlatform:startup:
>
> startup {
> if ( this.hasFeature( \emacs ) or:{ this.hasFeature('CocoaDocument') }) {
> Document.implementationClass.startup;
> };
>
> and then,
> 1 - The user would have to manually disable the CocoaDocument class
> (as in place the file in a 'test' folder) if they want to use the
> library with sclang. Be it stand alone or in scel.
> but...
> 2 - The method creates the servers windows and the interpreter will
> whine if there is no views server so these would still have to be
> commented out:
>
> startup {
> if ( this.hasFeature( \emacs ) or:{ this.hasFeature('CocoaDocument') }) {
> Document.implementationClass.startup;
> };
> // make server window
> // Server.internal.makeWindow;
> // Server.local.makeWindow;
> this.loadStartupFiles;
> }
>
> I dont see a better way to have this working clean w/o user mods.
the windows could only be made if Cocoa is active.
> Currently we dont have a way to tell if it is the app, scel, or
> nothing at all (as in sclang from the command line) that is actually
> compiling the library.
well...
for scel we do have this actually, since if the FIFO with Emacs is not
created the feature \emacs is not set.
there should be a way for the app to define something somewhere that
the lang can retrieve. isn't the app a separate .cpp file, in which
this could be done?
sincerely,
Marije
>
> cheers,
>
> x
>
> On Mon, May 12, 2008 at 1:57 PM, nescivi wrote:
>> Hiho,
>>
>> On Monday 12 May 2008 11:49:02 scacinto wrote:
>>> Hey x,
>>> This actually fails with the same error. I must be doing something
>>> wrong in the build process, as I followed the rest of your instructions
>>> to
>>> a tee (though I'm not sure what the problem was with the '\emacs \emacs'
>>> thing... was that something wrong on my end? (I haven't even installed
>>> emacs, let alone called it for anything... perhaps that's the
>>> problem?...)
>>
>> The \emacs feature is set when the Emacs class has succesfully created a
>> command FIFO between emacs and SC.
>> So I guess, OSXPlatform should also have this bit in *startup, just like
>> LinuxPlatform:
>>
>> if ( this.hasFeature( \emacs ) ) {
>> Document.implementationClass.startup;
>> };
>>
>> (or maybe that should be moved to Main, assuming windows can theoretically
>> also use the emacs interface).
>>
>> sincerely,
>> Marije
>> _______________________________________________
>> sc-users mailing list [EMAIL REMOVED] >> http://lists.create.ucsb.edu/mailman/listinfo/sc-users
>>
>
_______________________________________________
sc-users mailing list [EMAIL REMOVED] http://lists.create.ucsb.edu/mailman/listinfo/sc-users