System package with common (abstract and atomic) types, views, and view components. Other packages either inherit from the abstract types or use other containers.

Goals

• Reduce code re-use.
• Provide developers with all functionality required to have a single, simple method of developing other packages.

Scenarios

• Graph
• List
• Table
• Tags
• Tree
• Universal document

Personal information manager to collect and organize all personal information: notes, thoughts, contacts, appointments, and so on.

Goals

• One place for all personal information.
• Cross linking for all pieces of information
• Tagging
• Place for quick data entry to be organized later. People generally perform better when they do these tasks separately - enter information first and only then organize. If they try to do both everything becomes harder.

Scenarios

• Algorithm - Set of steps or a simple to-do list (for recipe and so on)
• Contacts
• Journal
• Notes
• Shopping list

Managing all work. In many cases it work is related to some project, but sometimes it isn't (like doing dishes. I guess the project is to keep dishes, or house clean, but most people don't think in such way). Both scenarios are supported, but main empasize is on the project management.

There are various methodologies to manage projects and they need to be supported in a manner that will allow users to select what to use, without forcing them on the user.

Goals

• Single place to capture, plan, schedule and track work
• Balance time between different project and different times of activities (to make sure all important things get done and I don't get burned out in the process)
• Provide me with different ways to manage my work and allow me to choose the most appropriate way

Scenarios

• Agile development
• Documentation
• Issues - user story, task, defect
• Iterations
• Versions

Collections to organize and trick different types of items (books, games, music, etc.)

Goals

• Download addition information for an item from the Internet
• Advanced search and filtering

Scenarios

• Book collection
• Game collection
• Movie collection
• Music collection
• Universal collection

Workflow or pipe-line simulation when some document (resource) go through many stages. In each stage people or other processes can be involved. This is often used in business to co-ordinate people working on the same document.

Goals

• Graphical designer
• Support any document or file
• Co-ordinate activity and resources with other applications and many different people

Editing of different documents in their native format, without using Sider internal XML data representation. Essentially some document is imported into Sider on load and exported on save.

Goals

• Handle invalid formats and data
• Full compatibility with native document format. Original program needs to work with the document after it was modified in Sider without any problems.
• Support files in any original form, not only XML. Other formats are simple text file and binary format.

Scenarios

• XML, XSLT, XSD and other XML related files editing
• Microsoft and Open Office documents
• HTML and other web-related files
• Code source (C#, C++, Java, SQL, etc.)
• Data-base editing and management