<div dir="auto">Hi Robin,</div><div dir="auto"><br></div><div dir="auto">I would strongly advise you *against* writing such a proposal without first writing a rationale and overview of the technical approach and its trade offs. Choosing a particular implementation without doing what I suggest will likely be a waste of time. </div><div dir="auto"><br></div><div dir="auto">JF</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 1, 2023 at 5:35 AM Robin Rowe via SG13 &lt;<a href="mailto:sg13@lists.isocpp.org">sg13@lists.isocpp.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Thank you everyone for the feedback! Interesting.<br>
<br>
Herb has advised that my first step should be to write a proposal. I&#39;ve <br>
collaborated with ISO before and understand the process. The proposal I <br>
am planning is different from the past Cairo/PDF-inspired proposal. I am <br>
thinking of proposing to make FLTK the C++ GUI standard. I will ask on <br>
the FLTK list how folks there feel about it.<br>
<br>
To both write a proposal and participate in committee meetings may be <br>
more ambitious than what I can give now. I won&#39;t make it in-person to <br>
the committee meeting in Seattle next week.<br>
<br>
If I will draft the proposal, who would like to team with me to handle <br>
the committee process?<br>
<br>
Best,<br>
<br>
Rob<br>
--<br>
Robin Rowe, CTO<br>
HeroicRobots.com<br>
323-535-0952 (Los Angeles)<br>
Tech blog: <a href="http://goshrobin.com" rel="noreferrer" target="_blank">goshrobin.com</a><br>
<br>
-- <br>
SG13 mailing list<br>
<a href="mailto:SG13@lists.isocpp.org" target="_blank">SG13@lists.isocpp.org</a><br>
<a href="https://lists.isocpp.org/mailman/listinfo.cgi/sg13" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/sg13</a><br>
</blockquote></div></div>

