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.
Related
I found a pdf containing all the information I need, unfortunately it is (currently) for version 1.2019.6 http://plantuml.com/guide
I'm currently using 1.2019.3, and can't upgrade because the changes to preprocessing break my project, where can I find a similar helpful PDF but for version 1.2019.3(or older versions in general)?
You'll find something interesting here:
http://pdf.plantuml.net/1.2019.3/PlantUML_Language_Reference_Guide_en.pdf
:-)
And we are interested by the issue you have with the new preprocessor. Maybe we can fix them ? So tell us more about it... Thanks
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.
I fear I've missed it, but I can't seem to find a spot in the docs that specifically lays out what version(s) of Django are tested to work. I did notice the requirements.txt file. Should that be my guide then? Thanks!
The definitive source of information about supported Django versions is setup.py in the Wagtail codebase. The release notes section of the documentation will tell you when a new version is supported, or an old version is dropped, but there's currently no place in the documentation that will tell you the supported Django versions for a given Wagtail release. (There probably should be!)
The requirements.txt in the project template won't tell you the full range of supported versions - usually it points to the latest compatible major Django release, as that's the one you're encouraged to use on new projects.
Yes! As of this writing you can find them here: http://docs.wagtail.io/en/v2.0.1/releases/upgrading.html
I had the same question today and thanks to #gasman who lead me to the right place where I should be digging.
Currently our application is on the Angular 2.0 version.
How important is it to keep updating it as and when Angular releases a new update?
In the changelog i dont see any breaking changes that need to be addressed immediately going from 2.0.0 to 2.4.2.
So is it necessary to upgrade our application from 2.0.0 to 2.4.2? Or should we just wait till there is another big release?
I would suggest upgrading to newer version of major release when:
You came across the issue/bug which was fixed in newer version.
There's a new feature which will come in handy.
Changes positively affecting performance - e.g. AOT compiler which can be a deal breaker to some people, but it might require some code to be rewritten to make it AOT-friendly.
Angular uses semantic versioning. Going from 2.0.x to 2.0.y means that a bug has been fixed. It's usually a good idea to avoid having bugs. Going from 2.0.y to 2.1.0 means that a new feature is available. You might want or need to benefit from this new feature.
You won't have any breaking change until the next major version, which will be 4.0.0 (there won't be a 3.x version, in order to align angular and its router versions)
As mentioned on this link under Best Practices Section
Best practices
Keep current with the latest Angular library releases. We regularly update our Angular libraries, and these updates may fix security
defects discovered in previous versions. Check the Angular change log
for security-related updates.
Don't modify your copy of Angular. Private, customized versions of Angular tend to fall behind the current version and may not include
important security fixes and enhancements. Instead, share your
Angular improvements with the community and make a pull request.
Avoid Angular APIs marked in the documentation as “Security Risk.”
Note: This question will be changed to eliminate old question with lower rating.
I see AngularJS console errors as follows:
Lexer Error: Unexpected next character at columns 0-0 [#] in expression [#].
The problem now is how to locate the source of this error among thousands of lines of code?
Old Question:
NOTE: This is the old question, please ignore.
I was working with a sample application from ng-flow file upload. I then moved the developed parts to my colleague's environment who is using bootstrap for CSS. I noticed that the look and feel changed on from his environment.
I realized that my colleague is using this css file:
http://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
and I am using the css file the came with the download:
http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.2/css/bootstrap-combined.min.css
and both work fine, but they have clear differences on how the look and feel and how layout is presented.
I included both, and it seems the application is still working fine, and the look and feel is now merged.
I am just wondering if there is documentation that explains the differences and how to decide which one to use.
Appreciate your feedback.
The reason they look different is that they're referring to different versions of Bootstrap - version 3.3.7 vs version 2.3.2. (The other difference is where the files are hosted.) 3.3.7 is more recent than 2.3.2.
Generally, you want to use the most recent version available for whatever libraries you're including, unless you need to stay compatible with an older one. You shouldn't include both, though; that's going to have your users downloading a lot of redundant css.