Update of /cvsroot/pure-data/pd/src In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5052

Modified Files: Tag: devel_0_39 TODO Log Message: .

Index: TODO =================================================================== RCS file: /cvsroot/pure-data/pd/src/Attic/TODO,v retrieving revision 1.1.2.24 retrieving revision 1.1.2.25 diff -C2 -d -r1.1.2.24 -r1.1.2.25 *** TODO 27 Nov 2006 21:43:40 -0000 1.1.2.24 --- TODO 27 Nov 2006 22:51:50 -0000 1.1.2.25 *************** *** 157,172 **** [ ] inlet inspector to show what are the message types expected by an inlet that could read like "int: set left operand; bang: do it"

- <zkink> matju: can you add a hotkey configuration dialog. it lets you hit a hotkey and it puts down any object under your mouse - <zkink> puts down a [t b i] - <matju> yea, of course... eventually... and a button bar manager at the same time - <zkink> and color code them, and same with wires <zkink> as well as select multiple wires, or multiple objects, and color code them - <zkink> the little square PD window needs cleaning up - <zkink> it takes 5x more space than is needed, for the amount of information it shows - <zkink> PD should highlight the inlet you're connecting to - <zkink> when they're close together, it's difficult to tell which one you're going on - <zkink> max doesn't use a circle icon, instead, it highlights the inlet - <zkink> much more informative <zkink> if you do segmented patchchords, it needs some functions: <zkink> a hotkey to click on the chord, and add a new segment --- 157,168 ---- [ ] inlet inspector to show what are the message types expected by an inlet that could read like "int: set left operand; bang: do it" + [ ] custom buttonbars (including premade objects with args like a [t b f] and such) + [ ] with configurable hotkeys + [ ] colored wires + [ ] insert_object makes error with multiple selection. + [ ] popup_properties on multiple selection. + [ ]

<zkink> as well as select multiple wires, or multiple objects, and color code them <zkink> if you do segmented patchchords, it needs some functions: <zkink> a hotkey to click on the chord, and add a new segment *************** *** 178,184 **** <zkink> like _| instead of / <zkink> it makes it into three lines: _|~ ! <zkink> also: pd should have a NULL object. it looks like a point * on the GUI. ! <zkink> it does nothing but pass data through a splitter/merger. ! <zkink> circuits do this. they can split. they dont need to go into a module to split. <zkink> PERHAPS, a hack for multisegmented patchchords, would be to make a null object <zkink> a null object is an actual object that just looks like a . --- 174,182 ---- <zkink> like _| instead of / <zkink> it makes it into three lines: _|~ ! ! [ ] [t a] could be a very small GUI object (called "null object") ! [ ] all the [t] could be GUI objects ! [ ] GUI objects for [inlet] and [outlet] and [pd] ([page]) ! <zkink> PERHAPS, a hack for multisegmented patchchords, would be to make a null object <zkink> a null object is an actual object that just looks like a . *************** *** 195,201 **** <zkink> if you select any wire, it reports whats coming through that wire <matju> the NULL object looks like jMax's [fork] except with only one outlet - <zkink> yes <matju> or almost like [t a] - <zkink> yep <zkink> that would work as a makeshift plan for multisegmented chords <matju> except [t a] is more like "list $1" and converts scalars into 1-element lists (yuck) --- 193,197 ----