741:. See, Windows API has nothing to do with a virtual machine at all and doesn't encapsulate functionality into objects. .NET is on the other hand not mandatory depending on Windows API. Of course it uses native API of the host OS, but that may be an API under Linux or Mac (as soon as .NET supports those systems), too. Furthermore, .NET does not allow to do all you can do with the Windows API, because some of the Windows API functions are (of course) not platform independend and also considered "unsafe". This diskussion shows there is confusion about Windows API and .NET. So in my opinion it would make sense to clearly state how different they are. .NET is no "Windows API Version 2". --
372:
fundamental changes to the input and event models, reorganization of the fledgling
Windows Registry, and the introduction of long file names. These changes had repercussions that required redesign to portions of the API. Some functions (notably many that dealt with window messages) had to be called with different parameters. To ease porting from Win16 to Win32, message-crackers and the Win32s overlay were offered to paper over some of the breaking changes. But most program required some changes to work with the new API.
42:
102:
75:
162:
255:
1024:
withdrawn from the market before satisfactorily implementing the ARM-level language. Turbo C++ became
Borland C++. I owned all three. Watcom and Symantec supplied "memory extenders" which allowed Win32 programs to run on Win16 with Microsoft's redistridutable "win32s" shim DLL. I can't remember why I switched from Borland to Watcom but I think it was because Borland lacked 32-bit support.
33:
198:
582:"However, in general, the interface remained fairly consistent, and an old Windows 1.0 application will still look familiar to a programmer who is used to the modern Windows API." I love how if you look at reference 14, it's a book written in 1998. Yes, clearly modern (2009) programmers will think Windows 1.0 applications look "familiar."
1138:
I saw a place in the software infobox for OS. Currently, I've placed
Windows and OS/2 there as these were the only operating systems that were publicly claiming Windows compatibility. ReactOS, Wine, etc. strive for it, but do not have Microsoft's stamp of approval. OS/2 is debatable as it implemented
770:
I removed the citation needed tag from this section - it *is* generally accepted (I have worked on the leading reimplementation of Win32 for years), although if you wanted the legal precedence for this you would have to dig out the Sega case where it was shown that header files cannot be copyrighted.
678:
I've had a short to do list for a while on my userpage on what I still wanted to do on this article. I haven't had too much time to do it, so I've moved it over to this page, and expanded it a bit. Feel free to add to the list, or make comments if I listed something stupid on it. Also, for reference,
1161:
The overview section currently lists categories of functions in the API, but I have two concerns about that. 1) Does not seem a good purpose for wikipedia to cover all the technical details of an API. Let the
Microsoft docs cover the technical details and let this article cover higher-level concepts
1023:
In my recollection, this is not true. Before Visual Studio came out, there was
Microsoft C/C++, but also Zortech C/C++, Watcom C++ and Turbo C++. Zortech C++ became Symantec C++, was dropped by them, and then bought back by its original author and survives to this day as Digital Mars C++. Watcom was
367:
There is not a distinct "major version" of the
Windows API called Win64. 64-bit editions of Windows implement Win32. It's the same interface. Even the "Getting Ready for 64-bit Windows" article cited to support the notion that there is a Win64 is part of the Win32 documentation set (and it never
724:
Yeah, I'd agree. The "Windows API" to me means the C/C++ and maybe the VB APIs, but .NET is entirely new and is no more "Windows" than Java is. The only parts that are really Win32 specific are S.W.F and some of the low level OS semantics. Maybe that section should just be dropped, or rewritten to
751:
As there is great demand on mentioning .NET in the article, I put a note about .NET into the "Wrapper
Libraries" section. .NET wrapps many of the Windows API functions, like all application frameworks and programming languages under windows do. Maybe (someday) Microsoft will merge the Windows API
375:
For 64-bit systems, the API did not need to change in incompatible ways. The _ABI_ is different (pointer sizes, calling conventions, etc.). Details of the implementations may be different. But the _API_ is the same. The same functions accept the same parameters and return values have the same
395:
The article says that "Both 32-bit and 64-bit versions of an application can be compiled from one codebase, although some older API functions have been deprecated, and some of the API functions that were deprecated in Win32 were removed." The disappearance of deprecated-in-Win32 functions might
371:
The reason Win32 is distinct from Win16 is that the API changed in incompatible ways. For starters, Win16 was the API for an OS that used cooperative multitasking, but Win32 used pre-emptive multitasking, so there were swaths of new functionality (e.g., synchronization objects, virtual memory),
608:
For such a widely used api, this page seems to be a bit barren. I'm going to see how much I can clean it up in a few weeks, because I can see why the cleanup tag was added. I certainly wouldn't mind it if anyone was looking over my shoulder while I do so, since I am rather new to wikipedia
1162:-- mostly what's _not_ covered by Microsoft. 2) There's a note saying the list is out-of-date. What would one update to? the latest version? This article is about _all_ versions; not just the latest. Could list the categories for _each_ version, but that's too hard to do and to get right.
701:
Doesn't the .NET winFX unnecessarily complicate it? Pretty much the only thing they have in common are that they are "an" API and run on "Windows" (and the latter even is not fully decided). "The windows API" is the native one. The .NET api's are different ones, I'd keep that apart.
1203:
Most of the tech listed as wrappers are not what I'd call a wrapper. IMO a wrapper exposes roughly the same capabilities as the wrapped tech -- just in a different form (interface). Just because one tech uses another tech, does not make it a wrapper. Consuming is not wrapping.
927:
959:
These individual API/dll subsections need articles of their own, and should also be organized in part according to implementation (in/outside of kernel, "nt exec", some service, system library, etc). anyone have any ideas for how to do this, or votive to start an article?
774:
More specifically, you cannot legally copyright an interface, only an implementation (which the Sega dispute formalised in case law). Therefore because Win32 is an interface (usually but not always paired with the
Windows implementation) you can reimplement it legally.
620:
win32 move and the introduction of a 64-bit version of the API. Overall though, I've tried to err on the side of too much information, so some of it may need to be trimmed down a bit eventually. Any comments, if anyone is reading this, would be appreciated.
379:
If a
Windows program cannot be compiled for both 32- and 64-bit systems, it's due to a non-portable assumption baked into the code about pointer sizes or ranges of representable values—it's not because of an incompatible difference in the Windows API.
557:
that calls the ExitWindowsEx function. I propose removing it from the list to avoid confusion early on. We could replace it with a function that is more commonly used, as this function is not very commonly used by applications developers anyway.
1019:
The compiler support section says that "For a long time, the
Microsoft Visual Studio family of compilers and tools and Borland's compilers were the only tools that could provide this" (meaning the ability to handle Win32 headers etc.).
641:
I've gone ahead and removed the cleanup tag. I'm not quite finished with this article yet, but I think it has been cleaned up enough to warrant removal of the tag. If anyone disagrees, feel free to put the cleanup tag back up again.
921:
The API is built right into Windows, so if you have Windows, you already got it. But to have compilers you need, you need the headers and associated tools that describe the API to the compiler. This is available as a part of the
1210:
Taking a step back: What is the point of this section? For example, it says MFC uses Windows API. ok. Everything built for Windows uses Windows API. What is interesting about MFC doing that? Goes without saying. Adds no value.
1134:
I've used a screenshot of ReactOS, as a screenshot of Windows would not be acceptable on Wikimedia Commons. ReactOS, the 3 Windows applications, and the novel Frankenstein can all be licensed under the GPL without
944:
explains how to use Windows SDK with VC++ Express 2008. The Windows SDK, however, won't allow you to use MinGW or GCC compilers. Use the MinGW Windows runtime/api for an analogous functionality. --
473:"Internet Explorer has been an integrated component of the operating system since Windows 98, and provides web related services to applications . The integration will stop with Windows Vista."
1257:
986:"History" paragraph : what has Petzold said about 150 lines of code, still needs clarification. At least good that there is explicitly said, that he has told about Windows 1.0 SDK.
897:
according to the article, they are in built in to windows. Just find a compiler that supports them i think. that is normally the case with API's i believe. 12:01, 7 May 2008 (UTC)
1139:
the Windows API up to a certain version. ReactOS could possibly go there, if they explicitly claim to support the Windows API but I think they state something slightly different.
1030:
Towards the end of this era COM appeared and assumed a certain binary vtable layout. At least Zortech tracked this change. I don't accept that COM is part of Win32, by the way.
1207:
Wrapping requires design intent to replace all consumption need for the underlying tech. For example, MFC and ATL are not intended to replace all consumer need for Windows API.
1214:
Suggest: Either remove this section or at least that these other techs are wrappers -- just list them as other Microsoft Windows tech that the reader might want to peruse.
1272:
152:
142:
1079:
The Pascal calling convention was used because it saves on code size. That doesn't mean that the Pascal language was used. This fallacious claim should have a citation.
1292:
1247:
1262:
941:
871:
I think it would be important to include a link or some kind of direction as to where this API's files can be found so people like me can start learning it.
307:
Rework the leader so that it contains only high-level info; focus on the non-programmer reader; move low-level info into suitable sections (after the leader)
118:
730:
Yes, I also agree. I just removed a paragraph about Mono (mentioned as Win API implementation in error). .NET is (like Java or Mono) a platform independent
1282:
1267:
213:
176:
46:
1297:
1242:
1006:
1252:
109:
80:
659:
Hey I tried clarifying a small thing in the introduction for beginners who want to learn the Win32 API but don't quite understand what it is.
1184:
The paragraph with "communication among different Windows applications" seems to be about stuff that Windows API is not. Suggest: remove it.
1037:
494:
1061:
961:
520:
232:. The original page is now a redirect to this page. For the contribution history and old versions of the redirected article, please see
1277:
1086:
447:
This is absolutely not the same. It is much harder to implement and maintain an ABI. In case you want to run already compiled programs,
1115:
882:
589:
343:
link "Windows API Code Pack for Microsoft .NET Framework is a .Net wrapper library for Windows API." no longer exists as of 2/10/2016
709:
1287:
1237:
171:
85:
912:
778:
Again I am not sure what you could cite to prove this in the case of Win32 specifically. It's just how copyright law works.
55:
320:
add a short section on the anatomy of an average Windows API application, just going through the basic concepts, like:
735:
1057:
1002:
794:
I don't think IMimeMessage should be merged here; instead, I think the IMimeMessage article should be deleted. --
1027:
I think you'll find the Zortech compiler was the first usable C++ on Win32/Win16, before even Microsoft had one.
490:
209:
1041:
965:
524:
1130:
I've added an infobox. I realize there are 2 things that may seem odd about it, so I thought I would explain:
1065:
1090:
998:
934:
886:
756:
into .NET someday, if mankind persists on earth long enough. No need to diskuss that in this article. ;) --
396:
constitute an API change, although a citation for the claim that some APIs were removed should be provided.
713:
1219:
1189:
1170:
1111:
593:
486:
855:
757:
660:
738:
385:
61:
1056:
The person that added the stuff about the NSA being able to 'access our computers' should really read:
742:
875:
Where do I get the file(s) for Windows API? Is it a secret? No web site I can find seems to know....
477:
1103:
1082:
1033:
994:
900:
878:
813:
705:
680:
585:
516:
482:
401:
259:
781:
32:
822:
That's not a bug. The colon after the title, before the reference, is the delineation between the
381:
117:
on Knowledge. If you would like to participate, please visit the project page, where you can join
908:
570:
The history section here does not make much sense grammatically and needs expansion and cleanup.
559:
429:
619:
I completely rewrote the history section. I still have to add a paragraph on the big win16-: -->
509:"Windows API is basically considered not the property of Microsoft as is its implementation."
1215:
1185:
1166:
1107:
832:
539:
225:
114:
1147:
456:
428:
programs. The same API can be maintained over multiple instruction sets, e.g. x86, ARM and
731:
688:
643:
633:
622:
610:
448:
441:
397:
310:
In the history section, describe/expand on transition from win16 to win32 and then win64
945:
1231:
904:
795:
684:
930:
835:
101:
74:
1143:
1058:
http://www.dailykos.com/story/2013/06/15/1216509/-The-MSFT-NSA-conspiracy-theory
923:
452:
263:
229:
17:
161:
753:
752:
into .NET, but that's not relevant today. Maybe Microsoft also will merge the
632:
If nobody objects, I'm going to remove the cleanup tag in a couple of days. --
938:
571:
333:
is in the context of the WinAPI (everything from desktop windows to buttons)
808:
982:
When did it appear, in 1985, together with the first Windows release ?
1223:
1193:
1174:
1151:
1119:
1094:
1069:
1045:
969:
948:
890:
858:
839:
816:
798:
784:
760:
745:
717:
691:
663:
646:
636:
625:
613:
597:
528:
498:
460:
405:
389:
851:
554:
304:
Check the compiler support section for accuracy and add references
440:
programs. It is not possible to have the same ABI over different
420:
I serves source code portability, it results in being able to
245:
192:
26:
340:-- should not get to function name level like it was before
160:
323:
message based system with callback functions and everything
830:
tags. I've moved the colons so that it looks a bit better.
301:
Describe the relationship of Windows API to .net and WinFX
850:
If so, shouldn't this be mentioned in the article, since
436:
I server binary portability, it results in being able to
1100:
I'll bet Raymond Chen knows whether it is true. -steve
1075:
Note #3 claims that Pascal was used to implement Windows
287:
281:
275:
269:
237:
233:
204:
804:
See bug 9660 - this article shows a bug in Mediawiki
113:, a collaborative effort to improve the coverage of
1180:communication among different Windows applications
1165:Suggestion: KISS -- remove the list of categories
809:http://bugzilla.wikimedia.org/show_bug.cgi?id=9660
1258:Knowledge level-5 vital articles in Technology
326:object-oriented inspired window classes system
8:
681:User talk:Codemonkey#WinAPI_compiler_support
451:or some Video game, you care about the ABI.
679:I got this reply on my userpage todo list:
1101:
1080:
990:Alexander Ilyin 20:16, 4 July 2010 (UTC)
703:
514:
480:
69:
1273:Top-importance Microsoft Windows articles
127:Knowledge:WikiProject Microsoft Windows
71:
30:
1293:WikiProject Microsoft Windows articles
1248:Knowledge vital articles in Technology
130:Template:WikiProject Microsoft Windows
505:Windows API not property of Microsoft
7:
1263:B-Class vital articles in Technology
107:This article is within the scope of
60:It is of interest to the following
1283:High-importance Computing articles
1268:B-Class Microsoft Windows articles
25:
1298:Knowledge pages with to-do lists
1243:Knowledge level-5 vital articles
253:
196:
100:
73:
40:
31:
980:Per whole article, no one date.
725:point to the main .net article?
363:There is no such thing as Win64
147:This article has been rated as
1253:B-Class level-5 vital articles
1052:The MSFT-NSA conspiracy theory
976:No any date per whole article.
868:I am a beginner learning C++.
553:This "function" is actually a
1:
1046:07:54, 7 September 2011 (UTC)
970:06:17, 18 February 2010 (UTC)
929:). You can use that with the
891:23:49, 27 December 2007 (UTC)
799:16:45, 21 November 2006 (UTC)
785:11:13, 4 September 2006 (UTC)
647:17:20, 4 September 2005 (UTC)
499:21:45, 25 November 2006 (UTC)
469:Internet Explorer Integration
461:12:02, 27 February 2014 (UTC)
169:This article is supported by
121:and see a list of open tasks.
110:WikiProject Microsoft Windows
1224:11:54, 29 January 2024 (UTC)
1194:11:28, 29 January 2024 (UTC)
1175:11:22, 29 January 2024 (UTC)
1120:11:56, 29 January 2024 (UTC)
937:IDE (including VC++ Express
859:16:28, 10 October 2007 (UTC)
1152:05:45, 5 January 2023 (UTC)
972:not an ip -- not signed in
846:Is Win32 still a trademark?
761:09:10, 10 August 2006 (UTC)
692:20:15, 8 October 2005 (UTC)
664:04:09, 28 August 2007 (UTC)
637:18:43, 29 August 2005 (UTC)
626:16:42, 27 August 2005 (UTC)
614:09:49, 19 August 2005 (UTC)
1314:
1278:B-Class Computing articles
840:07:10, 22 April 2007 (UTC)
817:06:52, 22 April 2007 (UTC)
746:21:10, 8 August 2006 (UTC)
718:20:30, 25 April 2006 (UTC)
406:22:21, 13 April 2024 (UTC)
390:14:58, 13 April 2024 (UTC)
153:project's importance scale
133:Microsoft Windows articles
1095:18:44, 20 June 2015 (UTC)
1070:14:02, 14 July 2013 (UTC)
864:Where can we download it?
598:20:33, 29 July 2009 (UTC)
574:06:41, 28 Apr 2005 (UTC)
562:22:07, 29 Jan 2005 (UTC)
476:This seems to contradict
236:; for its talk page, see
168:
146:
95:
68:
1015:Compiler support section
478:Microsoft's publications
438:execute already compiled
949:12:29, 7 May 2008 (UTC)
935:Microsoft Visual Studio
542:01:43 26 May 2003 (UTC)
529:12:47, 8 May 2003 (UTC)
1288:All Computing articles
1238:B-Class vital articles
933:line of compilers and
854:redirects here? -andy
165:
766:Other implementations
739:application framework
513:What does this mean?
172:WikiProject Computing
164:
47:level-5 vital article
224:. Its contents were
220:with a consensus to
1157:Function categories
999:Cantregistermynick
790:IMimeMessage merge
430:Power Architecture
412:API or rather ABI?
293:Updated 2024-01-30
208:was nominated for
166:
56:content assessment
1122:
1106:comment added by
1097:
1085:comment added by
1036:comment added by
1011:
997:comment added by
916:
903:comment added by
893:
881:comment added by
720:
708:comment added by
588:comment added by
531:
519:comment added by
501:
485:comment added by
360:
359:
244:
243:
191:
190:
187:
186:
183:
182:
124:Microsoft Windows
115:Microsoft Windows
81:Microsoft Windows
16:(Redirected from
1305:
1048:
1010:
991:
898:
876:
838:
829:
825:
600:
442:Instruction sets
294:
257:
256:
246:
218:01 December 2013
200:
199:
193:
135:
134:
131:
128:
125:
104:
97:
96:
91:
88:
77:
70:
53:
44:
43:
36:
35:
27:
21:
18:Talk:Windows.pas
1313:
1312:
1308:
1307:
1306:
1304:
1303:
1302:
1228:
1227:
1201:
1182:
1159:
1128:
1077:
1054:
1038:118.209.147.103
1031:
1017:
992:
978:
957:
866:
848:
831:
827:
823:
814:Ta bu shi da yu
806:
792:
768:
736:object-oriented
732:virtual machine
699:
676:
606:
583:
580:
568:
551:
538:Better now? --
507:
487:ItsProgrammable
471:
449:Adobe Photoshop
414:
368:says "Win64").
365:
356:
355:
329:exactly what a
268:
254:
197:
177:High-importance
132:
129:
126:
123:
122:
89:
83:
54:on Knowledge's
51:
41:
23:
22:
15:
12:
11:
5:
1311:
1309:
1301:
1300:
1295:
1290:
1285:
1280:
1275:
1270:
1265:
1260:
1255:
1250:
1245:
1240:
1230:
1229:
1200:
1197:
1181:
1178:
1158:
1155:
1141:
1140:
1136:
1127:
1124:
1076:
1073:
1062:212.121.112.33
1053:
1050:
1016:
1013:
987:
985:
983:
981:
977:
974:
962:68.110.212.162
956:
953:
952:
951:
942:This blog post
918:
917:
874:
865:
862:
856:194.138.39.140
847:
844:
843:
842:
805:
802:
791:
788:
767:
764:
758:213.169.107.51
749:
748:
727:
726:
698:
695:
675:
672:
671:
670:
669:
668:
667:
666:
661:198.82.127.155
652:
651:
650:
649:
629:
628:
605:
602:
579:
578:Opinion, much?
576:
567:
564:
550:
547:
546:
545:
544:
543:
533:
532:
521:217.158.203.79
506:
503:
470:
467:
465:
413:
410:
409:
408:
364:
361:
358:
357:
349:
348:
347:
346:
345:
344:
334:
327:
324:
312:
311:
308:
305:
302:
296:
251:
249:
242:
241:
216:was closed on
214:The discussion
201:
189:
188:
185:
184:
181:
180:
167:
157:
156:
149:Top-importance
145:
139:
138:
136:
119:the discussion
105:
93:
92:
90:Top‑importance
78:
66:
65:
59:
37:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1310:
1299:
1296:
1294:
1291:
1289:
1286:
1284:
1281:
1279:
1276:
1274:
1271:
1269:
1266:
1264:
1261:
1259:
1256:
1254:
1251:
1249:
1246:
1244:
1241:
1239:
1236:
1235:
1233:
1226:
1225:
1221:
1217:
1212:
1208:
1205:
1198:
1196:
1195:
1191:
1187:
1179:
1177:
1176:
1172:
1168:
1163:
1156:
1154:
1153:
1149:
1145:
1137:
1133:
1132:
1131:
1125:
1123:
1121:
1117:
1113:
1109:
1105:
1098:
1096:
1092:
1088:
1087:50.159.105.93
1084:
1074:
1072:
1071:
1067:
1063:
1059:
1051:
1049:
1047:
1043:
1039:
1035:
1028:
1025:
1021:
1014:
1012:
1008:
1004:
1000:
996:
988:
975:
973:
971:
967:
963:
954:
950:
947:
943:
939:
936:
932:
928:
925:
920:
919:
914:
910:
906:
902:
896:
895:
894:
892:
888:
884:
880:
872:
869:
863:
861:
860:
857:
853:
845:
841:
837:
834:
821:
820:
819:
818:
815:
811:
810:
803:
801:
800:
797:
789:
787:
786:
783:
779:
776:
772:
765:
763:
762:
759:
755:
747:
744:
740:
737:
733:
729:
728:
723:
722:
721:
719:
715:
711:
707:
696:
694:
693:
690:
686:
685:User:tyomitch
682:
673:
665:
662:
658:
657:
656:
655:
654:
653:
648:
645:
640:
639:
638:
635:
631:
630:
627:
624:
618:
617:
616:
615:
612:
609:writing :).--
603:
601:
599:
595:
591:
587:
577:
575:
573:
565:
563:
561:
556:
548:
541:
537:
536:
535:
534:
530:
526:
522:
518:
512:
511:
510:
504:
502:
500:
496:
492:
488:
484:
479:
474:
468:
466:
463:
462:
458:
454:
450:
445:
443:
439:
435:
431:
427:
423:
419:
411:
407:
403:
399:
394:
393:
392:
391:
387:
383:
377:
373:
369:
362:
354:
353:
350:
342:
341:
339:
335:
332:
328:
325:
322:
321:
319:
318:
316:
315:
309:
306:
303:
300:
299:
298:
295:
292:
289:
286:
283:
280:
277:
274:
271:
267:
265:
261:
250:
248:
247:
239:
235:
231:
227:
223:
219:
215:
211:
207:
206:
202:
195:
194:
178:
175:(assessed as
174:
173:
163:
159:
158:
154:
150:
144:
141:
140:
137:
120:
116:
112:
111:
106:
103:
99:
98:
94:
87:
82:
79:
76:
72:
67:
63:
57:
49:
48:
38:
34:
29:
28:
19:
1216:Stevebroshar
1213:
1209:
1206:
1202:
1186:Stevebroshar
1183:
1167:Stevebroshar
1164:
1160:
1142:
1129:
1108:Stevebroshar
1102:— Preceding
1099:
1081:— Preceding
1078:
1055:
1032:— Preceding
1029:
1026:
1022:
1018:
989:
979:
958:
955:API articles
883:71.37.65.160
873:
870:
867:
849:
812:
807:
793:
780:
777:
773:
769:
750:
743:82.83.68.136
704:— Preceding
700:
677:
607:
590:173.9.45.237
581:
569:
552:
540:Tim Starling
515:— Preceding
508:
481:— Preceding
475:
472:
464:
446:
437:
433:
426:then execute
425:
421:
417:
415:
378:
374:
370:
366:
352:
351:
337:
330:
317:
314:
313:
297:
290:
284:
278:
272:
258:
252:
221:
217:
203:
170:
148:
108:
62:WikiProjects
45:
993:—Preceding
984:1981-1983Â ?
924:Windows SDK
899:—Preceding
877:—Preceding
828:<dt: -->
824:<dd: -->
710:84.35.41.43
584:—Preceding
549:ExitWindows
264:Windows API
234:its history
230:Windows API
205:Windows.pas
1232:Categories
931:Visual C++
754:Native API
689:Codemonkey
644:Codemonkey
634:Codemonkey
623:Codemonkey
611:Codemonkey
398:Guy Harris
260:To-do list
782:MikeHearn
604:clean up?
376:meaning.
86:Computing
50:is rated
1199:wrappers
1116:contribs
1104:unsigned
1083:unsigned
1034:unsigned
1007:contribs
995:unsigned
913:contribs
905:Oxinabox
901:unsigned
879:unsigned
796:Mikeblas
706:unsigned
683:, from
586:unsigned
517:unsigned
495:contribs
483:unsigned
382:Aidtopia
336:keep is
210:deletion
1126:Infobox
566:History
422:compile
288:refresh
276:history
151:on the
52:B-class
1144:Rjjiii
1135:issue.
836:Warren
560:SteveS
453:ScotXW
432:. An A
331:window
226:merged
58:scale.
852:Win32
674:To do
555:macro
338:short
282:watch
228:into
222:merge
39:This
1220:talk
1190:talk
1171:talk
1148:talk
1112:talk
1091:talk
1066:talk
1042:talk
1003:talk
966:talk
946:soum
909:talk
887:talk
826:and
734:and
714:talk
697:.NET
687:. --
594:talk
572:Dsav
525:talk
491:talk
457:talk
416:An A
402:talk
386:talk
270:edit
262:for
238:here
940:).
833:-/-
212:.
143:Top
1234::
1222:)
1192:)
1173:)
1150:)
1118:)
1114:•
1093:)
1068:)
1060:--
1044:)
1009:)
1005:•
968:)
926:(
915:)
911:•
889:)
716:)
642:--
621:--
596:)
527:)
497:)
493:•
459:)
444:!
424:,
404:)
388:)
179:).
84::
1218:(
1188:(
1169:(
1146:(
1110:(
1089:(
1064:(
1040:(
1001:(
964:(
907:(
885:(
712:(
592:(
523:(
489:(
455:(
434:B
418:P
400:(
384:(
291:·
285:·
279:·
273:·
266::
240:.
155:.
64::
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
