[PDCurses] Updates to Win32a fork
Hello all, I've made various changes to the Win32a fork of PDCurses at https://github.com/Bill-Gray/PDCurses In the past few days, I've added real blinking to X11 (i.e., "blinking" text really blinks if PDC_set_blink( true) is called, or it's just highlighted if it's not); modified the Win32a mingwin32.mak file to support 64-bit and 32-bit builds; and added a makefile for DOS for the Digital Mars C/C++ compiler. (Which is very useful to me; it's the only way I have left to test out 16-bit builds or DOS builds. Turns out I can fire up a command shell using Wine, compile within it using DMC, then run the DOS executable using DOSBox.) I'm still hoping all this will eventually make it into the "mainstream" version of PDCurses -- I put in a pull request a while back -- but it'll be a lot to merge in, and it may be that some aspects of Win32a remain forever forked. -- Bill
Re: [PDCurses] Win32a now on Github, with some X11 changes
On 01/18/2016 01:31 AM, Mark Hessling wrote: I've forked Bill's fork so I can get the changes I've made to the X11 port (XCurses) made available. Some nice changes here. I've pulled them in to my fork, and it looks as if they are now ready to be merged into the "official" version at https://github.com/wmcbrine/PDCurses . -- Bill The changes are: - support for "proper" bold font. Note that the user CAN select what font they want by adding entries to their ~/.Xresources file - added the ability to build a shared library with ABI versioning - ability to build XCurses from anywhere, not just in the PDCurses/x11 directory. I need this as I often build debug/wide etc versions for testing - targets for building a Debian .deb and RedHat .rpm package - build multiple architectures in a fat binary on MacOS X - made PDC_set_function_key() available on all platforms, and implemented shutdown capability on X11 My fork is at: https://github.com/rexx-org/PDCurses I've created a Pull Request for Bill Cheers, Mark On 18/01/16 01:49, Bill Gray wrote: Hello all, I've forked the version of PDCurses on Github, and folded in the Win32a changes. It's now at https://github.com/Bill-Gray/PDCurses It is somewhat modified from the version on my Web site at http://www.projectpluto.com/win32a.htm in that I've fixed up the X11 flavor of PDCurses to allow most of the things the Win32a fork does: RGB colors, triple mouse clicks, overlined and strikeout and dimmed text, 256 colors and 256 color pairs, and fullwidth characters. The X11 flavor now also recognizes most keys, such as the "back" and "forward" and "refresh" and such special keys on some keyboards. (Almost all my development these days is in Linux, so the X11 flavor has become somewhat important to me.) Ideally, I'd also extend the X11 flavor to have "real" bold and italic fonts, programmatic resizing, "real" blinking text, and the ability for the user to choose a font... no promises that I'll get quite that far, though. I've put in a pull request, so this may eventually end up in "mainstream" PDCurses. (And on a side note, my thanks to Laura for the pointer to CDetect. It looks like a generally useful tool... probably helpful with PDCurses, but definitely useful for some of my own projects. Anatoly, I don't know of any "attempt to define standard set for those #define's and their meaning across compilers", and I could see some real problems in doing so. Which is why I'd think a CDetect that can figure out what headers, functions, etc. are available on a given system ought to be quite useful.) -- Bill
[PDCurses] Win32a now on Github, with some X11 changes
Hello all, I've forked the version of PDCurses on Github, and folded in the Win32a changes. It's now at https://github.com/Bill-Gray/PDCurses It is somewhat modified from the version on my Web site at http://www.projectpluto.com/win32a.htm in that I've fixed up the X11 flavor of PDCurses to allow most of the things the Win32a fork does: RGB colors, triple mouse clicks, overlined and strikeout and dimmed text, 256 colors and 256 color pairs, and fullwidth characters. The X11 flavor now also recognizes most keys, such as the "back" and "forward" and "refresh" and such special keys on some keyboards. (Almost all my development these days is in Linux, so the X11 flavor has become somewhat important to me.) Ideally, I'd also extend the X11 flavor to have "real" bold and italic fonts, programmatic resizing, "real" blinking text, and the ability for the user to choose a font... no promises that I'll get quite that far, though. I've put in a pull request, so this may eventually end up in "mainstream" PDCurses. (And on a side note, my thanks to Laura for the pointer to CDetect. It looks like a generally useful tool... probably helpful with PDCurses, but definitely useful for some of my own projects. Anatoly, I don't know of any "attempt to define standard set for those #define's and their meaning across compilers", and I could see some real problems in doing so. Which is why I'd think a CDetect that can figure out what headers, functions, etc. are available on a given system ought to be quite useful.) -- Bill
Re: [PDCurses] Update to Win32a posted: trying to "re-unify" PDCurses
Hi Anatoly, I've been sidetracked by several other projects. I really should do this, though... it would be relatively easy to put the Win32a changes in to the new hosting at this point, and I should do it before there's much divergence between what I've got and what is on github. (A quick look at the github version tells me that a fair bit of divergence has occurred -- there are a lot of things "reformatted slightly, markdown-style", and the Win32 console flavor has been heavily revised for the "new Win32 console API". Shouldn't be too tough to re-sync, though.) Once we're re-synced, I will probably attempt to extend the X11 version to include full colors, bold/italic text, "real" blinking text and cursor, recognition of all keys, etc... in other words, the improvements Win32a already has. -- Bill On 01/10/2016 10:59 PM, anatoly techtonik wrote: Hi Bill, How it's going? Have you tried submitting pull requests to the new hosting - https://github.com/wmcbrine/PDCurses ? On Sun, May 31, 2015 at 11:37 PM, Bill Gray <pl...@projectpluto.com> wrote: Hello all, I've just posted an update at http://www.projectpluto.com/win32a.htm This has a few bug fixes in it, and adds a makefile for the Intel(R) compiler. But the big change is that I'm trying to get things such that the Win32a changes can be merged back into "mainstream" PDCurses, and at least some of its improvements conveyed to other flavors. (There is, as best I can tell, no real reason for forking here.) Current progress is discussed at http://projectpluto.com/win32a.htm#2015may31 Short version: the Win32 console, DOS, X11, and SDL1 flavors all get at least some benefit from the Win32a changes. I obviously can't support overlined or struck-out text in DOS or Windows console, for example, and there are limits to how far I've gone with the other flavors thus far. However, the road is now paved for full RGB and full Unicode support for X11 and SDL. Note that I couldn't try out OS/2 or FlexOs. -- Bill
[PDCurses] Update to Win32a posted: trying to re-unify PDCurses
Hello all, I've just posted an update at http://www.projectpluto.com/win32a.htm This has a few bug fixes in it, and adds a makefile for the Intel(R) compiler. But the big change is that I'm trying to get things such that the Win32a changes can be merged back into mainstream PDCurses, and at least some of its improvements conveyed to other flavors. (There is, as best I can tell, no real reason for forking here.) Current progress is discussed at http://projectpluto.com/win32a.htm#2015may31 Short version: the Win32 console, DOS, X11, and SDL1 flavors all get at least some benefit from the Win32a changes. I obviously can't support overlined or struck-out text in DOS or Windows console, for example, and there are limits to how far I've gone with the other flavors thus far. However, the road is now paved for full RGB and full Unicode support for X11 and SDL. Note that I couldn't try out OS/2 or FlexOs. -- Bill
[PDCurses] Win32a update posted
Hello all, Mark Hessling provided a fix to a rather serious bug in the Win32a (graphical) flavor of PDCurses. It turns out that the way Win32a stored font and screen size preferences in the Windows registry required administrative privileges in Vista and Win7 (and, at least in some cases, XP). If you weren't an administrator, ran a Win32a app, and changed the font or screen size or menu display, you'd find that the next time you ran that app, all of your settings would be lost. See http://www.projectpluto.com/win32a.htm for the current version. (Which includes a few other small fixes, to SLK handling and to allow 64-bit chtypes on the Win32 console flavor of PDCurses. -- Bill
