To my knowledge CN1 does not allow to keep patch version in the Version number. Please advise if there is a way I can do it.
Thanks
Codename One only supports decimals because Android and iOS handle versioning very differently. It's really hard to create common code that works everywhere that's still easy to use.
As a workaround you can use the build hint ios.bundleVersion=1.1.1. Notice that this overrides the version value you set in the UI.
Related
I have been tasked with upgrading a legacy system from Cakephp2.6.2 to Cakephp3.8. Obviously the 2 are drastically different but is there a simple way of getting the old project to work with the new cake version? Or could anyone steer me in the right direction for the best way to do this?
There is no generic "best way" that fits all. The best way is the easiest way for your specific application that results in a properly working application, but that's something that you need to determine for yourself.
There's an upgrade tool that can automate some of the repetitive stuff, like changing directory structures, renaming classes, adding namespaces, etc, but in 99.999999% of all cases the result will not be a working application, you'll still have lots of manual migration to do. How much that is, and how complicated it might be, totally depends on your application, it might be rather simple, but it can also be so complicated that rewriting from scratch might be the better choice.
IMHO you should first make yourself familiar with CakePHP 3.x, to the point where you are able to confidently create robust applications. Lots of questions that you may have about upgrading will solve themselves once you are familiar with CakePHP 3.x.
You should not directly upgrade from Cakephp 2.x.x to Cakeph 3.x.x, here are reasons,
Code base and directory structure is entirely different and it will not work properly.
If you have not good grip on both version trails then you will find yourself in trouble.
Best way in your case, you should upgrade to some higher version of cakephp 2.x not jump to cakephp 3.x. If you want to switch to cakephp 3.x you should rebuild app from scratch.
About obfuscation, what is the meaning of "rim.obfuscation"? I didn't find on Internet what is the "rimc compiler".
It's a legacy build hint related to RIM (Blackberry) support. Since that support is deprecated we removed some of the docs for it.
Our old plugin UI in the preferences still has UI for this and adds those hints automatically. We hope to remove that UI on NetBeans/Eclipse so only Codename One Settings remains but removing code is sometimes just as hard as adding it.
My company recently came up with an idea to include using smartwatches with the app I wrote using codename one.
Is this possible? If yes, which libraries do I need?
We are evaluating the possibility of smartwatch support, this depends on customer demand.
We currently have a major enterprise prospect that has expressed interest in this but hasn't signed up. If your company is serious about this please contact us directly.
Assuming we don't go that route or you need something immediately this depends on your supported platform, you would need to use native interfaces for most functionality. In Android notifications (which we support) should work for Android wear. In iOS we are transitioning to the new xcode 7.x which should support smartwatches too but I'm not sure what would need doing.
I'm looking to add functionality to the built in Java SDK classes beyond the CLDC 1.1 standard which is where the API seems to be compatible with. Specifically looking to implement StringBuffer#replace(...)
What is the best way to go about this?
Thanks
cldc1.1 is a very old standard. Codename One supports far more than what that standard had but retained the filename due to legacy issues.
There is a guide on how to use the Codename One source and contribute it back to the git repository: http://codenameone.com/blog/how-to-use-the-codename-one-sources.html
However, the main issue is the need to fix this for all OS's which is pretty challenging.
To just fix the stubs for the method to appear to compile you can change the project here. However, this will only work for targets where the method is already there (Android, JavaSE etc.).
You will then need to make sure there is an implementation for all other targets:
For Windows you will need to fix the ikvm target and fork, for iOS you will need to fix the code in the JavaAPI directory under the VM directory for JavaScript you will need to contribute your changes to TeaVM if required.
For older platforms you will need to implement your changes into the retroweaver support although this might not be as relevant.
I've been wondering about this since the latest version of Internet explorer. It has an emulate function as most of you might know, this is where we test for the prehistoric versions of Internet explorer by changing the document mode.
The default document mode is "Edge". I thought this was IE specific, but aparently it has something to do with versions.
I recently noticed that when selection a jQuery version on jsfiddle.com you can select 1.x and 2.x "edge" versions.
What does this mean? What exactly is an "Edge" version?
Aparently it's the "latest" version. Some extra info would be nice though, like when to use Edge in stead of the actual version number.
Related
As answered in the related question, "Edge" means the latest version.
The reason Shanimal suggested seems logical to me.
When referring, including or linking the latest version, one could always implement "Edge". This will then automaticaly mean the latest. Especialy for includes this can come in handy.