<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/108616/">http://git.reviewboard.kde.org/r/108616/</a>
</td>
</tr>
</table>
<br />
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Marble.</div>
<div>By Thibaut Gridel.</div>
<p style="color: grey;"><i>Updated Jan. 27, 2013, 5:36 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Changes</h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">First, let me introduce that the menus at stake in the patch have one checkbox per plugin to toggle the visibility, nothing more fancy.
The patch tries to fix the current approach of hardcoding plugins, which doesn't make nice code.
I uploaded the result of that "Tools" menu and you are absolutely right that this is a mess.
The intent however is to provide a scalable solution for those forgotten plugins and decide if they should be
- Top level entries tools that users can hide/show (crosshairs, current position arrow, annotation)
- "hidden" plugins (and thus not user toggable and not present in menus ever)? (measure tool, elevation plugin specific cross)
- plugins to enable for user choice by theme settings (think different planets: atmosphere, stars, sun)
In the initial description i proposed: "An alternative can be to use more RenderPlugins::renderTypes and separate further ..."
Can we agree this is the way forward and provide enough rendertypes to feed the necessary menus?
On the functionnal side, can we discuss the different values for RenderTypes?</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Builds 3 menu lists with all the render plugins:
- Info boxen
- Online Services
- Tools
More work needed to have atmosphere totally integrated.
An alternative can be to use more RenderPlugins::renderTypes and separate further real tools, {sun/atmosphere/stars}, info boxes, online services</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>src/QtMainWindow.h <span style="color: grey">(bfe9ba7)</span></li>
<li>src/QtMainWindow.cpp <span style="color: grey">(9224240)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/108616/diff/" style="margin-left: 3em;">View Diff</a></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">File Attachments (updated)</h1>
<ul>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/01/27/renderplugins.jpg">Render Plugins</a></li>
</ul>
</td>
</tr>
</table>
</div>
</body>
</html>