I am using cakephp 2.2.5-0 version to develop my project. I want to create a separate theme so that i can built new theme without modify the default theme files.
Problem is when i google for it. I got solution with older version. Current package (cakephp 2.2.5-0) folder structure is not same as older version.
Using themes is described well in the official docs, and covers CakePHP version 2.2.5.
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'm using Eclipse with the Codename One Plugin.
Now I am starting a second project.
I would like to setup one or more "fragment" projects to avoid code duplication between projects. For example if I'm having a utility class for string concatenation I'd like to have this in a Utilities fragment project which then would be referenced by my projects.
What is the recommended way of doing this with Codename One?
For Codename One that's a cn1lib unfortunately at this time the Eclipse plugin is the only one that doesn't support the creation of a cn1lib (although it allows using them just fine).
Since a cn1lib is just an Ant project you can just download an existing project and put in your own code instead of what's there.
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.
In Joomla 3.x. there is a folder on libraries/legacy. Where there are folder like 'model', 'controller', 'application'. What is the purpose of that folder? I am very much new in Joomla.
There are many extensions which are still in the older legacy version, like Joomla 2.x or joomla 1.x. The controllers, and Models of current version may be significantly different than the previsions versions. Having the legacy folder ( which contains older version of Model and Controller) is a good idea since the old extensions using the older Controller now can change their Controller classes extends to JControllerLegacy ) and still able to run in the current version of Joomla. So this requires very minimal change than conforming to the newer version of JContorller or JModel for that matter.
I understand Codenameone 2.0 has been released. When I updated the plugin from my IDE, the plugin version on Netbeans says it is version 1.0.68? Is this the 2.0?
The plugin version has nothing to do with the version of Codename One.
Codename One versions are mostly a code stabilization milestone that can then be used in versioned builds. Since Codename One is a cloud service you are effectively always using the latest version of Codename one unless you explicitly use a versioned build.