IntroToPeak/ToDo

UserPreferences

Misc. ideas/issues for the tutorial:

• Lesson 4
• needs to mention readline/history in n2 (and n2's help looks maybe broken in a couple of areas, which I should bug Ty about)
• more about n2's functions/abilities
• Ty is n2 author
• Use n2 \python mode to illustrate SQL calls from Python, so it's not new in the DM usage
• URL is "scheme:body", body is not a "path"
• URL schemes are effectively "private" (E.g.: "What kind of a URL is sqlite:foo? It doesn't work in my browser", etc.)
• Use example.com instead of server.com
• Connection isn't a config key/component key - the name is
• Use hello.db instead of test.db
• More LinkRef explanation: when you can or can't use it
• Put global.ini in PEAK_CONFIG, explain loading order again
• First cut SQL usage is BROKEN; forCmd will load/save customer rather than group
• i.e., won't work unless the for user is in both the SQL db and the text one
• text should be called message, since aGroup.text doesn't make sense
• referenceType is a typo
• DM's and commands need to use get() instead of __contains__
• Lesson 2
• Recap is missing info about storage.DMFor
• All the examples use print, but should use print >>self.stdout,
• Should we fix this in the early lessons, so folks aren't misled about good practice?
• Should we encapsulate the actual greeting code?
• Need an IGreetingService or some such, so we can demo the [Component Factories] configuration
• This would then be usable by UI's like web, XMLRPC, etc.
• Might be a good way to encapsulate certain aspects, including both greetings and edits
• Create a "hello world" socket service, that you connect to and are greeted by (then disconnected); this would let us demo several things, including:
• EventDriven
• ZConfig schemas
• PEAK+Twisted
• accessing the IGreetingService to get the greeter
• Need for commands to write where they're told (self.stdout)
• Maybe adaptation from IGreetingService to a Twisted protocol or factory?
• Kind of hard to show in context of EventDriven, though.
• Minimal CGI using print >>self.stdout w/generic greeting
• Add PATH_INFO parsing to greet a specific person
• Use CGI and FastCGI containers to launch the app
• (Maybe other containers, too, if PyWCI standard catches on by then...)
• Move up to peak.web
• Adapt the IGreetingService to a Web UI wrapper
• Unfortunately, peak.web is a huge leap, since it requires path/hierarchy and adaptation
• Perhaps there's a less steep area we can find to introduce those concepts in first
• 'peak.security' might also need a gentler introduction, so it's familiar by the time you get to peak.web
• Maybe the socket "hello service" could grow a bit of a protocol with user/password, so we can show security there