| # |
Jun 27th 2017, 10:01 |
 neon1024 |
Most JS libraries I use are on Packagist. So I install them with Composer and symlink them into /webroot |
| # |
Jun 27th 2017, 10:01 |
birdy247 |
and then copy/paste it to an "assets" folder in webroot |
| # |
Jun 27th 2017, 10:01 |
birdy247 |
I currently download something i.e. bootstrap |
| # |
Jun 27th 2017, 10:01 |
birdy247 |
I mean the files |
| # |
Jun 27th 2017, 10:01 |
neon1024 |
Yeah, don’t do that. |
| # |
Jun 27th 2017, 10:00 |
neon1024 |
Er :S |
| # |
Jun 27th 2017, 10:00 |
birdy247 |
I never really feel right doing that |
| # |
Jun 27th 2017, 10:00 |
birdy247 |
Better than copy/pasting js |
| # |
Jun 27th 2017, 10:00 |
neon1024 |
Perhaps my front-end stuff isn’t complex enough |
| # |
Jun 27th 2017, 10:00 |
neon1024 |
Just feels totally superfluous to me |
| # |
Jun 27th 2017, 09:59 |
birdy247 |
Thats how we intend to use it |
| # |
Jun 27th 2017, 09:59 |
birdy247 |
Cant you just install locally and push to dev? |
| # |
Jun 27th 2017, 09:59 |
neon1024 |
Perhaps you can use it to build assets in development before pushing the compiled stuff up to production |
| # |
Jun 27th 2017, 09:59 |
neon1024 |
I don’t want those on production |
| # |
Jun 27th 2017, 09:59 |
neon1024 |
I don’t like that it has both NodeJS and NPM has dependancies |
| # |
Jun 27th 2017, 09:59 |
birdy247 |
Any reason why? |
| # |
Jun 27th 2017, 09:58 |
neon1024 |
But I’m a back-end developer. What do I know about front-end? |
| # |
Jun 27th 2017, 09:58 |
neon1024 |
Really |
| # |
Jun 27th 2017, 09:58 |
birdy247 |
@neon1024 for real or sarcastic? |
| # |
Jun 27th 2017, 09:58 |
hmic |
like, at least, foollow the tutorials in the book closely and play a litte with that code base |
| # |
Jun 27th 2017, 09:57 |
hmic |
IMHO you should not start with that app as your first 3.x project. i highly recommend you do some 3.x work before |
| # |
Jun 27th 2017, 09:57 |
neon1024 |
@birdy247 No, I would not. |
| # |
Jun 27th 2017, 09:57 |
hmic |
it might be better to create a new app and move stuff over from the old one, as this is clearly a cleaner approach. and if you need to refactor the controllers completely anyways, i'd go this way likely |
| # |
Jun 27th 2017, 09:57 |
birdy247 |
neon1024 would you recomend using bower? |
| # |
Jun 27th 2017, 09:55 |
birdy247 |
never used bower before |
| # |
Jun 27th 2017, 09:54 |
birdy247 |
using it as a way to learn how bower works |
| # |
Jun 27th 2017, 09:54 |
neon1024 |
:O |
| # |
Jun 27th 2017, 09:54 |
hmic |
at least the namespacing and other easily automated stuff will be done |
| # |
Jun 27th 2017, 09:54 |
birdy247 |
@neon1024 we are just checking out your cake exchange repo :slightly_smiling_face: |
| # |
Jun 27th 2017, 09:54 |
birdy247 |
Morning |
| # |
Jun 27th 2017, 09:54 |
hmic |
it helps with some aspects, sure |
| # |
Jun 27th 2017, 09:54 |
bordplate |
Great tips, thanks! Is the upgrade-tool a good way to go for this? |
| # |
Jun 27th 2017, 09:52 |
neon1024 |
Good opportunity to refactor! |
| # |
Jun 27th 2017, 09:52 |
hmic |
you can do that before the 3.x migration though - just keep in mind to have good seperatin implemented already, make use of events where applicable |
| # |
Jun 27th 2017, 09:51 |
hmic |
you can start - and should- remvoe the business logic from the controllers and build seperate classes for them |
| # |
Jun 27th 2017, 09:51 |
hmic |
the ORM/model level has changed completely though |
| # |
Jun 27th 2017, 09:50 |
bordplate |
Great! That’s all the motivation I need for this. I’m also trying to get developers to stop putting *all* business logic in controllers. It’s beyond annoying to have to recreate all code when adding a new feature. |
| # |
Jun 27th 2017, 09:50 |
hmic |
besides the usage of namespaces and autoloading with composer not much has changed on the surface of your controller and view levels |
| # |
Jun 27th 2017, 09:49 |
hmic |
bordplate: very feasable project. and very much worth it, if you want to develop this app for years still... |
| # |
Jun 27th 2017, 09:37 |
slackebot |
appreciated. |
| # |
Jun 27th 2017, 09:37 |
bordplate |
I need some advice here. We have a CakePHP 2.x project that is at right above 32 000 lines of code (most of which is just in controllers) and I want to migrate this over to CakePHP 3.4, because I’m sure this system will be used here and be actively developed for at least another decade. Is this an infeasible amount of work? Also, I’m kind of struggling to see how the new structure is, so any good blog posts or so about migrating would |