Hi,
During the last couple of weeks I have not been able to comepletely follow all the stuff going on in this mailinglist. I completely missed the introduction of the "view as HTML" feature. I noticed a couple of references to it and have seen that some people use it now in their bundles.
However, when I wanted to get into it, I found that bundles are not really documented. Could people perhaps put some documentation on the wiki about their bundles? But an even better way would be to have some help/description feature for bundles within TM...Allan, what's your take on that?
Jeroen.
At 7:49 PM +0100 2/9/05, Jeroen van der Ham wrote:
However, when I wanted to get into it, I found that bundles are not really documented. Could people perhaps put some documentation on the wiki about their bundles?
What is this "documentation" you speak of?
:)
Anyway, it might be beyond us to all document the bundles, as some of us are spare-time-hackers. But the new features are definitely getting ahead of us. I don't get drag commands or, really, the full power of snippets. But maybe there is some distributed way we can each highlight one neat trick from our bundles, and together we could cover most of the neat new features...
- Eric
On Feb 9, 2005, at 19:49, Jeroen van der Ham wrote:
However, when I wanted to get into it, I found that bundles are not really documented. Could people perhaps put some documentation on the wiki about their bundles?
But an even better way would be to have some help/description feature for bundles within TM...Allan, what's your take on that?
I've been wanting to add the ability to view/edit each bundles README in the bundle editor. That probably will help a bit.
Also, I am seriously considering the thing people have requested about having bundles as separate downloads. That'd give them a version number, release notes etc.
On Feb 9, 2005, at 11:39 AM, Allan Odgaard wrote:
On Feb 9, 2005, at 19:49, Jeroen van der Ham wrote:
However, when I wanted to get into it, I found that bundles are not really documented. Could people perhaps put some documentation on the wiki about their bundles?
But an even better way would be to have some help/description feature for bundles within TM...Allan, what's your take on that?
I've been wanting to add the ability to view/edit each bundles README in the bundle editor. That probably will help a bit.
Also, I am seriously considering the thing people have requested about having bundles as separate downloads. That'd give them a version number, release notes etc.
+1 (!). TM could download initially with a smallish set, or have a first-time wizard like Quicksilver.
On 09-02-2005 20:39, Allan Odgaard wrote:
I've been wanting to add the ability to view/edit each bundles README in the bundle editor. That probably will help a bit.
That would help a bit, but is too limited to provide documentation for all bundles (everyone wants everything quickly, and providing large amounts of texts is not helping...)
I'd propose to change the Bundle Editor to a Bundle Browser (<insert joke about Bare Bones Software here>) where you can browse the contents of bundles and not only see it's innards, but also a textfield for documentation.
Also, I am seriously considering the thing people have requested about having bundles as separate downloads. That'd give them a version number, release notes etc.
I think this would play very nicely with the idea of a Bundle Browser...
Jeroen.
On 9 Feb 2005, at 19:39, Allan Odgaard wrote:
I've been wanting to add the ability to view/edit each bundles README in the bundle editor. That probably will help a bit.
Allan, just a few thoughts on this. IF this ReadMe file could be viewed in different formats depending on the file name extension. Eg. ReadMe.txt it's treated as plain text, but ReadMe.html is treated as HTML. Perhaps it would just be easier to treat it as HTML all the time. I'm not sure which is easier for you/everyone ?
Why? Well, if it's HTML then we could have internal links to read more Snippets, Commands, Templates, etc. files or even to a website URL that could have more detailed descriptions of what's in the various bundles, rather than - perhaps - one single long ReadMe document that contains it all. This might not be absolutely crucial in every case, but it might just give greater flexibility to everyone for the future. Who knows what type of great bundles that will arrive up ahead ?
Also, I am seriously considering the thing people have requested about having bundles as separate downloads. That'd give them a version number, release notes etc.
Yes, I think that could be an improvement as well, especially for shared bundles that might be worked in the community. Perhaps something along the lines of Firefox's Extensions system type functionality thing ??
Kind regards,
Mats
---- "TextMate, coding with an incredible sense of joy and ease" - www.macromates.com -