[Openmcl-devel] Contrib: window-parking
lisp at clairvaux.org
Fri Sep 11 07:37:23 EDT 2009
Great suggestions as usual, Rainer.
You're definitely right about cl-documentation and hemlock-commands
having nothing to do with "context". I put them there mostly to show
how multiple tools could be managed. As the IDE evolves, they should
be put somewhere else.
You know as much about UI design in general and IDE design in
particular as any Lisper I know. It's obviously something that
interests you and something to which you have given a lot of thought.
Experienced programmers often look down their noses at IDEs. -- "Real
programmers don't use IDEs". And if an IDE doesn't hit the target,
they are right. The trick will be to develop a Lisp specific IDE that
really hits the target. Then we will have a wonderful tool.
I would like to see you and Terje take the lead in this. Even if you
don't have time to write code, your experience and overview would be
Thanks for your comments --
On Sep 11, 2009, at 4:47 AM, Rainer Joswig wrote:
> Am 09.09.2009 um 03:18 schrieb Glen Foy:
>> To give it a try:
>> cd ccl/contrib/
>> svn update
>> That will pull in new versions of all contribs, including Context-
>> Menu-CM, List-Definitions-CM and Window-Parking-CM.
>> In the Listener or in ~/ccl-init.lisp execute these forms:
>> ;;; Use your own path here, if you are using a local copy of the
>> (setq gui::*hyperspec-root-url* (gui::pathname-to-url "/Lisp/
>> (require :context-menu-cm)
>> (require :cl-documentation-cm)
>> (require :list-definitions-cm)
>> (require :hemlock-commands-cm)
>> (require :window-parking-cm)
>> (cmenu:set-default-tool "List-Definitions-CM")
> That's easy enough. Loads fine.
> Boy, it is hard to keep up with Glen's contributions. Glen, thanks
> for your stuff. You deserve some feedback. CCL users should check it
> out. There is a lot of potential. With some more help we are getting
> in 'MCL mode' with many good IDE enhancements by contributors.
> Some general feedback (feel free to ignore them ;-) ) :
> * don't put too much in the context menu. But look for the context
> menu in Apple Mail for an example, or Xcode:
> <Bildschirmfoto 2009-09-11 um 10.23.14.png>
> * the 'context' menu often implies that the command is invoked on
> the context (the current point, the current selection, the current
> paragraph, the current symbol, the current buffer, ...).
> * the cl-documentation and hemlock-commands contributions are really
> really great and very useful, but I would like to see them in the
> menu bar under the HELP menu or the TOOLS menu. Possibly with a
> palette style window, that floats on top. The palette window even
> could watch the current active buffer/listener and update the CL
> documentation info while you type or move over symbols. The
> hierarchical information is great.
> DashCode uses them for example for a snippet library.
> <Bildschirmfoto 2009-09-11 um 10.38.46.png>
> It would be great to have your CL documentation hierarchy and some
> code snippets that could be contributed and copied from there. Like
> WITH-OPEN-FILE, snippets for opening a file for reading/writing,
> appending to a file, etc.
> * the existing commands (like cut, copy paste, and the stuff from
> the services menu) should still be there. (I wonder why in stock CCL
> 64 under Mac OS X 10.6.1 I only get one useful service command 'Make
> New Mail Note'.)
> * I would put a configuration command for the context menu in some
> menu in the menubar, not in the menu itself.
> * it would be very useful if several command collections could be
> Warmest regards,
> Rainer Joswig
> Rainer Joswig, Hamburg, Germany
> mailto:joswig at lisp.de
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel