<p>Meta Issue Description todo:</p>

<ul>
<li>Update the requirements list, showing potential callback signatures (as discussed in the <a href="http://lists.geany.org/pipermail/devel/2016-August/010093.html">'[FT-plugins] Proposed "Features'</a> on the mailing list).</li>
<li>Update the signatures proposed for at least sidebar symbol tree, and most likely auto-completion and calltips to have the ft-plugin provide information to Geany using TMTag structures (as <a href="http://lists.geany.org/pipermail/devel/2016-August/010120.html">mentioned</a> in the same thread as above).</li>
<li>Add more details about underlying basic implementation strategy once fleshed-out more on the mailing list <a href="http://lists.geany.org/pipermail/devel/2016-August/010088.html">"Proposed Design"</a> thread).</li>
<li>Remove "Development/Contribution Strategy" section. <a href="https://github.com/b4n" class="user-mention">@b4n</a> confirmed it's OK to make a new branch, and we will have to see how it goes with keeping the changes in-sync with master branch.</li>
<li>Replace the "Discussion Guidelines" with a simple note about not polluting this particular Github issue, and using the mailing list instead.</li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1195#issuecomment-243637343">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ-kWX3Slp8LRqu9dk05I8hdJu2oyks5qlODsgaJpZM4Jtspj">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ8EWjhzZK2YJzkCPZ5Ahde2YS7Gkks5qlODsgaJpZM4Jtspj.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1195#issuecomment-243637343"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@codebrainz in #1195: Meta Issue Description todo:\r\n  - Update the requirements list, showing potential callback signatures (as discussed in the ['[FT-plugins] Proposed \"Features'](http://lists.geany.org/pipermail/devel/2016-August/010093.html) on the mailing list).\r\n  - Update the signatures proposed for at least sidebar symbol tree, and most likely auto-completion and calltips to have the ft-plugin provide information to Geany using TMTag structures (as [mentioned](http://lists.geany.org/pipermail/devel/2016-August/010120.html) in the same thread as above).\r\n  - Add more details about underlying basic implementation strategy once fleshed-out more on the mailing list [\"Proposed Design\"](http://lists.geany.org/pipermail/devel/2016-August/010088.html) thread).\r\n  - Remove \"Development/Contribution Strategy\" section. @b4n confirmed it's OK to make a new branch, and we will have to see how it goes with keeping the changes in-sync with master branch.\r\n  - Replace the \"Discussion Guidelines\" with a simple note about not polluting this particular Github issue, and using the mailing list instead.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1195#issuecomment-243637343"}}}</script>