Home » Archived » Visual Editor (VE) » VE and OS X
| VE and OS X [message #84656] |
Thu, 24 March 2005 01:35  |
Eclipse User |
|
|
|
Hi,
can anybody give me an advice if VE runs on OS X? And if so, how to get
it running.
I tried Eclipse 3.0.1 with GEF 3.0.1, EMF 2.0.1 which gave me the
following error in .log when trying to create a visual class:
!MESSAGE Failed to execute runnable (java.lang.InternalError: Can't
start the AW
T because Java was started on the first thread. Make sure
StartOnFirstThread is
not specified in your application's Info.plist or on the command line)
In Eclipse's Info.plist there is nothing about StartOnFirstThread and I
didn't find any Info.plist for Java.
Then I tried Eclipse 3.1M3 which gave me a NullPointerException when
trying a visual class.
Can anybody help? Any advice is welcome.
Thanks in advance, regards
Thomas P. Niesel
|
|
| |
| Re: VE and OS X [message #84696 is a reply to message #84683] |
Thu, 24 March 2005 07:20  |
| Eclipse User |
|
|
|
Hey Joe (sorry, couldnt help to cite Jimi Hendrix),
> It isn't a supported platform at the moment although this is just
> through lack of time against other tasks being worked on.
:-((
> We'd love to
> have the VE running on OSX. Another issue is that the VE comitters are
> weak on OSX skills which is something we'd love to address, so if you or
> anyone else is prepared to help get VE running on OSX that'd be wonderful
Hm, I am working one year with OS X and mainly as a Network
administration tool, but I am an old C and Java programmer and architect
(C on AIX, Linux and Windows, Java on Linux and Windows). Even if I am
working as a network 'guru' (Novell NetWare, ZENWorks in a Citrix
Metaframe Environment) today, I think I am not too anxious to try to
help to get that beast running on OSX.
But before promising too much - where can I get informations about the
things to be done and the level of programming skill to do them?
>
>
> Interesting errors. What we had antipciated would be our biggest issue
> is the technique that we use to get an image of the SWT controls into a
> stream of raw pixels that we can render into a GEF figure.
Wow, that sounds interesting.
> The
> techniques we use for this involve JNI calls and are platform dependent,
> although at Eclipsecon we did talk to the Mac folks and hopefully opened
> a dialog to get some assistance in porting the Win API calls to their
> equivalent OSX platform calls.
>
> You however are using AWT (I think from your post) and we don't use any
> JNI for that so we should really have no good excuse for not working.
No, thats not right - I tried to create SWT visual classes and in this
special case a composite.
> The only excuse really is that we don't have a box to do development on,
> however you do which is cool
> so we might be able to figure stuff out
> just by looking at stack traces and giving you fixes to try out.
I will do my very best.
>
> Can you please supply the full contents of the .log file for the
> scenario you are using ? Clear this file out (i.e. delete it) before
> you scenario and then open the VE and post this file as an attachment to
> a bugzilla please.
OK, I will set up a separate Eclipse 'sandbox' for that. Perhaps I get
that into bugzilla today, but if not, it will take a while, because its
eastern (the family, you know...).
> Also - showing my ignorance of AWT on OSX what is
> the issue about threading ?
If I only knew... I will try to figure out a few details about that at
Apple Developer Connection of which I am (the simplest form of) a member.
> The VE starts a separate JVM for every open
> editor (so it has somewhere it can host the actual widgets within) and I
> could talk you through how this occurs and ask you several things to
> tweak if you feel up to it.
Well, thats an idea - should we do this coram publico in the newsgroup
or by personal mail?
> Before this however you would need to set
> up a full IDE development environment for Eclipse - Attach to the
> repository /home/tools and host name dev.eclipse.org and user id of
> anonymous with password left blank. Then expand HEAD in the CVS
> repositories view and check out ve-dev-base. After you have done this
> sniff around the class FreeFormComponentProxyHost. This is responsible
> for creating the target VM class that builds the first AWT dialog on the
> target VM.
OK, I try to do that today also, but if i cant get it done, see above
(eastern, family and so on...)
>
> Best regards and many thanks,
Not for that. Eclipse an VE are great work and worth the effort and
hopefully my knowledge is not too small to get the thing working.
Best regards
Thomas P. Niesel
|
|
| | | | |
| Re: VE and OS X [message #606063 is a reply to message #84656] |
Thu, 24 March 2005 04:46 |
| Eclipse User |
|
|
|
Hi Thomas,
> can anybody give me an advice if VE runs on OS X? And if so, how to get
> it running.
It isn't a supported platform at the moment although this is just
through lack of time against other tasks being worked on. We'd love to
have the VE running on OSX. Another issue is that the VE comitters are
weak on OSX skills which is something we'd love to address, so if you or
anyone else is prepared to help get VE running on OSX that'd be wonderful
> I tried Eclipse 3.0.1 with GEF 3.0.1, EMF 2.0.1 which gave me the
> following error in .log when trying to create a visual class:
>
> !MESSAGE Failed to execute runnable (java.lang.InternalError: Can't
> start the AW
> T because Java was started on the first thread. Make sure
> StartOnFirstThread is
> not specified in your application's Info.plist or on the command line)
>
> In Eclipse's Info.plist there is nothing about StartOnFirstThread and I
> didn't find any Info.plist for Java.
>
> Then I tried Eclipse 3.1M3 which gave me a NullPointerException when
> trying a visual class.
Interesting errors. What we had antipciated would be our biggest issue
is the technique that we use to get an image of the SWT controls into a
stream of raw pixels that we can render into a GEF figure. The
techniques we use for this involve JNI calls and are platform dependent,
although at Eclipsecon we did talk to the Mac folks and hopefully opened
a dialog to get some assistance in porting the Win API calls to their
equivalent OSX platform calls.
You however are using AWT (I think from your post) and we don't use any
JNI for that so we should really have no good excuse for not working.
The only excuse really is that we don't have a box to do development on,
however you do which is cool so we might be able to figure stuff out
just by looking at stack traces and giving you fixes to try out.
Can you please supply the full contents of the .log file for the
scenario you are using ? Clear this file out (i.e. delete it) before
you scenario and then open the VE and post this file as an attachment to
a bugzilla please. Also - showing my ignorance of AWT on OSX what is
the issue about threading ? The VE starts a separate JVM for every open
editor (so it has somewhere it can host the actual widgets within) and I
could talk you through how this occurs and ask you several things to
tweak if you feel up to it. Before this however you would need to set
up a full IDE development environment for Eclipse - Attach to the
repository /home/tools and host name dev.eclipse.org and user id of
anonymous with password left blank. Then expand HEAD in the CVS
repositories view and check out ve-dev-base. After you have done this
sniff around the class FreeFormComponentProxyHost. This is responsible
for creating the target VM class that builds the first AWT dialog on the
target VM.
Best regards and many thanks,
Joe Winchester
|
|
|
| Re: VE and OS X [message #606068 is a reply to message #84683] |
Thu, 24 March 2005 07:20 |
| Eclipse User |
|
|
|
Hey Joe (sorry, couldnt help to cite Jimi Hendrix),
> It isn't a supported platform at the moment although this is just
> through lack of time against other tasks being worked on.
:-((
> We'd love to
> have the VE running on OSX. Another issue is that the VE comitters are
> weak on OSX skills which is something we'd love to address, so if you or
> anyone else is prepared to help get VE running on OSX that'd be wonderful
Hm, I am working one year with OS X and mainly as a Network
administration tool, but I am an old C and Java programmer and architect
(C on AIX, Linux and Windows, Java on Linux and Windows). Even if I am
working as a network 'guru' (Novell NetWare, ZENWorks in a Citrix
Metaframe Environment) today, I think I am not too anxious to try to
help to get that beast running on OSX.
But before promising too much - where can I get informations about the
things to be done and the level of programming skill to do them?
>
>
> Interesting errors. What we had antipciated would be our biggest issue
> is the technique that we use to get an image of the SWT controls into a
> stream of raw pixels that we can render into a GEF figure.
Wow, that sounds interesting.
> The
> techniques we use for this involve JNI calls and are platform dependent,
> although at Eclipsecon we did talk to the Mac folks and hopefully opened
> a dialog to get some assistance in porting the Win API calls to their
> equivalent OSX platform calls.
>
> You however are using AWT (I think from your post) and we don't use any
> JNI for that so we should really have no good excuse for not working.
No, thats not right - I tried to create SWT visual classes and in this
special case a composite.
> The only excuse really is that we don't have a box to do development on,
> however you do which is cool
> so we might be able to figure stuff out
> just by looking at stack traces and giving you fixes to try out.
I will do my very best.
>
> Can you please supply the full contents of the .log file for the
> scenario you are using ? Clear this file out (i.e. delete it) before
> you scenario and then open the VE and post this file as an attachment to
> a bugzilla please.
OK, I will set up a separate Eclipse 'sandbox' for that. Perhaps I get
that into bugzilla today, but if not, it will take a while, because its
eastern (the family, you know...).
> Also - showing my ignorance of AWT on OSX what is
> the issue about threading ?
If I only knew... I will try to figure out a few details about that at
Apple Developer Connection of which I am (the simplest form of) a member.
> The VE starts a separate JVM for every open
> editor (so it has somewhere it can host the actual widgets within) and I
> could talk you through how this occurs and ask you several things to
> tweak if you feel up to it.
Well, thats an idea - should we do this coram publico in the newsgroup
or by personal mail?
> Before this however you would need to set
> up a full IDE development environment for Eclipse - Attach to the
> repository /home/tools and host name dev.eclipse.org and user id of
> anonymous with password left blank. Then expand HEAD in the CVS
> repositories view and check out ve-dev-base. After you have done this
> sniff around the class FreeFormComponentProxyHost. This is responsible
> for creating the target VM class that builds the first AWT dialog on the
> target VM.
OK, I try to do that today also, but if i cant get it done, see above
(eastern, family and so on...)
>
> Best regards and many thanks,
Not for that. Eclipse an VE are great work and worth the effort and
hopefully my knowledge is not too small to get the thing working.
Best regards
Thomas P. Niesel
|
|
|
| Re: VE and OS X [message #606073 is a reply to message #84683] |
Thu, 24 March 2005 12:25 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
AS I recall, in OSX the UI thread MUST be the first thread (i.e. main
thread). Java needs to be started on a second thread. How this is done
in OSX land, I don't know. I don't know what an Info.plist is. It may be
something that is required in OSX but we aren't using one. We are doing
a simple Runtime.exec() under the covers and I don't think there is any
Info.plist involved.
--
Thanks,
Rich Kulp
|
|
|
| Re: VE and OS X [message #606077 is a reply to message #84656] |
Thu, 24 March 2005 18:02 |
| Eclipse User |
|
|
|
Hi Thomas,
FYI: the bugzilla report for tracking the status of VE's Mac OS X
support is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=47716 The
VE should work with Swing/AWT ok if you're developing with one of the
3.1 milestones. However no real work on the SWT screen scraping
implementation on OS X has started yet (other than some research into
the Carbon APIs that may be useful). If I recall correctly, SWT apps
need to be launched with a special java_swt app in order to work
properly. My guess is that we're not using this app when launching the
remote vm to work with SWT, which is causing that error you're receiving.
If you have any esperience with Carbon and the graphics system under OS
X (or would like to learn :) ) it'd be very helpful to try to get some
screen scraping code for SWT written and running on OS X.
- Jeff
|
|
|
| Re: VE and OS X [message #606079 is a reply to message #84726] |
Fri, 25 March 2005 07:21 |
| Eclipse User |
|
|
|
Hi Jeff,
> If you have any esperience with Carbon and the graphics system under OS
> X (or would like to learn :) )
I really like to learn about Carbon an the graphics system of OS X.
> it'd be very helpful to try to get some
> screen scraping code for SWT written and running on OS X.
Give me a hint, where to begin.
Regards
Thomas
|
|
| |
Goto Forum:
Current Time: Mon Jun 23 16:14:52 EDT 2025
Powered by FUDForum. Page generated in 0.24879 seconds |
Home