<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/13/2014 09:32 AM, Dan Wilcox
wrote:<br>
</div>
<blockquote
cite="mid:5AD9B4E2-F305-46CD-BB6E-D40A3B3C9BE0@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
As Hans has proposed for years, IMO this is really the only way to
perhaps solve the "PD gui development doesn't move fast enough"
problem in the long term. In this case, Miller would have the core
(in libpd) & the pd-vanilla wrapper gui formally separated
while everyone else can then use the same libpd core within other
flavors. The DSP core is the heart and soul and I see no reason to
try and change that in any way.</blockquote>
<br>
Sorry, I don't know quite what you're referring to here. The only
two examples I gave-- $@ and [initbang] wouldn't change anything in
the DSP core.<br>
<br>
<blockquote
cite="mid:5AD9B4E2-F305-46CD-BB6E-D40A3B3C9BE0@gmail.com"
type="cite">
<div><br>
<div>
<div>On Jan 13, 2014, at 1:54 AM, Jonathan Wilkes <<a
moz-do-not-send="true" href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); float: none;
display: inline !important;">#2 is hard. Where would you
start and how would you proceed?</span></blockquote>
</div>
<div><br>
</div>
<div>I think what makes sense is to list out the main interfaces
to the DSP core that are currently being used by TCL.</div>
</div>
</blockquote>
<br>
I think by DSP core you're referring to:<br>
* DSP graph stuff<br>
* message dispatching system<br>
* various widgetbehaviors and data structures parentwidgetbehaviors<br>
* all the gui logic in g_editor.c<br>
* gui queuing stuff, array selection/manipulation logic, mouse
motion callbacks, and probably other things I'm forgetting<br>
<br>
Is this correct?<br>
<br>
<blockquote
cite="mid:5AD9B4E2-F305-46CD-BB6E-D40A3B3C9BE0@gmail.com"
type="cite">
<div>
<div> In the simplest case, we could literally create wrapper
functions which emulate the tcl argument lists. libpd
currently wraps the formal message sending, midi, &
processing areas. I think now we need to see if it's possible
to wrap the DSP graph editing/manipulation, canvas, patch
loading/saving, etc.</div>
</div>
</blockquote>
<br>
I'm not clear on what libpd actually includes. For example, does
all the logic from g_editor remain intact?<br>
<br>
-Jonathan<br>
</body>
</html>