<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Feb 9, 2007, at 4:48 PM, Jacob Rus wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">subtleGradient / Thomas Aylott <oblivious@...> writes:</DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Ok!</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I have now played with this thing and we need it.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">It's really awesome stuff.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Forget about the filesize, it's just really necessary stuff.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'd really like this stuff to be in the default Javascript bundle.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">But, adding 4 megs to a default TextMate bundle seems wrong without <SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">express Allan permission.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I vote no on the 4 MB increase.<SPAN class="Apple-converted-space"> </SPAN>The *.tmcommand files themselves are surely</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">small, and can easily call out to these tools if they are installed elsewhere.<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">What's the downside to making people do a few extra clicks to actually install</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the large parts?<SPAN class="Apple-converted-space"> </SPAN>It's certainly easier for most than going through the hassle</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">of picking up a bundle from SVN.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">So, let's make an Experimental Javascript bundle and slap this stuff <SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">in there.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">No, this is exactly the wrong approach.<SPAN class="Apple-converted-space"> </SPAN>If this is so unbelievably cool, it</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">should be in the main bundle so that regular users can take advantage of it,</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">without needing to muck with svn, etc.<SPAN class="Apple-converted-space"> </SPAN>In fact, I think that putting things in</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Experimental bundles is generally bad, unless their inclusion in the regular</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">bundle could break something else.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">So my vote: slap it in the regular javascript bundle, document it in the</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">bundle's help file (it does have one, right?) with installation instructions,</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">and then bring up a way for users to install if you try to run the commands</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">without the relevant external tools.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">-Jacob</DIV></BLOCKQUOTE></DIV><BR><DIV>What I meant was that it should be in the default bundle.</DIV><DIV>But since Allan should be the final decider on what major stuff like that goes into the default bundles, I'm saying to temporarily put it in another bundle until we can get Allan's opinion on it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think your option is actually better in the short term.</DIV><DIV>Put it in the default bundle now, but leave out the larger bits.</DIV><DIV>Then make it easy for people to install the larger bits if they feel so inclined.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Good plan. Let's do it</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><DIV>thomas Aylott — <I>design</I><B>42</B> — <B>subtleGradient </B>— CrazyEgg</DIV></DIV></BODY></HTML>