Re: 3.0: a peek into CakePHP's future

I don't think we'll be introducing another tight coupling with a client side framework. In the past we had an integration with prototype, and anyone not using prototype was left out. Choosing something like ember or angular would make CakePHP unsuitable for people wanting to use the other client side framework. I'd rather leave CakePHP un-opinionated about client side frameworks and leave that integration up to the developer.

-Mark

On Wednesday, 17 July 2013 22:46:56 UTC-4, Benjamin Allison wrote:

I suppose the larger point is this: right now, most web apps require two separate frameworks: server-side and client-side. While the name itself, CakePHP, implies what its focus is, maybe it's worth considering including some more Javascript utilities, so that AJAXy web apps can follow Cake conventions, and both halves can be integrated more tightly.

-- 

benjamin allison – designer

b...@roestudios.com

http://www.roestudios.com

http://www.benjamin-samuel.com

On 2013-07-17, at 10:34 PM, mark_story wrote:

The current plan that Jose and I have discussed is to return objects from the Models/Repo/Table objects. (The name isn't decided yet).  This fixes many of the data format issues and also mostly makes afterFind irrelevant which is nice.

We've also removed containable in name but mainlined it in spirit. Instead of being a separate behavior controlling joins is part of the query builder.

What parts of SecurityComponent are hard for ajax applications? I don't think there will be a way to use the form tampering prevention with ajax forms, however it is already possible to protect those forms from CSRF issues with re-usable CSRF tokens.

-Mark

On Sunday, 5 May 2013 23:52:14 UTC-4, Benjamin Allison wrote:

If you're reworking the model layer, I think the most important things are:

1) Harmonizing the format that data and associated data is save in and returned in. Right now, it's all over the map, and is sometimes hard to keep straight.

2) Allowing for a smoother way to filter models by their associated models; having to write joins is kind of a pain.

In addition, a smoother way of using AJAX with the Security component to help accomodate the growing trend of JS based web apps.

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to a topic in the Google Groups "CakePHP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cake-php/-TLn6RpHt4U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cake-php+u...@googlegroups.com.
To post to this group, send email to cake...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.