Best Practices of Plone Development

More documents

Recommendations

Info

1.10 Testing 1 BEST PRACTICES FOR PLONE DEVELOPMENT 1.10.7 Selenium Text Checks • verifyText – For a particular node, exact match • verifyTextPresent – Anywhere on page • verifyTextNotPresent 52
1.11 Developing With Others 1 BEST PRACTICES FOR PLONE DEVELOPMENT 1.11 Developing With Others 1.11.1 You Have a Laptop: Use It • It’s not a $2000 ssh client • Faster edit/test/debug cycle. • No wires, no wireless • Easier to work privately 1.11.2 Subversion for Sharing • Work on your laptop • When at the “right point”, check-in your code • ’rsync’ to your sandbox on server • Emergency changes on server can be handled, too 1.11.3 Simple Sandboxes • Each developer gets a skin folder in your product • rsync your skin changes to your skin folder • Each developer has their own skinpath, with their skinfolder as most customized • Developers can switch from their sandbox skinpath to common skinpath. 53
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 and 24: 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: 1.10 Testing 1 BEST PRACTICES FOR P
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?