Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 months ago.
Improve this question
We have a project based in primeng 9.1.3, and when I attempt to look at the documentation, there seems to be a discrepancy, or maybe I'm just overlooking something. We started this project a few years ago and it seems like there isn't an easy path to upgrading to 10.0 and beyond, so that's why we're staying with 9.x.
On the primeng releases (https://www.npmjs.com/package/primeng) the latest 9.x I see is 9.1.3. But when I go to the docs (https://www.primefaces.org/primeng-v9-lts/#/), I see 9.2.8-lts.
I looked into some of the source code and some things that are in the docs properties are not in the release... The main issue is the 508 compliance functionality discrepancies in the docs vs release. I'm not sure if I'm missing something, and hoping those that are more familiar with primeng can point me in the right direction.
I can't figure out why the docs version and the release version don't match up. I can't find the docs for 9.1.3 and I can't find the release for 9.2.8, and its painful to try and dig through the source code each time I want something to pass 508 compliance.
The latest 9.x version is actually 9.2.8, as can be seen under the primeng-lts npm package.
The reason why the latest version that appears on https://www.npmjs.com/package/primeng is 9.1.3 is that 9.1.3 is the last version of 9.x that isn't an LTS version and is an STS version, under the MIT license. The LTS versions are commercial versions.
You can read about the PrimeNG version lifecycle here. You can also see in the diagram there that version 9.1.4 is marked as the first 9.x version to receive LTS status.
Related
Apparently, the ExtJS' forum isn't working anymore, so asking the question here.
I am trying to upgrade ExtJS integrated in a big application. Currently, it's using version 3.4.1 and I have to upgrade it to 7.5.0, so a lot of changes are expected. It's my first time working with ExtJS. I've been reading their documentation & examples for a while now, but I'm having issues understanding some things.
If someone's experienced with ExtJS, could you tell how big is the difference between these versions? What kind of effort is expected for this upgrade? Will I have to rewrite everything, or just changing files and API calls would be enough?
Another thing is that the folder structure in the new version looks quite different from the older version. Ours using 3.4.1 looks like this -
ext-js 3.4.1 image
There are no new adapter or resources folders in the new verion. Are these folders not required anymore, or is it possible to get the same folder structure with the new version?
Is it possible to download older versions of ExtJS like 4.x, 5.x etc.? I tried but couldn't find it, I was able to download the older documentation though.
Downloaded the latest ExtJS version from here.
Referring this Sencha ExtJS documentation.
Any help would be appreciated. Thanks in advance.
Download
You should download the version from support.sencha.com. There you can find all versions.
To access the download page, you need to log in. If you have lost your login, you can contact Sencha's licensing department.
Make sure you have a valid license.
Upgrade
If you are new to Sencha, you should not do the work yourself. Between version 3 and 7, there are at least two new coding paradigms and you'll have to rewrite everything. Unfortunately, there is no easy upgrade process from 3 to 7. If you had to upgrade from 5 to 7, it would be possible to ignore all the cool new features, but if you are starting from 3, you will have to rewrite everything.
Building process
In your screenshot, I can see that you are using the full ExtJS file. But are you really building the application? That means you end up with a single js file and a single css file.
Are you building your application?
Are you using SCSS?
You should definitely contact someone with experience. I've done quite a few upgrades in ExtJS to know that you need help with this.
TWO very related questions in this post.
How to install 6.5 & 6.5.1 in eclipse(more detail below)
Intellij Toolbox last version supported is 2019.2.4 but looks like codeone plugin doesn't support it?
In intellij, codenameone 6.5.1 simulator is not working(font is way too small) but it's working in 6.0.0 with my eclipse(from when I played with it 6 months ago). I am trying to test out each version to see what the latest version is that is not broken for me(hopefully at least 6.5). When I go to eclipse marketplace, there is no upgrade and it just shows this for codename one (eclipse verison 2020-06 as I clicked update all)
I don't see a way to download a zip file and install it in eclipse and only see the install from marketplace method here
https://www.codenameone.com/download.html#step2
Is there a zip download for eclipse somewhere I can try of 6.5, then 6.5.1?
I also want to try to downgrade my intellij version but we also need the latest so I grabbed the new intellij toolbox but this only goes back to version 2019.2.4. The compatibility list on codenameone plugin is such
I wonder about that first line for 6.5.1. A dot release and they added support all the way back to 2016 version which 6.5 didn't have? Seems like a type. Also, 6.5.1 did not work with latest intellij and honestly getting worn down in playing the version mismatch game of uninstall/install to see what works and doesn't work (it's just takes quite a bit of time).
If anyone can post a STABLE list of IDE version / plugin version they are using, I would LOVE to know that <- If I know that, I will just jump to that. I can cope with eclipse or intellij. In fact, eclipse debugging is way better and intellij refactoring is way better so I am always torn between each.
Trying 2019.1.4 with many versions next.
Figure this out finally. Not sure exactly but this repo https://github.com/deanhiller/codenameOneExamples
now works with latest intelij 2020.1.3 !!
I updated Silverlight on my dev. machine, but clients still have older Silverlight version and they do not want to update.
Now I need to revert Silverlight 4 back to older version (50401). I tried to uninstall Silverlight and install older version, this required my to install developer tools, too.
No luck, still it requires newer version on clients machines. So I suppose real version is inside developer tools?
The question is, how do I make VS2010 to compile project for specific Silverlight 4 build?
I already stumbled on that kind of problem, and I had to re-install my sdk.
Check out that great article from Tim Heuer:
http://timheuer.com/blog/archive/2010/09/28/keeping-your-silverlight-dev-environment-stable-through-service-releases.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+timheuer+%28Method+%7E+of+%7E+failed+by+Tim+Heuer%29
I noticed a few tweets this morning about a new version of Silverlight having been released - Silverlight 2 GDR 1 (2.0.40115.0). Details of what/why/should I target it/is it backward compatible/etc seem incredibly thin on the ground.
Hitting this Silverlight page on Microsoft.com tells me my version (RTW) is now out of date and I should upgrade to GDR 1. But hitting silverlight.net - there's no mention of it, the Silverlight elements on the page don't tell me my version is out of date and the Getting Started page still links to RTW tools.
This kinda leads me to presume that if you upgrade your dev tools to target the GDR release, then your users will need to upgrade their Silverlight install also?
A few details on what's in GDR can be found in the release notes - but it sure would be nice if Microsoft would clarify it's purpose and suggested adoption. Anyone got any more details?
Tim Heuer explains all: http://timheuer.com/blog/archive/2009/02/19/silverlight-2-gets-minor-update-gdr1.aspx
It seems to be only bug fixing.
So if your applications (so your users) are not concerned by those bugs, it is not mandatory to update your plugin for the moment.
I received this error "Arithmetic operation resulted in an overflow." when trying to upload any file in the Repository module of DotNetNuke. I'm using dotnetnuke version 4.5.1.
What is the size of the file? What version of the repository module are you using?
Otherwise, a few general recommendations....
Try to upgrade to the most current supported version of Repository and/or DotNetNuke. There are many security and performance related fixes in the versions between 4.5.1 and 4.9.0 (The most current).
You might also post over on DotNetNuke.com as I am not sure how many DotNetNuke people really frequent this site, I haven't gotten much response in my attempts to get DNN discussions going here.