I've been looking around to find the release notes for the latest releases but I couldn't find it. Anyone have a link?
Different parts of the project have different logs of the changes between versions. The most comprehensive changelog for the project is the one for the Java language bindings, and it can be found here. Other portions of the project may have their own changelogs, but they are usually limited to changes only within that part of the project. Examples include the changelogs for the .NET language bindings and for the IE driver standalone server.
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.
I have seen answers to this question using other tools but I cannot see how to do it with CN1. If I release a LITE version of an app, what is the process for the user to get the PRO version once they have paid?
Like I said I have seen other answers but they talk about settings within the development studio itself which makes me think that it may be related to the toolset I am using - in this case Codename One.
Thanks.
P.S. I will need to know this for both Android and Apple
This will work for all the platform Codename One supports and is explained in this tip. Effectively you keep two or more codenameone_settings.properties and multiple Main packages/classes. Then toggle them by replacing the codenameone_settings.properties file.
I recently read FIRST CLASS ECLIPSE SUPPORT which made me expect a cn1lib-wizard. But there still is none, right?
The gist of the article is that we will update the Eclipse plugin with the NetBeans & IntelliJ versions. With the trend of migrating towards common code across IDE's within our plugin (the new settings UI) this should be much easier and Eclipse should no longer be out of date with the other IDE's.
I'm not sure when we'll get around to do the library template, unlike the other features it requires some work since the Ant implementation on Eclipse is rather different. So it's hard to give a specific date.
Yesterday I downloaded the new Agile Toolkit 4.3 and found that the licensing and subscription model has been changed. Additionally a "developer sandbox" has been included which launches when the toolkit is first run and requires me to login with a registered account.
While I understand the reasons for these changes, and I'm fully supportive, the sandbox appears to be unnecessarily restrictive. However, there seems to be no easy way to bypass the sandbox, and logging in to the sandbox in a vanilla install of 4.3 leads to a screen where you are forced to choose between a pre-canned Admin or Frontend site.
The key reason for me to upgrade from 4.2 to 4.3 is the introduction of an Application class to support RESTful services. I have no need for either an Admin, nor a Frontend web user interface and yet the sandbox does not provide this option.
Is it possible to bypass the sandbox setup process and, if so, how would one go about doing this?
Looking at this in a different way, the folder structure of the ATK4 library seems to have changed under 4.3. Version 4.2 included documentation on the folder structure and how a developer should setup their application in relation to that structure. I have been unable to find corresponding documentation for Version 4.3 which would give clear guidance on how to build an application around the toolkit without relying on the included sandbox.
Hi Tim (i'm author of Agile Toolkit)
Agile Toolkit framework will continue to be available on github. You will find link to github on the bottom of the page, simply select branch 4.3. All of the documentation still applies and you can use the framework (you still need to respect the license). Github does not contain "admin" or "frontend", it is included for the convenience of new users.
The licensing terms has slightly changed, Agile Toolkit has always used AGPL and Commercial licensing. The reason to introduce the sandbox is because developers were not respecting the license terms. I also wanted to give easier ability to deploy projects for new PHP developers and for security it can only be done through sandbox.
Here is a blog-post outlining all of the changes: http://www4.agiletoolkit.org/blog/rebooting-agile-toolkit
The folder structure have changed, but it must still be compatible with the 4.2 branch. I've adopted the usage of "public" folders for improved security, but please do look into PathFinder documentation on how to customise folder structure.
My sincerest apologies, if this has been asked before. I've searched the site but have not seen an answer for what I'm looking for yet.
For years, my company has referenced custom binaries in a local folder hierarchy within source control. We're in the process of changing our source control, and in the process are defining new strategies for many things. One of the things I've been working on is to setup a local NuGet feed for our custom packages to replace the old source control folder method. I've been able to successfully create custom packages and using the package restore feature, log into our build box to restore both NuGet packages from our local feed, as well as those from the official NuGet feed. Everything has worked well up to this point.
The time has come to begin testing our migration process from our old source control to the new source control, and convert all of the references over to NuGet packages. Where needed, we're creating packages and placing them on our local NuGet server. The issue I came across today involves a project that uses an old version of a vendor library. I searched the official NuGet feed and found the library as a package, but the particular version we used at the time is no longer available.
I know from the fact that package restoration was a highly requested feature, that other companies are already employing the strategy we're attempting now. My question is what strategy is your company implementing when operating under this criteria? Is there a best practice we should be considering?
Thanks for your time and assistance.
That's quite a big question to answer so I'll recommend you some resources to read up on this topic.
I wrote an MSDN article on some patterns and practices I'd recommend when using NuGet into the organization. Maybe you'll find something useful in there: http://msdn.microsoft.com/en-us/magazine/jj851071.aspx.
There's also the book Pro NuGet available at http://bit.ly/ProNuGet.