> I'd appreciate some suggestions on which aspects you would like me to
> cover and some help clarifiying doubts I have on how to best
> implement parts I might not be too familiar with (if any ;)
I think that approach is a bloody good idea, especially if you can pull the
SVN logs and generate a pretty HTML tutorial using TurboGears. ;^D
For things I'd like showcased, they include:
- Complex widget forms, specifically the shiny new WYSIWYG widget.
- Including custom HTML form.
- Textual labels with additional description.
- I.e. "make it look good, not stock".
- MochiKit AJAX.
- Hit "New" swapping current view for creation interface.
- Hit "Save" (New/Modify) and swap page view for editing interface.
- Hit "Delete" and immediately update list view or switch to updated list.
- Drag-and-drop organization of Wiki pages.
- Data structure -and- AJAX.
- Etc.
The above are points I'll have to incorporate into my CMS in a post-1.0
release. Right now I'm too busy squashing bugs and optimizing to add new
features. ;_;
- Matthew
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
