We are upgrading our CakePHP 3 project to CakePHP 4 because we need to support PHP 8.1.
We are also using https://github.com/FriendsOfCake/bootstrap-ui plugin's HTML/Flash/FormHelpers to generate Bootstrap 3 styled HTML. We do not need the bake functionalities of the library, only the helpers.
The newer versions that are for CakePHP 4 core are using either Bootstrap 4 or 5. So do you guys have any ideas on how to migrate our project so we don't need to upgrade from Bootstrap 3?
I tried finding information about this but there is not really that much. Upgrading from Bootstrap 3 to 4 would cause rewriting huge amount of our HTML also.
You could try to configure the helper's template's to make the output Bootstrap 3 compatible, and possibly extend the plugin helpers to add/change functionality where necessary and possible.
If that doesn't suffice, then another option could be to use your own fork of friendsofcake/bootstrap-ui, either from the 1.x branch which you could try to make compatible with CakePHP 4, or from the 3.x branch which you can try to make compatible with Bootstrap 3.
I can't really tell you which one would be easier, you should probably expect having to invest quite some time into it either way.
Related
I have been upgrading my application from cakephp 3 to cakephp 4. I was using fheider/cakephp-datatables and I have come across ypnos-web/cakephp-datatables where both support cakephp 3.
I am currently looking for a cakephp-datatable plugin which supports cakephp 4.
If anybody has an idea, I would be happy.
Thanks in Advance.
Isn't the built-in pagination is what you are looking for ? you can do advanced dynamic database links with your HTML tables.
I successfully use ypnos-web/cakephp-datatables on CakePHP 4.2.7. It works very well for me.
You might have to play around a bit to get it working correctly. Read some of the issues (open and closed) on the ypnos-web/cakephp-datatables github repository and you can likely get it working.
Good Luck!
Have a few projects in angular 1.x and wondering if its really necessary/efficient to move them to angular 4 / later.
Smaller dashboards would not be necessary as it is used internally by minimum number of people. But the bigger customer facing application (3 year old product ) is under the question, as new requirements are being developed.
According to surveys, Angular 1.x is still being used in many companies and the community is still active on making new libraries.
So is it worth shifting?
In my opinion you should leave those projects in Angular 1 and start using Angular 7 for newer Projects. Here is a good article comparing the two: https://www.uruit.com/blog/angular-1-vs-2-migrate/
If you have projects on angular1 developed, then those can be migrated to angular 7 module by module.
Means Using Current angular version, you can run your project in hybrid mode, where you can run angular 7 and angular 1 code together.
For clear understanding, please read these below links
1) https://angular.io/guide/upgrade
2) https://medium.com/contentsquare-engineering-blog/angularjs-to-angular5-upgrading-a-large-application-7e6fbf70bafa
I know many of you are asking how to migrate from Angular 1 to Angular 5. Or from 2 to 5. But my question is a little different. I have my personal application written in Angular 1.2.16 and I would like to know:
1. Is it worth to migrate at all?
2. How complicated that will be?
I know there is a change log in Angular's gitlab which is good thing but it is huge in between two versions. Most of the changes are bugfixes. But is there a lot of incompatibilites between those two versions?
I think that you cannot migrate directly from angularJS 1.2 to 1.6.9, it will be more difficult this way.
You have to make it step by step by looking to this migration guide:
https://docs.angularjs.org/guide/migration
They exposed detailed way to do it from:
1- Migrating from 1.2 to 1.3
2- Migrating from 1.3 to 1.4
3- Migrating from 1.4 to 1.5
Last step:
4- Migrating from 1.5 to 1.6
So you can look at each step and see the changes that you can modify and test if it works as expected.
it can be more time consuming this way but the level of success can be more important.
I am trying to find examples of how to wrap ExtJs and ExtJs 'modules' up for use with a javascript dependency framework such as RequireJS or LAB.
I am working with a large ExtJs based project and there are many separate module files which are just bulk included everywhere and it is getting a little out of control.
Has anyone used an existing depenency management framework with ExtJs? (I know ExtJs 4 may include something similar, but I am fixed on using ExtJs 3)
I wrote my own dependency utility (well my boss wrote it as a method for another framework we are building, and I just ported it to ExtJS) as a mixin where you can just define what your dependencies are, and include events for when they are loaded.
Using Grunt
https://github.com/mattgoldspink/grunt-sencha-dependencies
Sencha Cmd now does it automatically as well - unfortunately it considers ExtJS4.1 as legacy, let alone 3.
What are the risks associated with updating from ExtJS 3.x to Ext JS 4 Beta?
Would you expect that user extensions which work with Ext JS 3.x will work with Ext JS 4 Beta?
Would it be as simple as replacing Ext Js 3.x with ExtJs 4?
Should I update or wait until there is an official stable release?
What are the risks associated with
updating from ExtJS 3.x to Ext JS 4
Beta?
Ext 4 is not backwards-compatible to Ext 3. Expect to spend significant time upgrading and testing, depending on how large your existing application is. Once you see the impact on your specific app, you'll be able to evaluate your own specific risk. It all depends. There will be migration documentation, so hopefully that will mitigate the risk somewhat.
Would you expect that user extensions
which work with Ext JS 3.x will work
with Ext JS 4 Beta?
No, not by default. I would expect most will need to be upgraded, but again, it depends on the specific component.
Would it be as simple as replacing Ext
Js 3.x with ExtJs 4?
No. You might want to watch this thread on the Sencha forums.
I think this question isn't specific to ext js at all. I think the answer to the same for the following question: "Upgrade from <some library i'm using> to <Beta version of next release for library I'm using>?"
And the answer is a recommended no. Betas for 3rd party libs aren't like betas for websites. They could have major changes by the time the final release comes out and any code you write on top of a beta could become useless. To be honest, the most I would do with a beta release is just try and plug it in to my project to gauge how much work is going to be involved in upgrading once the final release comes out.