<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Zhenbo<small>,</small><br>
<br>
On 03/11/14 15:32, Zhenbo Li wrote:<br>
</div>
<blockquote
cite="mid:CAKMejPOSsn8h1ekK94U_Z+=C1z33sn3G7F+Rj8SPa8JBXJzJAg@mail.gmail.com"
type="cite">
<pre wrap="">Thank you very much!
2014-03-11 17:35 GMT+08:00 Jacek Caban <a class="moz-txt-link-rfc2396E" href="mailto:jacek@codeweavers.com"><jacek@codeweavers.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I think that MSHTML may make a good GSoC project. The application will
probably need some more concrete task. We will also need to see that
you're prepared to the task and sending those patches is a good start.
</pre>
</blockquote>
<pre wrap="">If I concentrate on implementing most IHTMLTable* functions, would it be a
good idea?
</pre>
</blockquote>
<br>
Sorry for the delay. I'm not sure that's the best strategy for
having results that will help users in general. Having all functions
implemented is a nice thing, but many of them don't cause problems
in real world application and web pages. I think I would prefer
testing random web pages and implementing things that they need.
This, however, would be tricky to set goals required for GSoC
application. Maybe you could come up with a mix of both? Start with
selected area (say, IHTMLTable*, not necessarily whole) and move to
random APIs required by pages as the project progresses?<br>
<br>
Cheers,<br>
Jacek<br>
</body>
</html>