Content deleted Content added
→Article length: reply to soum, sorry it took so long |
|||
Line 27:
: Another thought, and this is a bit ambitious (even for us!), would be to integrate information about new APIs into articles about those APIs where appropriate. I was thinking about this a few weeks ago, about how it would make a lot of sense to have a bit of text in, for example, [[Desktop Window Manager]] describing the existance of a programmable API for thumbnails. Code samples would be going a bit far, but a summation with the candour of, say, [[Dashboard (software)#Creation of widgets]], would be nice. The programmability of an operating system feature seems like an important aspect to cover! <span style="color:blue;font-weight:bold;font-family: Monotype Corsiva;"> [[User talk:Warrens|-/-]] [[User:Warrens|Warren]]</span> 11:24, 23 March 2007 (UTC)
::Splitting the management features sounds like a good idea. And yes, I totally agree APIs should be given a bit more coverage. And delegating overlapped text (like the .net part you mentioned) to their own article keeping only summary here is necessary for the sake of size. We already have articles on WCF, etc. They should be enhanced. And for the DRM features, I am first inclined to expand the Protected Media Path and Windows Rights Management Services first. if needed, thenafter, a separate DRM article may be created. Also, each subsystem (WCF/WPF/WF as also Media Framework, DirectX, DWM, Sidebar Gadgets etc) should have an API coverage in their own article. I am quite willing to give it a try. And, what about those subsystems which do not have their own article (networking, sound, print etc) - I still support an API article for their sakes. This wont repeat stuff from the dedicated articles. --<span style="background-color: #Fda;">''[[User:Soumyasch|<font color="#ff6633">soum</font>]]'' [[User talk:Soumyasch|(0_o)]]</span> 12:07, 23 March 2007 (UTC)
| |||