<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 30, 2010, at 4:16 PM, András Murányi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">2010/11/30 Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at">hans@at.or.at</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div style="word-wrap: break-word;"><br><div><div>On Nov 29, 2010, at 4:43 PM, András Murányi wrote:</div><br><blockquote type="cite"><div class="gmail_quote">2010/11/29 Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span><br> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div style="word-wrap: break-word;"><div><br></div><div>Hey Andras, this is great! My only request is: can we call them "GUI plugins"? "startup plugins" sounds too vague for me. Also, here's a bit more documentation:</div> <div><br></div><div><a href="http://puredata.info/docs/PdGuiPluginsAPI" target="_blank">http://puredata.info/docs/PdGuiPluginsAPI</a></div><div><br></div><div>Now I'm thinking we should start a "guiplugins" wiki folder section in the doc wiki, so like:</div> <div><div><br></div><div><a href="http://puredata.info/docs/PdGuiPluginsAPI" target="_blank">http://puredata.info/docs/</a>guiplugins (this would be your page, also be called FrontPage)</div></div><div><div><div><a href="http://puredata.info/docs/PdGuiPluginsAPI" target="_blank">http://puredata.info/docs/</a>guiplugins/<a href="http://puredata.info/docs/PdGuiPluginsAPI" target="_blank">GuiPluginsAPI</a></div> </div></div><div><div><div><div><a href="http://puredata.info/docs/PdGuiPluginsAPI" target="_blank">http://puredata.info/docs/</a>guiplugins/ExamplePlugins</div></div></div></div><div><br></div><div>How does that sound?</div> <div><br></div><div>.hc</div><div><div></div><div></div></div></div></blockquote><div><br>Sounds great. Please go ahead and rename & move 'my' page, then i'll go on.<br><br>Andras<br> </div></div></blockquote> </div><div><br></div><div>Ok here goes:</div><div><br></div><div><a href="http://puredata.info/docs/guiplugins/FrontPage" target="_blank">http://puredata.info/docs/guiplugins/</a></div><div><a href="http://puredata.info/docs/guiplugins/SimpleExamples" target="_blank">http://puredata.info/docs/guiplugins/SimpleExamples</a></div> <div> <div style="word-wrap: break-word;"><a href="http://puredata.info/docs/guiplugins/GuiPluginsAPI" target="_blank">http://puredata.info/docs/guiplugins/GuiPluginsAPI</a></div><div style="word-wrap: break-word; font-size: 12px;"> <br></div><div style="word-wrap: break-word; font-size: 12px;">Some possible fodder for more stuff for the Gui Plugins wiki:</div><div style="word-wrap: break-word; font-size: 12px;"><a href="http://puredata.info/dev/PdGuiRewriteTheming" target="_blank">http://puredata.info/dev/PdGuiRewriteTheming</a></div> <div style="word-wrap: break-word; font-size: 12px;"><a href="http://puredata.info/dev/PdGuiRewriteTheming" target="_blank"></a><br><div>So the current FrontPage and the GuiPluginsAPI pages have some overlap, and should be combined. Andras, if you can take that on, please do. You're page looks quite good so far.</div> <div><br></div><div>.hc</div><div><br></div></div></div></div></blockquote><div><br>OK, i have my request concerning combining... or rather a question:<br>it is not a real API that we're having and may be misleading to call it so, still API is a word that is good lead for somewhone looking for anything that plays the role of an API... what do you think? is there a better word to use, or we just call it API and then explain it's nor really? (or do you consider it an API?)<br></div></div></blockquote></div><div><br></div>I'm not stuck on the term API, but the stuff that I outlined there is stuff that I added to the new GUI code specifically to support plugins, rather than internal needs. Of course, being Tcl, a plugin can override really anything, so all of the GUI code can't really be called the API, tho it could be changed by a plugin.<div><br></div><div>Does that make sense?</div><div><br></div><div>.hc<br><div><br></div><div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><br class="Apple-interchange-newline"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div><br class="khtml-block-placeholder"></div><div>----------------------------------------------------------------------------</div><div><br class="khtml-block-placeholder"></div><div> <a href="http://at.or.at/hans/">http://at.or.at/hans/</a></div><br class="Apple-interchange-newline"></span></span> </div><br></div></div></body></html>