<div class="gmail_quote">On Sun, Apr 19, 2009 at 7:52 AM, DeKay <span dir="ltr"><<a href="mailto:dekaymail@gmail.com">dekaymail@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
OK. After some discussions in IRC, I put a bunch of new issues into<br>
the google bug tracker. I know Andrea wanted to stick with sf, but<br>
nobody else can stand it. So in to google they went.<br>
<br>
It seems that the project is going to need better communication<br>
between the members if it is to keep making progress. People seem to<br>
be taking the project in different directions. There has been the<br>
removal of some functionality that seemed to have a good reason for<br>
being there. I hope we can find a way to communicate the various<br>
ideas, show some flexibility, and agree on a common goal going<br>
forward.</blockquote><div><br>Yes, good communication is crucial/critical. (I'm not sure what word is better) <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
So here are a few of my thoughts to kick things off, in no particular order:<br>
- don't put out a new release until the browser becomes more stable.<br>
There are a lot of bugs, crashes, and even some dangerous behavior<br>
right now (eg <a href="http://code.google.com/p/rekonq/issues/detail?id=25" target="_blank">http://code.google.com/p/rekonq/issues/detail?id=25</a>).<br>
The last thing you want is to give people a bad impresssion early on,<br>
because you'll lose many of those people forever. I still think of<br>
Nautilus as crap even though I haven't used it for many years :-)</blockquote><div><br>I totally agree.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- improve communication. This mailing list needs more activity. <br>
- pick a new name.</blockquote><div> </div><div>Maybe reKon ;D<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- settle on a bug tracker</blockquote><div> </div><div>Google code / KDE bugzilla (if available)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- (most importantly) come up with some kind of roadmap. The TODO list<br>
is relatively short term. Stuff like this needs to be in there so we<br>
can aim for longer term goals:<br>
* What needs refactoring and what doesn't?</blockquote><div> </div><div>Downloads've been refactored, they still need some love thou.<br><br>MainWindow and MainView are the biggest classes with lots of methods and initialization.<br>
We could break them into pieces, e.g.:<br>- make new class MainWindowPrivate with all the boring initialization and stuff and leave in MainWindow only the necessary logic.<br>- divide MainView to get new class(es) WebTab (and if needed MainViewPrivate)<br>
WebTab is most important to make class responsibilities clearer, make testing easier and prepare for future enhancements (like bookmarks:/ protocol widget or Chrome-like "home page" with recent pages and stuff, etc...) - I have initial work donw in my experimental branch and I've already backported some of the stuff.<br>
<br>UrlBar has been rewriten byt this is only initial stuff, we need to reimplement KCompletion and KCompletionBox for starters an than move forward to awsomebar-like funcionality (bookmark menu, tags, etc)<br><br>History needs some love (we can try to port latest Qt demo browsers history manager), there are lots of bugs there.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * Multiple window support. Will it be added back or is it removed forever?</blockquote>
<div> </div><div>I think we need multiple windows support (is there any browser that don't have it?)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Plugin / extension system</blockquote><div><br>Plugins as in shared libraries are fairly easy to do (in fact rekonq in my and avaddons branch is a shared library to make testing possible and to allow prefetching by preload daemon)<br>
As I said earlier,side panel should (will) be made as shared library.<br><br>But for extensions, IMHO the ideal thing would be to share common extensions system with konqueror (they already have basic adblock), but I'm not sure how it's implemented.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
* Bookmarks</blockquote><div><br>Bookmarks needs some further changes as well (new pixmap provider among the others) and an BookamarkModel for the bookmark sidepanel and UrlBar awsome-bar-like funcionality.<br>Bookmarks taging is essential IMO (with ability to search by tag from urlbar)<br>
</div><br></div>We need RSS support as well, this is basic feature (integration with Akregator and Google Reader is a must)<br><br><br>And lots of small things like:<br>Drag'n'drop doesn't work.<br>301 is not supported.<br>
ctrl+f5 cache flush and reload<br><br><br><br><br>