History for OnePointOh
??changed:- Overview This is a new cut; see HystericalOnePointOh for the old one. PTK 1.0 Roadmap ASAP * Fix or close out remaining PTK Tracker issues. * Release PTK 0.9.3. This release will fix a couple of issues which make 0.9.2 hard to use; CVS will still be the preferred source until 1.0, however. Must-Have for 1.0 * Address the problem that new PTK releases break customized portal instances (i.e., finish out the PortalSkinsTool that Shane has in work). See the "skins explanation", http://lists.zope.org/pipermail/zope-ptk/2001-January/002161.html Shane posted recently for more details. ShaneH (2001-01-26) -- I have created a document, SkinsProposal, that explains the motivations behind skins and has brief details on how to use them. * "Transparent membership" (checked in as the new 'portal_memberdata' tool). This feature allows the PTK to operate without needing its own 'acl_users' folder; it wraps the authenticated users from its acquired user folder in a "member" object (which has portal-specific properties/behavior). * Implement "topics" as member-addable content (like ZTopics, but "portalized", with perhaps less knowledge of / dependency on ZCatalog internals). See: - http://www.zope.org/Members/MikeP/Products/ZTopic, but note that it needs a "one-line patch", http://lists.zope.org/pipermail/zope/2001-January/038621.html to make it work under current Zopes. * Integrate Ethan's "new 'div' chrome", http://www.zope.org/Builder (layout without 'table' tags!). Clean up the stylesheets, as well. The point here is to make style-based design possible, degrading cleanly in browsers (NS4, particularly) which implement CSS poorly. * Complete integration with "hookable PUT", http://dev.zope.org/Wikis/DevSite/Proposals/HookablePUTCreation to enable content creation via WebDAV / Amaya / Composer / FTP; needs to handle both STX w/ headers and HTML (ripping metadata from 'meta' and 'title' tags, maybe ripping content from a specially-marked 'div' tag, as an alternative to the whole 'body'). May need some kind of registry for mapping MIME-types (and filename extensions?) to classes. Desirable for 1.0 * State-machine-driven WorkflowTool (needs to be ripped out from a consulting gig version, refactored a bit). See the "mailing list discussion", http://lists.zope.org/pipermail/zope-ptk/2000-December/002007.html * Implement "proposed PortalMetadataTool", http://www.zope.org/Products/PTK/ZWiki/PortalMetadataToolProposal Can Wait / Parallel * Package Rochester's PortalEventCalendar product (developed for a consulting gig) as a PTK add-in. * Package Rochester's PortalPoll product (developed for a consulting gig) as a PTK add-in. * Implement "proposed PortalEventsTool", http://www.zope.org/Products/PTK/ZWiki/PortalEventsToolProposal (this one is important, but requires touching almost everything). * Reimplement saner DiscussionsTool (keep discussion items with their anchor content; perhaps make discussability an instance- level option, rather than set on the class). * Re-integrate Kevin/Bill's Membership product.