Index: openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/Attic/detailed-todo.adp,v diff -u -r1.1 -r1.2 --- openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp 14 Oct 2001 21:42:58 -0000 1.1 +++ openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp 23 Oct 2001 17:28:11 -0000 1.2 @@ -7,25 +7,57 @@
-
Only one tcl script is explicitly sourced: +www/render-element.tcl. I've looked at this, and I don't see how it +can be changed at the moment. I'm moving on. + +
Further clean up (not altering functionality) of the display code and
+templates will be ONGOING.
+
+
+
+
+
+
Fixed in all portlets. +
ALPHA by Oct. 25 +
-
+Perms scheme complete ALPHA by Oct. 25 +
AKS: There is only one special, "clonable" portal per-instance, right? +
AKS: "locks" in PEM +
What Ben means: we have data sources in the overall system, say bboard, faq, and fs. However, to page #123, only bboard and faq are *available* as potential data sources. The dotlrn-bboard package will first make the bboard datasource AVAILABLE to the page in question, and then will actually add it. Thus, when removed, the datasource remains available to be re-added.
More on removing portal elements: anyone with page-level permissions (which permission exactly is yet to be determined) can add available data sources to the given page. Each portal element that is added by the user will automatically gain the permission to be removed. However, some portal elements added programmatically might not be removable by the viewing user. + +
AKS: Adding portlet to already registered users issue. +