Content deleted Content added
Guy Harris (talk | contribs) →.NET: {{subst:unsigned IP}} a comment. |
|||
| (8 intermediate revisions by 2 users not shown) | |||
Line 27:
"Internet Explorer has been an integrated component of the operating system since Windows 98, and provides web related services to applications [10]. The integration will stop with Windows Vista."
This seems to contradict [http://www.microsoft.com/windowsvista/features/foreveryone/ie7.mspx Microsoft's publications] <!-- Template:Unsigned --><small class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:ItsProgrammable|ItsProgrammable]] ([[User talk:ItsProgrammable#top|talk]] • [[Special:Contributions/ItsProgrammable|contribs]]) 21:45, 25 November 2006 (UTC)</small>
== Windows API not property of Microsoft ==
Line 160:
Suggestion: KISS -- remove the list of categories [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:22, 29 January 2024 (UTC)
:Half measure: Added "notable" so that there is no need to be complete. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:14, 18 October 2024 (UTC)
== communication among different Windows applications ==
The paragraph with "communication among different Windows applications" seems to be about stuff that Windows API is not. Suggest: remove it. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:28, 29 January 2024 (UTC)
:I moved it to the section on related tech. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:13, 18 October 2024 (UTC)
== wrappers ==
Line 171 ⟶ 175:
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.
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.
Suggest: Either remove this section or
:I updated that section (some time ago). No comments on the change or to my comment here. Hope it's OK. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:12, 18 October 2024 (UTC)
== History ==
The history section starts with ''The Windows API has always exposed a large part of the underlying structure of the Windows systems to programmers. This had the advantage of giving them much flexibility and power over their applications, but also creates great responsibility in how applications handle various low-level, sometimes tedious, operations that are associated with a graphical user interface.''
I don't know what do with that, but it's got issues.
* WinAPI exposes functionality; not structure
* WinAPI does not '''force''' developers to handle low-level stuff; it '''allows''' them to do low-level stuff
* How is GUI related to this?
[[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:25, 18 October 2024 (UTC)
:"WinAPI exposes functionality; not [the underlying structure of the Windows systems]" Given that a lot of the Win32 API was implemented in Windows 9x, the structure of which is a bit different from that of Windows NT, it definitely doesn't expose the "underlying structure" of Windows.
:"WinAPI does not '''force''' developers to handle low-level stuff; it '''allows''' them to do low-level stuff" Perhaps what they meant is that if you use ''only'' the Windows API, you have to do the low-level stuff yourself.
:"How is GUI related to this?" Perhaps they're saying that doing the low-level GUI stuff is more work than doing it elsewhere. But a citation for all of that would probably be called for here. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 00:15, 14 November 2024 (UTC)
== How are "Microsoft Windows library files" not shared libraries? ==
The article currently says:
{{blockquote|Programs can access API functionality via [[Shared library|shared-library]] technologies or via [[Microsoft Windows library files|system-file]] access.}}
[[Microsoft Windows library files]] says, right at the top of the page:
{{blockquote|The [[Microsoft Windows]] [[operating system]] and [[Microsoft Windows SDK]] support a collection of [[shared libraries]] that [[software]] can use to access the [[Windows API]]. This article provides an overview of the core libraries that are included with every modern Windows [[Installation (computer programs)|installation]], on top of which most Windows [[Application software|applications]] are built.}}
So the "system-files" (or just "system files - no need for the hyphen, at least in English) are, apparently, shared libraries.
In what way are they ''not'' shared libraries? If they are shared libraries, that statement is redundant. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 05:08, 2 February 2025 (UTC)
:I went ahead and cleaned this up, but next time feel free to clean it up directly. There's no need to open a discussion on such trivial matters. As an aside, thanks for all your contributions on all of these related topics. If you think it needs further refinement, be my guest. <span style="font-family:Verdana">{{u|[[User:Jamarr81|Jamarr81]]}}</span><sup>[[User talk:Jamarr81|🗣]][[Special:Contributions/Jamarr81|⸎]]</sup> 15:37, 20 July 2025 (UTC)
▲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. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:54, 29 January 2024 (UTC)
| |||