2008/10/14 Mikkel Kamstrup Erlandsen <span dir="ltr"><<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div dir="ltr">2008/10/7 Arun Raghavan <span dir="ltr"><<a href="mailto:arunisgod@gmail.com" target="_blank">arunisgod@gmail.com</a>></span><br><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tue, Oct 7, 2008 at 5:35 PM, Mikkel Kamstrup Erlandsen<br> <<a href="mailto:mikkel.kamstrup@gmail.com" target="_blank">mikkel.kamstrup@gmail.com</a>> wrote:<br> [...]<br> <div>> Yes, it makes sense to keep the breakage between 1.0 and 2.0 as<br> > minimal as possible.<br> <br> </div>My main thoughts on this ("borrowed", as you can no doubt see):<br> <br> 1) Release early, release often: get the spec out and let people have<br> something stable to use<br> <br> 2) Make one to throw away: it's okay if some things need to change<br> radically over the API after the first version. If comaptibility can<br> remain, that's good, but let's deal with that particular problem when<br> we get to it. As Mikkel says, if there is a compelling reason to use<br> the newer API, clients will get (re)written switch to it. And there<br> are always ways to make that transition less painful.</blockquote></div><div><br>I understand this as agreement to some degree...<br><br>Based on the responses here I'll try and add the proposal where SearchChanged signal passes along the relevant content- and source categories. Then when we have it written down it might be easier to discuss.</div> </div></div></blockquote><div><br>I flushed my mind onto <a href="http://xesam.org/main/Drafts/LiveAPIChanges">http://xesam.org/main/Drafts/LiveAPIChanges</a> before I am starting to write it to the spec. <br><br>Please note that I shifted away from the SearchChanged version passing in the content and source categories affected, for the reason stated in the last paragraph of the section entitled "The SearchChanged Signal".<br> </div></div><br clear="all">Please comment or forever hold your peace (no I did not say "piece" you dirty-thinking-mind).<br><br>-- <br>Cheers,<br>Mikkel<br>