mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

[mcclim-devel] Scigraph's DWIM layer
by Clemens Fruhwirth 13 Mar '06

13 Mar '06

I'm interested in using Scigraph for generating histograms, but atm scigraph isn't in a good shape. The compatiblity layer for DWIM generates about 5-8 compile warnings (depends whether one is compiling to a fresh image or an image already containing dwim). I would like to ask what's the future of the compatiblity layer. We have a lot read-time conditionals for genera or clim 0.9/1 in the dwim files. I'm pondering to remove these conditionals, as mcclim isn't clim-0.9 nor clim-1. Also there are some hacks for non-ansi CL environments. I'm temped to remove them too as I would have to wrap those things in #-ansi-cl. But that's not really useful anyway, as mcclim is ansi-cl. So what about that: DWIM as contained in the mcclim repository is a compatiblity layer for running dynamic window code on mcclim (and only on mcclim) in an ANSI CL environment. With a definition as above I could kick out ~25% of the DWIM code. Opinions? -- Fruhwirth Clemens - http://clemens.endorphin.org for robots: sp4mtrap(a)endorphin.org

2 1

[mcclim-devel] [CfP] 3rd European Lisp Workshop
by Christophe Rhodes 13 Mar '06

13 Mar '06

[ Apologies for the circular; no doubt most people have already seen this -- though note that this Call for Papers contains important information about a financial incentive! With nothing to do for now but test and fix bugs, there should be loads of spare energy for writing papers... ] +----------------------------------------------------------------------+ | 3rd European Lisp Workshop | | July 3 & 4 - Nantes, Frances - co-located with ECOOP 2006 | | Supported by ALU and Ravenbrook Limited | +----------------------------------------------------------------------+ Important News * Nick Levine will be giving a keynote presentation at the workshop. He has been a professional Lisp consultant for over two decades and is the organizer of the upcoming International Lisp Conference in Cambridge, UK. We are grateful to Ravenbrook Limited for sponsoring the keynote presentation. * The Association of Lisp Users has kindly sponsored a $500 prize fund for exceptional papers submitted to this year's workshop. Both the ALU and the workshop organizers are looking forward to your submissions. Important Dates Submission deadline (papers & breakout groups): April 1, 2006 Notification of acceptance: May 1, 2006 ECOOP early registration deadline: May 23, 2006 For more information visit http://lisp-ecoop06.bknr.net/ Contact: Pascal Costanza, pc(a)p-cos.net Organizers ********** Pascal Costanza, Programming Technology Lab, Vrije Universiteit Brussel Theo D'Hondt, Programming Technology Lab, Vrije Universiteit Brussel Arthur Lemmens, Independent Consultant, Amsterdam Christophe Rhodes, Goldsmiths College, University of London Overview ******** "...Please don't assume Lisp is only useful for Animation and Graphics, AI, Bioinformatics, B2B and E-Commerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list." -- Kent Pitman Lisp is one of the oldest computer languages still in use today. In the decades of its existence, Lisp has been a fruitful basis for language design experiments as well as the preferred implementation language for applications in diverse fields. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. Common Lisp, with the Common Lisp Object System (CLOS), was the first object-oriented programming language to receive an ANSI standard and retains the most complete and advanced object system of any programming language, while influencing many other object-oriented programming languages that followed. It is clear that Lisp is gaining momentum: there is a steadily growing interest in Lisp itself, with numerous user groups in existence worldwide, and in Lisp's metaprogramming notions which are being transferred to other languages, as for example in Aspect-Oriented Programming, support for Domain-Specific Languages, and so on. This two-day workshop will address the near-future role of Lisp-based languages in research, industry and education. We solicit papers and suggestions for breakout groups that discuss the opportunities Lisp provides to capture and enhance the possibilities in software engineering. We want to promote lively discussion between researchers proposing new approaches and practitioners reporting on their experience with the strengths and limitations of current Lisp technologies. The workshop will have two components on separate days; there will be a day for formally-presented talks, and a day for breakout groups discussing or working on particular topics. Additionally, there will be opportunities for short, informal talks and demonstrations on experience reports, underappreciated results, software under development, or other topics of interest. Papers ****** Formal presentations in the workshop should take between 20 minutes and half an hour; additional time will be given for questions and answers. We encourage that papers be published on the website in order to provide background information in advance. Suggested Topics New language features or abstractions Experience reports or case studies Protocol Metaprogramming and Libraries Educational approaches Software Evolution Development Aids Persistent Systems Dynamic Optimization Implementation techniques Innovative Applications Hardware Support for Lisp systems Macro-, reflective-, meta- and/or rule-based development approaches Aspect-Oriented, Domain-Oriented and Generative Programming Breakout Groups *************** The workshop will provide for the opportunity to meet face to face and work on focused topics. We will organize these breakout groups and provide for rooms and infrastructure. Suggested Topics for Breakout Groups Lisp Infrastructure Development and Distribution Language Features (e.g. Predicate Dispatching) Environments for creating web applications Brainstorming sessions for new or existing open source projects Persistence Systems Compiler technology Lisp on bare metal / Lisp hardware / Lisp operating systems Compare and enhance curricula for computer science education Submission Guidelines ********************* Potential attendees are encouraged to submit * a long paper (10 pages) presenting scientific and/or empirical results about Lisp-based uses or new approaches for software engineering purposes; * a short essay (5 pages) defending a position about where research, practice or education based on Lisp should be heading in the near future; * a proposal for a breakout group (1-2 pages) describing the theme, an agenda and/or expected results. Submissions should be mailed as PDF to Pascal Costanza (pc(a)p-cos.net) before the submission deadline.

1 0

[mcclim-devel] Plans for McCLIM 0.9.2 "Laetare Sunday" release
by Andreas Fuchs 11 Mar '06

11 Mar '06

hi all, I (and a few others, hi Clemens and Christophe) would like to see a new McCLIM release. As Mothering Sunday is on the 26th of March, and we wanted to do time-slot releases anyway ((-;), I suggest we go for that date. Proposed schedule: * Heavy McCLIM hacking until 19th March. Then, freeze. * test test test, * Release McCLIM 0.9.2, "Laetare Sunday" on Sunday, 26th March (-: Is everybody happy with that? I'll take silence (until say, the 12th) as a "yes" (-: -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

4 3

[mcclim-devel] device font text styles
by Christophe Rhodes 08 Mar '06

08 Mar '06

Hi, I attach a patch for discussion and review, reworking the support for device fonts; in particular, one can do things like (with-text-style (s (make-device-font-text-style port (make-postscript-device-font-name :font-file "Dingbats.pfb" :metrics-file "Dingbats.afm" :size 14))) (write-line "Hello, World!" s)) We use this patch to draw lute tablature, using home-designed fonts for the tab glyphs, in both TrueType and Postscript formats (TrueType for display, Postscript for printing). I don't know whether this patch breaks the ordinary CLX backend's support for device fonts; is anyone in a position to test this? I also suspect that there are bits and pieces of the postscript code which are not entirely right, though I can say that Examples/postscript-test.lisp seems to be about right. This bit of CLIM is almost completely unspecified; all that we know about MAKE-DEVICE-FONT-TEXT-STYLE is that it takes a port and a "font name" and returns some kind of TEXT-STYLE object. The reasoning I've applied in this implementation is that since device-font-text-styles are defined not to merge (in the MERGE-TEXT-STYLE sense) with any other text style, a device-font-text-style-name needs to have all the information required to identify uniquely a font that we can use in the backend. Under X, calling this a "name" makes a certain amount of sense, because X fonts are in fact uniquely identified by their X name: something like "-adobe-courier-medium-r-normal-and-so-on-". I don't think this is true for any other backend :-) so I think it's reasonable to define names as structures, rather than attempting to parse some ad-hoc string representation. I also don't want to present this patch as a final interface; it is fairly ugly to have to specify the port type when making a name. Ultimately, we may want to move back to string names: something like (define-font "Varietie3" :freetype (:font-file "fonts/Varietie3.ttf" :size 14) :postscript (:font-file "fonts/Varietie3.pfa" :metrics-file "fonts/Varietie3.afm" :size 12)) but I certainly think that designing something like that is out of scope in the next three weeks... Anyway, with all that, the patch (which is by far the majority of my diff with HEAD) attached. Cheers, Christophe

1 0

[mcclim-devel] standard-tree-output-records using spatial-trees
by Andreas Fuchs 08 Mar '06

08 Mar '06

Hi all, As this is the first weekend of my holidays, I hacked on mcclim a little. So, I implemented standard-tree-output-records as per Tim Moore's suggestion, using R-trees from Christophe's excellent spatial-trees library. This one didn't take as long as I expected: about 4 hours. Props to Xof (-: I tested the change against beirc, which seems to be working. No performance measurements yet. I'll just sit on #lisp and wait for the scrollback buffer to grow (-: Here's the patch: Comments and testers (both for correctness and for performance improvements/degradation) welcome! Have fun, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

2 4

Re: [mcclim-devel] Infinite loop in McCLIM
by pw＠snoopy.mv.com 07 Mar '06

07 Mar '06

> "Paul Werkowski" <pw(a)snoopy.mv.com> writes: > > > The attached program works the same in McCLIM and Lispworks CLIM, > > except McCLIM gets into an infinite loop (CMUCL latest) unless > > incremental-redisplay > > is enabled. > > [ Belatedly ] Um, I didn't see an attachment to your original > mail... did you forget to attach it? Is this still a problem? > > Cheers, > > Christophe > > I think that problem went away - probably some cockpit trouble in my environment. Paul

1 0

[mcclim-devel] Infinite loop in McCLIM
by Paul Werkowski 07 Mar '06

07 Mar '06

The attached program works the same in McCLIM and Lispworks CLIM, except McCLIM gets into an infinite loop (CMUCL latest) unless incremental-redisplay is enabled. The program just wants its displayed output to track resizing the frame from the window manager. The attachment should run correctly. But then comment out the :incremental-redisplay as shown below and trouble is at hand. (defclass test-pane (application-pane) () (:default-initargs :display-function 'tpdf ;;; YIKES - in McCLIM; without this, infinite loop!! ; :incremental-redisplay t ; :display-time :command-loop )) ;;; Paul

2 1

[mcclim-devel] Scrollbar/text-editor-bug in McCLIM?
by Troels Henriksen 05 Mar '06

05 Mar '06

Observe the behavior of this simple application: (define-application-frame buggy-editor () () (:panes (text-edit :text-editor) (interactor :interactor :scroll-bars nil)) (:layouts (default (vertically () (scrolling (:scroll-bars t) text-edit) (scrolling (:scroll-bars t) interactor))))) If a line wider than the pane is written to the text-editor pane, it will correctly update the scroll-bars and the pane size to allow one to navigate through the entire line. This does not happen when more lines are inserted than it is possible to display in the pane, though: in that case, the horizontal scrollbars will not be adjusted, thus rendering it impossible to see the surplus lines. Is this behavior a bug in my application or in McCLIM? -- \ Troels "Athas" Henriksen /\ sigkill.dk - KILL -9

1 0

[mcclim-devel] [patch] make goatee search & execute frame commands by gesture
by Andreas Fuchs 26 Feb '06

26 Feb '06

Hi all, as it is now, goatee doesn't search for commands by keystroke gesture in the application frame's command table. This means that any command-invoking keystrokes that are entered when goatee is active will be ignored. This seems to affect all applications that have an interactor pane, like beirc. So, here's a patch that makes goatee search for & execute the command in the current application frame, if there is one. I'm not sure if this is the right thing to do, but it allows us to use keystroke accelerators in beirc commands, so I'd like it to go in, after goatee-literate people (hi, tim!) have OKed it. Here's the patch (sorry for the big hunk; the upper part is what I changed; the lower part is emacs cl-indent playing games): Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

1 1

[mcclim-devel] Spiffy code sought for elegant pop-up dialog!
by Peter Braroe 22 Feb '06

22 Feb '06

Hello all! As I have understood, it seems that :own-window t for accepting-values or NOTIFY-USER is not available yet in McCLIM. I really have my heart set on using a pop-up windows to manage prefs etc. but it seems non-trivial... What I want to do is: 1 Create a child window 2A Populate with text-fields, checkboxes, and buttons (like gadet-test) 2B Add "Save" button and method that returns/stores the values selected 3 Move focus to child, put original window in background 4 Destroy child window, refocus on original window It certainly seems possible looking at the Clim spec, but when I google it seems that I can't find much about it or examples. Sooo i am wondering if there is a reason for this... So if anyone has a nice example* of how to do this that would be a dream, and if not the next best thing would be if someone had a clear understanding of how it should be donwe. And if not some vauge ideas on how to get started, and where to look would be excellent! Thanks all! /Peter (*Even just a "About" pop-up example would be loveley!)

5 7

← Newer
1
...
48
49
50
51
52
53
54
...
82
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel