1. Lets loose PHP4 asap
2. Hidden input fields should a default class applied something
like: .hidden-input perhaps - if you have forms with coloured
background then it can be a real nightmare making sure hidden fields
stay hidden (not everybody uses firefox) - I'm sure everybody has
scratched their heads over the little stripes that sometimes randomly
appear in forms !
3. It would be great if there was another layer of built in helpers so
we could overload the core helpers e.g. FormHelper extends
FormHelperBase extends AppHelper - what is now FormHelper becomes
FormHelperBase and FormHelper become an empty class that you can just
use to override methods in the built in helpers.
4. $model->find() bringing back all the associated data unless you
tell it not too - it should be the other way around - if you need
associations create them, use things like Containable and Rafael
Bandeira's Linkable behaviour.
There is a lot to be said for the built in admin in Django (although
on balance I think it maybe take it a bit far) - I think there are
ideas that could be borrowed - built in and configured ACL seems a
great idea and lots of built in widget / component type things are
handy.
On a general note though I'd just really like to say thanks to all the
core developers and everyone who contributes for building such a cool
framework.
Cheers
John
On May 13, 11:47 am, "Mark (Germany)" <dereurom...@googlemail.com>
wrote:
> after so many years still too "american"!
> no real multi-lingual support for usage in other languages than just
> englisch
>
> e.g. the mb_() function problem i already pointed out 12 months ago
> with utf8 as default + mb_() functions there wouldn't be any trouble
>
> On 13 Mai, 11:57, majna <majna...@gmail.com> wrote:
>
> > Think Routing.admin and prefix routing implementation is not complete.
> > -prefix routing ignores reverse routing and pagination
> > -Routing.admin accepts only one string
>
> > maybe Routing.admin should be removed and replaced with prefix routing
> > completely.
>
> > On May 8, 3:08 pm, Smelly Eddie <ollit...@gmail.com> wrote:
>
> > > I hate that it is a powerful framework that can make the tedious work
> > > of developing sites a breeze. Its strict adherence to the tried and
> > > true MVC model is a pain point as well. Why so logical?
>
> > > I hate the active community involvement and powerful documentation and
> > > API sites. I hate that people expect Cake to do every little thing.
>
> > > It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> > > manager-blog-forum.
>
> > > Use the framework to create an upload component, it takes all of 5
> > > minutes!!
>
> > > On May 8, 8:56 am, "Dennis S. Hennen" <dennis.hen...@gmail.com> wrote:
>
> > > > Consider Post hasMany Comment
>
> > > > Comment->find('all') returns {n}.Comment.*
>
> > > > Post->find('all') gives you Comment.{n}.*
>
> > > > If I want a helper to do processing on a list of comments, I have to
> > > > handle both potential formats, or massage the data.
>
> > > > Related to this is the $primary parameter to the afterFind callback.
>
> > > > Perhaps find results as objects instead of arrays?
--~--~---------~--~----~------------~-------~--~----~
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
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
