Best Practices of Plone Development

More documents

Recommendations

Info

1.4 Form Controller 1 BEST PRACTICES FOR PLONE DEVELOPMENT 1.4.3 Dispatching / Actions (2) • Context – What kind <strong>of</strong> object/context this work on – eg “Document”, “News Item” • Button – What button name was pushed – Allows “Ok”, “Cancel” buttons 1.4.4 Dispatching / Actions (3) • Action – What happens next • Argument – Argument for action 1.4.5 Dispatching / Actions (4) • Actions – redirect_to: HTTP redirect to argument ∗ eg “http://yahoo.com” – redirect_to_action: HTTP redirect to action ∗ eg “view”, “edit” – traverse_to, traverse_to_action: same, but no redirect, just calls ∗ Keeps request object 24
1.4 Form Controller 1 BEST PRACTICES FOR PLONE DEVELOPMENT 1.4.6 Dispatching / Actions (5) • Arguments – TALES expression – “string:http://www.yahoo.com” – “string:view” – or “python:”, or just path, <strong>of</strong> course 1.4.7 Example Dispatching • Form friend_edit_form, should go to friend_edit – Template: “friend_edit_form” – Status: “success” – Context: “Any” or “Friend” A subtle difference. It’s possible that our friend_edit_form might be used for just Friend portal types. It’s also possible that we re-use it for CoWorker portal types. If we want the behavior to be the same, we can keep this as “Any”. If we want to have different dispatching for the two (perhaps coworker-editing needs a special coworker_edit script that does things differently, we can specify “Friend” here and put in a different action for “CoWorker”. – Button: Any (unless you have cancel!) – Action: “traverse_to” – Argument: “string:friend_edit” 1.4.8 Controlled Scripts • After validation what dispatching can go to • Can use regular script – Controlled can participate in dispatching 25
Page 1 and 2: Best Practices for Development Nort
Page 3 and 4: CONTENTS CONTENTS 1.3.5 Sample foo_
Page 5 and 6: CONTENTS CONTENTS 1.9.3 Limitations
Page 7 and 8: 1 BEST PRACTICES FOR PLONE DEVELOPM
Page 9 and 10: 1.1 Introduction 1 BEST PRACTICES F
Page 11 and 12: 1.2 Products 1 BEST PRACTICES FOR P
Page 17 and 18: 1.3 Filesystem Skins 1 BEST PRACTIC
Page 23: 1.4 Form Controller 1 BEST PRACTICE
Page 27 and 28: 1.4 Form Controller 1 BEST PRACTICE
Page 29 and 30: 1.5 Skinning Plone 1 BEST PRACTICES
Page 31 and 32: 1.5 Skinning Plone 1 BEST PRACTICES
Page 33 and 34: 1.6 Version Control 1 BEST PRACTICE
Page 35 and 36: 1.6 Version Control 1 BEST PRACTICE
Page 37 and 38: 1.8 Setup and Scaffolding 1 BEST PR
Page 39 and 40: 1.8 Setup and Scaffolding 1 BEST PR
Page 41 and 42: 1.9 Debugging 1 BEST PRACTICES FOR
Page 51 and 52: 1.10 Testing 1 BEST PRACTICES FOR P
Page 53 and 54: 1.11 Developing With Others 1 BEST
Page 55 and 56: 1.11 Developing With Others 1 BEST

Best Practices of Plone Development

Create successful ePaper yourself

Delete template?

Save as template?