Any one can tell me that how to Blackberry sdk installation with netbeans for Mobile application development
i am trying to plugin but not able to do .
I have used this tutorial in the past. You can ignore the part about J2ME Polish. Also, I think the Mobility Pack might come with new versions of Netbeans now (it didn't use to). Or, it's possible that in the Netbeans -> Tools -> Plugins menu, you might need to make sure the Java ME plugin is installed.
He references much older SDK versions, but as long as you download the newer JDE versions here (SDKs) from BlackBerry, the same basic instructions should work for you.
I've been using Netbeans less and less, and the BlackBerry Eclipse plugin more, in recent years, despite the fact that I like Netbeans better, as a general-purpose IDE. Unfortunately, you'll find that RIM is focused on Eclipse at this point.
But, you should still be able to use Netbeans if you like.
Related
Netbeans 8 works quite well with Grails. I can click New Project to create a new Grails project. Netbeans 8 can show the project with Domain, Controller, Views folders on the left nicely. I can even debug the project with breakpoint. Netbeans 8 only works well with Grails 2. But at lease it can show the project folder structures nicely with newer versions of Grails like 4 and 5.
Netbeans 14 is missing all of these with/without the default Groovy plugin. It can't even open a simple Helloworld Grails project I create using the grails create-app helloworld command.
I googled Netbeans and Grails but the posts were quite outdated from many years ago. They said to use the Netbeans 8 Groovy plugin.
Is there any updated way to setup Netbeans 14 to work with Grails?
I attached 2 pictures. One is how it looks with 14. The other is how it looks with 8.
Unfortunately, I think the answer to your question is that Netbeans 14 does not support Grails. It's tough to prove a negative, but there is very strong circumstantial evidence of that being the case:
If you go to the homepage for Apache NetBeans there is a Plugins menu entry,and clicking that yields a list of the 62 available plugins. If you search that list list for "Grails" nothing is returned, so there is no "official" plugin for Grails.
Within NetBeans 14, if you select Tools > Plugins and search the Installed and Available Plugins tabs for "Grails", nothing is returned.
If you review the "What's Changed" entries for NetBeans 14 there is no mention of Grails.
Note this comment from GeertJan Wielenga, Release Manager for Apache NetBeans in 2019 (emphasis mine): "I would recommend to keep the name at Groovy, because otherwise when we re-add support for Grails, we’ll need to call it ‘Groovy, Gradle, and Grails’. And anyway both Gradle and Grails derive from Groovy, so keeping the name Groovy makes sense."
Notes:
For some releases since NetBeans 8.2 it has been possible to add Grails support using the old 8.2 plugin (e.g. this answer), but the approaches were brittle, and did not offer any functionality beyond that available in NetBeans 8.2. I suppose you could try a similar workaround to get Grails running on NetBeans 14, as described in SO answers for other NetBeans releases, but stability might be an issue.
For what it's worth, Intellij IDEA provides a Grails plugin, though I haven't tried it.
Finally, Grails not working in NetBeans 14 should not be viewed as a NetBeans issue. Instead, it's a third-party plugin issue, and as far as I know there has been no development on the 8.2 plugin you are currently using for years. (That said, it would be helpful if the NetBeans documentation for each release formally stated any new functionality, and any functionality that was no longer supported, or no longer worked.)
I know that developing with Ruby on Rails in Windows is not always easy, and I read lots of complaints that it just isn't fully compatible with Windows.
Is grails the same? Does it matter whether I dev on Windows/Linux/OSX?
Thanks!
Use the OS that you prefer. I've been developing Grails apps on Windows at work (because I have to) for a few years. Outside of work I use Linux exclusively.
Where I am, people use Linux and Windows to develop in Grails. There has been no problem regarding OS specific stuff.
In fact you should be more concerned about the Java flavor and version you have (some linux distros have an open source implementation), and, of course, the Grails version.
My advices:
Pick any OS you want (I even use both on the same Grails project with no problems)
Try to use the Oracle JDK (for me openJDK is a bit slower)
Pick a Grails version and stick to it as much as you can (preferably don't change the version it can be painful to upgrade a project)
I developed Grails apps on Windows and Linux. IMHO, use the OS you'll be the most productive with and has the toolset you want. Linux is definitively more friendly to programmers in terms of available tools in general. Windows developer community is coming up with interesting project such as Chocolatey and Console2 among other things. I personally prefer Linux because it offers me a lot more to learn besides just learning Grails for example.
i am trying to setup the tidesdk in titanium studio but it won't work for some reason... Here is what i've done so far:
Downloaded Titanium Studio v2.1.2.201208301612 from appcelerator
Downloaded TideSDK v1.2.0.RC4 from tidesdk.org
Added the sdk in Titanium Studio like this: "Help > install specific
titanium sdk"
Basically i just followed the instructions from this: https://groups.google.com/forum/?fromgroups=#!topic/titanium-desktop-transition/wv6fiRD6Sbo
But the option to start a new desktop project won't come up. Is there something i am doing wrong or something?
I am using lion 10.7.4, according to this google group that shouldn't be a problem. Anyone's got any ideas?
Here are a couple of things to help you on your way:
Lion and Mountain Lion with Xcode 4.x are supported in the upcoming 1.3.0 but not 1.2.0.RC4. 1.2.0.RC4 will work fine with Snow Leopard 10.6.x on Xcode 3.x. Another possibility in the short term is to consider developing on either a Windows 7, or Ubuntu 11.04 virtual machine until the 1.3.0-beta has released. This release is expected very soon and provides updates to core libraries and offers support for current operating system versions of OSX, Windows and Linux.
Code you write in 1.2.0.RC4 will work fine in 1.3.0 since there are no API changes. The only change will be in the JavaScript namespace. In 1.3.0, the JavaScript namespace for the future will use 'Ti' as opposed to 'Titanium'. By setting a global variable in your code, you can start using 'Ti' to begin with.
var Ti = Titanium;
As far as Titanium Studio, unfortunately Appcelerator dropped the desktop support but have revived it. They have come out with an update that is reported to work:
http://preview.appcelerator.com/appcelerator/studio/desktop/update/beta/
If your run into any issue, an alternative is to download TiDev Community:
http://api.appcelerator.net/p/pages/app_page?token=m4rZLSv6
TiDev Community is really reaching the end of its life cycle but it will work for creating in running your apps in the short term.
The TideSDK team has a new app under development called TideSDK Builder. TideSDK Builder will provide the basics of creating, running and packaging your apps. It will also feature scaffolds for kickstarting your app projects. A new tidebuilder CLI will also be available with comparable functionality. We are hoping to bundle these for the official release of 1.3.0 that is targeted for the end of September.
Appcelerator has provided a Titanium Studio SDK. The TideSDK team is exploring this to see that Titanium Studio IDE can continue for the future.
One last thing to keep in mind is that Titanium Studio and TiDev Community no longer support the network packaging service that Appcelerator once offered. This means local packaging in the interim while TideSDK team continues to examine options.
Please follow TideSDK on twitter for updates and announcements at http://twitter.com/TideSDK
i have developed an application that will basically run on all versions of the blackberry unit (ver 4.5 and above). however, i have noticed that navigationClick() is not consumed with a touch blackberry. i know that i have to use touchEvent method instead, however, my eclipse project is set up to use jde 4.5. so is there any way of just including the classes necessary for touch events inside my eclipse project? most of our customers are still using phones with 4.5 or 4.6. so setting up the project to use jde 4.7 as the foundation is out of the question.
i know that eclipse doesn't like packaging a project with 2 different jde versions configured for the same application (because of contentions).
how does everyone else roll out an application that is compatible with ALL versions (including those with the touch)? or do you guys roll out different versions of the same app (one to support click and the other to support touch)?
any help would greatly be appreciated.
thank you so much in advance.
ac
We have several applications for the BlackBerry, and the ones that are compatible with touch-screen RIM devices have two versions: the Standard edition, which supports RIM OS 4.1+ and is built on that platform, and the TouchScreen edition which supports Storm, Storm2, and Torch devices, and is built with the 4.7 platform.
The code base is the same and the touch code is separated with preprocessor statements, but as far as I understand it, there is no way to build on a platform before 4.7 and get access to the methods introduced in 4.7.
I am new to Blackberry. Present I am working on 4.7 Blackberry component pack.Now I want to move my old projects to newer versions like 5.0 and 6.0. For that I installed eclipse Galileo 3.5 version and configured latest component packs and Blackberry java plug_in 1.1.2.
I searched in google and find somewhere that use File menu option Import>Import Legacy Blackberry projects and it is asking .jdw file in the workspace.I dont want to move entire workspace, I want only single project. am not able to find it.can any one help me to get this......
In Eclipse, for your old project, try to compile with the new JDE like say 5.0. See what breaks, fix it, repeat till it compiles. Then run on handset to ensure it looks ok.