<table><tr><td style="">dhaumann added a subscriber: mwolff.<br />dhaumann added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D18894">View Revision</a></tr></table><br /><div><div><p>This approach spreads they key "Word Wrap Column" across many files. You have to know the key and avoid typos. Currently we have this hard-coded and therefore statically checked by the compiler, which is very good.</p>
<p>In grneral, I am not against the string based approach in addition to a statically checked approach. The string based setter then would take a QVariant as value. This way, we would also be close to the KTextEditor::ConfigInterface and could have a KTextEditor::Command 'set', i.e. F7: set word-wrap-column 80.</p>
<p><a href="https://phabricator.kde.org/p/mwolff/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@mwolff</a> Didn't you once propose a template based approach to this?</p>
<p>I have the feeling there are better solutions that perform just as well.</p>
<p>Other comments?</p>
<p>PS: yes, currently we have to write a lot of boilerplate code, but this is simple, the code is fast, and the functions are compile time checked.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R39 KTextEditor</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D18894">https://phabricator.kde.org/D18894</a></div></div><br /><div><strong>To: </strong>loh.tar, cullmann, dhaumann<br /><strong>Cc: </strong>mwolff, kwrite-devel, kde-frameworks-devel, KTextEditor, michaelh, ngraham, bruns, demsking, cullmann, sars, dhaumann<br /></div>