<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - [GTK] Allow to save and restore session"
href="https://bugs.webkit.org/show_bug.cgi?id=115600#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - [GTK] Allow to save and restore session"
href="https://bugs.webkit.org/show_bug.cgi?id=115600">bug 115600</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=115600#c15">comment #15</a>)
<span class="quote">> Well, we normally do it the other way around, we propose a new API and once
> we agree on it in the mailing list we write a patch. Once the patch is
> written, people can comment here about the API or the implementation.</span >
I would post it anyway; I'm pretty sure this API is ideal, but you never know if someone might suggest an improvement.
<span class="quote">> > I almost gave this r- for the messy implementation, since it took me a long
> > time to accept that a GVariant of type
> > (qa(ts(ssssasmaytt(ii)dm(sa(uaysxmxmds))av)u)mu) is really the best way to
> > handle this, rather than using nice C++ iostreams like in your previous
> > patch...</span >
To be clear, this is nuts, but I can't think of any better way to do it, and I really want the API. ;)
<span class="quote">> Yes. I would rather create a watchlist rule to watch patches changing
> SessionState.h :-P</span >
OK, that's fine too.
<span class="quote">> Yep, we should update
> <a href="http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API">http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API</a> to suggest adding
> autoptrs for new public objects/boxed types.</span >
Done.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>