Thursday, July 13, 2006
Documentation
One often mentioned problem with the plugin is the documentation.
It is sad to say that the documentation has changed in a similar style
to the plugin itself. I've had to make numerous 'bug fixes' and the
additional features are poorly described. Inspired by Panos's initial
draft I've started to create a proper piece of help to include with the
downloads. If I get time I'll finish it off this weekend.
I'd also like to thank Panos for the lovely logo sported underneath the
link on the right. He's knocked up a 'powered by' style image as well:
Very nice.
Anyway: new docs are coming and I'm trying to gather together some examples for different languages as well. If you have any you'd like to share then post them in the comments. Mention what your start and end tags are as well. I'm tempted to remove the customability of start and end tags in order to make sharing easier. I was thinking of '<{' and '}>' as the new standard but let me know your thoughts on that as well. ¶ 4:59 pm
It is sad to say that the documentation has changed in a similar style
to the plugin itself. I've had to make numerous 'bug fixes' and the
additional features are poorly described. Inspired by Panos's initial
draft I've started to create a proper piece of help to include with the
downloads. If I get time I'll finish it off this weekend.
I'd also like to thank Panos for the lovely logo sported underneath the
link on the right. He's knocked up a 'powered by' style image as well:
Very nice.
Anyway: new docs are coming and I'm trying to gather together some examples for different languages as well. If you have any you'd like to share then post them in the comments. Mention what your start and end tags are as well. I'm tempted to remove the customability of start and end tags in order to make sharing easier. I was thinking of '<{' and '}>' as the new standard but let me know your thoughts on that as well. ¶ 4:59 pm
Comments:
<< Home
Panos: I'd looked into using ${} as tags but I think it'll break certain languages. TextMate can get away with this as it removes its tags on insert and remembers where to jump to. As we leave ours in (removing them would require more magic leading to more breakage) we need to be more careful about cross-language compatibility. This is why the option exists for definined your own tags.
Karl: I've added the problem from your version to my test suite. There is still a similar issue with the current version. Two commands on the same line will get substituted but only it they're separated by 'some' whitespace. No whitespace works if the value is not changed. The next release will fix this now that I know about it. Thanks for the post.
Post a Comment
Karl: I've added the problem from your version to my test suite. There is still a similar issue with the current version. Two commands on the same line will get substituted but only it they're separated by 'some' whitespace. No whitespace works if the value is not changed. The next release will fix this now that I know about it. Thanks for the post.
Subscribe to Post Comments [Atom]
<< Home
