Module: wine
Branch: master
Commit: 7f715458350dc2138f33acb921b4c49212011849
URL: http://source.winehq.org/git/wine.git/?a=commit;h=7f715458350dc2138f33acb92…
Author: Rob Shearman <rob(a)codeweavers.com>
Date: Thu Oct 26 12:38:38 2006 +0100
oleaut32: Update comments at the top of typelib.c and remove "stub" from several traces that are in implemented functions.
---
dlls/oleaut32/typelib.c | 12 ++----------
1 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/dlls/oleaut32/typelib.c b/dlls/oleaut32/typelib.c
index 0f8f287..8a7cf52 100644
--- a/dlls/oleaut32/typelib.c
+++ b/dlls/oleaut32/typelib.c
@@ -29,27 +29,19 @@
* - dual interface dispinterfaces. vtable-interface ITypeInfo instances are
* creating by doing a straight copy of the dispinterface instance and just changing
* its typekind. Pointed structures aren't copied - only the address of the pointers.
- * So when you release the dispinterface, you delete the vtable-interface structures
- * as well... fortunately, clean up of structures is not implemented.
*
* - locale stuff is partially implemented but hasn't been tested.
*
* - typelib file is still read in its entirety, but it is released now.
- * - some garbage is read from function names on some very rare occasions.
*
* --------------------------------------------------------------------------------------
* Known problems left from previous implementation (1999, Rein Klazes) :
*
* -. Data structures are straightforward, but slow for look-ups.
* -. (related) nothing is hashed
- * -. there are a number of stubs in ITypeLib and ITypeInfo interfaces. Most
- * of them I don't know yet how to implement them.
* -. Most error return values are just guessed not checked with windows
* behaviour.
- * -. didn't bother with a c++ interface
* -. lousy fatal error handling
- * -. some methods just return pointers to internal data structures, this is
- * partly laziness, partly I want to check how windows does it.
*
*/
@@ -739,7 +731,7 @@ HRESULT WINAPI UnRegisterTypeLib(
ITypeLib* typeLib = NULL;
int numTypes;
- TRACE("(IID: %s): stub\n",debugstr_guid(libid));
+ TRACE("(IID: %s)\n",debugstr_guid(libid));
/* Create the path to the key */
get_typelib_key( libid, wVerMajor, wVerMinor, keyName );
@@ -4542,7 +4534,7 @@ static HRESULT WINAPI ITypeInfo_fnGetTyp
{
ITypeInfoImpl *This = (ITypeInfoImpl *)iface;
- TRACE("(%p)->(%p) stub!\n", This, ppTComp);
+ TRACE("(%p)->(%p)\n", This, ppTComp);
*ppTComp = (ITypeComp *)&This->lpVtblTypeComp;
ITypeComp_AddRef(*ppTComp);
ChangeSet ID: 29294
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/10/26 14:41:04
Modified files:
news : 2006091701.xml 2006100201.xml
Log message:
clean up and validation fixes
Patch: http://cvs.winehq.org/patch.py?id=29294
Old revision New revision Changes Path
1.1 1.2 +7 -5 lostwages/news/2006091701.xml
1.1 1.2 +2 -3 lostwages/news/2006100201.xml
Index: lostwages/news/2006091701.xml
diff -u -p lostwages/news/2006091701.xml:1.1 lostwages/news/2006091701.xml:1.2
--- lostwages/news/2006091701.xml:1.1 26 Oct 2006 19:41: 4 -0000
+++ lostwages/news/2006091701.xml 26 Oct 2006 19:41: 4 -0000
@@ -2,16 +2,18 @@
<date>September 17, 2006</date>
<title>WineConf 2006</title>
<body>
-<p>
-<center>
-<a href="/images/wineconf06_grp.jpg"><img src="/images/wineconf06_grp_thmb.jpg" /></a>
-</center>
+<p align="center">
+<a href="{$root}/images/wineconf06_grp.jpg"><img src="{$root}/images/wineconf06_grp_thmb.jpg" width="145" height="109" alt="WineConf 2006 Group Photo" /></a>
+</p>
+<p>
WineConf 2006 has just about wrapped up. Approximately 35 developers
convened in Reading, England for the event. A summary will follow,
but for now you can check out this year's
-<a href="/images/wineconf06_grp.jpg">group photo</a> (1MB).</p><p>
+<a href="{$root}/images/wineconf06_grp.jpg">group photo</a> (1MB).
+</p>
+<p>
The Wine team would especially like to thank Lars Mathiassen and the members
of the
<a href="http://www.tightpoker.com/">Party Poker Strategy Guide</a> for their
Index: lostwages/news/2006100201.xml
diff -u -p lostwages/news/2006100201.xml:1.1 lostwages/news/2006100201.xml:1.2
--- lostwages/news/2006100201.xml:1.1 26 Oct 2006 19:41: 4 -0000
+++ lostwages/news/2006100201.xml 26 Oct 2006 19:41: 4 -0000
@@ -2,8 +2,7 @@
<date>September 28, 2006</date>
<title>Wine 0.9.22 Released</title>
<body>
-<p>
-Wine 0.9.22 came out last week with these changes:
+<p>Wine 0.9.22 came out last week with these changes:</p>
<ul>
<li> The usual assortment of MSI improvements.</li>
@@ -11,7 +10,7 @@ Wine 0.9.22 came out last week with thes
<li> Pixel shaders enabled by default in D3D.</li>
<li> Various improvements to the build process.</li>
<li> Many translation updates.</li>
-</ul></p>
+</ul>
<p>
Binary packages are in the process of being built and it may take a few days
ChangeSet ID: 29293
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/10/26 14:40:51
Added files:
news : 2006102501.xml
Log message:
Tom Wickline <twickline(a)gmail.com>
News Wine 0.9.23 release
Patch: http://cvs.winehq.org/patch.py?id=29293
Old revision New revision Changes Path
Added 1.1 +0 -0 lostwages/news/2006102501.xml
Index: lostwages/news/2006102501.xml
diff -u -p /dev/null lostwages/news/2006102501.xml:1.1
--- /dev/null 26 Oct 2006 19:40:51 -0000
+++ lostwages/news/2006102501.xml 26 Oct 2006 19:40:51 -0000
@@ -0,0 +1,25 @@
+<news>
+ <date>October 25, 2006</date>
+ <title>Wine 0.9.23 Released</title>
+ <body>
+<p>Wine 0.9.23 came out last week with these changes:</p>
+
+<ul>
+<li> Massive update of printf formats for Win64 compatibility.</li>
+<li> Dynamic drive support on MacOSX.</li>
+<li> Still more MSI fixes and improvements.</li>
+<li> Lots of bug fixes.</li>
+</ul>
+
+<p>
+ Binary packages are in the process of being built and it may take a few days
+ for them to appear, but the source is
+ <a href="http://prdownloads.sourceforge.net/wine/wine-0.9.23.tar.bz2">available
+ now</a>. You can find out more about this release in the
+ <a href="?announce=1.127">announcement</a>. Check out our
+ <a href="/site/download">download page</a> for packages for your favorite
+ distribution.
+</p>
+
+ </body>
+</news>
ChangeSet ID: 29291
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/10/26 14:25:39
Modified files:
templates/en : sending_patches.template
Log message:
Jan Zerebecki <jan.wine(a)zerebecki.de>
sending_patches: Add usual response time and rearrange some sentences.
Patch: http://cvs.winehq.org/patch.py?id=29291
Old revision New revision Changes Path
1.17 1.18 +15 -9 lostwages/templates/en/sending_patches.template
Index: lostwages/templates/en/sending_patches.template
diff -u -p lostwages/templates/en/sending_patches.template:1.17 lostwages/templates/en/sending_patches.template:1.18
--- lostwages/templates/en/sending_patches.template:1.17 26 Oct 2006 19:25:39 -0000
+++ lostwages/templates/en/sending_patches.template 26 Oct 2006 19:25:39 -0000
@@ -11,7 +11,10 @@ chapter in our online documentation.</p>
<a href="mailto:wine-patches@winehq.org">wine-patches(a)winehq.org</a>.
(Note that if you're not <a href="{$root}/site/forums">subscribed</a> to the mailing
list, the mailing list administrators must first check your submission
-to make sure it's not spam before they can let it through.)</p>
+to make sure it's not spam before they can let it through.
+There is no attempt to apply patches that appear in the newsgroup
+or anywhere else to the Git tree.)
+</p>
<p>When submitting patches, please:</p>
<ul>
@@ -51,15 +54,22 @@ to make sure it's not spam before they c
<li> Write a mail to wine-devel, explain your patch and request it be
reviewed by anybody that cares to review it.
+ <li> Ask for advice about your patch on #winehackers.
+
<li> Unless one already exists, open a bug in bugzilla describing the
problem you are trying to solve (eg. ./configure fails on Solaris,
etc) and attach your patch.
-
- <li> Ask for advice about your patch on #winehackers.
</ul>
-<p> You may find it difficult to solicit feedback,
- so think carefully about the comments you receive.
+<p>
+ If your patch didn't receive a response for 3 days of WineHQ Git commits
+ your patch has a high chance of being in this category.
+ <br/>
+ You may find it difficult to solicit feedback,
+ so think carefully about the comments you receive.
+ <br/>
+ Just do not give up!
+</p>
<hr>
@@ -98,8 +108,4 @@ if you have setup the mail headers in th
<p>That should generate a number of txt files, which you can send manually.</p>
-<p>There is no attempt to apply patches that appears in the newsgroup
-to the Git tree. Please send patches to
-<a href="mailto:wine-patches@winehq.org">wine-patches(a)winehq.org</a>.</p>
-
<p> </p>