Re:Design and Implementation of a Win32 Text Editor (2005)
by nacs on Sunday December 04, 2016 @06:30PM
(#13102346)
Has the cutting edge techniques for implementing Notepad changed that much since 2005?
[ Parent
| on HN ]
Re:Design and Implementation of a Win32 Text Editor (2005)
by imron on Sunday December 04, 2016 @09:50PM
(#13103054)
Actually yes!
The Unicode text handling in Windows has been significantly revamped from the APIs listed in these articles, as has the text rendering APIs which now go through DirectX.
Re:Design and Implementation of a Win32 Text Editor (2005)
by batina on Monday December 05, 2016 @04:03AM
(#13104233)
You can still use Uniscribe in Windows 10 but as you said it has been superseded by DirectWrite (used in Microsoft Word, WPF, etc).
Re:Design and Implementation of a Win32 Text Editor (2005)
by imron on Monday December 05, 2016 @04:13AM
(#13104261)
Yep, you can definitely still use it all, just like you can continue to use the even older APIs too - hooray for backwards compatibility.
Just pointing out that the technology for Notepad has actually changed and improved since 2005.
Re:Design and Implementation of a Win32 Text Editor (2005)
by maxerickson on Sunday December 04, 2016 @06:38PM
(#13102377)
It's the house style to add the year to titles from previous years.