On Sun, 2007-09-16 at 22:03 +0200, [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 ...
which would be already significantly different from netpd. netpd does
_only_ synchronize patches on load time. you cannot edit patches
collaboratively in realtime.
however, i think, giving nova the necessary interfaces would be very
cool indeed (and probably more flexible than implement such a system in
nova itself).
what pd lacks and what would be cool for nova, is an opportunity to
receive all messages, that are generated by user actions like object
creation and connection creation.
what is also a drawback of pd, is that you cannot just send the every
message of the a .pd-file to a canvas in order to recreate the patch
dynamically, since pd-messages to a canvas and the pd file format use a
slightly different format. i think this is a fault by design.
i admit, i haven't tried nova yet, but these are issues, where nova
definitely could score.
roman
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
_______________________________________________
nova-dev mailing list
[email protected]
http://klingt.org/cgi-bin/mailman/listinfo/nova-dev
http://tim.klingt.org/nova
