JDE compatibility

Similar Questions

• If compatibility mode is allowed inside the JDE

  I use JDE v7.0.  I want to prevent my application to start in compatibility mode.

  I am aware that I can put "RIM-TouchCompatibilityMode: false" in my .jad file, but I'm worried that this setting will be deleted when the .jad file are written to JDE when I compile.  At the same time, I have found no way to specify in JDE If compatibility mode is allowed for the application.

  Is there a way to define if the compatibility mode is permitted within JDE? If this is not the case, how should I worry JDE remove the parameter "RIM-TouchCompatibilityMode" the .jad file?

  Applications built in version 7.0 BlackBerry JDE / BlackBerry Java SDK do not work in compatibility mode.  This applies to applications created in versions pre 4.7.0 (who did not have access to the touch API).

• JDE 4.5.0 Installation of Rimlet compatibility on old BB devices

  Hello

  I wrote a Rimlet using the JDE 4.5.0 and hit compatibility problems during the installation of the application on the BB devices. For example, try to install a 8100 Series device, I have so far also have included net_rim_xml_org.cod

  for the installation package. Now, I get the following error:

  Class 'net.rim.device.api.ui.component.keywordFilterField' not found.

  I know why this is. But I don't know what the best thing to do. I think that trying to replace older versions of runtime libraries is not the right thing to do.

  Should I be worried simply not using JDE 4.5.0 for five years, or is there some redistributable library of the standard runtime can I include safely in my installation that will all my problems disappear?

  OK thx for this. feared that it might be the case.

• 5.0 operating system compatibility mode

  Hello

  I have successfully used this property jad to install OTA with the original Storm 9500 on OS 4.7:

  RIM-TouchCompatibilityMode: false

  However, it is not working touchscreen OS 5.0 devices.

  My application is compiled with JDE 4.7.

  If I download on a Storm II (5.0.0.334 - 9550), it will always be in compatibility mode, even with the property defined in the jad.

  Also the 9500 on 5.0.0.252 does not behave as expected:

  If I download an application compiled with JDE 4.2 it comes into compatibility mode.

  But if I compile the same application against the JDE 4.7 it won't in compatibility mode.

  I'm wiping the Simulator each between each test.

  Has anyone else seen elsewhere?

  Or y at - it some new system that I must follow to ensure that my application will not start in compatibility mode for OS 5.0 devices?

  Thank you

  Hi Mark,

  Finally, there is a problem in my download script where a code is compiled with the a previous JDE was included.

  Its solved now.

  Thanks for looking into it.

• BB JDE: Font smoothing in the Editor window

  Hello everyone,
  is there someone out there who is just as annoyed by the smoothing of font that does not exist in BlackBerry JDE?
  I suspect that the standard JDE uses Java control for reasons of compatibility instead of taken anti-aliasing supported components of the OS.
  There is a similar issue in NetBeans that can be resolved by manually changing some configuration files. However, I have not found a way to solve the smoothing of the internal policies of the JDE Editor.
  In an attempt to avoid the headaches (it's 2010!), I'd appreciate a lot of clues on how to solve this problem.
  See you soon!

  -Jonas

  You can switch to eclipse.

• I could develop Java Application for Blackberry device software version 5.0 to 6.0 JDE

  Hi, expert,

  I saw this line of the ' BlackBerry Java Development Environment - 4.7.0 - fundamentals Guide'.

  It is said:

  ===============================

  With each major version of the BlackBerry Device Software and the FMV of BlackBerry, Research In Motion includes the
  corresponding Java API and version of the BlackBerry® Java® development environment. The version of the BlackBerry device
  Software determines the version of the BlackBerry® integrated development environment that you can use to develop
  applications. For example, RIM released BlackBerry Device Software version 4.0 and BlackBerry JDE version 4.0 in even
  time. BlackBerry JDE version 4.0 supports APIs that were introduced in BlackBerry Device Software version 4.0
  and BlackBerry JVM version 4.0.

  The applications that you create by using BlackBerry JDE Version 4.0 only work on BlackBerry devices
  running BlackBerry Device Software version 4.0 or later.

  =========================

  The last sentence talking about version 4.0 of JDE. I think that would mean that I could not develop a java application on JDE 6.0 for Blackberry 5.0 version of the software, even if I do not use any new API to 6.0. However, it seems to me that it is a useless limitation. Could someone throw some lights on it?

  I'm going to agree with superdirt here.

  I have the 5.0 OS update of applications work well on OS 5.0, 6.0 and 7.0 of the OS OS phones.  I try not to recompile for levels of the OS, if I can, and so far I've been perfectly safe with OS 5.0 running on the later levels of the operating system.  So you should be able to get away with just using OS 5.0.

  Not that it is important for you, but I just thought I documents some historical information about level changes.  .

  As far as I know it 2 change cod in the file format, one to the 4.0 OS and the other in OS 4.2.  Therefore, if you want to run anything in OS 6.0 or above, it must be compiled in OS 4.2 or higher.  Again, I have applications compiled to OS 4.2 running on OS 6.0, without no problem devices.

  There have been changes to the API - the result is that the code that works in OS xx does not work in OS yy where yy is after xx.  I hit a few of them and have so far managed to rework the code so that it works very well on both levels of the operating system.  In general it is things that I do wrong anyway, as the older operating systems (from memory) are not as strict on when the event Thread must be used.

  The problem with OS 4.7 compatibility is an impact and to get more of this, for devices touch screen only, I compile using OS 4.7.  If an application that uses only the functionality that was available in the OS 4.2, I compile on OS 4.2 for non touch screen phones and OS 4.7 for touchscreen phones.  And everything works fine.

  I hope this helps.

• Cannot add properties of jad for the compatibility mode for the COD file metadata.

  Hi all.

  I need to disable the application that are installed compatibility mode using the ALX file. I read in an another messages it is possible to add custom file JAD directly properties in the COD file. I tried to create test projects using Blackberry JDE, Blackberry Eclipse plugin generation tools and use Eclipse with ant. Then I tried to add a JAD file for projects and by adding the following properties:

  RIM-TouchCompatibilityMode: false
  RIM-TouchCompatibilityMode-UserChangeable: true
  

  Also I tried specifying the properties of this:

  RIM-TouchCompatibilityMode: 0
  RIM-TouchCompatibilityMode-UserChangeable: 1
  

  But it seems that it does not help to automatically avoid compatibility mode for applications that are built using JDE4.2.1 or earlier. I ran the test on Storm 9530 camera with 5.0.0.32 8 preinstalled JDE. I also wipe my phone several times to avoid the capabilities that the compatibility mode settings is saved.

  In addition, before installing the application I also checked this jar file compatibility mode properties which was built contained in this manifesto.

  Please, anobody can advise which go bad. Or it seems that there is no possibility to implement the solution that are built with the JDE at first then 4.7 and are installed using the ALX file.

  I never could get this job.

  Sorry, don't know what the deal is.

• Simulating the different devices in the JDE

  Hello..

  Currently with my JDE 4.6 it only allows me to simulate a storm and the 8900. I want to simulate my app on a few different devices (to see how it looks and feels more small/more large screens). I was just wondering how to install of new simulators for my JDE and where can I get them out?

  I'm new on this and any help would be greatly appreciated

  Thank you

  Devices come usually with of the JDE. You can download new devices by downloading the new JDE versions. You can then run the emulator from the command line and choose to install the application in the menu. Point of the dialog in the JAD/COD that you created and it will be installed in the emulator. Of course, you can simply use the new JDE to build and run your project but if you try to maintain compatibility with a version of the OS, but testing on the new devices, which tends to work ok.

  Thank you

  Rick

• Confusion between OS & JDE

  Hello

  I developed application in jde 4.7. The code is designed keeping backwards compatibility with 4.5. So, now I want to test the code in the Simulator with OS 4.5.

  My confussion is:

  1. I would like to download jde 4.5 and add build my project inside and test with the simulators available in jde
  2. I can download Simulator bundle 4.5. Wish will give me OS 4.5 Simulator. and test my application in this OS 4.5 Simulator.

  Earlier, I think my concept was to download jde 4.5 and test in it. But now, looking at the beams of Simulator, I'm confused.

  Kindly help me

  Thank you

  sonicboomboy is not correct.

  You can not run code developed in 4.7 4.5 Simulator (or other device).  In fact, it is not 100% reliable.  It can work.  But it is not supported.  If this does not work, it is not accident, because of the way that you coded.

  Always develop on an OS/JDE/component pack which is older than or at the same level as the simulator/device you are targeting.

  Then download JDE 4.5 and compile using that.

  Then download and test with 4.5 desired simulators.

• Mode of compatibility in the operative part of Strom

  Hello

  So I am writing an application that will eventually be used on the BlackBerry. I designed originally for the program to work for "BOLD" and now, I'm testing a version of the storm. I used the IDE for the "BOLD" 4.6.1.

  I have reviewed the Article number: DB-00710 "Compatibility Mode on BlackBerry smartphones with touch screen", but:

  When I turn on activate to compatibility mode:

  1. it shows a blue border.
  2. the menu does not display the options hide/show keyboard.
  3 Select to use the touch screen.

  When I turn disable it for compatibility mode:

  1. the application appear on the main screen. It's Ok.
  2. the menu options hide/show keyboard. It's Ok.
  3 disable use the touchscreen. It comes to my questions.

  I need that my application:

  1. the application appear on the main screen. Fact.
  2. the menu options hide/show keyboard. Fact.
  3 activate use the touchscreen. Pending.

  Then, I need compile my application on JDE 4.7.0 IDE and this problem will be solve?

  Thank you.
  Jorge Luis.

  If you compile an application in JDE lower version and running it on JDE 4.7 Storm, compatibility issues will be there.

  two ways to avoid it.

  (1) If you don't want new compileit in JDE 4.7, just install cod on storm, go to option-> advance-> application options.

  Select your make from the menu, select disable compatibility. It runs very well.

  (2) to compile the app again to the JDE 4.7.

• BB JDE 4.7.0 trying to build/run sample source apps errors

  Welcome,

  I'm trying to build and run some of the source sample apps that install with JDE. After struggling with the apparent x 64 defects of decision-making supported for a while, I started my old system 32-bit, all had installed, and it opened with the samples.jdw workspace - looked like success is at hand, to me.  But I tried build and run several applications, all closed with a message like this:

  Building HelloWorldDemo
  C:\Program Research In Motion\BlackBerry JDE 4.7.0\bin\rapc.exe-silencieux import =... name of code \lib\net_rim_api.jar = com\rim\samples\device\helloworlddemo\HelloWorldDemo com\rim\samples\device\helloworlddemo\HelloWorldDemo.rapc warnkey = 0 x 52424200; 0 x 52525400; 0 x 52435200 "C:\Program research in Motion\BlackBerry JDE 4.7.0\samples\com\rim\samples\device\helloworlddemo\HelloWorldDemo.java" "C:\Program research in Motion\BlackBerry JDE 4.7.0\samples\com\rim\samples\device\helloworlddemo\img\helloworld_jde.png"
  I/o Error: CreateProcess: javac-source 1.3 - 1, 3 - g - O d 'C:\DOCUME~1\mmcginty\Local Settings\Temp\rapc_450f47b5.dir' - bootclasspath to target... \lib\net_rim_api.jar - classpath... \lib\net_rim_api.jar "C:\Program research in Motion\BlackBerry JDE 4.7.0\samples\com\rim\samples\device\helloworlddemo\HelloWorldDemo.java" error = 2
  Error while building project

  I have also installed the Java plug-in for Eclipse (which is the environment that I would prefer to use) and copied a couple of samples in its workspace.  After I find it necessary to move the .java files in the. \src dir and adding net_rim_api.jar as an external .jar, I get the following error when you try to debug:

  java.lang.ClassFormatError: field modifiers illegal net/rim/device/api/ui/UiEngine classroom: 0x1A
  at java.lang.ClassLoader.defineClass1 (Native Method)
  at java.lang.ClassLoader.defineClass (unknown Source)
  at java.security.SecureClassLoader.defineClass (unknown Source)
  at java.net.URLClassLoader.defineClass (unknown Source)
  in java.net.URLClassLoader.access$ 100 (unknown Source)
  java.net.URLClassLoader to $1.run (unknown Source)
  at java.security.AccessController.doPrivileged (Native Method)
  at java.net.URLClassLoader.findClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  to Sun.misc.Launcher$appclassloader$ AppClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClassInternal (unknown Source)
  at java.lang.ClassLoader.defineClass1 (Native Method)
  at java.lang.ClassLoader.defineClass (unknown Source)
  at java.security.SecureClassLoader.defineClass (unknown Source)
  at java.net.URLClassLoader.defineClass (unknown Source)
  in java.net.URLClassLoader.access$ 100 (unknown Source)
  java.net.URLClassLoader to $1.run (unknown Source)
  at java.security.AccessController.doPrivileged (Native Method)
  at java.net.URLClassLoader.findClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  to Sun.misc.Launcher$appclassloader$ AppClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClassInternal (unknown Source)
  at java.lang.ClassLoader.defineClass1 (Native Method)
  at java.lang.ClassLoader.defineClass (unknown Source)
  at java.security.SecureClassLoader.defineClass (unknown Source)
  at java.net.URLClassLoader.defineClass (unknown Source)
  in java.net.URLClassLoader.access$ 100 (unknown Source)
  java.net.URLClassLoader to $1.run (unknown Source)
  at java.security.AccessController.doPrivileged (Native Method)
  at java.net.URLClassLoader.findClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  to Sun.misc.Launcher$appclassloader$ AppClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClass (unknown Source)
  at java.lang.ClassLoader.loadClassInternal (unknown Source)
  Exception in thread "main".

  When I try to run the same sample, he complains no head type, even if the field is entered in the config to run (just as it is in the debug configuration.)

  Anyone know what I'm doing wrong here?

  TIA,

  Mark McGinty

  Addendum:

  When I run IDE. BAT (via the shortcut created in the start menu) on my x 64 system, I get the following error in a pop-up window:

  "Cannot find RIMIDEWin32Util.dll.  It is an essential component of the IDE. »

  This file exists in the same directory as the lot.  This error does not on my 32-bit system, so apparently a x 64 32-bit compatibility layer support problem?  (God forbid we would never lack of x 64 native dev tools.)

  I assume that you are addressing the BB JDE problem, and that by JDK you are referring to the Sun JDK (which installed to C:\Program Files\Java\jdk1.5.0_19, by default.)  I added the JAVAHOME env variable with that path as the value, and also appended that path + \bin to the PATH variable -- no change.
  

  Go to the window "CMD" (start-> Run-> CMD) and type javac and press ENTER. The use of the java compiler appear?

  However, I noticed that the target dir is a sub in my Temp folder?  Why is it using a tunneled path name?  (e.g., "C:\DOCUME~1\mmcginty\Local Settings\Temp\rapc_769c5235.dir")  Tunneled paths may not be valid on all systems, including mine, I hate that crap, there's no reason, other than lame apps that depend on it, for them to persist to this day -- they were designed for FAT16 down-level compatibility, for cryin out loud, will we never be done with that?
  

  Compiler CAP makes the files and temporary files during the compilation process. It is not a wrong behavior. It is a part of the compilation process.

  btw, I made some headway on the Eclipse Java plug-in end, I found I must create the project as a "Blackberry Project" (by clicking "Other" from the New menu, and choosing BB from the tree.)  Now the app builds without errors but it only creates .class files, and it does not deploy the app to the simulator.
  

  I left using Eclipse a long time ago. Now I do not use it at all. So I have no information about its glitches, sorry.

  From my point of view JDE is best tool.

  Make sure that javac is accessible from the window cmd and post here how are you.

• To display the option/Hide keyboard in storm of BB + 4.3 JDE

  Hi all

  my project is to build on 4.3 JDE. It works fine on the device version 4.3 and higher. When I install this same build the BB Storm that even I don't see the option to hide or show the keyboard. For this, I have compiled my project in JDE 4.7 and now I see these options.

  But the problem is I want to keep just one generation. and the obligation for versions 4.3 and higher. so I don't want to keep two different builds.

  Can someone suggest a solution.

  If you use the search button and search for 'compatibility mode' you will find numerous threads on the subject.

  Here's one of many:

  http://supportforums.BlackBerry.com/T5/Java-development/sticky-quot-compatibility-mode-quot-issue-on...

• Storm App is running in compatibility mode

  I'm new new Blackberry.  I feel very uncomfortable with RIM JDE 4.5, so I moved the RIM JDE 4.7.

  For my first program, I just copied the SVG Pick demo code in my program.  When I build and run, it runs in compatibility mode.

  I've searched the knowledge base that says:

  1. If the application is compiled with BlackBerry® development environment (BlackBerry JDE) 4.7 Java or later version, it will not automatically run in compatibility mode. If the application is compiled with an earlier version of BlackBerry JDE, it will run in compatibility mode.

  I even checked the jar of my workspace, and it looks like 4.7.  I am at a loss.

  Thank you in advance for your help!

  I saw that too. In my case it was caused by the first running version 4.5 on the device. The storm decides this app is app "compatibility mode" and will not erase the attribute once it is recompiled under 4.7.

  Go to Options / Advanced / Applications and disable the compatibility mode for your application.

• 4.2 portage app to Storm, rebuilt in JDE 4.7, does not appear in the Simulator

  I have a 4.2.1 application that needs the entire screen of the storm and would not run in compatibility mode even when (did even not appear in apps), so I thought I have to rebuild for storm and then perhaps reprogram how he feels entry directional.

  For starters, I rebuilt the same code using the JDE 4.7 and said: "GO!"  The simulator of the storm came, but my application was not found.

  I tried to launch the Simulator independently and using 'Load Java application' and in charge of the application but the icon does not appear.

  Is so different storm of 'ball' berries that I can't even get my app to appear without doing something special?  He appears and works fine in all other simulators.

  Thank you.

  This is!  Thank you

• software compatibility

  Before I dive and upgrade to Sierra, I'm looking for a reliable source check the compatibility of the applications, I currently rely on.  Many are a bit dated.  Any suggestions?

  Main applications:

  Microsoft Office for Mac 2011 v 14.6.8

  Quicken for Mac 2007 v 16.2.4

  Photoshop CS5 x 64 new v12.0

  Roxio Toast 10 Titanium v 10.0

  Apple Pages, Numbers and Keynote ' 09

  Running OS X Lion mountain.

  Click here.

  (145086)