| MrSpud_Cyt@em8kceu_4l_721dw4ed0wc.biz: Jul 15 08:24AM On Wed, 14 Jul 2021 19:08:22 -0000 (UTC) >>Maybe some people have, but I get the impression most haven't. >There's no need to. Really, talk about wheel re-invention. Hey, here's an >idea, why not write a new OS? Who needs Linux? Who need z/OS? (etc) The irony of mentioning Linux there. But you probably won't get it :) >trn (and similar, such as "tin") does everything you need, so why not use It doesn't do everything I need. Given writing software to get and post articles on usenet isn't exactly arduous (providing you understand networking) and that it was a fun project to do , why shouldn't I write my own? >it? You'd spend a lot of time, just to get up to the level of >functionality of trn. Why go through the hassle? It wasn't hassle and I like being able to use unix tools to parse the downloaded articles. |
| MrSpud_0zkkxn6jj@uncf5cotva75ujdt.gov: Jul 15 08:27AM On Wed, 14 Jul 2021 20:02:08 -0000 (UTC) >not because there are no X11 Display Managers available, but because I wish to >learn about X11, and I would like a Display Manager that works the way /I/ want >it to work. Good luck with that (genuinely, I'm not being sarcastic). I wrote one about 20 years ago and it was a fun project to do but the problem was that even the venerable O'Reilly XLib manuals didn't provide all the information required as they're more geared towards developing user applications. In the end I had to look through other code to see how stuff was done but even then some things I never got working properly. |
| scott@slp53.sl.home (Scott Lurndal): Jul 15 02:20PM >required as they're more geared towards developing user applications. In the >end I had to look through other code to see how stuff was done but even then >some things I never got working properly. Hm.. All the X11Rx code is open source; it's easy enough to use the source of libX11, libXt, and libXaw as a reference. |
| MrSpud_6wa4@1h0c.net: Jul 15 02:34PM On Thu, 15 Jul 2021 14:20:58 GMT >>some things I never got working properly. >Hm.. All the X11Rx code is open source; it's easy enough to use the >source of libX11, libXt, and libXaw as a reference. The source of another window manager would be a lot more useful IMO as looking at the source of the above won't show you how to use the required APIs without doing some reverse engineering nor will it show you what to use when. |
| Lew Pitcher <lew.pitcher@digitalfreehold.ca>: Jul 15 02:59PM On Thu, 15 Jul 2021 08:27:41 +0000, MrSpud_0zkkxn6jj wrote: > required as they're more geared towards developing user applications. In the > end I had to look through other code to see how stuff was done but even then > some things I never got working properly. Thanks for the best wishes. Yah, I'm about 50 pages into the Xlib manual, and have completed (and played with) the basicwin example. And then, I left the manual alone, except for the reference information. I quickly found that Xlib alone wasn't conducive to effective programming; I need a widget set or toolkit. But, I haven't abandoned Xlib; I'm simply putting together, from scratch, the sort of widgets I need to make things work. I have a rudimentary edit widget, and a toggleswitch widget, and a way of abstracting the event loop into widget/window event handlers, all cobbled together over the last couple of weeks. I intend to build enough of a framework to familiarize myself with the practice and pitfalls of Xlib, before I move on to other toolkits. The project isn't really about building a DM; it's about learning Xlib. If I get a usable DM from it, then "bonus", otherwise I will still have learned something. -- Lew Pitcher "In Skills, We Trust" |
| "Fred. Zwarts" <F.Zwarts@KVI.nl>: Jul 15 09:45AM +0200 Op 04.jul..2021 om 00:04 schreef Real Troll: >> cout << "value of a: " << a << "; address of a: " << ptrA << endl; >> cout << "vaue of b: " << b << "; address of b: " << ptrB << endl; >> cout << "value of c: " << c << "; address of c: " << &ptrC << endl; Doesn't that print the address of ptrC, instead of the address of c? |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment