ParaQ v1.0 Features: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
| Line 25: | Line 25: | ||
| 001 | | 001 | ||
| 1 | | 1 | ||
| ParaQ should be able to automatically generate a complete object inspector UI for each filter. Currently, the inspector generated for the Clip filter is insufficient - there is no UI to control the implicit function object it needs to work. | | ParaQ should be able to automatically generate a complete object inspector UI for each filter. Currently, the inspector generated for the Clip filter is insufficient - there is no UI to control the implicit function object it needs to work. The Glyph filter is another one like this - it needs an input glyph object. | ||
|- | |- | ||
|} | |} | ||
Revision as of 15:37, 26 January 2006
List of features we'll need in future versions (no matter how outlandish they seem ... we can prioritize anything :) ) - things that occur to you as you're testing, coding, or using ParaQ.
Features
| ID | Prority | Description |
|---|---|---|
| 001 | 1 | View/Application snapshot. This should include useful tags in image formats that support them. |
Requirements
| ID | Prority | Description |
|---|---|---|
| 001 | 1 | ParaQ should be able to automatically generate a complete object inspector UI for each filter. Currently, the inspector generated for the Clip filter is insufficient - there is no UI to control the implicit function object it needs to work. The Glyph filter is another one like this - it needs an input glyph object. |
