Index: openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/Attic/left-to-finish-core.adp,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp 14 Nov 2001 19:40:25 -0000 1.2
+++ openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp 29 Nov 2001 02:17:34 -0000 1.3
@@ -10,39 +10,64 @@
Portal
-- Adjust buttons on portlets as a function of capabilities
- Implement portlet locking capability.
- Implement cloning stuff.
+
-
Clean up UI on configuration page (change backlink)
+ - add roles and permissions (admin create|delete)(from dotlrn_community API)
- code review (Wednesday, 11/21, 2pm).
+
+- change theme data model to map to pages.
- Refactor some functionality as part of base portal package.
-
- Clean up UI on configuration page (change backlink)
- add acs-service-contract support.
-
- change theme data model to map to pages.
-
- add roles and permissions (admin create|delete)
- (from dotlrn_community API).
+
- update all portlets for datasource.new, user_editable_p, shadeable_p, hideable_p, sc, new procs
+
- Adjust buttons on portlets as a function of capabilities
- Remove render-element.tcl ::get_pretty_name other render cleanup
-
- Params issues
-
- code review (Monday, 11/19, 10am-12pm).
+
+
dotLRN Core
- Review exactly what the roles are
- Write up permissions procs!
-
- Move administration to community-specific pages! Duh!
+
-
Move administration to community-specific pages! Duh!
- Allow for addition of users who haven't registered yet? Check that.
- Automatically redirect single-community guests to the right location.
-
- Fix registration/deregistration bugs!
+
-
Fix registration/deregistration bugs!
- Get clubs working
- !! Figure out Relational Segments !!
+Operations
+
+- prepare staging server:
+
+-
AOLserver 3.3ad13
+ -
Oracle 8.1.7
+ -
drivers
+ -
+
+ - review existing SloanSpace site
+
+
+
+
calendar
- make group calendar work!
- each user has *ONE* personal calendar, and has access to each community calendar.
- calendar works as multi-package view in portlet.
+how this works
+
+
+- part of this involves figuring out multiple values for single parameters (instance_id in particular).
+
- every user has only ONE personal calendar
+
- every community has only ONE community calendar
+
- when a user views a community-specific page, he/she only sees that community's event.
+
- on personal calendar, they see everything
+
+
bboard
- test a bit more
@@ -60,7 +85,7 @@
FAQ
-- Clean up portlet UI (display list of FAQs)1
+
- Clean up portlet UI (display list of FAQs)
News