'Re: Porting to Qt5'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: Porting to Qt5
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2013-04-09 6:29:47
Message-ID: 5163B55B.4060700 () dipe ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On 04/09/2013 03:36 AM, Kevin Krammer wrote:
> On Monday, 2013-04-08, Boudewijn Rempt wrote:
>> On Mon, 8 Apr 2013, Kevin Krammer wrote:
>>> On Monday, 2013-04-08, Boudewijn Rempt wrote:
>>>> * replace kconfig with qsettings
>>> Doesn't that lose all support for OSV and admin default values, immutable
>>> settings, build time generated config access instead of typo-prone string
>>> based access, and so on?
>> None of which are actually used in Calligra, as far as I can tell... But
>> please go back to the rest of the discussion, this point was already
>> discussed with Sebastian. We'll likely make some kind of shim to chose
>> between kconfig or qsettings.
> Sorry, didn't want to bring up something already closed, I am not following
> this list that closely.
> Just saw this in the list and remembered a lengthy discussion on this on the
> frameworks-devel list.

And its important to raise voice and point out anything we may missing. 
So, thanks.

For "immutable not used by Calligra": Actually it is since it comes for 
free :) The trick here is that with KConfig you can build up 
config-chains like having a single specific global setting (that applies 
then to all user-accounts on the system) and user-specific overwrites. 
An administrator can then mark a single config-item in that global 
settings as immutable. Then for that specific config-item the global 
setting will be preferred over the users config whereas all other 
non-immutable config-items can still be overwritten by the user.

Only wrote that as explanation / closer for those interested in that 
topic not as argument for anything.

>
> Cheers,
> Kevin
>
>
>
> _______________________________________________
> calligra-devel mailing list
> calligra-devel@kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 04/09/2013 03:36 AM, Kevin Krammer
      wrote:<br>
    </div>
    <blockquote cite="mid:201304082236.56808.krammer@kde.org"
      type="cite">
      <pre wrap="">On Monday, 2013-04-08, Boudewijn Rempt wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">On Mon, 8 Apr 2013, Kevin Krammer wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">On Monday, 2013-04-08, Boudewijn Rempt wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">* replace kconfig with qsettings
</pre>
          </blockquote>
          <pre wrap="">
Doesn't that lose all support for OSV and admin default values, immutable
settings, build time generated config access instead of typo-prone string
based access, and so on?
</pre>
        </blockquote>
        <pre wrap="">
None of which are actually used in Calligra, as far as I can tell... But
please go back to the rest of the discussion, this point was already
discussed with Sebastian. We'll likely make some kind of shim to chose
between kconfig or qsettings.
</pre>
      </blockquote>
      <pre wrap="">
Sorry, didn't want to bring up something already closed, I am not following 
this list that closely.
Just saw this in the list and remembered a lengthy discussion on this on the 
frameworks-devel list.</pre>
    </blockquote>
    <br>
    And its important to raise voice and point out anything we may
    missing. So, thanks.<br>
    <br>
    For "immutable not used by Calligra": Actually it is since it comes
    for free :) The trick here is that with KConfig you can build up
    config-chains like having a single specific global setting (that
    applies then to all user-accounts on the system) and user-specific
    overwrites. An administrator can then mark a single config-item in
    that global settings as immutable. Then for that specific
    config-item the global setting will be preferred over the users
    config whereas all other non-immutable config-items can still be
    overwritten by the user.<br>
    <br>
    Only wrote that as explanation / closer for those interested in that
    topic not as argument for anything.<br>
    <br>
    <blockquote cite="mid:201304082236.56808.krammer@kde.org"
      type="cite">
      <pre wrap="">

Cheers,
Kevin

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
calligra-devel mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/calligra-devel">https://mail.kde.org/mailman/listinfo/calligra-devel</a>
 </pre>
    </blockquote>
    <br>
  </body>
</html>

_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

[prev in list] [next in list] [prev in thread] [next in thread] 