From whistler at blinksoft.com Sun Aug 26 06:51:40 2007 From: whistler at blinksoft.com (Ken Perry) Date: Sat, 25 Aug 2007 23:51:40 -0700 Subject: [graphic-forms-devel] Getting Started Message-ID: <005401c7e7ad$8f127b20$6601a8c0@Aiden> I have downloaded the latest Graphic-forms. I have clisp on cygwin. When I try running the any of the three lisp files in graphic-forms directory (tests.lisp, config.lisp, or build.lisp) I get errors. Most of the errors show that a file doesn't exist in a certain directory. I think I have recreated the directory correctly but I am new to lisp so I am not sure if there is something I am just not doing right. Where should I have unzipped the graphic-forms directory so that the examples work. Are these even examples or should I be trying to run something else? Should I be using the clisp in Cygwin or is there a version of clisp that runs at the XP dos cmd.exe that I can download. Thanks for any help. Ken From whistler at blinksoft.com Sun Aug 26 07:18:52 2007 From: whistler at blinksoft.com (Ken Perry) Date: Sun, 26 Aug 2007 00:18:52 -0700 Subject: [graphic-forms-devel] Getting started Message-ID: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> Ok I think I fixed the path problem but I just realized I don't have the required dependent libraries. I tried to download the ones in the readme but the links didn't work. Is there a new set of links for that or do I need to hunt them down on the web. Ken From jdunrue at gmail.com Sun Aug 26 16:20:48 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Sun, 26 Aug 2007 10:20:48 -0600 Subject: [graphic-forms-devel] Getting started In-Reply-To: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> References: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> Message-ID: On 8/26/07, Ken Perry wrote: > > Ok I think I fixed the path problem but I just realized I don't have the > required dependent libraries. I tried to download the ones in the readme > but the links didn't work. Is there a new set of links for that or do I > need to hunt them down on the web. The links for CFFI, Closer to MOP, and lw-compat mentioned in the readme are all still valid. But the latter two projects do need you to use darcs to pull the repositories in order to get the source. As for CFFI, there is a link off the main project web page for downloading tarballs, and you'll want the most recent. The main darcs.net project page seems to be out of commission at the moment, but you can download a Windows binary from here: http://glozer.net/darcs/darcs-1.0.8-win32.zip BTW, in your earlier email, you mentioned build.lisp as one of the files that you tried to load. That may be a leftover from older releases; I got rid of it in the 0.6.0 release since the details of loading Graphic-Forms are going to vary on each person's machine. But it sounds like you have got that figured out now; just thought I'd clarify. -- Jack Unrue From jdunrue at gmail.com Sun Aug 26 16:23:05 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Sun, 26 Aug 2007 10:23:05 -0600 Subject: [graphic-forms-devel] Getting started In-Reply-To: References: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> Message-ID: I wrote: > > The main darcs.net project page seems to be out of commission at the > moment, but you can download a Windows binary from here: > > http://glozer.net/darcs/darcs-1.0.8-win32.zip Ah, the Internet. Don't you just love it? Apparently that person has put a newer version up. So try this instead (I just checked it): http://glozer.net/darcs/darcs-1.0.9-win32.zip -- Jack Unrue From jdunrue at gmail.com Sun Aug 26 17:59:08 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Sun, 26 Aug 2007 11:59:08 -0600 Subject: [graphic-forms-devel] Getting started In-Reply-To: <001801c7e7ff$7bfb4510$6601a8c0@Aiden> References: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> <001801c7e7ff$7bfb4510$6601a8c0@Aiden> Message-ID: On 8/26/07, Ken Perry wrote: > > Ok thanks I will go make sure I have the latest release. I downloaded it as > a zip from some page but I think I will just attach to the subversion and > make sure I am up to date. After that I will try that link you just sent > out in your second mail and hopefully get this working. Do you think this > will work with UFAsoft's version of lisp in the future. I only ask because > the lispworks IDE is not accessible to blind coders currently and that > leaves me out. I don't have any plans to support UFAsoft. The immediate problem is that the libraries that I need for Graphic-Forms, especially CFFI and Closer to MOP, don't support it. But also, in the past there has been some question about UFAsoft's use of CLISP as part of a proprietary product without also following the terms of the GPL (under which CLISP is licensed). So I feel little motivation to pursue a port to UFAsoft at this time. Have you tried the Allegro CL evaluation? Perhaps their IDE has better accessibility support. Speaking of which, accessibility support in Graphic-Forms is yet another item on the future todo list. If you have some knowledge of the APIs and would ever like to contribute patches, I'd be happy to review and apply them. > Also am I right to be using the clisp that comes with Cygwin or should I get > another version of it to just compile at the XP command prompt. The Cygwin version should be OK, but note that I don't test with it. I use the MinGW version, and I'm currently running version 2.41. -- Jack Unrue From jdunrue at gmail.com Sun Aug 26 21:27:48 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Sun, 26 Aug 2007 15:27:48 -0600 Subject: [graphic-forms-devel] Getting started In-Reply-To: <002001c7e813$03595fc0$6601a8c0@Aiden> References: <005501c7e7b1$5bfccbb0$6601a8c0@Aiden> <001801c7e7ff$7bfb4510$6601a8c0@Aiden> <002001c7e813$03595fc0$6601a8c0@Aiden> Message-ID: On 8/26/07, Ken Perry wrote: > > Anyway if I ever get this mess to work and figure out > lisp I will be more than willing to help. I figured I code in everything > else so why not lisp. I haven't messed with it since college and that was > in Unix. In case you didn't know, Practical Common Lisp was recently released in its entirety in PDF format by Apress. http://www.apress.com/free/content/practicalcommonlisp.pdf It's a really good book that I highly recommend if you don't already have it. -- Jack Unrue From whistler at blinksoft.com Mon Aug 27 07:38:16 2007 From: whistler at blinksoft.com (Ken Perry) Date: Mon, 27 Aug 2007 00:38:16 -0700 Subject: [graphic-forms-devel] Still have problems Message-ID: <000401c7e87d$3c544460$6601a8c0@Aiden> Ok I have all the packages but it still says it can't find asdf. I am betting that I have to do something other than just the darcs. How do I go about loading the asdf library? Ken From jdunrue at gmail.com Tue Aug 28 02:50:45 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Mon, 27 Aug 2007 20:50:45 -0600 Subject: [graphic-forms-devel] Still have problems In-Reply-To: <000401c7e87d$3c544460$6601a8c0@Aiden> References: <000401c7e87d$3c544460$6601a8c0@Aiden> Message-ID: On 8/27/07, Ken Perry wrote: > > Ok I have all the packages but it still says it can't find asdf. I am > betting that I have to do something other than just the darcs. How > do I go about loading the asdf library? Ken, It depends on the CL implementation, but for CLISP it is a matter of loading the asdf.lisp source file. For example: (load "c:/path/to/asdf.lisp") I'm not sure why the direct path to the file in CVS is failing, but in lieu of that, you'll need to check out the cclan project from CVS and then load asdf.lisp from there. http://sourceforge.net/projects/cclan is the main project page, and which has instructions for using CVS to check out a local working directory, inside of which you'll find asdf.lisp. Many people, including myself, put the above load command in the init file that is read when Lisp starts up. For CLISP, you can create a file called .clisprc.lisp in the default location returned by the USER-HOMEDIR-PATHNAME function, which is probably something similar to c:\Documents and Settings\username on your Windows machine. Or you can name the file anything you want and place it anywhere you want, and use the -i command-line option when you start CLISP. The command-line interface is documented here: http://www.podval.org/~sds/clisp/impnotes/clisp.html There is a mailing list for CLISP that you can subscribe to here: https://lists.sourceforge.net/lists/listinfo/clisp-list >From your other email, the REPL is the read-eval-print-loop which is the basic interface for interacting with the Lisp system. Every Lisp implementation offers a REPL, but you can also use other interfaces, such as SLIME. That's an Emacs-based interface that you'll want to investigate sometime in the near future. You mentioned downloading ImageMagick-6.3.5-6-Q8-windows-dll.exe but I think you want ImageMagick-6.3.5-6-Q16-windows-dll.exe instead. The difference is the latter is the Q16 version rather than the Q8 version. I haven't tested with this newer revision of ImageMagick and can't guarantee it will work, so please send bug reports if you run into problems. Finally, I should mention that you're tackling a lot all at once, given that you're a relative newcomer to Common Lisp. Many projects, and admittedly mine is one of them, assume a certain amount of experience with the language. It's not ideal, but that's the situation today, and hopefully the approachability of project's like mine will get better with time. Good luck! -- Jack Unrue From kperry at blinksoft.com Tue Aug 28 05:45:36 2007 From: kperry at blinksoft.com (Ken Perry) Date: Mon, 27 Aug 2007 22:45:36 -0700 Subject: [graphic-forms-devel] Up and running Message-ID: <004001c7e936$a95da1a0$6601a8c0@Aiden> Ok I have all the libraries loaded. I also ran config.lisp and it ran fine. I then set the variables I think I set them right since I already have the libraries loaded the readme said to set them to nill so I did something like (setq gfsys::*cffidir* "") (setq gfsys::*gfdir* "c:/graphic-forms") Etc... Then when I ran (gfsys::configure-asdf) I got nill is that correct? I assumed it was so I did the next thing which was (asdf:operate 'asdf:load-op :graphic-forms-uitoolkit) And got this: (asdf:operate 'asdf:load-op :graphic-forms-uitoolkit) ; loading system definition from C:graphic-forms-uitoolkit.asd into # ;; Loading file C:graphic-forms-uitoolkit.asd ... "Graphic-Forms UI Toolkit" "Copyright (c) 2006-2007 by Jack D. Unrue" " " ; registering # as GRAPHIC-FORMS-UITO OLKIT WARNING: The generic function # is being modified, but has already been called. ;; Loaded file C:graphic-forms-uitoolkit.asd *** - component "binary-data" not found, required by # Did I do something wrong? Ken From jdunrue at gmail.com Wed Aug 29 02:26:17 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Tue, 28 Aug 2007 20:26:17 -0600 Subject: [graphic-forms-devel] Up and running In-Reply-To: <004001c7e936$a95da1a0$6601a8c0@Aiden> References: <004001c7e936$a95da1a0$6601a8c0@Aiden> Message-ID: On 8/27/07, Ken Perry wrote: > > ;; Loaded file C:graphic-forms-uitoolkit.asd > *** - component "binary-data" not found, required by # "graphic-forms-uitoolkit" #x19F18DF5> I suspect your current working directory is not the top of the graphic-forms directory when you go to load the system, which is mentioned as step 3 in the How To Configure and Build section of the readme. If you're using SLIME, you can use the ,cd command. That is, a comma followed by the letters 'cd'. SLIME will prompt you for the destination path. Keep in mind that config.lisp and the instructions in the readme are just a 'default' procedure for loading graphic-forms. As you get more experience, you may decide you want to re-organize where all the pieces go, in which case you'd probably just write your own local script for loading everything. -- Jack Unrue From whistler at blinksoft.com Wed Aug 29 06:33:45 2007 From: whistler at blinksoft.com (Ken Perry) Date: Tue, 28 Aug 2007 23:33:45 -0700 Subject: [graphic-forms-devel] Is there a missing package? Message-ID: <002b01c7ea06$8daeb950$6401a8c0@Aiden> IN this line :depends-on ("cffi" "lw-compat" "closer-mop" "macro-utilities" "binary-data" ) Of the file graphic-forms-uitoolkit.asd I can not find where the two libaraies "macro-utilities" "binary-data" Are in the graphic-forms folder anywhere. I have the other librairies loaded but couldn't find these in the readme.txt or in the source. Where do I get them? It seems that the Grahpic forms is trying to find them and can't well I figure if I can't find them its hard to tell it where to look. Ken From whistler at blinksoft.com Wed Aug 29 06:52:39 2007 From: whistler at blinksoft.com (Ken Perry) Date: Tue, 28 Aug 2007 23:52:39 -0700 Subject: [graphic-forms-devel] Found them Message-ID: <002c01c7ea09$3177f9a0$6401a8c0@Aiden> Ok found the two libraries its complaining about under the external libraries under src. So now I will see if I can figure out why its not finding them. Ken From david at lichteblau.com Wed Aug 29 09:46:23 2007 From: david at lichteblau.com (David Lichteblau) Date: Wed, 29 Aug 2007 11:46:23 +0200 Subject: [graphic-forms-devel] Up and running In-Reply-To: References: <004001c7e936$a95da1a0$6601a8c0@Aiden> Message-ID: <20070829094623.GA4360@radon> Hi Jack, Quoting Jack Unrue (jdunrue at gmail.com): > I suspect your current working directory is not the top of the > graphic-forms directory when you go to load the system, > which is mentioned as step 3 in the How To Configure and Build > section of the readme. I have not followed graphic-forms changes in the last year, and when I tried building it with clbuild the last time it worked well, but in general the whole procedure described in "How To Configure and Build" is a little bit unusual. IIRC when adding graphic forms to clbuild I just ignored all that was written there; the only trick is to set up .asd file symlinks for src/external-libraries/*/*/*.asd While that is easy enough, I think most users will be confused by extra instructions (config.lisp, gfsys::configure-asdf) that are not strictly necessary and not familiar from other projects. Having to special-case graphic-forms in build scripts that would otherwise expect to just symlink graphic-forms/*.asd is also slightly inconvenient. I would suggest either moving those extra .asd files into the top-level graphic-forms directory or to move those external-library directories into separate installations. Finally, I seem to recall various configuration variables for absolute paths that could have been computed automatically using (slot-value (asdf:find-system :graphic-forms) 'asdf::relative-pathname) in the appropriate places. Thanks, d. From jdunrue at gmail.com Thu Aug 30 01:59:26 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Wed, 29 Aug 2007 19:59:26 -0600 Subject: [graphic-forms-devel] Up and running In-Reply-To: <002a01c7ea04$6d2cf4a0$6401a8c0@Aiden> References: <004001c7e936$a95da1a0$6601a8c0@Aiden> <002a01c7ea04$6d2cf4a0$6401a8c0@Aiden> Message-ID: On 8/29/07, Ken Perry wrote: > Well I just did (cd) in clisp which is supposed to print the current working > directory and it says > > #P"C:\\graphic-forms\\" > > > Which I believe is where the readme told me to run the clisp in. What I > don't understand is what it is looking for when it gives me the error: > > > *** - component "binary-data" not found, required by # References: <004001c7e936$a95da1a0$6601a8c0@Aiden> <20070829094623.GA4360@radon> Message-ID: On 8/29/07, David Lichteblau wrote: > Hi Jack, Hi David, thanks for your comments. > Quoting Jack Unrue (jdunrue at gmail.com): > > I suspect your current working directory is not the top of the > > graphic-forms directory when you go to load the system, > > which is mentioned as step 3 in the How To Configure and Build > > section of the readme. > > I have not followed graphic-forms changes in the last year, and when I > tried building it with clbuild the last time it worked well, but in > general the whole procedure described in "How To Configure and Build" is > a little bit unusual. Yep, I grant you that is true. > IIRC when adding graphic forms to clbuild I just ignored all that was > written there; the only trick is to set up .asd file symlinks > for src/external-libraries/*/*/*.asd I haven't tested shortcut support in the 4 Lisps that I currently develop with. I should do that. But, as you point out on your clbuild webpage, in the case of SBCL a patch is needed in order to understand shortcuts. Is a newcomer to Lisp expected to be able to do that? Ken may be in luck since he is using CLISP on Cygwin, and perhaps for him clbuild is the way to go. Note for Ken, the URL for clbuild is: http://common-lisp.net/project/clbuild/ In general, I'm not sure how I could expect symlinks to be available to all Windows users, unless they are running a shell like bash from MSYS or Cygwin. What you did to get clbuild working is what I had intended. Experienced developers may prefer different/better ways of loading this stuff. But I was trying (and I guess failing) to give new users an 'easier' way to get started. You may have guessed that gfsys::configure-asdf pushes a bunch of values onto asdf:*central-registry*. Well, that's something anyone can do themselves if they are familiar with ASDF. > While that is easy enough, I think most users will be confused by extra > instructions (config.lisp, gfsys::configure-asdf) that are not strictly > necessary and not familiar from other projects. > > Having to special-case graphic-forms in build scripts that would > otherwise expect to just symlink graphic-forms/*.asd is also slightly > inconvenient. I would suggest either moving those extra .asd files into > the top-level graphic-forms directory or to move those external-library > directories into separate installations. That's a good idea. > Finally, I seem to recall various configuration variables for absolute > paths that could have been computed automatically using > (slot-value (asdf:find-system :graphic-forms) 'asdf::relative-pathname) > in the appropriate places. At least some of those locations are for libraries such as CFFI which the user may have placed anywhere. My motivation for config.lisp, et. al., in the first place was because I figured that explaining what asdf:*central-registry* was, and explaining why symlinks may or may not work on Windows, was a bit more than I wanted to bite off in terms of instructions for new users. So I came up with this other mechanism. I won't argue that the current system is surprisingly different from other projects, or that improvements can't be made (c.f. your idea about relocating the .asd files for the bundled libraries). I just didn't think I'd be any better off leaving Windows users to their own devices to configure ASDF by hand, from a support standpoint. -- Jack Unrue From jdunrue at gmail.com Thu Aug 30 02:44:55 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Wed, 29 Aug 2007 20:44:55 -0600 Subject: Fwd: [graphic-forms-devel] Up and running In-Reply-To: References: <004001c7e936$a95da1a0$6601a8c0@Aiden> <002a01c7ea04$6d2cf4a0$6401a8c0@Aiden> <006801c7eaae$042f0d30$6401a8c0@Aiden> Message-ID: Ken, sorry if you get this twice. I should have replied to graphic-forms-devel. -- Jack ---------- Forwarded message ---------- From: Jack Unrue Date: Aug 29, 2007 8:43 PM Subject: Re: [graphic-forms-devel] Up and running To: Ken Perry On 8/29/07, Ken Perry wrote: > You asked, > "After you execute (gfsys::configure-asdf) can you tell me what > asdf:*central-registry* evaluates to? Just type that fully-qualified symbol > at the REPL, and you'll get back it's value." > > Here is what I got: > > [2]> asdf:*central-registry* > ("c:/graphic-forms" NIL > "c:/graphic-formssrc/external-libraries/practicals-1.0.3/Chapter24/" > "c:/graphic-formssrc/external-libraries/practicals-1.0.3/Chapter08/" > #P"C:\\clisp-2.41\\asdf\\cffi\\" #P"C:\\clisp-2.41\\asdf\\closer-mop\\" > #P"C:\\clisp-2.41\\asdf\\lw-compat\\" *DEFAULT-PATHNAME-DEFAULTS*) > [3]> Aha, there is the problem. I think you need trailing slash in your value for *gf-dir*. You are getting paths that have "c:/graphic-formssrc/...." instead of "c:/graphic-forms/src/...." -- Jack Unrue From kperry at blinksoft.com Thu Aug 30 03:57:14 2007 From: kperry at blinksoft.com (Ken Perry) Date: Wed, 29 Aug 2007 20:57:14 -0700 Subject: [graphic-forms-devel] Up and running In-Reply-To: References: <004001c7e936$a95da1a0$6601a8c0@Aiden><002a01c7ea04$6d2cf4a0$6401a8c0@Aiden><006801c7eaae$042f0d30$6401a8c0@Aiden> Message-ID: <006901c7eab9$da68d060$6401a8c0@Aiden> Perfect that fixed it I have it all loaded now. I will go play with your samples now. Thanks for the help I can't believe it was one little "/" Ken -----Original Message----- From: graphic-forms-devel-bounces at common-lisp.net [mailto:graphic-forms-devel-bounces at common-lisp.net] On Behalf Of Jack Unrue Sent: Wednesday, August 29, 2007 7:45 PM To: graphic-forms-devel at common-lisp.net Subject: Fwd: [graphic-forms-devel] Up and running Ken, sorry if you get this twice. I should have replied to graphic-forms-devel. -- Jack ---------- Forwarded message ---------- From: Jack Unrue Date: Aug 29, 2007 8:43 PM Subject: Re: [graphic-forms-devel] Up and running To: Ken Perry On 8/29/07, Ken Perry wrote: > You asked, > "After you execute (gfsys::configure-asdf) can you tell me what > asdf:*central-registry* evaluates to? Just type that fully-qualified > symbol at the REPL, and you'll get back it's value." > > Here is what I got: > > [2]> asdf:*central-registry* > ("c:/graphic-forms" NIL > "c:/graphic-formssrc/external-libraries/practicals-1.0.3/Chapter24/" > "c:/graphic-formssrc/external-libraries/practicals-1.0.3/Chapter08/" > #P"C:\\clisp-2.41\\asdf\\cffi\\" #P"C:\\clisp-2.41\\asdf\\closer-mop\\" > #P"C:\\clisp-2.41\\asdf\\lw-compat\\" *DEFAULT-PATHNAME-DEFAULTS*) > [3]> Aha, there is the problem. I think you need trailing slash in your value for *gf-dir*. You are getting paths that have "c:/graphic-formssrc/...." instead of "c:/graphic-forms/src/...." -- Jack Unrue _______________________________________________ graphic-forms-devel mailing list graphic-forms-devel at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/graphic-forms-devel From whistler at blinksoft.com Thu Aug 30 04:07:09 2007 From: whistler at blinksoft.com (Ken Perry) Date: Wed, 29 Aug 2007 21:07:09 -0700 Subject: [graphic-forms-devel] For your information Message-ID: <006a01c7eabb$3d2fdf80$6401a8c0@Aiden> I have ran the Hello-world and textedit demo programs. They work fine for me with my screen reader and now I will go see if I can make my own program. Good job Jack. Thanks, Ken From jdunrue at gmail.com Thu Aug 30 04:31:02 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Wed, 29 Aug 2007 22:31:02 -0600 Subject: [graphic-forms-devel] For your information In-Reply-To: <006a01c7eabb$3d2fdf80$6401a8c0@Aiden> References: <006a01c7eabb$3d2fdf80$6401a8c0@Aiden> Message-ID: On 8/29/07, Ken Perry wrote: > > I have ran the Hello-world and textedit demo programs. They work fine for > me with my screen reader and now I will go see if I can make my own program. > Good job Jack. That's great news! -- Jack Unrue From david at lichteblau.com Thu Aug 30 11:46:07 2007 From: david at lichteblau.com (David Lichteblau) Date: Thu, 30 Aug 2007 13:46:07 +0200 Subject: [graphic-forms-devel] Up and running In-Reply-To: References: <004001c7e936$a95da1a0$6601a8c0@Aiden> <20070829094623.GA4360@radon> Message-ID: <20070830114607.GA4160@radon> Quoting Jack Unrue (jdunrue at gmail.com): > In general, I'm not sure how I could expect symlinks to be available to all > Windows users, unless they are running a shell like bash from MSYS or > Cygwin. Okay, the whole ASDF-on-Windows situation is not ideal, so your configuration file to get people started is probably a good idea. I was hoping that the shortcut patch for ASDF makes things a little easier (because ordinary windows shortcuts created manually can be used), but that does not help much as long as it's not committed. clbuild is something I find valuable to avoid having to install everything manually, but I don't test it regularly on Windows, so it might be more trouble than it's worth for others. From jdunrue at gmail.com Fri Aug 31 05:12:54 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Thu, 30 Aug 2007 23:12:54 -0600 Subject: clbuild, was Re: [graphic-forms-devel] Up and running Message-ID: On 8/30/07, David Lichteblau wrote: > > Okay, the whole ASDF-on-Windows situation is not ideal, so your > configuration file to get people started is probably a good idea. > > I was hoping that the shortcut patch for ASDF makes things a little > easier (because ordinary windows shortcuts created manually can be > used), but that does not help much as long as it's not committed. > > clbuild is something I find valuable to avoid having to install > everything manually, but I don't test it regularly on Windows, so it > might be more trouble than it's worth for others. It's nice to have graphic-forms supported in clbuild, so I thank you for making that happen. I think the trouble is the uneven functionality provided by different Unix-compatibility layers for Windows, not clbuild itself. For instance, MSYS has a broken version of ln which behaves like cp instead. If I were running Cygwin I suspect clbuild would work fine on my machine. One comment to the wider audience. The shortcut patch mentioned above, which is available at: http://www.lichteblau.com/blubba/shortcut/ is very easy to apply, if you're inclined to build SBCL/Win32 from source. -- Jack Unrue From whistler at blinksoft.com Fri Aug 31 06:08:54 2007 From: whistler at blinksoft.com (Ken Perry) Date: Thu, 30 Aug 2007 23:08:54 -0700 Subject: [graphic-forms-devel] Documents Message-ID: <000801c7eb95$69cdadd0$6401a8c0@Aiden> I went to source forge to download the chm. After getting it when ever I open a topic the chm tells me it can't get to the web site. Is there something wrong with that chm file that is on source forge? Is there a online manual for Graphic-forms? I don't want to download the stuff for making the manual if I don't have to. Ken From jdunrue at gmail.com Fri Aug 31 06:21:09 2007 From: jdunrue at gmail.com (Jack Unrue) Date: Fri, 31 Aug 2007 00:21:09 -0600 Subject: [graphic-forms-devel] Documents In-Reply-To: <000801c7eb95$69cdadd0$6401a8c0@Aiden> References: <000801c7eb95$69cdadd0$6401a8c0@Aiden> Message-ID: On 8/31/07, Ken Perry wrote: > > I went to source forge to download the chm. After getting it when ever I > open a topic the chm tells me it can't get to the web site. Is there > something wrong with that chm file that is on source forge? Is there a > online manual for Graphic-forms? I don't want to download the stuff for > making the manual if I don't have to. I'm sorry Ken, I'm not sure why you're having problems with it. It's a valid chm and the links between various topics work OK here. I don't currently offer an online version of the manual. -- Jack Unrue From kperry at blinksoft.com Fri Aug 31 06:27:33 2007 From: kperry at blinksoft.com (Ken Perry) Date: Thu, 30 Aug 2007 23:27:33 -0700 Subject: [graphic-forms-devel] Documents In-Reply-To: References: <000801c7eb95$69cdadd0$6401a8c0@Aiden> Message-ID: <001501c7eb98$04d5df30$6401a8c0@Aiden> Thanks for checking I will go try downloading it again even though I doubt that is the problem. Ken -----Original Message----- From: graphic-forms-devel-bounces at common-lisp.net [mailto:graphic-forms-devel-bounces at common-lisp.net] On Behalf Of Jack Unrue Sent: Thursday, August 30, 2007 11:21 PM To: graphic-forms-devel at common-lisp.net Subject: Re: [graphic-forms-devel] Documents On 8/31/07, Ken Perry wrote: > > I went to source forge to download the chm. After getting it when > ever I open a topic the chm tells me it can't get to the web site. Is > there something wrong with that chm file that is on source forge? Is > there a online manual for Graphic-forms? I don't want to download the > stuff for making the manual if I don't have to. I'm sorry Ken, I'm not sure why you're having problems with it. It's a valid chm and the links between various topics work OK here. I don't currently offer an online version of the manual. -- Jack Unrue _______________________________________________ graphic-forms-devel mailing list graphic-forms-devel at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/graphic-forms-devel From whistler at blinksoft.com Fri Aug 31 06:36:46 2007 From: whistler at blinksoft.com (Ken Perry) Date: Thu, 30 Aug 2007 23:36:46 -0700 Subject: [graphic-forms-devel] Docs work Microsoft is interesting Message-ID: <001601c7eb99$4e7c6f90$6401a8c0@Aiden> Here is the trouble I was having with the Document file. I downloaded the chm and opened it by just hitting enter on the file. That nice Microsoft dialog popped up and asked if I really wanted to open the file. I didn't uncheck the box to keep asking if I wanted to open the file. And that caused the chm file not to work. As soon as I unchecked the continue to ask if I want to open the file the problem went away. . I find that really strange but that is a Microsoft strangeness not a Graphic-forms. Thanks, Ken From whistler at blinksoft.com Fri Aug 31 07:20:34 2007 From: whistler at blinksoft.com (Ken Perry) Date: Fri, 31 Aug 2007 00:20:34 -0700 Subject: [graphic-forms-devel] Accessibility question Message-ID: <002301c7eb9f$6ce31fa0$6401a8c0@Aiden> Jack, I just tested your layout tester and found a problem. Is there no tab index property on the controls? You had asked me about accessibility earlier and one big part of accessibility for your forms would be to have tab index working and the ability to add short cut keys. Currently it seems the only way to use the buttons is to click on them with the mouse for example I have 4 buttons on the layout tester and can't tab between them and select them with enter is this true? Or is there a property I have not found in the API to add keyboard access. Ken