(This is also covered in a short section on the upcoming libpd paper.) With the success of libpd, the vanilla sources have proven to be an adaptable basis as a core library without substantially altering the purpose or maintainability of vanilla itself. We now have an ecosystem of applications which all share the same vanilla core. Can this model be extended so vanilla/libpd can be used as the core for the other variants of the Pure Data GUI?
Similarly, can the GUI communication with the core be standardized around a messaging API to allow something like libpd to be used as this basis? Jonathan Wilkes has done work in this area with the Purr Data messaging API. I can foresee various GUIs all sharing the same core, objects, etc Also, can the vanilla sources be greater modularized to allow overriding of various aspects of the GUI / internals when used by variants ie. undo/redo, etc? This could allow for a better sharing of development resources while maintaining both the goal of vanilla stability and allowing for customization and experimentation with newer, better GUIS. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
