+1.

This is the first behavior i change when creating my own admin gen theme...

COil




________________________________
De : Tom Boutell <[email protected]>
À : [email protected]
Envoyé le : Jeudi, 23 Avril 2009, 18h24mn 29s
Objet : [symfony-devs] Symfony 1.2 admin generator: _save_and_list 
undersupported and  nonfunctional in Doctrine, should be fully supported 
everywhere


For a long time folks have been pointing out that the list of actions
available in the admin generator does not include _save_and_list. This
is a problem because _save_and_list is the normal behavior in most
applications when you click on the Save button. It is also a problem
because the default "save and redisplay the same item" behavior
requires the user to click "cancel" to move on, which is conceptually
confusing and causes anxiety. When you're happy with your work you
should not have to "cancel" things just to move along normally.

But it's not necessary to argue about whether _save_and_list should be
the default behavior of _save. It's just necessary to support
_save_and_list for those of us who really, really prefer it and want
to build web apps that act like normal apps in this way.

Unfortunately support for _save_and_list has been regressing, not progressing.

In Symfony 1.0, there was no _save_and_list action per se. You had to
fake it in _edit_actions.php, which is not good. But if you set up
your own <input type="submit" name="save_and_list" /> button, it
worked. Code in the admin generator took care of it from there.

In Symfony 1.2, things are worse. There is still no _save_and_list
action. The Propel admin generator class still implements the
save_and_list case, so you can do the "_edit_actions" trick with
Propel. But the Doctrine admin generator doesn't have that feature.

That means you have to hack it in by adding a custom action to your
admin generated class. And that is not straightforward because the
redirect at the end of the normal save action means you can't reuse
the implementation.

I've spent a lot of time working around this issue in Symfony 1.0
projects, and now even more time for Symfony 1.2. The admin generator
should make it easier to do the usual thing. I think _save_and_list
should be implemented as a first-class option in the admin generator.
Also, its default label should just read "Save," or at least be easy
to override.

-- 
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com



      
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to