<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Daniel Wilcox</b> <span dir="ltr"><<a href="mailto:danomatika@gmail.com">danomatika@gmail.com</a>></span><br>
Date: Mon, May 31, 2010 at 5:42 PM<br>Subject: Re: [PD] loading an .aif file into an array<br>To: "<a href="mailto:padawan12@obiwannabe.co.uk">padawan12@obiwannabe.co.uk</a>" <<a href="mailto:padawan12@obiwannabe.co.uk">padawan12@obiwannabe.co.uk</a>><br>
<br><br>Hrmph. Now I'm being harangued for suggesting people use spaces in filenames? This is 2010, not 1985. Spaces in paths/filenames are handled by OSX, Windows, Linux, etc. Personally, I use both, with a preference for spaces on the Gui and no spaces when I'm working in the terminal. Tab completion works just fine with spaces.<div>
<br></div><div>I see you're point, but it's not going to convince all of the people out there to batch convert their filenames because the *should*.</div><div><br></div><div>Add a disclaimer to the heading of the floss manual page.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Mon, May 31, 2010 at 3:54 PM, <a href="mailto:padawan12@obiwannabe.co.uk" target="_blank">padawan12@obiwannabe.co.uk</a> <span dir="ltr"><<a href="mailto:padawan12@obiwannabe.co.uk" target="_blank">padawan12@obiwannabe.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p style="margin:0px"> </p>
<p style="margin:0px"><span></span></p>
<p style="margin:0px"><span>Hey Dan,</span></p>
<p style="margin:0px"><span></span></p>
<p>Three times per year, to a class of 72 students, at about lecture 2,</p>
<p>I do a 5 minute chunk which is basically</p>
<p> </p>
<p>"Why you should NOT use spaces in filenames":</p>
<p> </p>
<p>Of course that extends to good naming style and why some other</p>
<p>characters like !"£$%^&*()}{[];:.<> are not a good idea either.</p>
<p> </p>
<p>The impression they get (I am frequently told) is a rather good one.</p>
<p>They are suprised and delighted to discover there is a bit of deeper</p>
<p>computer science knowledge which explains why sometimes, certain filenames</p>
<p>don't work with a whole range of applications.</p>
<p> </p>
<p>This is something true of not just Pd, but many applications on many</p>
<p>platforms.</p>
<p> </p>
<p>We agree that one should not accept everything that a machine will</p>
<p>let you do as OK, just because you can. After all a car will let</p>
<p>you steer it off the road.</p>
<p> </p>
<p> </p>
<p>Allowing spaces in filenames was something Windows introduced,</p>
<p>to the horror of many, back in the 90's. There are still problems</p>
<p>caused by this 20 years later because Microsoft broke with what</p>
<p>was a widely understood convention (spaces are delimiters and should</p>
<p>be replaced by underscore _ or endash - in file names .</p>
<p> </p>
<p>So, my opinion is that not using spaces in filenames is good advice.</p>
<p>Especially to new users who might not understand why.</p>
<p> </p>
<p>All the same, I totally agree with you that Pd is wanting when</p>
<p>an informed programmer cannot easily deal with this situation</p>
<p> </p>
<p>Best to you,</p>
<p> </p>
<p>Andy</p><div>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<div style="margin:5px 0px 5px 0px;font-family:monospace">
On 31 May 2010 at 12:36 Dan Wilcox <<a href="mailto:danomatika@gmail.com" target="_blank">danomatika@gmail.com</a>> wrote:<br>
<br>
<br>
> I hope you don't suggest this as the solution to new pd users, I'm sure it doesn't give a very good impression ...<br>
<br>
</div>
</div></div>
</blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br>Dan Wilcox<br>danomatika<br><a href="http://www.robotcowboy.com" target="_blank">www.robotcowboy.com</a><br>
</div></div>
</div><br><br clear="all"><br>-- <br>Dan Wilcox<br>danomatika<br><a href="http://www.robotcowboy.com">www.robotcowboy.com</a><br>