Cleanup developer guide content (#4735)

* Removed unused images and fixed asciidoc

* Removed old references to blackberry/J2ME

Author: shai-almog

docs/developer-guide/Advanced-Topics-Under-The-Hood.asciidoc

@@ -349,19 +349,9 @@ Currently only supported for App Store builds.  See https://www.codenameone.com/
 | (Optional)  The version of TeaVM to use for the build.  *Use caution*, only use this property if you know what you are doing!
 
 
-|rim.askPermissions
-|true/false defaults to true. Indicates whether the user is prompted for permissions on Blackberry devices.
-
 |google.adUnitId
 |Allows integrating Admob/Google Play ads into the application see link:https://www.codenameone.com/blog/adding-google-play-ads.html[this]
 
-|rim.ignor_legacy
-|true/false defaults to false. When set to true the Blackberry build targets only 5.0 devices and newer and doesn’t build the 4.x version.
-rim.nativeBrowser	true/false defaults to false. Enables the native blackberry browser on OS 5 or higher. It is disabled by default since it might casue crashes on some cases.
-
-|rim.obfuscation
-|true/false defaults to false. Obfuscate the JAR before invoking the rimc compiler.
-
 |ios.entitlementsInject
 |Content to inject into the iOS entitlements file.  This should be in the Plist XML format.  See https://developer.apple.com/documentation/bundleresources/entitlements?language=objc[Apple Entitlements Documentation].
 
@@ -488,8 +478,6 @@ rim.nativeBrowser	true/false defaults to false. Enables the native blackberry br
 |noExtraResources
 |true/false (defaults to false). Blocks codename one from injecting its own resources when set to true, the only effect this has is in slightly reducing archive size. This might have adverse effects on some features of Codename One so it isn't recommended.
 
-|j2me.iconSize
-|Defaults to 48x48. The size of the icon in the format of width x height (without the spacing).
 |===
 
 === Android Permissions
@@ -768,7 +756,7 @@ Codename One doesn't include the native platforms in its bundle e.g. the full An
 
 TIP: When implementing a non-trivial native interface, send a server build with the "Include Source" option checked. Implement the native interface in the native IDE then copy and paste the native code back into Codename One
 
-The implementation of this interface is nearly identical for Android (Java/Kotlin), J2ME & Java SE.
+The implementation of this interface is nearly identical for Android (Java/Kotlin) & Java SE.
 
 ===== Swift (iOS) and Kotlin (Android) options
 
@@ -1335,7 +1323,7 @@ include::../demos/android/src/main/java/com/codename1/sms/intercept/NativeSMSInt
 Native interfaces standardize the invocation of native code from Codename One, but it doesn't standardize the reverse of callbacks into Codename One Java code. The reverse is naturally more complicated since its platform specific and more error prone.
 
 A common "trick" for calling back is to just define a static method and then trigger it from native code. This works
-nicely for Android, Java SE, Blackberry & Java ME since those platforms use Java for their "native code". Mapping this to iOS requires some basic understanding of how the iOS VM works.
+nicely for Android & Java SE since those platforms use Java for their "native code". Mapping this to iOS requires some basic understanding of how the iOS VM works.
 
 For the purpose of this explanation lets pretend we have a class called NativeCallback in the src hierarchy under
 the package `com.mycompany` that has the method: `public static void callback()`.
@@ -1647,7 +1635,6 @@ javascript.minifying
 javascript.proxy.url
 javascript.sourceFilesCopied
 javascript.teavm.version
-rim.askPermissions
 google.adUnitId
 ios.includePush
 ios.headphoneCallback
@@ -1669,7 +1656,6 @@ desktop.themeMac
 desktop.themeWin
 desktop.windowsOutput
 noExtraResources
-j2me.iconSize
 android.permission.<PERMISSION_NAME>
 ----
 
@@ -1723,7 +1709,6 @@ The table below covers the files that can/should be a part of a cn1lib file:
 | nativeios.zip        | &#215;   | Native iOS sources if applicable
 | nativeand.zip        | &#215;   | Native Android sources if applicable
 | nativejavascript.zip | &#215;   | Native JavaScript sources if applicable
-| nativerim.zip        | &#215;   | Native RIM sources if applicable
 | nativese.zip         | &#215;   | Native JavaSE sources if applicable
 | nativewin.zip        | &#215;   | Native Windows sources if applicable
 | nativeme.zip         | &#215;   | Native Java ME sources if applicable

docs/developer-guide/Index.asciidoc

@@ -45,9 +45,9 @@ E.g.: Since building native iOS applications requires a Mac OS X machine with a
 
 Subscribers can receive the C source code back using the include sources feature of Codename One and use those sources for benchmarking, debugging on devices etc.
 
-The same is true for most other platforms. For the Android, J2ME & Blackberry the standard Java code is executed as is.
+The same is true for most other platforms. For the Android and Java SE the standard Java code is executed as is.
 
-Java 8 syntax is supported thru https://github.com/orfjackal/retrolambda[retrolambda] installed on the Codename One servers. This is used to convert bytecode seamlessly down to Java 5 syntax levels. Java 5 syntax is translated to the JDK 1.3 cldc subset on J2ME/Blackberry to provide those language capabilities and API's across all devices. This is done using a server based bytecode processor based on retroweaver and a great deal of custom code. Notice that this architecture is transparent to developers as the build servers abstract most of the painful differences between devices.
+Java 8 syntax is supported through https://github.com/orfjackal/retrolambda[retrolambda] installed on the Codename One servers. This is used to convert bytecode seamlessly down to Java 5 syntax levels. This is done using a server based bytecode processor based on retroweaver and a great deal of custom code. Notice that this architecture is transparent to developers as the build servers abstract most of the painful differences between devices.
 
 ==== How does Codename One Work?
 

docs/developer-guide/developer-guide.iml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="JAVA_MODULE" version="4">
+  <component name="NewModuleRootManager" inherit-compiler-output="true">
+    <exclude-output />
+    <content url="file://$MODULE_DIR$">
+      <sourceFolder url="file://$MODULE_DIR$" isTestSource="false" />
+    </content>
+    <orderEntry type="inheritedJdk" />
+    <orderEntry type="sourceFolder" forTests="false" />
+  </component>
+</module>

docs/developer-guide/graphics.asciidoc

@@ -373,7 +373,6 @@ you need a fallback path.
 | JavaScript
 | Yes
 
-| Yes
 |===
 
 
@@ -1324,8 +1323,7 @@ to the image itself (e.g. the `scaled` method) it will generate a new image whic
 image.
 
 TIP: Since https://www.codenameone.com/javadoc/com/codename1/ui/util/ImageIO.html[ImageIO] is used to perform the operations of the adapter interface its required that `ImageIO` will work.
-It is currently working in JavaSE, Android, iOS & Windows Phone. It doesn't work on J2ME/Blackberry devices so if you
-pass an adapter instance on those platforms it will probably fail to perform its task.
+It is currently working in JavaSE, Android, iOS & Windows Phone.
 
 If the file in the URL contains an image that is too big it will scale it to match the size of the placeholder precisely! +
 There is also  an option to fail if the sizes don't match. Notice that the image that will be saved is the scaled