Re: rfe: seamless windows integration
In response the post below: http://www.cygwin.com/ml/cygwin-xfree/2003-08/msg00187.html I just wanted to say that it's possible to run XWin.exe as a service on Windows NT/2K/2K3 using SRVANY.exe and properly configuring the Xn.hosts file. We ran into a situation with an Oracle Reports service that a customer of ours was using that needed to use the fonts supplied from an XServer running on Windows (using Microsoft TTF fonts). The solution they were using was not a very good one but, nonetheless, we were able to get it working in order to fulfill their needs. Just something to pass along. Thanks, John Peery __ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: rfe: seamless windows integration
On Tue, Aug 05, 2003 at 07:46:43PM -0400, Harold L Hunt II wrote: >2. All X client application on one's machine should have shortcuts >associated with them in the start menu, and these shortcuts should be >created automatically during installation. > >This is icing on the cake. This is the kind of thing that Microsoft >hires 500 college interns to write in the summer because it takes a hell >of a lot of time and attention to detail to get it 'right', whereas the >overall benefit is very small in comparison. > >Furthermore, this requires interacting with the Cygwin setup developers. > You think I am mean? The setup developers aren't all that mean, actually. But, then neither are you. However, I don't see why this would require any setup changes. A postinstall script should be able to set up icons, etc. I can't decide if the thought of a folder filled with scores of icons for X programs is intriguing or frightening, though. cgf
Re: rfe: seamless windows integration
Brian E. Gallew wrote: Christopher Faylor wrote: However, I don't see why this would require any setup changes. A postinstall script should be able to set up icons, etc. I can't decide if the thought of a folder filled with scores of icons for X programs is intriguing or frightening, though. First, create a folder in the Programs section of your Start Menu named "Cygwin-XFree86". Then, the following script will produce working links, BUT it's not what you want. cd /usr/X11R6/bin for d in *.exe do mkshortcut -P --icon=/cygwin.ico \ --arguments="$d -display :0" \ --name=Cygwin-XFree86/$(basename $d .exe) \ --workingdir=$HOME /usr/X11R6/bin/run.exe done This skips any shell scripts, which is (usually) what you want. Unfortunately, there are a lot of programs in that directory which really want a terminal (e.g. xdpyinfo). Further, there are programs in there that don't belong here like this (e.g. Xwin.exe). So, to do this *right*, we'd need a couple things: 1) A canonical hierarchy structure (e.g. Start Menu/Program/Cygwin/XFree86) 2) A script which defines two shortcut functions (or more?), one like the above shortcut for "real" X11 programs, and one which appends "|xterm -e more" to the commands 3) Someone to take the time to carefully pick and choose which kind of shortcut (if any!) gets generated for each application. The up side of this is, if implemented, we could then ask other package maintainers to add an appropriate shortcut for their X-enabled application (e.g. emacs, vim). I wouldn't ask that of the GNOME or KDE port, though, as they already have menu setups that work. Brian, Interesting idea. Probably the easiest thing to do here would be to either create a list of 'term' programs or 'non-term' programs along with a list of excluded programs. Of course, we would want to figure out which list, 'term' or 'non-term', was going to be shortest before deciding which to make. To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply stuff the above lists and a modified version of your script in a new package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. What do you think of that? I think this would work just fine as a sort of confirmation that the user wants start menu icons. We could leave the package out of the XFree86-base dependency list, so only those users that really wanted the icons would end up getting them. Sure, it would be nice to eventually add a setup question, but doing the above first would at least demonstrate to the setup folks that we actually have something completed. Harold
Re: rfe: seamless windows integration
Yes please. Brian E. Gallew wrote: Harold L Hunt II wrote: To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply stuff the above lists and a modified version of your script in a new package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. What do you think of that? Actually, this is probably a really, really easy way to handle it. If you want, I'll take a stab at such a script.
Re: rfe: seamless windows integration
Christopher Faylor wrote: However, I don't see why this would require any setup changes. A postinstall script should be able to set up icons, etc. I can't decide if the thought of a folder filled with scores of icons for X programs is intriguing or frightening, though. First, create a folder in the Programs section of your Start Menu named "Cygwin-XFree86". Then, the following script will produce working links, BUT it's not what you want. cd /usr/X11R6/bin for d in *.exe do mkshortcut -P --icon=/cygwin.ico \ --arguments="$d -display :0" \ --name=Cygwin-XFree86/$(basename $d .exe) \ --workingdir=$HOME /usr/X11R6/bin/run.exe done This skips any shell scripts, which is (usually) what you want. Unfortunately, there are a lot of programs in that directory which really want a terminal (e.g. xdpyinfo). Further, there are programs in there that don't belong here like this (e.g. Xwin.exe). So, to do this *right*, we'd need a couple things: 1) A canonical hierarchy structure (e.g. Start Menu/Program/Cygwin/XFree86) 2) A script which defines two shortcut functions (or more?), one like the above shortcut for "real" X11 programs, and one which appends "|xterm -e more" to the commands 3) Someone to take the time to carefully pick and choose which kind of shortcut (if any!) gets generated for each application. The up side of this is, if implemented, we could then ask other package maintainers to add an appropriate shortcut for their X-enabled application (e.g. emacs, vim). I wouldn't ask that of the GNOME or KDE port, though, as they already have menu setups that work.
Re: rfe: seamless windows integration
Harold, On Wed, 6 Aug 2003, Harold L Hunt II wrote: > Christopher Faylor wrote: > > > On Tue, Aug 05, 2003 at 07:46:43PM -0400, Harold L Hunt II wrote: > > > >>2. All X client application on one's machine should have shortcuts > >>associated with them in the start menu, and these shortcuts should be > >>created automatically during installation. > >> > >>This is icing on the cake. This is the kind of thing that Microsoft > >>hires 500 college interns to write in the summer because it takes a hell > >>of a lot of time and attention to detail to get it 'right', whereas the > >>overall benefit is very small in comparison. > >> > >>Furthermore, this requires interacting with the Cygwin setup developers. > >>You think I am mean? > > > > The setup developers aren't all that mean, actually. But, then neither > > are you. > > Heh heh... Indeed. > > However, I don't see why this would require any setup changes. A > > postinstall script should be able to set up icons, etc. I can't decide > > if the thought of a folder filled with scores of icons for X programs is > > intriguing or frightening, though. CGF is right (on both counts ;-)). The cygwin-doc package already does that, BTW. > I think the thing that would require modification is the part where we > confirm with the user whether or not they want such icons to be created. > It would probably be worse to just create 100 icons without asking > than it would be to not create them at all. > > Harold I believe the suggestion of a "dialog" utility for postinstall script user interaction has floated up on the cygwin-apps list a couple of times. The main problem is propagating the unattended mode of setup onto it, so there must be some setup integration (i.e., you don't want setup to sit there waiting for user input from the desktop when running over ssh on a remote machine). Perhaps setting an environment variable in setup to notify the postinstall scripts that they should use the console, for example? If you're seriously considering the icon creation suggestion, this might be a good time to revive that discussion. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: rfe: seamless windows integration
Harold L Hunt II wrote: Interesting idea. Probably the easiest thing to do here would be to either create a list of 'term' programs or 'non-term' programs along with a list of excluded programs. Of course, we would want to figure out which list, 'term' or 'non-term', was going to be shortest before deciding which to make. To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply stuff the above lists and a modified version of your script in a new package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. I would go a step further. As Brian (and others) have pointed out, the default X install contains a bunch of programs that aren't really "important", e.g., xlogo. Creating a huge list of them in the start menu would indeed be "clutter", and I concede that what I initially suggested (shortcuts for all clients) would be silly. I don't know the functionality of 90% of what's in /usr/X11R6/bin/*.exe, but I'm sure some things are used more widely than others, and some are more and some less appropriate for the start menu. Here's what would be useful, though: if I install a Cygwin-ized Emacs, for example, there should be a shortcut for it in the start menu. Granted, I should be taking this request to Emacs' packagers, but the folks here have unique expertise suited to this task, and perhaps could work with apps' packagers to provide this functionality. It would be a bad idea to install icons for apps that aren't there, though, and so I'm tempted to argue against a XFree86-start-menu-icons-4.3.0-1.tar.bz2. On the other hand, there may be a smart way of writing the scripts for that tarball, such that a particular icon is installed only if the app is actually present. This way Emacs and all the other packages wouldn't have to be altered. The rule of thumb for what's a good application to add to the start menu could be this: if you use it as a GUI, and you can get reasonable mileage out of the app without passing varying parameters on start up, it should have a shortcut. (Filename parameters would be easy exception to pass using the standard windows technique of drag-and-drop to start menu.) -JT
rfe: seamless windows integration
This is a pipe dream, but it's a pipe dream worth striving for. 1. X should run as a service. There's no reason for it to run as a user-launched app. 2. All X client application on one's machine should have shortcuts associated with them in the start menu, and these shortcuts should be created automatically during installation. 3. Exiting X (e.g., by stopping the service) should list all cygwin processes that were launched under X and prompt the user to terminate them. For example, an ssh-agent launched from an xterm should be killed automatically. I know there are ways of approximating these behaviors now; I'm just suggesting that these be built in. -JT
Re: rfe: seamless windows integration (fwd)
On Wed, 6 Aug 2003, Jim Drash wrote: > Sorry, I posted this to the wrong list (a finger-fuddle), > > -- Forwarded message -- > Date: Wed, 6 Aug 2003 11:04:43 -0400 > From: Jim Drash <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: rfe: seamless windows integration > > Maybe I am a little slow but if someone wants a shortcut to the "X" apps > can't they just create a short cut to the "C:\cygwin\use\X11R6\bin" > directory? > > Again, I am into the KISS (Keep It Simple, cause I am Stupid) method for > most things. > > Am I missing something? > > Jim Drash Some programs require parameters (or, at least, DISPLAY to be set). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: rfe: seamless windows integration
Jack Tanner wrote: Harold L Hunt II wrote: Interesting idea. Probably the easiest thing to do here would be to either create a list of 'term' programs or 'non-term' programs along with a list of excluded programs. Of course, we would want to figure out which list, 'term' or 'non-term', was going to be shortest before deciding which to make. To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply stuff the above lists and a modified version of your script in a new package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. I would go a step further. As Brian (and others) have pointed out, the default X install contains a bunch of programs that aren't really "important", e.g., xlogo. Creating a huge list of them in the start menu would indeed be "clutter", and I concede that what I initially suggested (shortcuts for all clients) would be silly. I don't know the functionality of 90% of what's in /usr/X11R6/bin/*.exe, but I'm sure some things are used more widely than others, and some are more and some less appropriate for the start menu. Yes, most of the programs would go in the 'exclude' list. Here's what would be useful, though: if I install a Cygwin-ized Emacs, for example, there should be a shortcut for it in the start menu. Granted, I should be taking this request to Emacs' packagers, but the folks here have unique expertise suited to this task, and perhaps could work with apps' packagers to provide this functionality. It would be a bad idea to install icons for apps that aren't there, though, and so I'm tempted to argue against a XFree86-start-menu-icons-4.3.0-1.tar.bz2. On the other hand, there may be a smart way of writing the scripts for that tarball, such that a particular icon is installed only if the app is actually present. This way Emacs and all the other packages wouldn't have to be altered. I think the package should probably be called 'XFree86-bin-icons', that way it is clear that you are installing icons only for the programs in XFree86-bin. I don't want this package to have to be updated every time someone makes a new package for Cygwin/XFree86 that might need an icon. This was new packages could have their own -icons package if they chose to do so. This also splits the maintenace of the icons to the current maintainers of each Cygwin/XFree86 package, which is very important. The rule of thumb for what's a good application to add to the start menu could be this: if you use it as a GUI, and you can get reasonable mileage out of the app without passing varying parameters on start up, it should have a shortcut. (Filename parameters would be easy exception to pass using the standard windows technique of drag-and-drop to start menu.) Of course. Harold
Re: rfe: seamless windows integration (fwd)
Sorry, I posted this to the wrong list (a finger-fuddle), -- Forwarded message -- Date: Wed, 6 Aug 2003 11:04:43 -0400 From: Jim Drash <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: rfe: seamless windows integration Maybe I am a little slow but if someone wants a shortcut to the "X" apps can't they just create a short cut to the "C:\cygwin\use\X11R6\bin" directory? Again, I am into the KISS (Keep It Simple, cause I am Stupid) method for most things. Am I missing something? Jim Drash
Re: rfe: seamless windows integration
Jack Tanner <[EMAIL PROTECTED]> wrote in <[EMAIL PROTECTED]> in gmane.os.cygwin.xfree on Mon, 04 Aug 2003 22:03:50 -0400: > 1. X should run as a service. There's no reason for it to run as a > user-launched app. Harold's dealt with this one. An X-server on Windows is not a background service. It makes no sense whatsoever to have it running when nobody's logged in. Therefore the StartUp folder is the place for it or in HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Run, if and only if the particular user wants to have it start when he logs in to Windows. > 2. All X client application on one's machine should have shortcuts > associated with them in the start menu, and these shortcuts should be > created automatically during installation. No thanks. a.) If I'm running Cygwin/Xfree86 as a X-terminal to another machine, I don't use local X client programs anyway. b.) If I'm running Cygwin/Xfree86 with a manager like openbox or WindowMaker, they have their own configurable menus for launching programs which are a more appropriate place for this. c.) Even if I'm running local clients and using the "-multiwindow" option, the programs to which I want mouse-click access aren't necessarily the same as the ones you'd want. I certainly don't want to clutter up the start menu with /every/ X client on the system. That would quickly become an unmanageably large menu. > 3. Exiting X (e.g., by stopping the service) should list all cygwin > processes that were launched under X and prompt the user to terminate > them. For example, an ssh-agent launched from an xterm should be killed > automatically. This is entirely the wrong way to go about things. It's the job of your X session manager interacting with the clients on the X desktop to provide this sort of "Shutting down now. Please save files. Okay to exit?" functionality, not of the X server. You can then use the -once switch to make the X server exit cleanly after the last client - i.e. the session manager - exits. It /would/ make sense for the -multiwindow window manager to implement X session-end functionality when the user (Alt-F4/Close) or system (WM_QUERYENDSESSION) requests X server shutdown. But this should /only/ happen in -multiwindow mode. As Harold has pointed out, even without a session manager handling session-end requests, X clients exit when the server closes down. Other things like ssh-agent should shut down only when I tell them too. Just because I'm ending a X session doesn't mean I'm not going to continue using ssh from a Windows-GUI rxvt or console shell. > I know there are ways of approximating these behaviors now; I'm just > suggesting that these be built in. Absolutely not. The X server should be an X server. If you want a session manager, install a session manager. (If you don't have one, write one or convince someone to write one.) That way you get the functionality you want while I can choose not to use up disc/memory/CPU resources on my machine on something I don't want. Try looking up the term "feature bloat" some time. ;-) Regards -- Sam Edge
Re: rfe: seamless windows integration
Christopher Faylor wrote: On Tue, Aug 05, 2003 at 07:46:43PM -0400, Harold L Hunt II wrote: 2. All X client application on one's machine should have shortcuts associated with them in the start menu, and these shortcuts should be created automatically during installation. This is icing on the cake. This is the kind of thing that Microsoft hires 500 college interns to write in the summer because it takes a hell of a lot of time and attention to detail to get it 'right', whereas the overall benefit is very small in comparison. Furthermore, this requires interacting with the Cygwin setup developers. You think I am mean? The setup developers aren't all that mean, actually. But, then neither are you. Heh heh... However, I don't see why this would require any setup changes. A postinstall script should be able to set up icons, etc. I can't decide if the thought of a folder filled with scores of icons for X programs is intriguing or frightening, though. I think the thing that would require modification is the part where we confirm with the user whether or not they want such icons to be created. It would probably be worse to just create 100 icons without asking than it would be to not create them at all. Harold
Re: rfe: seamless windows integration
Jack Tanner wrote: Harold L Hunt II wrote: Thanks. Let me tell you, we already have a laundry list of dream features. We just need people to start working on them. Harold, Thanks. If I wanted to hear you be dismissive and condescending, I could've just gone back and read the list archive. Dismissive and condescending? No, that was not my intention, sorry that you got that impression. I'm not a developer, but I am a user interested in the development of this project, and I'm doing what I can to contribute through testing and reporting bugs. Moreover, I have a fair amount of academic traning in human-computer interaction and user experience engineering, and my suggestions are based on a thought-out analysis. I don't doubt that you have plenty of training. However, have you read your suggestions and talked to some programmers about them? Here, lets take a look. [Yes, now you should be intrepting my remarks as generally pissy, snotty, dismissive, and condescending]. 1. X should run as a service. There's no reason for it to run as a user-launched app. This really doesn't matter and, in fact, is probably incorrect. Cygwin/XFree86 needs to interact with the display (else you could use Xvfb), so running it as a service that won't always have a desktop connected is pointless. Furthermore, a machine shared by multiple users (like a Terminal Services server) will not be able to service all users with a single instance of XFree86 running. Another point is that, I believe, services that interact with the desktop need to run under an actual user account and it would be silly to have XFree86 running under 'bill' when 'steve' is logged in. Besides, this could be done with a simple shortcut in the Startup group in the Start menu. In fact, that should be done and had all of the bugs worked out before anyone talks any further of services. 2. All X client application on one's machine should have shortcuts associated with them in the start menu, and these shortcuts should be created automatically during installation. This is icing on the cake. This is the kind of thing that Microsoft hires 500 college interns to write in the summer because it takes a hell of a lot of time and attention to detail to get it 'right', whereas the overall benefit is very small in comparison. Furthermore, this requires interacting with the Cygwin setup developers. You think I am mean? 3. Exiting X (e.g., by stopping the service) should list all cygwin processes that were launched under X and prompt the user to terminate them. For example, an ssh-agent launched from an xterm should be killed automatically. Huh? Exiting X right now kills all connected clients. There is already an "Are you sure?" warning dialog. Free software is all about bang for the buck; the above feature might be nice, but it only matters to marketroids. Enmity aside, it wouldn't take too long to actually consider and respond to what I suggested, and I would welcome discussion. Yes it would. It took me like 10 minutes to write this reply. I don't have to be party to any and all discussions that take place on this list. I wrote my reply and said my piece. Others were free to jump all over your email and praise it. Furthermore, you got a reply to your message from Earle indicating his interest. So, I don't see why you have to have a beef with me when you appear to already have another supporter with influence. After all of that, my position is exactly as I stated, without malice, in my original email: those suggestions will go on the wish list, below other more fundamental problems like crashes (-clipboard when copying large amouns of text) and startup failures (with -clipboard and -multiwindow). There is still a lot of architectural work that needs to be done before we will start worrying about icing the cake. Harold
Re: rfe: seamless windows integration
Earle,
Can't remember if I replied to this yet. I am in the process of getting
my Inspiron 8500 returned after having it replaced (bought it 3 weeks
ago). Both the original and the replacement randomly freeze. Google
for ["Inspiron 8500" freeze] and you'll see exactly what I mean. I have
been setting up computers for the past two weeks now.
I have finally ordered a Gateway 450X notebook. Hopefully that will
work better and allow me to spend a little more time looking at patches.
In other words, I might look at your patch tomorrow, or I might look at
it next week. Can't say for sure.
In any case, thanks for the patch, I like the idea and am looking
forward to seeing what it does.
Thanks for contributing,
Harold
Earle F. Philhower III wrote:
Howdy Harold,
At 10:36 PM 8/4/2003 -0400, you wrote:
Thanks. Let me tell you, we already have a laundry list of dream
features. We just need people to start working on them.
There sure are a lot of managers and architects around here recently. ;)
In any case, since it's been a couple years since I did any parser work,
I've hacked out a flex/bison parser for a generic extensible xwin.rc
format,
and gotten all the info stuffed into a reasonably simple structure, now
all I need to do is crawl the structure and do CreateMenu()/AddMenuItem()
accordingly and LoadIcon(), and when creating windows compare the class
name to the ones in the prefs structure and possibly replace icon and/or
add to the system menu of that window.
I'm attaching a tar.bz2 below, give it a look-see whoever's interested
in the whole customizable menus thing, and if you want to integrate the
prefs structure parser let me know. The file format's simple and
explained in the input.rc, and has support for pretty much all that
XWin.exe can do now as far as customizations. [ Sure, you could add
an ALPHA {} block that would change the alpha-blend of windows under
Win2K and XP, but I'm not sure how really useful that would be. Maybe
a PaletteWindow style, though, for xload or xcalc... ]
For me the most interesting part was getting back up to speed on lex/yacc,
the implementing in the server is reasonably "plug-n-chug" as my physics
prof used to say.
Harold, if this is something you don't like for XWin just let me know...
-Earle F. Philhower, III
[EMAIL PROTECTED]
cdrlabel - ZipLabel - FlpLabel
http://www.cdrlabel.com
Re: rfe: seamless windows integration
Harold L Hunt II wrote: Thanks. Let me tell you, we already have a laundry list of dream features. We just need people to start working on them. Harold, Thanks. If I wanted to hear you be dismissive and condescending, I could've just gone back and read the list archive. I'm not a developer, but I am a user interested in the development of this project, and I'm doing what I can to contribute through testing and reporting bugs. Moreover, I have a fair amount of academic traning in human-computer interaction and user experience engineering, and my suggestions are based on a thought-out analysis. Enmity aside, it wouldn't take too long to actually consider and respond to what I suggested, and I would welcome discussion. Regards, JT
Re: rfe: seamless windows integration
Jack Tanner wrote: It would be a bad idea to install icons for apps that aren't there, though, and so I'm tempted to argue against a XFree86-start-menu-icons-4.3.0-1.tar.bz2. On the other hand, there may be a smart way of writing the scripts for that tarball, such that a particular icon is installed only if the app is actually present. This way Emacs and all the other packages wouldn't have to be altered. Yes, there's a "good" way to do this. And it will be done that way. Further, I'll write it so that it checks for certain common things that aren't X packages, but still make sense to be there (e.g. emacs). Finally, it'll be hierarchical because flat menu spaces (unlike flat address spaces) are Evil(tm). Oh, yeah, and my intent is to have a copy of the script in Harold's capable hands some time tonight.
Re: rfe: seamless windows integration
Harold L Hunt II wrote: To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply stuff the above lists and a modified version of your script in a new package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. What do you think of that? Actually, this is probably a really, really easy way to handle it. If you want, I'll take a stab at such a script.
Re: rfe: seamless windows integration
Harold L Hunt II <[EMAIL PROTECTED]> wrote in <[EMAIL PROTECTED]> in gmane.os.cygwin.xfree on Wed, 06 Aug 2003 09:41:03 -0400: > To skirt the setup "Create Cygwin/XFree86 icons?" step, we could simply > stuff the above lists and a modified version of your script in a new > package called, for example, XFree86-start-menu-icons-4.3.0-1.tar.bz2. /Much/ better idea. :-D -- Sam Edge
Re: rfe: seamless windows integration
Howdy Harold,
At 10:36 PM 8/4/2003 -0400, you wrote:
Thanks. Let me tell you, we already have a laundry list of dream
features. We just need people to start working on them.
There sure are a lot of managers and architects around here recently. ;)
In any case, since it's been a couple years since I did any parser work,
I've hacked out a flex/bison parser for a generic extensible xwin.rc format,
and gotten all the info stuffed into a reasonably simple structure, now
all I need to do is crawl the structure and do CreateMenu()/AddMenuItem()
accordingly and LoadIcon(), and when creating windows compare the class
name to the ones in the prefs structure and possibly replace icon and/or
add to the system menu of that window.
I'm attaching a tar.bz2 below, give it a look-see whoever's interested
in the whole customizable menus thing, and if you want to integrate the
prefs structure parser let me know. The file format's simple and
explained in the input.rc, and has support for pretty much all that
XWin.exe can do now as far as customizations. [ Sure, you could add
an ALPHA {} block that would change the alpha-blend of windows under
Win2K and XP, but I'm not sure how really useful that would be. Maybe
a PaletteWindow style, though, for xload or xcalc... ]
For me the most interesting part was getting back up to speed on lex/yacc,
the implementing in the server is reasonably "plug-n-chug" as my physics
prof used to say.
Harold, if this is something you don't like for XWin just let me know...
-Earle F. Philhower, III
[EMAIL PROTECTED]
cdrlabel - ZipLabel - FlpLabel
http://www.cdrlabel.com
prefsparser.tar.bz2
Description: Binary data
Re: rfe: seamless windows integration
Jack, Thanks. Let me tell you, we already have a laundry list of dream features. We just need people to start working on them. Harold Jack Tanner wrote: This is a pipe dream, but it's a pipe dream worth striving for. 1. X should run as a service. There's no reason for it to run as a user-launched app. 2. All X client application on one's machine should have shortcuts associated with them in the start menu, and these shortcuts should be created automatically during installation. 3. Exiting X (e.g., by stopping the service) should list all cygwin processes that were launched under X and prompt the user to terminate them. For example, an ssh-agent launched from an xterm should be killed automatically. I know there are ways of approximating these behaviors now; I'm just suggesting that these be built in. -JT
