I was recently new to PD, and now I'm new to Nova. It seems pretty clear that PD has a variety of "issues", so after I heard about you guys I decided to hop over here to check things out. It looks like Tim actually knows how to write software, which was great to see :-) Building a C++ core with boost and the top-end in a scripting language is exactly the strategy I would have chosen. (It's also how Ableton Live is implemented, for trivia sake.) Anyways, on to business...
We are compiled and running, and I've been taking notes, so I'll just go through the points. * scons doesn't seem to support --help to list optional arguments. Is there something else? * Is there a way to specify the path to portaudio in the build? (Using Ubuntu Gutsy I don't have the dev files for libportaudiocpp, and it would have been nice to just put the library into trunk/libs for compilation, or at least /usr/local...) * In a simple two object patch with an oscillator to a dac I get dropouts when I move around gui items. Is everyone getting this? Any idea what's going on? It seems odd given the separation of the engine and the gui. Are position changes being sent to the back-end? * Shouldn't the title of the project wiki get changed to Nova? * Maybe I'm blind and stupid... How do you create elements besides object nodes? Number boxes, toggles? I've at least seen push-buttons in the help patches, but I don't know how to make them. (Are people against the idea of having object palettes?) * Is right-click on object for help and properties the expected functionality? Can we not have path's that suck like PD? :-) I saw on the bug tracker that undo/redo is still to be done. This is something I've done a couple times now, and it is best done early because it effects how any command that needs to support undo/redo gets implemented. So, I started coding, to find that PyQt does not have bindings for the QtUndoStack. No big deal, the interface is simple. I can do it on top of a simple stack for now with the same interface, and I'll email the PyQt guys to ask about it. This sound fine to people? Supporting undo/redo requires that each command be pushed onto the stack, and that it contains an undo/redo method which can be called. If things are implemented as Actions (in Qt speak), then it should be pretty simple. That also makes it easy to put actions into menus, onto toolbars or palettes, assign hot-keys etc... I'll be using git-svn to manage my source for the project. Any other git users out there? Tim, you ever think about moving to a distributed versioning system? Ciao, Jeff _______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
