<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><div>>I read again my comment about this and I think I need to explain myself a bit <br>
>better (my english really sucks sometimes..)<br>
<br>
I have the same problem with english :)<br>
<br>
>Point 1: <br>
>your screenshot is F-A-N-T-A-S-T-I-C ! I just grabbed your code and <br>
>reimplemented in my local copy. I need just to understand how we can hide <br>
>menubar by default (in a first installation) and rekonq 0.1.10 will be ready. <br>
>With just your suggestions! <br>
<br>
If we choose a button-menu by default, I think the configuration panel must be modified to include items:<br>
Configure toolbars<br>
Configure shortcuts<br>
</div>Switch application language<br>
and perhaps others: all actions configuring rekonq. kde applications
have many menu items that are useless when you use the application.<br>
<br>
Print panels must also be fusionned. We don't need 2 items in the button-menu.<br>
<br>
What is "web inspector" ? it is for web developers ? if it is a
configuration, it must go to the "configure rekonq" panel, if it is an
action for developers (like Page source) we must create a submenu
"Develop" (in the button-menu).<br>
<br>
<br>
>Point 2:<br>
>I think it's time to stop dev for rekonq and start processes (bugfixes, <br>
>translations and so on) for rekonq 0.2 release. So, other changes (discussions <br>
>on statusbar vs popus, history and bookmarks menu, rekonqrun and multitask <br>
>rekonq, etc..) will be postponed for 0..3 release.<br>
<br>
Ok.<br>
<br>
<br>
>Point 3:<br>
>I suggested you in my comment to try using a bit better git potential.<br>
>Main idea behind git are "branches". And my git idea is "One feature = One <br>
>branch". You should never use master branch for dev and so on, but just to <br>
>link with others repos. And to maintain a "stable" sw version.<br>
>You can easily merge (when one feature is ready) your branches with your <br>
>master or with mine (performing a merge request).<br>
>So, master is always "safe" and a good starting point for a new idea. <br>
<br>
<div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><meta name="qrichtext" content="1"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><style type="text/css">
p, li { white-space: pre-w
</style>
<p style="margin: 0px; text-indent: 0px;"><!--StartFragment-->Ok, I'll try this afternoon.</p></div></div></div><br>
</body></html>