This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Mac OS X is definitely a big force in Java development. Why is J2ME not supported by NB? I love the new mobility modules. When will we see it supported on the mac? If someone is already working on it, I would be glad to help out in the effort.
I'm afraid that it's not matter of NetBeans but WTK which is not available for MacOX.
-mobility pack is available only on win and linux for 4.0 (the same plan for 4.1). -I'm changing it to enhancement and increasing priority -you;ll be informed when distribution for mac will be included in plans
unfortunately there is no emulator (either WTK or anything else) for the MacOS/X platform at the moment.
Hello, I just wanted to pint out that some thrid party develppers have created an emulator in java that runs on mac perfectly. Eclipse also has a third part plugin which is cross platform that supports creation of midlets, so i see this as a feasble idea to incoperate it on mac. thank you.
mPowerPlayer is a J2ME emulation for OS X. Have a look at http://mpowerplayer.com/sdk.jsp
We know about mpowerplayer and we are in touch with the author. The possibility of integration is being investigated.
Any news along that line ? -- Benoit Garbinato
still being investigated
Still nothing new on this, for 6.X perhaps?
I'm very sorry to say no progress. There are no technical issues. Actually this may help a little bit: http://blog.sun.com/roller/page/lukas/20051020
Yes, I have it running niceley on my PowerBook. But it would be nice if there were a ZIP distribution of the Mobility Pack, as mentioned here: http://blogs.sun.com/roller/page/lukas? entry=what_you_look_forward_in
moving to mobility component
*** Issue 80891 has been marked as a duplicate of this issue. ***
I understand that MobilityPack port to MacOS X might not seem as viable business decision, but please take in account what a message about the "cross-platform ability" of Java on the desktop it sends to the public. Even Sun, the creator of the platform isn't able to create application that runs across supported platforms. IMO Mobility pack should be supported everywhere even if you have to install the emulator (MPP) manually as the WTK is not available. Why WTK is still a non Java application is beyond me either...
doesn't seem to be issue anymore with the ZIP builds. please note: 1, there are only two supported/tested platforms for now - windows+linux. 2, the bundled WTK works only on the supported platform 3, user on _unsupported_ platform can use the zip distribution, link to how-to use it is bellow 4, user on _unsupported_ platform has to use their own emulator platform How-to use mobility on _unsupported_ platform. E.g. Mac OS http://wiki.netbeans.org/wiki/view/MobilityFromZipToNB No comment for the WTK, they upset me as well...
I tried to install the mobility pack following instructions in Wiki to NB 5.5 but I seem to be out of luck. I tried either daily build for NB6 (Mobility 8) and old Mobility 7.2 that works in 5.0 but I can get it up and running in 5.5 All I can do is get it listed in modules list (in Netbeans Platform Manager) but it is not either in Java Platforms and New Project. Am I using wrong version of Mobility Pack ? Is there a version that should work with NB 5.5 ? Regarding WTK : Is there any way for the community to help make next version of WTK in Java ? Thanks.
I would say that analyzing the amount of web traffic that Lukas receives in his tutorial would be rather good meter of the interest that such support could raise. Would that be possible? Even though there are workarounds for this issue, it's rather tricky to actually get the thing up-and- running: - I'm sure that many developers forget about the "etc/clusters" file. - Not to say how many have actually registered and read the forum post at http://developer.mpowerplayer.com/index.php?topic=216.0 in order to get the emulator debugging the code. - Thankfully I have a linux x86 box where I can run the WTK profiler, because there is no way to get mpowerplayer profiling with Netbeans. - It would be nice to find out if the mpowerplayer would consider going open if a special request is made from the Netbeans community. They could even do their own dual-licensing 'a la' mySql or J2mePolish (seems more appropriate) in order to keep making profits. kind regards, Jaume
I really think Netbeans needs to offer posibilities and Mac OS X is one of the best development environments. I also believe that Netbeans should make their own J2ME (CLDC and CDC profiles) emulator in Java. MPwerPlayer is fine but it is unbeliavable there is no other J2ME emulator in Java. And I cannot understand why not to make the others emulators in Java in the first place. The same for all the Mobility platforms. Computers are extremely more powerful than a Cell Phone or a Palm, Java code is perfectly fine emulating them. Why to have different emulators for different platforms?
I really think Netbeans needs to offer posibilities and Mac OS X is one of the best development environments. I also believe that Netbeans should make their own J2ME (CLDC and CDC profiles) emulator in Java. MPowerPlayer is fine but it is unbeliavable there is no other J2ME emulator in Java. And I cannot understand why not to make the others emulators in Java in the first place. The same for all the Mobility platforms. Computers are extremely more powerful than a Cell Phone or a Palm, Java code is perfectly fine emulating them. Why to have different emulators for different platforms?
As you probably all know mpowerplayer is based on http://www.microemu.org/ that is licensed under the LGPL so if anyone has the time to do something similar, I am all for it, M3G is done via lwjgl, and there is a bunch of other functionality that is added via third party libraries that are mostly open sourced, so it's a wrapp wrapp wrapp project, though it would be nice if the good fellas of mpowerplayer dual licensed it, i will sign up any petition ;) There are many places that the NB mobility team should be devoting more time...
I also agree. I think that support for the mobility pack is needed in OS X.
I really think Netbeans needs to offer posibilities and Mac OS X is one of the best development environments.
Agree, NetBeans is a great IDE, works perfectly on Mac. I really bored to develop J2ME projects separately under windows emulation
I too agree Mac OS X version of Mobility pack would be great. Saying that, I also say that Android SDK already works on Mac OS X so the window of opportunity for Sun is closing slowly :) There are number of lessons that can be learned from the Google's new SDK : platform is really consistent, optional parts are kept at real minimum and makes sense. The emulator for Android is considered identical to implementation in final phones and developers are advised that once they got thier code running in the emulator, they can pretty much expect it will work in real thing as well..if not, it is considered problem of the implementation in the phone, not problem of the application. What a contrast to that joke also known as JavaVerified (=you pay for getting your app tested on devices although those devices should run the aplication by default). All together, it seems Android is clearly superior to J2ME from the developers point of view. Hope Sun will learn their lesson from that and we'll soon will see brand new cross-platform version of WTK written in Java.
Mac users, it is time to celebrate. fixed by http://hg.netbeans.org/main/rev/c53684b3c855 1, mpowerplayer can be add as platform on Mac 2, there is no installer - you can either download NB in zip or update your NB IDE with Mobility functionality with Tools > Plugins for more details http://blogs.sun.com/lukas/entry/mobility_on_leopard http://blogs.sun.com/jara/entry/en_improved_netbeans_pluginmanager http://bits.netbeans.org/download/trunk/nightly/latest/
That's not really what I call a resolved issue, considering that MPowerPlayer only implements one optional API: MMAPI-1.1 What about JSR89, 172, 179 and so many useful others?
then fill issue against the SDK itself. We are offering tools for development not the runtimes. Please, note that the mpp isn't part of the NB build at all. I'm really sorry but your complain is not relevant. It is like blaming NB that glassfish supports only EJB 2.0.
So much for me.
Unfortunately SDK manufactures don't pay much attention to Mac OS but If I see any kind of SDK working on Mac OS I'll be first to implement NB Mobility support for it.
Sadly enough, I think it is too late to conquer back developers working on the Mac platform when it comes to mobile devices. Everyone I know from this community, even those who were convinced by and are still using the J2ME platform, are now impatiently waiting for the iPhone SDK... Too bad it took Sun so long to realize that the Apple developer community might not be the biggest one, but it is certainly the most motivated and skilled when it comes to user experience. And as we all know, this is a crucial point when it comes to convince people to use advanced applications on mobile resource-limited devices.
> It is like blaming NB that glassfish supports only EJB 2.0. Hey! GlassFish supports EJB 3.0!
> It is like blaming NB that glassfish supports only EJB 2.0. > Hey! GlassFish supports EJB 3.0! It was metaphor.
v