|FDT SWFBridge Examples||Alan Klement||5/29/12 8:29 AM|
|Re: FDT SWFBridge Examples||Alan Klement||5/30/12 12:58 PM|
|Re: FDT SWFBridge Examples||Pavel fljōt Pevnitskiy||5/31/12 5:58 AM|
So what's the difference here compared to code templates?
|Re: FDT SWFBridge Examples||Alan Klement||5/31/12 7:30 AM|
Good question. It's also reminded me that I need to create more context around the examples - instead of just cranking them out.
For that last example: SimpleQuickAssist, I'll explain why I added it.
This example is more about documenting how to use the API, not to demonstrate how far it can be taken. Once you understand what is going on, you start to realize the power.
Getting back to your question of how this is different than a template. It's not even comparable, really mostly to due #2 & #3. Templates are part of autocomplete, you start typing in a template name and hit autocomplete. As you type more of the template name, it gets filtered out. When you select it, the text just gets plopped into the editor.
With templates, you have no control over the context in which the text edit is either called or applied. It just plops down the text edit at the cursor offset and for the length of the text edit (template). There is no enforcement when you can / can't call a template. You can plop a template in the wrong place and break your code.
Templates are also single shot. It just plops down text and that's it.
Now...suppose you wanted a 'smart' template that....
...you get the idea
|Re: FDT SWFBridge Examples||Pavel fljōt Pevnitskiy||5/31/12 8:18 AM|
Well now that's an Answer) include some of it in the readme.
|Re: FDT SWFBridge Examples||Alan Klement||6/1/12 12:45 PM|