On Sat, Jan 12, 2013 at 10:42 PM, Sven Van Caekenberghe <span dir="ltr"><<a href="mailto:sven@stfx.eu" target="_blank">sven@stfx.eu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Julian,<br>
<div><div><br>
On 12 Jan 2013, at 16:29, Julian Fitzell <<a href="mailto:jfitzell@gmail.com" target="_blank">jfitzell@gmail.com</a>> wrote:<br>
> No need for a grease-specific selector - just need different versions of grease for Pharo 1 and Pharo 2 if people want both versions of Pharo supported.. Can't recall what other platforms use, but in general I prefer 'Substring' myself.<br>
<br>
</div></div>There are Grease-Pharo-[10|11|20]-Core packages in SqS/Seaside31 so I guess the possibility to differentiate is there.<br>
<br>
My point is however that the Seaside developers have to make a simple choice: keep the older #includesSubString: in the code base or switch to the newer (more logical) #includesSubstring:<br>
<br>
Either choice is OK, just pick one so that we can get this trivial issue out of the way.<br></blockquote><div><br>As I said, my personal preference is #includesSubstring: as "SubString" has always bothered me, but it depends what other platforms do. There's not much point using the version that only one platform uses and forcing all the others to implement a Grease extension...<br>
<br>Julian<br>
</div></div>