<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Grande'; font-size:9pt; font-weight:400; font-style:normal;">Hi!<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>On 8 апреля 2009 18:00:59 Paweł Prażak wrote:<br>
> I'm thinking about adding another layer of abstraction between mainView and<br>
> urlBar / webView pair something like webTab class or something, because<br>
> MainView is too big and have to many responsibilities and it's hard to<br>
> understand because of it, not to mention debugging it.<br>
><br>
> I think that by adding another level of abstraction we can achieve better<br>
> encapsulation and clearer code. We would have clear responsibility.<br>
> MainView (TabWidget) contains WebTabs and every WebTab contains WebView and<br>
> UrlBar. Now we have situation when MainView is involved in creating new<br>
> tabs in pieces so IMO there is greater possibility of introducing a bug. I<br>
> matter of facts, we have a new one I introduced while porting UrlBar to<br>
> KDE.<br>
><br>
> Maybe I'll try it out in a branch and show you what I mean. What do you<br>
> think?<br>
><br>
> --<br>
> Paweł<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Seems it would be the best solution.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
С уважением,<br>
Домрачев Александр.</p></body></html>