Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 156038

Summary: [Cheat Sheet Authoring] Implement basic simple cheat sheet editor functionality
Product: [Eclipse Project] PDE Reporter: Mike Pawlowski <mike.pawlowski>
Component: UIAssignee: Mike Pawlowski <mike.pawlowski>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: pde-ui-inbox
Version: 3.3   
Target Milestone: 3.3 M2   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 146988    

Description Mike Pawlowski CLA 2006-09-02 16:02:10 EDT
Create the basic editor functionality for the new simple cheat sheet editor.

Functionality required by Bug # 146988
Comment 1 Mike Pawlowski CLA 2006-09-19 14:52:37 EDT
Patch released to HEAD in CVS

Work Done:

* Updated cheatsheet model object to provide functionality for the following:
  -> add item
  -> remove item
  -> determine if first item
  -> determine if last item
  -> determine index of item

* Updated cheatsheet model object to provide functionality for the following:
  -> add subitem
  -> remove subitem
  -> determine if first subitem
  -> determine if last subitem
  -> determine index of subitem
  
* Updated all model and factory classes to store reference to their parent
  
* Updated all model classes to fire property and model insert, remove and
  change events as required to implement dirty / save functionality
  
* Implemented master details block functionality

* Created details sections for the following:
  -> cheatsheet, item, subitem, command, onCompletion, intro, description
  -> Implemented functionality to do the following:
     - Create the UI
     - Hookup the listeners
     - Update the UI

* Created master section   
  -> Implemented functionality for the following:
     - Add item
     - Add subitem
     - Remove item, subitem
     - Move item, subitem up and down
     - Preview cheatsheet
  -> Hooked functionality into context menu, buttons and global actions
  -> Created corresponding actions
  -> Add functionality to update master tree view accordingly when model
     changes