Re: [PDCurses] Win32a now on Github, with some X11 changes
I've forked Bill's fork so I can get the changes I've made to the X11 port (XCurses) made available. 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 -- * Mark Hessling, m...@rexx.org http://www.rexx.org/ * Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc. * Maintainer of Regina Rexx interpreter * Use Rexx? join the Rexx Language Association: http://www.rexxla.org/
[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] Need with Autotools compilation on X11
On Thu, Jan 14, 2016 at 4:26 PM, LM wrote: > On Wed, Jan 13, 2016 at 5:23 PM, anatoly techtonik > wrote: >> On Tue, Jan 12, 2016 at 3:54 PM, LM wrote: >>> CDetect >> >> Does that thing require installation of new tool? > > No just 3 include files (C files). One could even possibly distribute > them with pdcurses if desired. Correct me if I wrong, but this is a ./configure done in C? And actually I don't understand what "a tool to help you configure projects" really means, because I am not familiar with autoconf (that's why I asked the question in the first place). So I see that C files already have #define mechanism inside, but it looks like C compilers can not agree what #define's to set and what do they mean. That's why users need to create #defines themselves and define the meaning for them. Am I right? Is there any attempt to define standard set for those #define's and their meaning across compilers? Then tools like autoconf are used to detect which #define is correct for specific system and set its value accordingly. Right? This is made by perl script named ./configure. Right? What is the role of cDetect then? Is it a C program that does the job of Perl ./configure? -- anatoly t.
