| # |
Jun 5th 2021, 15:35 |
 admad |
I agree |
| # |
Jun 5th 2021, 15:28 |
kevin.pfeifer |
looking at https://packagist.org/packages/cakephp/cakephp/stats i wonder what happened last month :thinking_face: |
| # |
Jun 5th 2021, 15:03 |
ndm |
I know, but the shipped defaults are just for prototyping anyways... I'd personally would've rather seen the framework's userbase increase by giving the kinds the hip stuff. |
| # |
Jun 5th 2021, 15:02 |
kevin.pfeifer |
not only classes but some DOM changes too I guess |
| # |
Jun 5th 2021, 15:02 |
dereuromark |
Less easy to move away from again |
| # |
Jun 5th 2021, 15:02 |
dereuromark |
The idea Was minimal overhead on the default HTML. Bootstrap requires more class adding ootb |
| # |
Jun 5th 2021, 15:00 |
kevin.pfeifer |
I can imagine that this was definitely not an easy decision back then but as you said it wouldn’t matter that much any more I remember the “old” cake 3 default styling was even more “oldstyle” than the current milligram variant in my opinion :) |
| # |
Jun 5th 2021, 14:57 |
ndm |
Doesn't really matter anymore now though, that horse is already in a tube of glue. It would've mattered back then, but now, I don't think Bootstrap would attract many new users. |
| # |
Jun 5th 2021, 14:55 |
ndm |
and foundation, yeah... which is less esoteric, but still not even closely as popular as bootstrap, at least that was the case back then, not sure how it's nowadays. |
| # |
Jun 5th 2021, 14:53 |
kevin.pfeifer |
you mean miligram as esoteric? |
| # |
Jun 5th 2021, 14:52 |
ndm |
Still a pity IMHO that CakePHP chose the esoteric frameworks instead... going with Bootstrap would have been way more popular. But that's a different topic I guess. |
| # |
Jun 5th 2021, 14:50 |
ndm |
Understandable... I was never a fan of the "frontend" pages made with bootstrap to begin with, but for "backends" I don't mind it. |
| # |
Jun 5th 2021, 14:47 |
kevin.pfeifer |
but I worked with and looked at so many bootstrap pages that I just can’t stand them any more |
| # |
Jun 5th 2021, 14:47 |
kevin.pfeifer |
im sorry ,:) |
| # |
Jun 5th 2021, 14:43 |
ndm |
You're welcome... even after learning that you're a bootsrap-ophobe :P |
| # |
Jun 5th 2021, 14:38 |
kevin.pfeifer |
ok, then I will do that :) thx |
| # |
Jun 5th 2021, 14:36 |
ndm |
the browsers I mean |
| # |
Jun 5th 2021, 14:36 |
ndm |
Or maybe they wouldn't... sensitive data and what not. |
| # |
Jun 5th 2021, 14:35 |
ndm |
In a perfect world browsers would offer such functionality out of the box I guess... anyways, sure, why not, generally reasonable I guess :) I'd say it's a good fit for a component, it knows about the request object, you can inject the additional model dependency so that it can create entities with the data from the cookie, and you let it manually know (when your save succeeds) that you want the cookie to be set/updated. |
| # |
Jun 5th 2021, 14:31 |
slackebot |
(yea, i know) So I thought well, lets create a cookie with a 1 year lifespan or something stupid. |
| # |
Jun 5th 2021, 14:31 |
kevin.pfeifer |
OK, the full example is the following: I am in a choir and created a registration page for our choir members to “register” on each choir practice with name, email and phone because we need the info if one of our members has COVID. Since we have lazy ass members they now asked me if I can “save” their data without the need of them creating an account on my page so they don’t need to fill out those 3 input fields |
| # |
Jun 5th 2021, 14:27 |
ndm |
Well, it's definitely not something that should be in your model in any way shape or form, that's really not it's concern. Whether the concept makes sense... depends I'd say, on what kind of data it is, why it needs to seemingly survive across sessions, etc. |
| # |
Jun 5th 2021, 14:24 |
kevin.pfeifer |
or is this a horrible idea :) |
| # |
Jun 5th 2021, 14:19 |
kevin.pfeifer |
basically I want to provide prefilled data for users who have already entered a specific form. And I thought I could add a cookie with the filled in data on save, check for that cookie when loading the page and prefill the form with that data |
| # |
Jun 5th 2021, 14:14 |
ndm |
If you let us know what that cookie is good for, you may get a better answer :upside_down_face: |
| # |
Jun 5th 2021, 14:13 |
kevin.pfeifer |
ok, was just curious :) |
| # |
Jun 5th 2021, 14:12 |
ndm |
Given that the model layer in CakePHP apps is usually just ORM, yeah, that's not something that your model should do, or even know about in the first place. |
| # |
Jun 5th 2021, 14:06 |
kevin.pfeifer |
or should cookie logic always be present in the controller? |
| # |
Jun 5th 2021, 14:04 |
kevin.pfeifer |
is it possible to set a Cookie inside a beforeSave hook in the model? Currently I only find ways to set cookies via the request object which I can’t access in the model |
| # |
Jun 5th 2021, 11:26 |
fresnel.brieuc |
Thank you so much ! Exactly what I needed :) |
| # |
Jun 5th 2021, 11:24 |
slackebot |
contributor @markstory, • https://github.com/markstory/cakephp-typescript-react • https://github.com/markstory/docket-app Above projects are more than enough for you to get understanding I hope. |
| # |
Jun 5th 2021, 11:24 |
isvyas |
Hi @fresnel.brieuc, there's one repo that I've created to demonstrate CakePHP3 + Vue. Currently vue.js version is 2 but general idea would be the same for vue3 or react. • CakePHP + Vue: https://github.com/ishanvyas22/cakephpvue-spa Above project uses https://github.com/ishanvyas22/asset-mix plugin which makes using modern frontend with CakePHP a breeze. There's also couple of projects for CakePHP + React from core CakePHP |
| # |
Jun 5th 2021, 09:19 |
fresnel.brieuc |
Kinda new on making front-end and back-end frameworks together |
| # |
Jun 5th 2021, 09:17 |
fresnel.brieuc |
Hello there. I'm trying to use Cake4 + Vue3 and I can't find many resources on how to integrate vue properly with cake. Right now I have to build my vue project and copy/paste the production build into Cake webroot... does any one know of a tutorial on a clean way to do this ? Maybe a tutorial on how to integrate a js framework into cake, if there's none about vue specifically ? |
| # |
Jun 4th 2021, 19:40 |
kevin.pfeifer |
:+1: no problem |
| # |
Jun 4th 2021, 19:40 |
aengblom |
Makes sense to me now! I am working on an existing application that already had this incorporated into it. I didn't fully understand it. Today came the day where I actually had to worry about translations, lol. Thank you so much for your help and kindness! |
| # |
Jun 4th 2021, 19:38 |
kevin.pfeifer |
To explain what each file does: *default.pot* is basically just a template file for what can be translated in whatever language you desire *default.po* is the editable translation file for your desired language *default.mo* is the compiled translation file which cakephp actually reads |
| # |
Jun 4th 2021, 19:37 |
aengblom |
Thank you, Kevin! This helps a ton! I think I understand it now. |
| # |
Jun 4th 2021, 19:36 |
kevin.pfeifer |
so the process would be like 1. generate new `default.pot` file with `bin/cake extract` 2. update already present `default.po` (no t at the end!) with the new `default.pot` file via PoEdit 3. Translate your new strings 4. Save the `default.po` file so PoEdit generates a new `default.mo` 5. Check if strings are translated as you desire in your app 6. If not, do a `bin/cake cache clear_all` |
| # |
Jun 4th 2021, 19:34 |
aengblom |
Ok, gotcha |
| # |
Jun 4th 2021, 19:33 |
kevin.pfeifer |
which you then can translate |