[EMAIL PROTECTED] wrote: > The following issue has been UPDATED. > ====================================================================== > https://tim.klingt.org/mantis/view.php?id=22 > ====================================================================== > Reported By: mescalinum > Assigned To: tim > ====================================================================== > Project: nova > Issue ID: 22 > Category: gui > Reproducibility: N/A > Severity: feature > Priority: none > Status: assigned > ====================================================================== > Date Submitted: 09-16-2007 21:11 CEST > Last Modified: 09-16-2007 22:03 CEST > ====================================================================== > Summary: [feature request] networked collaborative patching > Description: > many programs are moving towards this conception of collaborative work. > also you are on the easy way (I hope) because your young and new project, > and things are more facilitated by the gui/server separation. > > basically the concept is: N users participate to a patching session. > every user uses a different machine, so there will be one gui and one > server for each user. > the operation of one user is reflected in the patch of all active > participants users. > to achieve this users connect to a network server - let's say a IRC-like > server for convenience - and every action a user does, is broadcasted to > all other guis through the IRC server. > > this enable people to collaborate on works, work together even when > distances are big, do jam sessions and more > > I hope you like the idea, and be able to implement it. > I'm here for any hep you might need. > ====================================================================== > > ---------------------------------------------------------------------- > tim - 09-16-07 22:03 > ---------------------------------------------------------------------- > i have an idea, what you are trying to propose ... it reminds me on the > netpd patches ... > > in principle, this could be done in nova, but i guess, the way to go would > be to provide the necessary means that this can be implemented ontop of > nova ... i don't think, that it would be necessary to implement in inside > the core ... > > the question is, what would one require in the nova language to implement > a system like this? possibly only dynamic patching and network io ... > >
Hey! I am wondering whether (gui)objects can have their own configuration-section in the .npx file-format for object-specific data such as sequencer-,color-,file-data. when you want to share the npx-files, it also makes sense to allow for some kind of "project"-management that looks for externally referenced stuff such as samples which then should be associated with the npx-file. maybe some sort of project-directory would fix that. when doing network-based patching-sessions it would at least allow for a consistent starting point. i guess "just" having dynamic patching would not be sufficient, because data-objects would not be shared among the users when the patch is being edited and therefore no user might have a consistent copy of the patch (for her/his own). on the other hand the language/objects must explicitely state, that they are associating/binding data-objects with the patch. Niklas _______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
