StvDee

Can any kind of Java program be transferred in a mxj object? (with the appropriate modifiations of course)

Is there any limitation that mxj cant handle vs Java? (i.e. library issues)

Hi exps!
Can any kind of Java program be transferred in a mxj object? (with the appropriate modifiations of course)

mxj-vs-java-apps

> Can any kind of Java program be transferred in a mxj object? (with the appropriate modifiations of course)

> Is there any limitation that mxj cant handle vs Java? (i.e. library issues)

>> Is there any limitation that mxj cant handle vs Java? (i.e. library 

Are there not still oddities to do with AWT playing nicely from within Max?

Ben Nevile wrote:
>> Is there any limitation that mxj cant handle vs Java? (i.e. library 
>> issues)
>
> I can't think of one!

> Are there not still oddities to do with AWT playing nicely from within Max?

Oh yeah, I totally forgot about that part of the Java world. I

haven't done any programming in that domain, so I only know that

Topher and Joshua spent many many hours getting things like the

Oh yeah, I totally forgot about that part of the Java world.  I
haven't done any programming in that domain, so I only know that
Topher and Joshua spent many many hours getting things like the
quickie class to work.

There are some weird things with swing on os x

A lot of the weird things can be avoided by following

sun's guidelines in terms of dispatching appropriate

quickie didnt take long at all to get working.

getting the AWT to work at all on os x was what

took such a long time. This was primarily dude

to the fact that AWT/swing uses cocoa and Max/MSP

is a carbon app. Getting them to play nicely with each

other took a lot of experimenting since there was

no documentation on getting java to work in

carbon. Carbon and cocoa have their own event

BTW, joshua finally tracked down the bug which

was preventing quickie from properly reporting

errors and the shell object from working. It was

some legacy code in the systhread API. As of

max 4.6.3 we should see quickie working again

To make a long story short though Ben is right.

Most java things should work fine within mxj with

the exception that some swing stuff may act funny

on OS X and may take some hacking around to get it

On Feb 24, 2007, at 09:35 AM, Ben Nevile wrote:

>> Are there not still oddities to do with AWT playing nicely from 

> Oh yeah, I totally forgot about that part of the Java world. I

> haven't done any programming in that domain, so I only know that

> Topher and Joshua spent many many hours getting things like the

It actually isn't all that bad.
There are some weird things with swing on os x
but it isn't so bad on windows.
A lot of the weird things can be avoided by following
sun's guidelines in terms of dispatching appropriate
things from the swing event thread.

quickie didnt take long at all to get working.
getting the AWT to work at all on os x was what
took such a long time. This was primarily dude
to the fact that AWT/swing uses cocoa and Max/MSP
is a carbon app. Getting them to play nicely with each
other took a lot of experimenting since there was
no documentation on getting java to work in
carbon. Carbon and cocoa have their own event
loops. This is the root of the problem.

BTW, joshua finally tracked down the bug which
was preventing quickie from properly reporting
errors and the shell object from working. It was
some legacy code in the systhread API. As of
max 4.6.3 we should see quickie working again
on MacTel. Thanks to Joshua!!

To make a long story short though Ben is right.
Most java things should work fine within mxj with
the exception that some swing stuff may act funny
on OS X and may take some hacking around to get it
to work properly.

>> Are there not still oddities to do with AWT playing nicely from  
>> within Max?
>
> Oh yeah, I totally forgot about that part of the Java world.  I
> haven't done any programming in that domain, so I only know that
> Topher and Joshua spent many many hours getting things like the
> quickie class to work.
>
> Ben


On Feb 24, 2007, at 9:35 AM, Ben Nevile wrote:

I think that the biggest issue with this stuff is making sure it's 

started on some thread other than the main thread. So if you open a 

window or do something which initializes AWT, launch a separate 

thread to do so. On windows this works without issue, but on Mac 

there is some subtle interplay between Cocoa vs. Carbon event loops.

>> Are there not still oddities to do with AWT playing nicely from  
>> within Max?
>
> Oh yeah, I totally forgot about that part of the Java world.  I
> haven't done any programming in that domain, so I only know that
> Topher and Joshua spent many many hours getting things like the
> quickie class to work.

I think that the biggest issue with this stuff is making sure it's  
started on some thread other than the main thread. So if you open a  
window or do something which initializes AWT, launch a separate  
thread to do so. On windows this works without issue, but on Mac  
there is some subtle interplay between Cocoa vs. Carbon event loops.

On 24 Feb 2007, at 19:18, topher lafata wrote:

> BTW, joshua finally tracked down the bug which

> was preventing quickie from properly reporting

> errors and the shell object from working. It was

I wonder if this is related to the problems I've had getting embedded 

file-based databases like HSQL DB and Derby to work on MacIntel?

> BTW, joshua finally tracked down the bug which
> was preventing quickie from properly reporting
> errors and the shell object from working. It was
> some legacy code in the systhread API.

I wonder if this is related to the problems I've had getting embedded  
file-based databases like HSQL DB and Derby to work on MacIntel?

On Feb 24, 2007, at 11:25 AM, Nick Rothwell wrote:

> I wonder if this is related to the problems I've had getting 

> embedded file-based databases like HSQL DB and Derby to work on 

This could easily be the case if it uses a secondary process and 

relies upon a file stream like stderr or stdout to communicate 

Either way, you should try again with 4.6.3, and let us know if it 

> I wonder if this is related to the problems I've had getting  
> embedded file-based databases like HSQL DB and Derby to work on  
> MacIntel?

This could easily be the case if it uses a secondary process and  
relies upon a file stream like stderr or stdout to communicate  
information.

Either way, you should try again with 4.6.3, and let us know if it  
does or doesn't solve your issues.

On 24 Feb 2007, at 19:34, Joshua Kit Clayton wrote:

> Either way, you should try again with 4.6.3, and let us know if it 

Will do. (I see that a Java update came down the wire a few days ago 

> Either way, you should try again with 4.6.3, and let us know if it  
> does or doesn't solve your issues.

Will do. (I see that a Java update came down the wire a few days ago  
as well.)

mxj vs Java apps ?