Metadata
- Source
- FLUID-476
- Type
- Sub-task
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Anastasia Cheetham
- Reporter
- Anastasia Cheetham
- Created
2008-04-08T16:17:43.000-0400 - Updated
2011-01-30T12:05:55.339-0500 - Versions
- N/A
- Fixed Versions
-
- 0.3
- Component
-
- Demos
Description
Any markup examples that are solely for testing purposes, and which don't serve as exemplars or QA test files, should be moved out of the sample-code folder and into tests somehow. The only thing in the sample-code should be:
- todo list
- generic lightbox (until that is merged into the template, once multiple key-sets are supported)
- uPortal sortable tabs
- uPortal sortable portlets
- nested reorderers
Comments
-
Anastasia Cheetham commented
2008-04-18T10:45:47.000-0400 The sample code now includes:
abstract:- portal examples
concrete: - todo list
- generic lightbox (multiple keysets are now supported, though, but this file will serve as a cut-paste source for Lightbox implementations, simpler than the template file)
- jquery tabs (this replaces the uPortal sortable tabs example)
- uPortal sortable portlets (updated, and includes the Lightbox in a portlet, showing nested reorderers)
- scheduler (the RSFStyleScheduler has been removed)
- portal examples
-
Anastasia Cheetham commented
2008-04-21T12:27:49.000-0400 Re abstract portlets example: Either use the test markup for this purpose (make it display, and ensure that the tests clean up after themselves) or move it out of sample code and into tests somewhere.
Re generic lightbox: Ensure that it is indeed nice and clean.
Re scheduler: What does this offer that the to-do list doesn't?
Re unordered-list-tabs: No longer necessary given the jQuery tabs example? Add a welcome tab to the tabs example with the intructions, and move this one out.
-
Anastasia Cheetham commented
2008-04-21T15:37:41.000-0400 Done.