<div id="reply-content">
Hi,
</div><div id="reply-content"><br></div><div id="reply-content">I'm glad you are taking this decision !</div><div id="reply-content"><br></div><div id="reply-content">I did the same move in Curses::Toolkit. A border should be a first class widget. The rest should be left to the themes realm. </div>
<div id="D2AC83F64F4B426D88699C175966EB7A"></div>
<p style="color: #A0A0A8;">Le mercredi 12 décembre 2012 à 11:12, Paul LeoNerd Evans a écrit :</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<div id="quoted-message-content"><div><div>I don't think I like the current implementation of Tickit::Widget::Box.</div><div><br></div><div>Or rather, I do but I think it should be renamed to</div><div>Tickit::Widget::Border. I'm also not sure I like the Borderable role.</div><div><br></div><div>So I'm going to make a new Tickit::Widget::Border, in the Tickit-Widgets</div><div>distribution, that contains the current behaviour of T:W:Box (i.e. has</div><div>the Borderable role mixed into it). Once that's out I'm going to remove</div><div>T:WR:Borderable, and recreate T:W:Box to a better idea.</div><div><br></div><div>I don't see any code around actually using T:W:Box or T:WR:Borderable in</div><div>its current form, other than some small examples that will be simple to</div><div>rewrite to T:W:Borderable instead, so I don't expect any issues.</div><div><br></div><div>Shout if you have or will have a problem,...</div><div><br></div><div>-- </div><div>Paul "LeoNerd" Evans</div><div><br></div><div>leonerd@leonerd.org.uk</div><div>ICQ# 4135350 | Registered Linux# 179460</div><div>http://www.leonerd.org.uk/</div><div>_______________________________________________</div><div>Tickit-dev mailing list</div><div>Tickit-dev@leonerd.org.uk</div><div>http://mail.leonerd.org.uk/mailman/listinfo/tickit-dev</div></div></div>
</blockquote>
<div>
<br>
</div>