Changes between Version 1 and Version 7 of Ticket #5


Ignore:
Timestamp:
08/27/06 03:31:08 (10 years ago)
Author:
dstillman
Comment:

Reassigning to Elena -- once the item type templating system is set up, I'll provide instructions on doing this via the Item Type Manager. (In the meantime you can still work on the lists, but to load them into the extension we'll want the template system to be in place.)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5

    • Property Reporter changed from david to dstillman
    • Property Priority changed from blocker to major
    • Property Milestone changed from to 1.0 Beta 2
    • Property Owner changed from somebody to erazlogo

  • Ticket #5 – Description

    v1 v7  
     1The extension should ship with a large set of item types and fields defined, though only a few (a dozen or so) will show as the primary types by default. (The others might be in a submenu, etc.) 
     2 
     3Necessary steps: 
     4 
     5 1. Define as large a set of item types and fields as possible 
     6 1. Map all reasonable combinations and choose the type-specific field display order (though we could also just have the field order be global, if we think that would be sufficient) 
     7 1. Choose a default set of show/hide settings for both item types (which item types display in the primary menu) and fields (which fields show up by default for each item type) based on common usage. 
     8 1. Create localized strings