you got a very good suggestion, this is the right place where you can ask these kind of questions
Are you building a native application or you're using the RhoElements Shared runtime?
because the answer depends on how you use the tool:
- Native application: you can set app name, icons and startup page using this guide:http://docs.rhomobile.com/rhodes/build#how-to-set-application-name-and-icon
- Shared Runtime: you can create a shortcut for your app, but I don't think that this allows to have a different icon: http://docs.rhomobile.com/rhoelements/rhoelements2-webapps#creating-shortcuts-for-your-web-app
In the second case an additional possibility it's to rebuild the shared runtime with a different icon, but it really depends on the platform you're targeting.
Thanks for your reply. In our case, it's #2. We're using the shared runtime. As the shortcut doesn't seem to be the fix, I'd like to see how to rebuild the shared runtime.
We're currently targetting Android (mostly MC40), Windows Mobile (MC55) and iOS. I have no idea where to start to rebuild the shared runtime. However, I think this would be an added value to more than just us. So perhaps it's worth creating a guide for?
Thanks in advance,
the instruction on how to do this on v2.2 are in the docs site: http://docs.rhomobile.com/rhoelements/rhoelements2-webapps#customizing-the-rhoelements-runtime
Just keep in mind that MC40 is not formally supported by RhoElements v2.2, but only by v4.0 that is currently in beta and the shared runtime for Android is no more supported in v4.0.
For MC40 may be necessary to build a very small native app that connect to your webpages. But the only supported rendering engine on Android with v4.0 it's the native browser with the new CommonAPIs:
RhoElements v.2.2 APIs are deprecated but still supported in RhoElements v4.0 for Windows Mobile/Windows CE.