Rough allocation / listing-of of tasks for Spring 2010:
Action widget: MZ
each action needs to know how many parameters
represent action and its pods visually
coloring based on completion
Menus for events and actions. Condense "set property" and "add action" into a single entity that will show up in the menu. (Talk to James)
Pipes: (Zach)
select pipes, delete pipes. (since they are presumably just graphics-drawn, keep hashmap of them as shapes).
lower priority make them not so damn ugly.
Multiple views:
WYSIWYG
condensed pipe view
full fledged underground view (MAYBE SOMEDAY pipes and involved actions & widgets MORE visible than the background "noise". alpha blending?..)
Pipe tool -- also store former view and restore it after its done
Controller?
Action tool / widget
***LOWER PRIORITY LIST:****
Refactor borders around widgets. in particular, add pods and context menus. that way can also restore look & feel.
always a spare "pod" ready for docking.
if click on it and release, menu shows up.
if drag, then connection first, then the two menus (which will persist and show connection as red until they are selected)
Comments (2)
Nov 21, 2008
Ben Peters says:
We really need to clean this up. There are still a bunch of pages inside old doc...We really need to clean this up. There are still a bunch of pages inside old doc pages here. If anyone gets a chance, let's get this thing in order so it makes sense for the next group.
Nov 21, 2008
Ben Peters says:
OK, we're getting there now. Just make sure you add your docs to this page, and ...OK, we're getting there now. Just make sure you add your docs to this page, and feel free to rearrange in whatever way makes sense.