Re: 3.0: a peek into CakePHP's future
I don't think that shift towards ORM is a bad choice. The Model Layer of CakePHP was quite staightforward, but it lacked efficiency in terms of readibility and flexibility. The implementation of ORM might frighten the old folks, accustomed to Active Record Queries, but in the end its a step forward, which will bring more developers, who are already using these tehcniques. Whether we like it or not, more data abstraction will be applied as the tools we use and programms we write become more complex and powerfull. A few drawbacks i have to mention about new version are competitiveness and community scale. Frameworks like Symfony2 have already a large community which provides a great number of standard components (called bundles) for various types of web applications. I think it would be tough for CakePHP to compete with other frameworks, which implemented similar techniques a long time ago and already built an extensive community around that. But the one thing that still encourages me to use CakePHP is it's strcuture that speaks to the core of issue you are trying to solve, an approach to problem not as a developer but a problem solver. I hope we will love to use CakePHP for a long time. -- 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+unsubscr...@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/d/optout.
Re: 3.0: a peek into CakePHP's future
I will also express my concerns about removing the named parameters. Will you be removing only short names or regular expressions also? -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Both. All named parameter support has been removed. The only aspect of it that remains is the ability to parse incoming URLs using named parameters. Named parameters were a big mistake. They duplicated GET parameters with almost no benefit for the additional pain they cause. If you've ever had to generate URLs with named parameters in systems that are not CakePHP you have some idea as to why named parameters were a mistake. -Mark On Sunday, 5 January 2014 06:25:13 UTC-5, Marush Denchev wrote: I will also express my concerns about removing the named parameters. Will you be removing only short names or regular expressions also? -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
This thread has been pretty popular, and I'm happy to announce that we've just published the first dev preview release for 3.0, which includes most of the new ORM features. A few behaviors are missing, but the basics are there. It would be great to hear any feedback you folks have. Make sure you check out the documentation to see how the ORM works without having to write any code. http://book.cakephp.org/3.0/en/orm.html -Mark On Thursday, 5 July 2012 22:36:03 UTC-4, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message
Re: 3.0: a peek into CakePHP's future
Gersonfs, you will be able to replace that with query string params, Cake 3 will change much anyway thus your app will need a big upgrade. On Thursday, September 12, 2013 7:15:54 PM UTC+2, gersonfs wrote: Remove support for named parameters would not be nice to me. I have a lot of code that makes use of this feature. Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo escreveu: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- 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
Re: 3.0: a peek into CakePHP's future
This has to be one of the funniest threads I have seen in a long time, thanks for the laughs guys. -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Remove support for named parameters would not be nice to me. I have a lot of code that makes use of this feature. Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo escreveu: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- 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+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at
Re: 3.0: a peek into CakePHP's future
It's been over a year now, and there is no real info when CakePHP 3.0 will be ready. Any chances guys to create more detailed Roadmap for cakephp development, like: alfa,RC1 - this would let developers to plan ahead with their work. Just because CakePHP Roadmap is so blurry I was forced to use Symfony in my few latest projects (MongoDB support, Namespaces, PHP 5.4 features), even thou learning curve was quite steep. Id love to use CakePHP but i feel like its getting far behind its competition. I would be even ready to start developemnt of long term project if there was draft Model layer integrated with ORM (at https://github.com/cakephp/cakephp/tree/3.0). If u guys got already some code maybe share a branch so we can all watch its development, or at least tell us it hasn't been started yet. W dniu piątek, 6 lipca 2012 16:11:50 UTC+2 użytkownik José Lorenzo napisał: On Friday, July 6, 2012 8:47:18 AM UTC-4:30, Marsson wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? Yes :) On Fri, Jul 6, 2012 at 6:33 AM, Kazik kaz...@gmail.com javascript:wrote: On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+u...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/cake-php -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
That sounds like a cool idea, try submitting a pull request for 3.0! On Tuesday, August 20, 2013 1:08:01 PM UTC-7, Vanja Dizdarević wrote: PROBLEM: After finally learning the Events system, I found myself wishing for a sub-event binding triggering scheme. If I have some callbacks bound on Order.change and some on Order.addProduct, I have to create and trigger two separate events and results for the same functionality. IDEA: Dispatched event Order.change:addProduct,updateShipment triggers callbacks which are bound to events: - Order.change - Order.change:addProduct - Order.change:updateShipment - Order.change:updateShipment,addProduct Something similar to *scope* resolution in CakeLog. I would love to have (or write) that in Cake3.0! -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
PROBLEM: After finally learning the Events system, I found myself wishing for a sub-event binding triggering scheme. If I have some callbacks bound on Order.change and some on Order.addProduct, I have to create and trigger two separate events and results for the same functionality. IDEA: Dispatched event Order.change:addProduct,updateShipment triggers callbacks which are bound to events: - Order.change - Order.change:addProduct - Order.change:updateShipment - Order.change:updateShipment,addProduct Something similar to *scope* resolution in CakeLog. I would love to have (or write) that in Cake3.0! -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Hi, I'm new to this group and I've just read this whole thread. I've been happily working with CakePHP for two years. *My thumbs up for OO models!* I understand you don't have a release date for 3.0, but is there any unofficial estimate? Like will it come during this year? I just can't wait! Congratulations to the core devs on their excellent work! I know it's not the right thread, but: - Since I'm from Argentina but I perfectly understand English, I'd like to help with Spanish localizations. Where could I start? - Is there such thing as an official Argentinean CakePHP community? Cheers! On Thursday, August 8, 2013 5:39:44 AM UTC-3, Muhammad Arslan wrote: It will return both i.e arrays and objects. On Friday, July 6, 2012 6:17:18 PM UTC+5, Marsson wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? On Fri, Jul 6, 2012 at 6:33 AM, Kazik kaz...@gmail.com wrote: On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+u...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
It will return both i.e arrays and objects. On Friday, July 6, 2012 6:17:18 PM UTC+5, Marsson wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? On Fri, Jul 6, 2012 at 6:33 AM, Kazik kaz...@gmail.com javascript:wrote: On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+u...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/cake-php -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Indeed, CakePHP shouldn't be (tightly) coupled with any frontend framework. Joomla! for example learnt its lessons when they wanted to get rid of the coupled mootools. If CakePHP should be coupled, then certainly with the most popular anyway. There are many tastes, preferences etc and thus opnions vary very much. Nonetheless jQuery is the most popular and most widely used one. But still I wouldn't couple CakePHP with it too tightly. It's too easy to download the newest version of jQuery or link it through a CDN in your views anyway. I think for many developers having scaffolding and baking with a powerful and javascript-empowered UI seem very useful at first. That's why they want to have CakePHP to also include those frontend tools. But after some experience with baking and scaffolding I must say I'd prefer that CakePHP would even dump it down. Integration of such frameworks or improved scaffolding in any way should be done trhough plugins. So the integration of jQuery itself or TwitterBootstrap (which is based on jQuery) for example, which are both very popular, could and should - IMHO - be done in a first class citizen plugin - if there is enough demand for it. There are already such projects around. For example: https://github.com/slywalker/cakephp-plugin-boost_cake (or it's predecessor). or some you find here: http://plugins.cakephp.org/packages?query=admin I think it would make sense to outsource these efforts away from the project itself to a few dedicated and by the CakePHP lead (oficially/inofficially) supported projects. Marc On Tuesday, August 6, 2013 6:21:54 PM UTC+2, mark_story wrote: 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 -- 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+unsubscr...@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.
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 javascript: 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 javascript:. To post to this group, send email to cake...@googlegroups.comjavascript: . 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
I'm starting to use angular.js, it's realy cool, and now i developing api first, with this i can distribute to smartphone, tablets, html5 applications more easy and fast. And the workflow looks better Em quarta-feira, 17 de julho de 2013 23h46min56s UTC-3, Benjamin Allison escreveu: 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 javascript: 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 javascript:. To post to this group, send email to cake...@googlegroups.comjavascript: . 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Mark, It's good you directly include the containable behavior. Since I'v started using CakePHP last winter I've heard it so many times from experienced developers (e.g. in IRC) that this is a must have in everyone's app, that I was wondering why is it not activated by default then? ;-) Thanks for your work! Marc On Thursday, July 18, 2013 4:34:10 AM UTC+2, 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 the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
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 the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Yes there will be an upgrade shell much like there was from 1.x to 2.x. While a script won't be able to handle all the changes made, we're also keeping a detailed list of changes to help people upgrade/learn about what has changed. -Mark On Monday, 6 May 2013 13:53:51 UTC-4, steve van christie wrote: is version 3.x. support upgrade from previous version? just a suggestion, why not use something like backward compatiblity like the others framework have. best regards -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
Perhaps if there was an easy interface, that sends a new token as a return value for AJAX requests? Something we could repopulate a form with in the DOM? I haven't thought anything through I'm just thinking out loud. -- 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+unsubscr...@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. -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
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+unsubscr...@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. -- 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+unsubscr...@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.
Re: 3.0: a peek into CakePHP's future
is version 3.x. support upgrade from previous version? just a suggestion, why not use something like backward compatiblity like the others framework have. best regards -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
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 the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
Also, maintaing data to afterFind, afterSave, and afterDelete would be super useful. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
I am super confused about people's hesitation to using objects. Objects are smarter than arrays and I am pretty sure we will be able to do something like toArray() on them. Furthermore, code that originally lived in our Model::afterfind() could be moved to the Objects making room for more complicated behavior and manipulation of the data without adding the complexity of 20 if statements in Model::afterFind(), lol, you know what I am talking about! Of course, this is me assuming that the Class that Model use to return Objects can be either auto-magically created by Cake or defined by the developer. I'm actually pretty damn excited about using Objects. On Monday, July 16, 2012 4:46:10 AM UTC-4, bruno wrote: When I started to build a behavior for queries to return object in place of array (Active Record Pattern for cakePHP, in the bakery), I was not aware of the plans for CakePHP 3.0. But according to the discussion here, some people seems worrying about being obliged of using objects in place of arrays (this would also make application upgrade really difficullt or nearly impossible). Wouldn't be wiser to let the developer to decide whether he wants arrays or objects? And to propose for example an integration with Doctrine (or to enhance the behavior I wrote)? Thank you anyway for your hard work to improve cakePHP! Op vrijdag 6 juli 2012 04:36:03 UTC+2 schreef José Lorenzo het volgende: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4
Re: 3.0: a peek into CakePHP's future
Nothing else at this subject? I am anxious for this version of Cake Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo escreveu: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- 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+unsubscr...@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?hl=en. For more options, visit
Re: 3.0: a peek into CakePHP's future
Dear, thanks for sending, i would like to be part of your team if you can give me chance. best wishes Nematullah Atef On Mon, Apr 1, 2013 at 5:42 PM, André Luis cavall...@live.com wrote: Nothing else at this subject? I am anxious for this version of Cake Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo escreveu: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- 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?hl=en. To
Re: 3.0: a peek into CakePHP's future
Dear Jose Lorenoz, thanks for detail, i would like to express i am new in PHP i want to start work in CakePHP with best interest but i am not able to start i installed but not able to go ahead i have knowledge of PHP but how can i do? could you send me the link of Video to find somewhere if help me please to get my new step in development section. looking from your side, best wishes Nematullah atef On Friday, July 6, 2012 7:06:03 AM UTC+4:30, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are
Re: 3.0: a peek into CakePHP's future
Dear Jose Lorenoz, thanks for detail, i would like to express i am new in PHP i want to start work in CakePHP with best interest but i am not able to start i installed but not able to go ahead i have knowledge of PHP but how can i do? could you send me the link of Video to find somewhere if help me please to get my new step in development section. looking from your side, best wishes Nematullah atef On Friday, July 6, 2012 7:06:03 AM UTC+4:30, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are
Re: 3.0: a peek into CakePHP's future
Dear Jose Lorenoz, thanks for detail, i would like to express i am new in PHP i want to start work in CakePHP with best interest but i am not able to start i installed but not able to go ahead i have knowledge of PHP but how can i do? could you send me the link of Video to find somewhere if help me please to get my new step in development section. looking from your side, best wishes Nematullah atef On Friday, July 6, 2012 7:06:03 AM UTC+4:30, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are
Re: 3.0: a peek into CakePHP's future
On Wed, Feb 20, 2013 at 12:57 PM, Cees-Jan Kiewiet ceesj...@gmail.comwrote: You're free in sending a PR to https://github.com/cakephp/docs with your improvements :). People who read documentation are usually not the best choice to write it. We're not talking about typos or poor grammar. However, I might do that. I just last night had an idea for improving how the API docs are browsed. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
You're free in sending a PR to https://github.com/cakephp/docs with your improvements :). On Wed, Feb 20, 2013 at 1:15 AM, lowpass zijn.digi...@gmail.com wrote: Anything but the Lord of the Rings examples! Nothing against LotR -- it's just that it's a huge distraction from the problem people are attempting to understand. I remember being really confused reading that. Wait -- which one's Pippin?! On Tue, Feb 19, 2013 at 7:28 AM, Novrian YF andi.novr...@gmail.com wrote: I'm a CakeNoobs, and I'm sure some noobs out there were been confusing to understand Cake Built-in ACL. So, I hope the core team will improve docs related on ACL :D -- 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+unsubscr...@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?hl=en. 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- http://wyrihaximus.net/ Websitehttp://wyrihaximus.net/?utm_source=signatureutm_medium=emailutm_campaign=emailsignature | Bloghttp://blog.wyrihaximus.net/?utm_source=signatureutm_medium=emailutm_campaign=emailsignature | Linkedin http://nl.linkedin.com/in/ceesjankiewiet | Twitterhttp://twitter.com/wyrihaximus | Facebook http://www.facebook.com/CeesJan.Kiewiet -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
I'm a CakeNoobs, and I'm sure some noobs out there were been confusing to understand Cake Built-in ACL. So, I hope the core team will improve docs related on ACL :D -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
Anything but the Lord of the Rings examples! Nothing against LotR -- it's just that it's a huge distraction from the problem people are attempting to understand. I remember being really confused reading that. Wait -- which one's Pippin?! On Tue, Feb 19, 2013 at 7:28 AM, Novrian YF andi.novr...@gmail.com wrote: I'm a CakeNoobs, and I'm sure some noobs out there were been confusing to understand Cake Built-in ACL. So, I hope the core team will improve docs related on ACL :D -- 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+unsubscr...@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?hl=en. 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
I got turned off for years the same reason. Then I had a project that *really* needed ACL, so I piled in and learned it. Now I use it on every project. The Acl plugin makes life easier but isn't very user friendly (or robust). Jeremy Burns Class Outfit http://www.classoutfit.com On 20 Feb 2013, at 00:15:17, lowpass zijn.digi...@gmail.com wrote: Anything but the Lord of the Rings examples! Nothing against LotR -- it's just that it's a huge distraction from the problem people are attempting to understand. I remember being really confused reading that. Wait -- which one's Pippin?! On Tue, Feb 19, 2013 at 7:28 AM, Novrian YF andi.novr...@gmail.com wrote: I'm a CakeNoobs, and I'm sure some noobs out there were been confusing to understand Cake Built-in ACL. So, I hope the core team will improve docs related on ACL :D -- 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+unsubscr...@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?hl=en. 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+unsubscr...@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?hl=en. 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
On Wednesday, December 5, 2012 11:22:33 PM UTC+1, pete wrote: I like the code first approach in doctrine and i'm really missing this in cakephp to write the model and generate the database. I like to start by writing up model test cases+fixtures and then moving them to cake schema when I'm satisfied with the result. I'm not really that familiar with doctrine, but I get the feeling that schema (or Migrations) is a very underused shell. Is it possible that a tighter coupling between Model, fixtures and SchemaShell which would allow for a more code first approach? -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: 3.0: a peek into CakePHP's future
With the re-writing of the model layer, I would like to suggest some base changes for the Master/Slave use-case. We can debate for hours on how to handle such a use-case - Proxy software like Tungsten or MysqlProxy - Extend models ( MyModelMyModelWrite) and configure connection and table settings on *Write Models - Overload the writing methods in the base Model and do connection switching in the Overload ( I use this method on a very high traffic website: hundred of millions of queries a day ) With the base support being php5.4 and the support for late static binding, I would like to see the implementation of a Connection Strategy using the strategy pattern and late static binding to handle connection referencing for such a common use-case. I would be more than glad to help contributing to such a feature if need be. -JH On Thursday, July 5, 2012 7:36:03 PM UTC-7, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the
Re: 3.0: a peek into CakePHP's future
I'm a little curious to see the Models... Em quarta-feira, 23 de janeiro de 2013 11h35min20s UTC-2, Sipatshi escreveu: cant wait to use the new query builder ;) -- *Von:* Celso cel...@gmail.com javascript: *An:* cake...@googlegroups.com javascript: *CC:* Serkan Sipahi serkan...@yahoo.de javascript: *Gesendet:* 14:22 Mittwoch, 23.Januar 2013 *Betreff:* Re: 3.0: a peek into CakePHP's future Thanks @Sipatshi, one more link, the José Lorenzo Slide: http://www.slideshare.net/josezap1/cakephp-30-embracing-the-future-15080099 Em quarta-feira, 23 de janeiro de 2013 11h08min44s UTC-2, Sipatshi escreveu: The latest news about cake 3.0 http://vimeo.com/56613033 https://www.engineyard.com/ podcast/future-of-php-part-ii- cakephphttps://www.engineyard.com/podcast/future-of-php-part-ii-cakephp https://github.com/markstory/ cakephp/wiki/Httpsocket- improvementshttps://github.com/markstory/cakephp/wiki/Httpsocket-improvements -- *Von:* Celso cel...@gmail.com *An:* cake...@googlegroups.com *Gesendet:* 13:45 Mittwoch, 23.Januar 2013 *Betreff:* Re: 3.0: a peek into CakePHP's future Anyone have some news about CakesPHP 3.0? -- Like Us on FaceBook https://www.facebook.com/ CakePHPhttps://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 post to this group, send email to cake...@googlegroups.com. To unsubscribe from this group, send email to cake-php+u...@ googlegroups.com. Visit this group at http://groups.google.com/ group/cake-php?hl=enhttp://groups.google.com/group/cake-php?hl=en . AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarian CatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGerman GreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalian JapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersian PolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedish ThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabic ArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrench GalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandic IndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalay MalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovak SlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelsh Yiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake...@googlegroups.comjavascript: . To unsubscribe from this group, send email to cake-php+u...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/cake-php?hl=en. AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarian CatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGerman GreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalian JapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersian PolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedish ThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabic ArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrench GalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandic IndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalay MalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovak SlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelsh Yiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
Anyone have some news about CakesPHP 3.0? -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
The latest news about cake 3.0 http://vimeo.com/56613033 https://www.engineyard.com/podcast/future-of-php-part-ii-cakephp https://github.com/markstory/cakephp/wiki/Httpsocket-improvements Von: Celso cels...@gmail.com An: cake-php@googlegroups.com Gesendet: 13:45 Mittwoch, 23.Januar 2013 Betreff: Re: 3.0: a peek into CakePHP's future Anyone have some news about CakesPHP 3.0? -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
Thanks @Sipatshi, one more link, the José Lorenzo Slide: http://www.slideshare.net/josezap1/cakephp-30-embracing-the-future-15080099 Em quarta-feira, 23 de janeiro de 2013 11h08min44s UTC-2, Sipatshi escreveu: The latest news about cake 3.0 http://vimeo.com/56613033 https://www.engineyard.com/podcast/future-of-php-part-ii-cakephp https://github.com/markstory/cakephp/wiki/Httpsocket-improvements -- *Von:* Celso cel...@gmail.com javascript: *An:* cake...@googlegroups.com javascript: *Gesendet:* 13:45 Mittwoch, 23.Januar 2013 *Betreff:* Re: 3.0: a peek into CakePHP's future Anyone have some news about CakesPHP 3.0? -- 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 post to this group, send email to cake...@googlegroups.comjavascript: . To unsubscribe from this group, send email to cake-php+u...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/cake-php?hl=en. AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarian CatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGerman GreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalian JapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersian PolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedish ThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabic ArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrench GalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandic IndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalay MalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovak SlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelsh Yiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
cant wait to use the new query builder ;) Von: Celso cels...@gmail.com An: cake-php@googlegroups.com CC: Serkan Sipahi serkan.sip...@yahoo.de Gesendet: 14:22 Mittwoch, 23.Januar 2013 Betreff: Re: 3.0: a peek into CakePHP's future Thanks @Sipatshi, one more link, the José Lorenzo Slide: http://www.slideshare.net/josezap1/cakephp-30-embracing-the-future-15080099 Em quarta-feira, 23 de janeiro de 2013 11h08min44s UTC-2, Sipatshi escreveu: The latest news about cake 3.0 http://vimeo.com/56613033 https://www.engineyard.com/ podcast/future-of-php-part-ii- cakephp https://github.com/markstory/ cakephp/wiki/Httpsocket- improvements Von: Celso cel...@gmail.com An: cake...@googlegroups.com Gesendet: 13:45 Mittwoch, 23.Januar 2013 Betreff: Re: 3.0: a peek into CakePHP's future Anyone have some news about CakesPHP 3.0? -- 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 post to this group, send email to cake...@googlegroups.com. To unsubscribe from this group, send email to cake-php+u...@ googlegroups.com. Visit this group at http://groups.google.com/ group/cake-php?hl=en. AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDetect languageDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish⇄AfrikaansAlbanianArabicArmenianAzerbaijaniBasqueBelarusianBulgarianCatalanChinese (Simplified)Chinese (Traditional)CroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGeorgianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatinLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishThaiTurkishUkrainianUrduVietnameseWelshYiddish Sprache erkennen » Hungarian -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
The modeling for me as PHP programmer is much more simpler when i can descripe my models in PHP. You also have to decide first which RDBMS you want to use. I think this is a limitation so it is not so easy to switch to another Datastore in development process because the code first approach is not implemented to generate new DB schema. Also i think is it more the right direction to change models on PHP-side and than apply changes automatted to the DB. I worked with both approaches and i feel better with the Doctrine code first way. greets pete by the way i got mail from 139.com in chinese related to this topic. it seems there is a spam bot in mailing list? -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
It would be great to support Doctrine, lots of PHP programmers know and master it so this can be a good point for adopting new CakePHP users. But, just a suggestion, what if CakePHP can handle any ORM layer? I mean, you can choose a built-in one developed by the framework people, but if you want you can choose a different one and just keep the views and the controller parts. If I'm not wrong, 3.0 will support the magnificent composer dependency manager, and other frameworks like Zend have the possibility to choose which components of Zend you want to use. Wouldn't this be better than the traditional full-stack framework? 2012/12/7 pete peerr...@googlemail.com The modeling for me as PHP programmer is much more simpler when i can descripe my models in PHP. You also have to decide first which RDBMS you want to use. I think this is a limitation so it is not so easy to switch to another Datastore in development process because the code first approach is not implemented to generate new DB schema. Also i think is it more the right direction to change models on PHP-side and than apply changes automatted to the DB. I worked with both approaches and i feel better with the Doctrine code first way. greets pete by the way i got mail from 139.com in chinese related to this topic. it seems there is a spam bot in mailing list? -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. -- Jorge González Web Developer twitter: @jorgonor website: http://jorgonor.blogspot.com.es github: https://github.com/jorgonor -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
I've always preferred to start with the schema because to me the data itself is the most important thing to understand before anything else. It helps that it's all there in front of me in one file, too. After baking up some models, I can go into each and round them out a bit with business logic. It's not that I don't think about that stuff until then, but prefer to sort out what the model records themselves need to look like first. I've migrated from one DB to another on a few occasions and haven't encountered any really big problems. Not to say that it will always be trivial, of course. I get the response from the Chinese site every time I post something to the list. It looks like a bounce. Probably someone is registered to the list but their email account no longer exists. On Fri, Dec 7, 2012 at 4:01 AM, pete peerr...@googlemail.com wrote: The modeling for me as PHP programmer is much more simpler when i can descripe my models in PHP. You also have to decide first which RDBMS you want to use. I think this is a limitation so it is not so easy to switch to another Datastore in development process because the code first approach is not implemented to generate new DB schema. Also i think is it more the right direction to change models on PHP-side and than apply changes automatted to the DB. I worked with both approaches and i feel better with the Doctrine code first way. greets pete by the way i got mail from 139.com in chinese related to this topic. it seems there is a spam bot in mailing list? -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
I much prefer the schema first approach. But then I've always approached a project by first working out the schema (generally, at least) and then moving on to code for doing something useful with it. On Wed, Dec 5, 2012 at 5:22 PM, pete peerr...@googlemail.com wrote: Doctrine was mentioned sometimes. I also think it would be a great idea to use this ORM for doing all the crazy DB things. There is no need for a self implementation because doctrine works very well by now. I like the code first approach in doctrine and i'm really missing this in cakephp to write the model and generate the database. Doctrine has also options to generate migration files for differences in database tables and models during the development process. I mean this features should bbe used in future. greets pete -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
I'm hoping there's still support for legacy databases. It's been one of the strong points for CakePHP so far, that it can handle when the primary key isn't id, and the model name isn't a strict conversion of the table name. -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
Doctrine was mentioned sometimes. I also think it would be a great idea to use this ORM for doing all the crazy DB things. There is no need for a self implementation because doctrine works very well by now. I like the code first approach in doctrine and i'm really missing this in cakephp to write the model and generate the database. Doctrine has also options to generate migration files for differences in database tables and models during the development process. I mean this features should bbe used in future. greets pete -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
Finally. On Friday, July 6, 2012 8:19:30 AM UTC-5, Andy Gale wrote: On Fri, Jul 6, 2012 at 2:17 PM, Marsson C. mars...@gmail.comjavascript: wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? Yes Model layer rewrite: Models to return objects from queries -- Andy Gale http://andy-gale.com http://twitter.com/andygale -- 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 post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
I consider Cake's model the only drawback of Cake in my daily work.
Since I usually operate with large amounts of complex associations in my
models, I have developed three relatively painful work patterns:
1. I use Containable behavior on almost ALL my models (and use it in
nearly every query I write)
2. I bind associations on-the-fly
3. I write my-own-damn-SQL-join-query myself
This takes up quite a lot of my time to optimize my model queries. 87% of
the time, I do not want *all *the related data and I consider it redundant.
Maybe I'm just a lousy programmer, but I find a big need to treat data as
objects, not just to have them deliver me arrays to cumbersomely fiddle
with. Not to mention the mental overload of planning to save related data...
This would be a dream:
$article = $this-Article-findBySlug($slug);
$user = $this-Auth-user('id');
if ($user-myOwnCustomAuthMethod('view', $article));
foreach($article-comments as $comment) //comments are not loaded until
property is requested
{
if ($comment-author-id == $article-id){
// $comment-author is also an overloaded property, returns Author instance
$authorsComments[] = $comment;
}
}
$article-view_count++;
$article-last_viewed = time();
$article-save();
I think Cake Model has some really strong points that should be kept, like
relation definitions, validation (it's maybe a lot of arrays, but it's
useful) and error handling. But I just prefer data objects over arrays and
I think it would sit perfectly into CakePHP. I feel it would offer a simple
way of adding DRY data logic.
So I say HOORAY for any objectification, even if my example is totally
off-road.
OR at least having the option to easily choose a database layer similar to
Doctrine/Propel, if I wanted. Would be very nice.
--
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 post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: 3.0: a peek into CakePHP's future
Cakephp Home:
No complicated XML or *YAML *files. Just setup your database and you're
ready to bake.
Em sexta-feira, 14 de setembro de 2012 12h17min02s UTC-3, Paolo Agostinetto
escreveu:
The var keyword was deprecated in cake 2 (dropping PHP 4 support), you
should use public instead.
Using dockblock doesn't seem to me the proper way to handle model
properties and configuration. Yeah, I know doctine 2 does that, but it
doesn't make sense to me giving to docblocks that kind of power, as
docblocks are just comments. I would use a yaml or ini file instead.
Talking about the ORM: use of arrays is just bad to return the results,
it's not the right tool for the job.
On Tuesday, August 21, 2012 9:52:00 PM UTC+2, Celso wrote:
A model Something like this?
?phpclass Post {var $id;var $title;var $body;var
$created;var $modified;//@belongsTo(class=User,
foreignKey=author_id)var $author;}?
Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo
escreveu:
Since its creation, more than 7 years ago, CakePHP has grown with a life
of its own. Its main goal has always been to empower developers with tools
that are both easy to learn and use, leverage great libraries requiring low
documentation and low dependencies too. We've had several big releases
along these years and an ever growing community. Being one of the most
popular frameworks out there and probably the first one (!) we have also
gotten a lot of criticism from the developer community in general. We have,
though, accepted it and learnt from our mistakes to keep building the best
PHP framework there is.
CakePHP is known for having a very slow pace of adopting new stuff and
it has served very well to its community. Back when we were doing version
2.0 we decided to hold on version 5.2 of PHP for multiple reasons and
despite it didn't let us innovate as much as we wished to, it was an
excellent choice given the general environment regarding hosting solutions
and general adoption of PHP 5.3. A look back into the past reminded us that
we were big innovators in PHP, bringing features to developers that few
dreamt possible to do in this language. Now, it's time to look ahead in
future and decide on staying in our comfort zone or take back our leading
position as innovators.
So it is with great excitement that we announce we are putting our our
efforts in bringing you the next major release of CakePHP. Version 3.0 will
leverage the new features in PHP 5.4 and will include an important change
in our models and database system. CakePHP 3.0 will not be ready less than
6 or 8 months and we reckon that, given the rise of cheap cloud hosting
solutions and upcoming release of new operating system versions, there is
no better time to jump on the most current stable version of PHP.
As you may already know, PHP 5.4 offers awesome features that would
introduce useful new concepts and interesting solutions to old problems.
Closure binding, traits, multibyte support are tools we see of great
usefulness for properly implemented advanced framework features we've had
in mind for a long time. Also new syntax sugar added to the language will
make it more pleasant to write both small and complex applications with the
framework and a always welcomed free performance increase.
We have a young but already well defined road map for what we want to
accomplish in next release and you are invited to contribute and suggest
what's next:
- Drop support for 5.2.x and support 5.4+ only
- Add proper namespaces for all classes. This will make it easier to
reuse classes outside CakePHP and to use external libraries and finally
no
chances of collisions between your app classes and core ones.
- Use traits were possible and makes sense
- Improve bootstrapping process to allow more developer control and
better performance
- Model layer rewrite:
- Models to return objects from queries
- Datamapper-like paradigm
- Richer query API
- Support for any database type
- Support for more database drivers both PDO and native
- Improve Router:
- Make it faster
- Remove named parameters
- Add support for named routes
- Smarter router prefixes
- Shorter url syntax
As you may imagine most of the time will be spent or rewriting the model
layer, but it will also be one of the most powerful features CakePHP 3.0
will have. It's new architecture based on PHP 5.4 capabilities will offer
an easier and more powerful set of tools to build web applications in no
time.
If you are already as excited as we are this all this new stuff coming,
you definitely should meet us on next CakeFest http://cakefest.org/ we'll
be talking about the future of CakePHP and hacking our way through to bring
you a dev release as soon as possible. Wouldn't it be
Re: 3.0: a peek into CakePHP's future
The var keyword was deprecated in cake 2 (dropping PHP 4 support), you
should use public instead.
Using dockblock doesn't seem to me the proper way to handle model
properties and configuration. Yeah, I know doctine 2 does that, but it
doesn't make sense to me giving to docblocks that kind of power, as
docblocks are just comments. I would use a yaml or ini file instead.
Talking about the ORM: use of arrays is just bad to return the results,
it's not the right tool for the job.
On Tuesday, August 21, 2012 9:52:00 PM UTC+2, Celso wrote:
A model Something like this?
?phpclass Post {var $id;var $title;var $body;var
$created;var $modified;//@belongsTo(class=User,
foreignKey=author_id)var $author;}?
Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo
escreveu:
Since its creation, more than 7 years ago, CakePHP has grown with a life
of its own. Its main goal has always been to empower developers with tools
that are both easy to learn and use, leverage great libraries requiring low
documentation and low dependencies too. We've had several big releases
along these years and an ever growing community. Being one of the most
popular frameworks out there and probably the first one (!) we have also
gotten a lot of criticism from the developer community in general. We have,
though, accepted it and learnt from our mistakes to keep building the best
PHP framework there is.
CakePHP is known for having a very slow pace of adopting new stuff and it
has served very well to its community. Back when we were doing version 2.0
we decided to hold on version 5.2 of PHP for multiple reasons and despite
it didn't let us innovate as much as we wished to, it was an excellent
choice given the general environment regarding hosting solutions and
general adoption of PHP 5.3. A look back into the past reminded us that we
were big innovators in PHP, bringing features to developers that few dreamt
possible to do in this language. Now, it's time to look ahead in future and
decide on staying in our comfort zone or take back our leading position as
innovators.
So it is with great excitement that we announce we are putting our our
efforts in bringing you the next major release of CakePHP. Version 3.0 will
leverage the new features in PHP 5.4 and will include an important change
in our models and database system. CakePHP 3.0 will not be ready less than
6 or 8 months and we reckon that, given the rise of cheap cloud hosting
solutions and upcoming release of new operating system versions, there is
no better time to jump on the most current stable version of PHP.
As you may already know, PHP 5.4 offers awesome features that would
introduce useful new concepts and interesting solutions to old problems.
Closure binding, traits, multibyte support are tools we see of great
usefulness for properly implemented advanced framework features we've had
in mind for a long time. Also new syntax sugar added to the language will
make it more pleasant to write both small and complex applications with the
framework and a always welcomed free performance increase.
We have a young but already well defined road map for what we want to
accomplish in next release and you are invited to contribute and suggest
what's next:
- Drop support for 5.2.x and support 5.4+ only
- Add proper namespaces for all classes. This will make it easier to
reuse classes outside CakePHP and to use external libraries and finally
no
chances of collisions between your app classes and core ones.
- Use traits were possible and makes sense
- Improve bootstrapping process to allow more developer control and
better performance
- Model layer rewrite:
- Models to return objects from queries
- Datamapper-like paradigm
- Richer query API
- Support for any database type
- Support for more database drivers both PDO and native
- Improve Router:
- Make it faster
- Remove named parameters
- Add support for named routes
- Smarter router prefixes
- Shorter url syntax
As you may imagine most of the time will be spent or rewriting the model
layer, but it will also be one of the most powerful features CakePHP 3.0
will have. It's new architecture based on PHP 5.4 capabilities will offer
an easier and more powerful set of tools to build web applications in no
time.
If you are already as excited as we are this all this new stuff coming,
you definitely should meet us on next CakeFest http://cakefest.org/ we'll
be talking about the future of CakePHP and hacking our way through to bring
you a dev release as soon as possible. Wouldn't it be lovely to attend to
awesome talks, workshops and also be part of the group deciding initial
architecture for next major version of the framework? Make sure you book
your tickets before we run out of
Re: 3.0: a peek into CakePHP's future
expecting cakephp3.0 dev -- You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: 3.0: a peek into CakePHP's future
A model Something like this?
?phpclass Post {var $id;var $title;var $body;var $created;
var $modified;//@belongsTo(class=User, foreignKey=author_id)
var $author;}?
Em quinta-feira, 5 de julho de 2012 23h36min03s UTC-3, José Lorenzo
escreveu:
Since its creation, more than 7 years ago, CakePHP has grown with a life
of its own. Its main goal has always been to empower developers with tools
that are both easy to learn and use, leverage great libraries requiring low
documentation and low dependencies too. We've had several big releases
along these years and an ever growing community. Being one of the most
popular frameworks out there and probably the first one (!) we have also
gotten a lot of criticism from the developer community in general. We have,
though, accepted it and learnt from our mistakes to keep building the best
PHP framework there is.
CakePHP is known for having a very slow pace of adopting new stuff and it
has served very well to its community. Back when we were doing version 2.0
we decided to hold on version 5.2 of PHP for multiple reasons and despite
it didn't let us innovate as much as we wished to, it was an excellent
choice given the general environment regarding hosting solutions and
general adoption of PHP 5.3. A look back into the past reminded us that we
were big innovators in PHP, bringing features to developers that few dreamt
possible to do in this language. Now, it's time to look ahead in future and
decide on staying in our comfort zone or take back our leading position as
innovators.
So it is with great excitement that we announce we are putting our our
efforts in bringing you the next major release of CakePHP. Version 3.0 will
leverage the new features in PHP 5.4 and will include an important change
in our models and database system. CakePHP 3.0 will not be ready less than
6 or 8 months and we reckon that, given the rise of cheap cloud hosting
solutions and upcoming release of new operating system versions, there is
no better time to jump on the most current stable version of PHP.
As you may already know, PHP 5.4 offers awesome features that would
introduce useful new concepts and interesting solutions to old problems.
Closure binding, traits, multibyte support are tools we see of great
usefulness for properly implemented advanced framework features we've had
in mind for a long time. Also new syntax sugar added to the language will
make it more pleasant to write both small and complex applications with the
framework and a always welcomed free performance increase.
We have a young but already well defined road map for what we want to
accomplish in next release and you are invited to contribute and suggest
what's next:
- Drop support for 5.2.x and support 5.4+ only
- Add proper namespaces for all classes. This will make it easier to
reuse classes outside CakePHP and to use external libraries and finally no
chances of collisions between your app classes and core ones.
- Use traits were possible and makes sense
- Improve bootstrapping process to allow more developer control and
better performance
- Model layer rewrite:
- Models to return objects from queries
- Datamapper-like paradigm
- Richer query API
- Support for any database type
- Support for more database drivers both PDO and native
- Improve Router:
- Make it faster
- Remove named parameters
- Add support for named routes
- Smarter router prefixes
- Shorter url syntax
As you may imagine most of the time will be spent or rewriting the model
layer, but it will also be one of the most powerful features CakePHP 3.0
will have. It's new architecture based on PHP 5.4 capabilities will offer
an easier and more powerful set of tools to build web applications in no
time.
If you are already as excited as we are this all this new stuff coming,
you definitely should meet us on next CakeFest http://cakefest.org/ we'll
be talking about the future of CakePHP and hacking our way through to bring
you a dev release as soon as possible. Wouldn't it be lovely to attend to
awesome talks, workshops and also be part of the group deciding initial
architecture for next major version of the framework? Make sure you book
your tickets before we run out of them!
We're always looking for different people having a vision on software
development, are you interested in helping out? There is no better time to
start sending patches and become one of the core team!
--
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com.
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: 3.0: a peek into CakePHP's future
Joomla offers to fetch data both as object as well as an array, but i always preferred to work with arrays, since it is easy to access any element from an array as well as to modify the array. I hope that cake is not going to lose this edge, which is one of the reasons i prefer cake over other framework. On Friday, July 6, 2012 7:42:57 PM UTC+5:30, José Lorenzo wrote: On Friday, July 6, 2012 6:12:47 AM UTC-4:30, tigr wrote: Hi! First of all, big kudos to the developers of CakePHP. It is an excellent, well thought out and well engineered framework. It does indeed look very traditional and conservative and that is a Good Thing(tm). That's why I see with horror the mention of moving to the objects returned by models from queries. Would you leave them alone, please? We work in a data-centric environment here and there is nothing better than associative arrays to do that. Please, leave data alone and better improve the handling of data arrays where the effects of various calls are not obvious. That will be a much better deal. I do not expect that many people selected CakePHP in the hope that it would move to object-oriented data. There are other frameworks for that. You will be able to work with the table object and have arrays returned back. Models (rows) will be objects, though. Thank you. Albert aka Tigr On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4
Re: 3.0: a peek into CakePHP's future
I just read a lot of the replies and noticed major pushback on the change to the model layer (data array to object). Now I'm sitting here completely perplexed as to why anyone would think that data arrays are a good choice for accessing the model over traditional objects?! I've worked with CakePHP for about 4 months now and everyday I bang my head against the wall because of how these darn data arrays pervade EVERYTHING. Look, using data arrays the way Cake does now, you are coupling your database schema to your model, your view, and usually your controller. Change one name in your schema and now you have to go change every other artifact that comes into contact with that data (yes I know you can bake stuff but maybe I don't want to lose all that hand-coded view functionality, or maybe I just don't feel like rebaking my app because user_name just became username). Perhaps the problem is that many people have forgotten why OOP exists in the first place. One comment event mentioned how arrays can be accessed via object notation so who cares about using objectsseriously? Objects don't exist so you can use dot notation, they exist to separate dependencies on behavior from dependencies on data. Business logic should depend on other business logic, not architecture logic. Changing queries to return objects is an absolutely necessary upgrade, IMO. I would even go further to say that the term model in CakePHP is grossly mis-used. A model right now in Cake just means a query machine...but a model should be any object of significant business purpose which abstracts the behavior of the application (because if its not a View and its not a Controller, it must be a Model). I have all sorts of models in my apps that I can't call models because their job is not to run CRUD operations. I believe the current concept of a model in Cake should be shrunk to something like a model.data package so that we can more easily include pure models which focus on business behavior over the very specific task of querying databases and other data sources. Said differently, we should be able to think of our models only in terms of their interface and still have a perfect understanding of what the system does. Anyway, BIG thanks to the Cake team for understanding the importance of object based queries. I can't applaud that enough. The one thing I might suggest is a little bit of public effort to educate everyone about the reasoning behind this changeit seems to me that a lot of people are reacting on some emotional attachment to data arrays instead of thinking about how this actually makes our lives easier without adding work. On Thursday, July 5, 2012 10:36:03 PM UTC-4, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it
Re: 3.0: a peek into CakePHP's future
Would the object returned from queries implement ArrayAccess and Iterator? If that is the case you should still be able to access data exactly as you did before. On Friday, July 6, 2012 12:36:03 PM UTC+10, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en-US.
Re: 3.0: a peek into CakePHP's future
Hi i am using cake php in windows in xampp server , when i am trying to do manually bake application it is working fine , but when i use console mode after setting environment vasriables and try to bake in console mode i get this errors Plz help me rectify this error *Warning*: include(Cake\bootstrap.php) [function.includehttp://localhost/c12/function.include]: failed to open stream: No such file or directory in* C:\wamp\www\c12\webroot\index.php* on line *79* *Warning*: include() [function.includehttp://localhost/c12/function.include]: Failed opening 'Cake\bootstrap.php' for inclusion (include_path='C:\wamp\www\lib;.;C:\php5\pear') in * C:\wamp\www\c12\webroot\index.php* on line *79* *Fatal error*: CakePHP core could not be found. Check the value of CAKE_CORE_INCLUDE_PATH in APP/webroot/index.php. It should point to the directory containing your \cake core directory and your \vendors root directory. in *C:\wamp\www\c12\webroot\index.php* on line *88* On Friday, July 6, 2012 8:06:03 AM UTC+5:30, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be
Re: 3.0: a peek into CakePHP's future
Make router faster = #win On Thursday, July 5, 2012 10:36:03 PM UTC-4, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
Make router faster = #win -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
When I started to build a behavior for queries to return object in place of array (Active Record Pattern for cakePHP, in the bakery), I was not aware of the plans for CakePHP 3.0. But according to the discussion here, some people seems worrying about being obliged of using objects in place of arrays (this would also make application upgrade really difficullt or nearly impossible). Wouldn't be wiser to let the developer to decide whether he wants arrays or objects? And to propose for example an integration with Doctrine (or to enhance the behavior I wrote)? Thank you anyway for your hard work to improve cakePHP! Op vrijdag 6 juli 2012 04:36:03 UTC+2 schreef José Lorenzo het volgende: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better
Re: 3.0: a peek into CakePHP's future
I'm not aware of any plans to make the good parts of Cake worse. We fully plan on keeping things like Convention over config, and features like bake and scaffolding around, perhaps even make them better. I find it strange that you think arrays are not adequate for configuration, but cite yaml + json as more adequate. Both these data formats parse into arrays. Wouldn't that also imply that arrays are equally good? I know that arrays can have a more finicky syntax than say yaml, but json is equally tedious to edit. I would be interested in alternative ways to declaratively create validation rules. One reason there are so many nested arrays, is that PHP doesn't really provide many other ways to statically define complex functionality. Perhaps validation rules shouldn't be treated as a declartive configuration type thing, and instead built at runtime using a fluent interface? I think trying to define validation rules in a format like ini files would end pretty horribly. -Mark On Friday, 6 July 2012 17:50:27 UTC-4, the_woodsman wrote: I've worked with Cake since the 1.1 release, and recently I've worked a lot with Symfony, and on larger scale apps, which has helped me understand the strengths and weaknesess of both frameworks. So, a chance to express an opinion on the future of Cake? How could I possibly resist :) (Disclaimer: All of this is just my opinion /POV, not preaching here...) Obviously it's important not to throw the baby out with the bath water - DRY, Convention over config, auto-magic/scaffold features, etc are some of the key features that differentiate Cake from other frameworks, and losing this for the sake of a design pattern or a ridiculous amount of abstraction shouldn't be risked. * A clearer Dependency Injection model for core classes. I didn't think Cake had anything like this then I read a post on overriding the Request class, and I was like 'is this DI?' SF2 has a DI component that can be reused for this I think. * Appropriate use of arrays. There's a time and a place for arrays, and, imho, data is a good use, and advanced config is not. I love Cake's convention over config approach (vs the bloated yaml files of Symfony) but when you *do* need that config, arrays won't cut-it for more complex stuff. The support for ini files in Cake 2 is a great step forward in this, and, imho, json, xml, and ini files should be natively supported for some app config, and similar for value-object creation. * Greater modularity - obviously the move to name spaces (and I hope PSR standards?) is linked to this. I think partitioning the folders as per https://groups.google.com/forum/?fromgroups#!topic/cake-php/msttsVAG9tI, and making the different libraries work independently, would be ideal- why shouldn't someone be able to use the SF2 Router and the ZF Controller layer and the Cake model layer if that's what works for them? Or migrate their enterprise app over to another framework incrementally? For example, take the model layer- Imho, the model later is one of Cake's best features, and changes should be cautious. * Standalone library - I think being able to use Cake's model layer as a stand-alone would massively increase the mind-share of Cake. * OO changes - it's a matter of opinion, but Cake's arrays aren't really a massive issue for me. Given you can usually access arrays with object syntax, and there's various community behaviors to achieve this effect anyway, I don't think this a deal breaker. Value Objects makes some sense, but I personally hope Cake never goes the way of $record-save, and always keeps with $model-save. Imho, putting too much DB behaviour into the row-level objects leads to a much more complex system, where it's a lot easier to implement poor SQL. If people want that approach, don't re-invent the wheel, Doctrine and Propel are mature libs and they don't need any more competitors :) One places the models could definitely do with a revamp is the setting of validation rules. Once I'm 4 levels deep into the array config, I wish I was making classes or objects or using a separate config format! Okay, sorry for the rant, but I'd be interested to see how closely my views align with the community at large... On Friday, 6 July 2012 03:36:03 UTC+1, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep
Re: 3.0: a peek into CakePHP's future
There isn't really an example yet, as no code has been written. Based on this thread it might be a helpful process to go through a public vetting of the proposed model api, and how some common use cases might work. I know that josé has begun implementing basic database abstraction which an api that resembles PDO, but no work on the actual model layer has started. -Mark On Friday, 13 July 2012 14:08:40 UTC-4, Celso wrote: A example of the new Model approach? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
A example of the new Model approach? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
http://php.net/manual/en/class.serializable.php :). On Tuesday, July 10, 2012 3:57:20 AM UTC+2, madi wrote: Wouldn't array be still used? For instance more than one objects are passed, should the objects be stored in an array? What would happen to the auto conversion to json? Array is easier to convert to json rite? On Jul 10, 2012 1:19 AM, Jamescowhen x...@splitp.com wrote: I would think moving to a more object oriented model will result in better readable code and IDE auto completion will be more useful. On Sunday, July 8, 2012 7:12:32 PM UTC-7, Greg wrote: For mine, being able to deal with objects in the view would greatly improve the readability of data (the whole $user['User']['email'] etc looks incredibly difficult to read to me, compared with $user-email which would be much nicer). I've always felt dealing with arrays is a bit of a 'hack'. I understand the choice, but I think the idea to move towards a more object oriented approach is more than hype, and long overdue. On Sat, Jul 7, 2012 at 7:35 PM, tigr alb...@tigr.net wrote: No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscribe@**googlegroups.comcake-php%2bunsubscr...@googlegroups.comFor more options, visit this group at http://groups.google.com/**group/cake-phphttp://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
I would think moving to a more object oriented model will result in better readable code and IDE auto completion will be more useful. On Sunday, July 8, 2012 7:12:32 PM UTC-7, Greg wrote: For mine, being able to deal with objects in the view would greatly improve the readability of data (the whole $user['User']['email'] etc looks incredibly difficult to read to me, compared with $user-email which would be much nicer). I've always felt dealing with arrays is a bit of a 'hack'. I understand the choice, but I think the idea to move towards a more object oriented approach is more than hype, and long overdue. On Sat, Jul 7, 2012 at 7:35 PM, tigr alb...@tigr.net wrote: No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
Wouldn't array be still used? For instance more than one objects are passed, should the objects be stored in an array? What would happen to the auto conversion to json? Array is easier to convert to json rite? On Jul 10, 2012 1:19 AM, Jamescowhen x...@splitp.com wrote: I would think moving to a more object oriented model will result in better readable code and IDE auto completion will be more useful. On Sunday, July 8, 2012 7:12:32 PM UTC-7, Greg wrote: For mine, being able to deal with objects in the view would greatly improve the readability of data (the whole $user['User']['email'] etc looks incredibly difficult to read to me, compared with $user-email which would be much nicer). I've always felt dealing with arrays is a bit of a 'hack'. I understand the choice, but I think the idea to move towards a more object oriented approach is more than hype, and long overdue. On Sat, Jul 7, 2012 at 7:35 PM, tigr alb...@tigr.net wrote: No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscribe@**googlegroups.comcake-php%2bunsubscr...@googlegroups.comFor more options, visit this group at http://groups.google.com/**group/cake-phphttp://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
For mine, being able to deal with objects in the view would greatly improve the readability of data (the whole $user['User']['email'] etc looks incredibly difficult to read to me, compared with $user-email which would be much nicer). I've always felt dealing with arrays is a bit of a 'hack'. I understand the choice, but I think the idea to move towards a more object oriented approach is more than hype, and long overdue. On Sat, Jul 7, 2012 at 7:35 PM, tigr alb...@tigr.net wrote: No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
On Saturday, 7 July 2012 11:35:08 UTC+2, tigr wrote: No, that is not nice. The strength of the CakePHP design is in being very straightforward when it comes to working with the data. I have seen other frameworks and I think that object-oriented ways are not suitable for working with data. Well, of course, you can, but would you want to, given a choice? My answer was no and that is why I am using Cake. I am worried that the object-oriented hype will get the best of you and we will lose a perfectly sensible data processing framework to the object-oriented glory. For practical reasons, it would be great to leave the model layer principles as they are. my few cents: a.) fork it b.) if cake is decoupled enough = forking will be easy (e.g. the decoupling between model layer from controller layer from view helper etc.) c.) instead of forking, add a 2nd model layer abstraction d.) learn from rails3 e.) look at how well AREL works so for me the questions are rather: can a similar decoupling be done well in php 5.4; can we get true objects or just read only? if we get read only, can't we just enable a bool to return nested data arrays? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
On Fri, Jul 6, 2012 at 9:47 AM, Ilie ilie.pan...@gmail.com wrote: Why the removal of named parameters in the Router? They are quite useful to me and the Paginator uses them to keep track of page. What would be used instead? Guess named routes and smarter prefixes in combo will probably work the same Just a speculation T -- = PHP for E-Biz: http://sanisoft.com = -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
Hi! First of all, big kudos to the developers of CakePHP. It is an excellent, well thought out and well engineered framework. It does indeed look very traditional and conservative and that is a Good Thing(tm). That's why I see with horror the mention of moving to the objects returned by models from queries. Would you leave them alone, please? We work in a data-centric environment here and there is nothing better than associative arrays to do that. Please, leave data alone and better improve the handling of data arrays where the effects of various calls are not obvious. That will be a much better deal. I do not expect that many people selected CakePHP in the hope that it would move to object-oriented data. There are other frameworks for that. Thank you. Albert aka Tigr On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run
Re: 3.0: a peek into CakePHP's future
On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
Does it mean Cake 3.0´s Model will return objects instead of arrays ? On Fri, Jul 6, 2012 at 6:33 AM, Kazik kaz...@gmail.com wrote: On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
On Fri, Jul 6, 2012 at 2:17 PM, Marsson C. marss...@gmail.com wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? Yes Model layer rewrite: Models to return objects from queries -- Andy Gale http://andy-gale.com http://twitter.com/andygale -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
nice :) Von: Andy Gale a...@salgo.net An: cake-php@googlegroups.com Gesendet: 15:19 Freitag, 6.Juli 2012 Betreff: Re: 3.0: a peek into CakePHP's future On Fri, Jul 6, 2012 at 2:17 PM, Marsson C. marss...@gmail.com wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? Yes Model layer rewrite: Models to return objects from queries -- Andy Gale http://andy-gale.com http://twitter.com/andygale -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
They were just a bad copy of the query string with tons of problems and performance issues. They will continue to work in read-only mode, but cake will produce query string variables instead. On Thursday, July 5, 2012 11:47:10 PM UTC-4:30, Ilie wrote: Why the removal of named parameters in the Router? They are quite useful to me and the Paginator uses them to keep track of page. What would be used instead? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
On Friday, July 6, 2012 8:47:18 AM UTC-4:30, Marsson wrote: Does it mean Cake 3.0´s Model will return objects instead of arrays ? Yes :) On Fri, Jul 6, 2012 at 6:33 AM, Kazik kaz...@gmail.com wrote: On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native The new model layer will be an exciting feature. But it also looks like it is going to be very different from CakePHP 2. Is there going to be an update path for CakePHP 2 apps to CakePHP 3? k -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
On Friday, July 6, 2012 6:12:47 AM UTC-4:30, tigr wrote: Hi! First of all, big kudos to the developers of CakePHP. It is an excellent, well thought out and well engineered framework. It does indeed look very traditional and conservative and that is a Good Thing(tm). That's why I see with horror the mention of moving to the objects returned by models from queries. Would you leave them alone, please? We work in a data-centric environment here and there is nothing better than associative arrays to do that. Please, leave data alone and better improve the handling of data arrays where the effects of various calls are not obvious. That will be a much better deal. I do not expect that many people selected CakePHP in the hope that it would move to object-oriented data. There are other frameworks for that. You will be able to work with the table object and have arrays returned back. Models (rows) will be objects, though. Thank you. Albert aka Tigr On Friday, July 6, 2012 4:36:03 AM UTC+2, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be
Re: 3.0: a peek into CakePHP's future
I'm also cautious about moving to objects. I really like the way Cake's arrays work. However, I presume that this will mean that the model will be available in the view, which will be useful in some cases. Whatever the case, I'm looking forward to 3. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
I've worked with Cake since the 1.1 release, and recently I've worked a lot with Symfony, and on larger scale apps, which has helped me understand the strengths and weaknesess of both frameworks. So, a chance to express an opinion on the future of Cake? How could I possibly resist :) (Disclaimer: All of this is just my opinion /POV, not preaching here...) Obviously it's important not to throw the baby out with the bath water - DRY, Convention over config, auto-magic/scaffold features, etc are some of the key features that differentiate Cake from other frameworks, and losing this for the sake of a design pattern or a ridiculous amount of abstraction shouldn't be risked. * A clearer Dependency Injection model for core classes. I didn't think Cake had anything like this then I read a post on overriding the Request class, and I was like 'is this DI?' SF2 has a DI component that can be reused for this I think. * Appropriate use of arrays. There's a time and a place for arrays, and, imho, data is a good use, and advanced config is not. I love Cake's convention over config approach (vs the bloated yaml files of Symfony) but when you *do* need that config, arrays won't cut-it for more complex stuff. The support for ini files in Cake 2 is a great step forward in this, and, imho, json, xml, and ini files should be natively supported for some app config, and similar for value-object creation. * Greater modularity - obviously the move to name spaces (and I hope PSR standards?) is linked to this. I think partitioning the folders as per https://groups.google.com/forum/?fromgroups#!topic/cake-php/msttsVAG9tI, and making the different libraries work independently, would be ideal- why shouldn't someone be able to use the SF2 Router and the ZF Controller layer and the Cake model layer if that's what works for them? Or migrate their enterprise app over to another framework incrementally? For example, take the model layer- Imho, the model later is one of Cake's best features, and changes should be cautious. * Standalone library - I think being able to use Cake's model layer as a stand-alone would massively increase the mind-share of Cake. * OO changes - it's a matter of opinion, but Cake's arrays aren't really a massive issue for me. Given you can usually access arrays with object syntax, and there's various community behaviors to achieve this effect anyway, I don't think this a deal breaker. Value Objects makes some sense, but I personally hope Cake never goes the way of $record-save, and always keeps with $model-save. Imho, putting too much DB behaviour into the row-level objects leads to a much more complex system, where it's a lot easier to implement poor SQL. If people want that approach, don't re-invent the wheel, Doctrine and Propel are mature libs and they don't need any more competitors :) One places the models could definitely do with a revamp is the setting of validation rules. Once I'm 4 levels deep into the array config, I wish I was making classes or objects or using a separate config format! Okay, sorry for the rant, but I'd be interested to see how closely my views align with the community at large... On Friday, 6 July 2012 03:36:03 UTC+1, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting
Re: 3.0: a peek into CakePHP's future
I'm excited to try out 3.0 but please, PLEASE don't make Cake into anything like Symfony! Do. Not. Like. I agree that model validation could use some freshening, although I don't personally have any great ideas for doing that. I don't understand the desire to use parts of one framework with another, btw. Or even using the model layer on its own. I know I may just be missing something but it seems bizarre to me. On Fri, Jul 6, 2012 at 5:50 PM, the_woodsman elwood.ca...@gmail.com wrote: I've worked with Cake since the 1.1 release, and recently I've worked a lot with Symfony, and on larger scale apps, which has helped me understand the strengths and weaknesess of both frameworks. So, a chance to express an opinion on the future of Cake? How could I possibly resist :) (Disclaimer: All of this is just my opinion /POV, not preaching here...) Obviously it's important not to throw the baby out with the bath water - DRY, Convention over config, auto-magic/scaffold features, etc are some of the key features that differentiate Cake from other frameworks, and losing this for the sake of a design pattern or a ridiculous amount of abstraction shouldn't be risked. * A clearer Dependency Injection model for core classes. I didn't think Cake had anything like this then I read a post on overriding the Request class, and I was like 'is this DI?' SF2 has a DI component that can be reused for this I think. * Appropriate use of arrays. There's a time and a place for arrays, and, imho, data is a good use, and advanced config is not. I love Cake's convention over config approach (vs the bloated yaml files of Symfony) but when you *do* need that config, arrays won't cut-it for more complex stuff. The support for ini files in Cake 2 is a great step forward in this, and, imho, json, xml, and ini files should be natively supported for some app config, and similar for value-object creation. * Greater modularity - obviously the move to name spaces (and I hope PSR standards?) is linked to this. I think partitioning the folders as per https://groups.google.com/forum/?fromgroups#!topic/cake-php/msttsVAG9tI, and making the different libraries work independently, would be ideal- why shouldn't someone be able to use the SF2 Router and the ZF Controller layer and the Cake model layer if that's what works for them? Or migrate their enterprise app over to another framework incrementally? For example, take the model layer- Imho, the model later is one of Cake's best features, and changes should be cautious. * Standalone library - I think being able to use Cake's model layer as a stand-alone would massively increase the mind-share of Cake. * OO changes - it's a matter of opinion, but Cake's arrays aren't really a massive issue for me. Given you can usually access arrays with object syntax, and there's various community behaviors to achieve this effect anyway, I don't think this a deal breaker. Value Objects makes some sense, but I personally hope Cake never goes the way of $record-save, and always keeps with $model-save. Imho, putting too much DB behaviour into the row-level objects leads to a much more complex system, where it's a lot easier to implement poor SQL. If people want that approach, don't re-invent the wheel, Doctrine and Propel are mature libs and they don't need any more competitors :) One places the models could definitely do with a revamp is the setting of validation rules. Once I'm 4 levels deep into the array config, I wish I was making classes or objects or using a separate config format! Okay, sorry for the rant, but I'd be interested to see how closely my views align with the community at large... On Friday, 6 July 2012 03:36:03 UTC+1, José Lorenzo wrote: Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in
3.0: a peek into CakePHP's future
Since its creation, more than 7 years ago, CakePHP has grown with a life of its own. Its main goal has always been to empower developers with tools that are both easy to learn and use, leverage great libraries requiring low documentation and low dependencies too. We've had several big releases along these years and an ever growing community. Being one of the most popular frameworks out there and probably the first one (!) we have also gotten a lot of criticism from the developer community in general. We have, though, accepted it and learnt from our mistakes to keep building the best PHP framework there is. CakePHP is known for having a very slow pace of adopting new stuff and it has served very well to its community. Back when we were doing version 2.0 we decided to hold on version 5.2 of PHP for multiple reasons and despite it didn't let us innovate as much as we wished to, it was an excellent choice given the general environment regarding hosting solutions and general adoption of PHP 5.3. A look back into the past reminded us that we were big innovators in PHP, bringing features to developers that few dreamt possible to do in this language. Now, it's time to look ahead in future and decide on staying in our comfort zone or take back our leading position as innovators. So it is with great excitement that we announce we are putting our our efforts in bringing you the next major release of CakePHP. Version 3.0 will leverage the new features in PHP 5.4 and will include an important change in our models and database system. CakePHP 3.0 will not be ready less than 6 or 8 months and we reckon that, given the rise of cheap cloud hosting solutions and upcoming release of new operating system versions, there is no better time to jump on the most current stable version of PHP. As you may already know, PHP 5.4 offers awesome features that would introduce useful new concepts and interesting solutions to old problems. Closure binding, traits, multibyte support are tools we see of great usefulness for properly implemented advanced framework features we've had in mind for a long time. Also new syntax sugar added to the language will make it more pleasant to write both small and complex applications with the framework and a always welcomed free performance increase. We have a young but already well defined road map for what we want to accomplish in next release and you are invited to contribute and suggest what's next: - Drop support for 5.2.x and support 5.4+ only - Add proper namespaces for all classes. This will make it easier to reuse classes outside CakePHP and to use external libraries and finally no chances of collisions between your app classes and core ones. - Use traits were possible and makes sense - Improve bootstrapping process to allow more developer control and better performance - Model layer rewrite: - Models to return objects from queries - Datamapper-like paradigm - Richer query API - Support for any database type - Support for more database drivers both PDO and native - Improve Router: - Make it faster - Remove named parameters - Add support for named routes - Smarter router prefixes - Shorter url syntax As you may imagine most of the time will be spent or rewriting the model layer, but it will also be one of the most powerful features CakePHP 3.0 will have. It's new architecture based on PHP 5.4 capabilities will offer an easier and more powerful set of tools to build web applications in no time. If you are already as excited as we are this all this new stuff coming, you definitely should meet us on next CakeFest http://cakefest.org/ we'll be talking about the future of CakePHP and hacking our way through to bring you a dev release as soon as possible. Wouldn't it be lovely to attend to awesome talks, workshops and also be part of the group deciding initial architecture for next major version of the framework? Make sure you book your tickets before we run out of them! We're always looking for different people having a vision on software development, are you interested in helping out? There is no better time to start sending patches and become one of the core team! -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: 3.0: a peek into CakePHP's future
Why the removal of named parameters in the Router? They are quite useful to me and the Paginator uses them to keep track of page. What would be used instead? -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
