The document "Extra Numerical Types for Common Lisp" has been
submitted by Marco Antoniotti and has been accepted as CDR document 5.
According to the CDR process, this document is now in its initial
stage and will be finalized on April 9, 2008, unless withdrawn by the
author beforehand. See http://cdr.eurolisp.org/document/5/ for the
details of this document.
Pascal
--
1st European Lisp Symposium (ELS'08)
http://prog.vub.ac.be/~pcostanza/els08/
Pascal Costanza, mailto:pc@p-cos.net, http://p-cos.net
Vrije Universiteit Brussel, Programming Technology Lab
Pleinlaan 2, B-1050 Brussel, Belgium
_______________________________________________
cdr-announce mailing list
cdr-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce
Hi all,
I've set up a wiki about CLFSWM here:
http://hocwp.free.fr/clfswm-wiki/
Feel free to enhance it, share your ideas or your feeling about
clfswm.
There is a page for free discution if you find it more convenient than
the mailing list.
PS: Also, the devel mailing list is the prefered way to discuss about
CLFSWM in general.
Have fun,
Philippe
--
Philippe Brochard <pbrochard(a)common-lisp.net>
http://hocwp.free.fr
_______________________________________________
clfswm-announce mailing list
clfswm-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/clfswm-announce
Hi all,
As I said in the last mail, I've done a lot of rework on CLFSWM to
change its internal structure. Now the code is much simple and there
is no more needs for the pager.
If you look at the code and want to walk throw the group tree, don't
crash your head on a recurcif algorithm. You can simply use the
with-all-* macros. Here are some examples:
--------------------------------------------------
;; Walk throw all childs
(with-all-childs (*root-group* child)
(typecase child
(xlib:window (print (xlib:wm-name child)))
(group (print (group-number child)))))
;; Walk throw all groups
(with-all-group (*root-group* group)
(print (group-number group)))
;; Walk throw all windows
(with-all-windows (*root-group* window)
(print (wm-name xlib:window)))
;; Walk throw all childs - First form is applied on windows and the
;; second on groups
(with-all-groups-windows (*root-group* child)
(print (xlib:wm-name child))
(print (group-number child)))
--------------------------------------------------
Also there is less keybinding, just press 'm' in the second mode to
open a menu.
All is not already there (like pack, resize, the mouse...) but I use
this version already so there is nothing that prevent to have it in
the CVS.
Philippe
--
Philippe Brochard <pbrochard(a)common-lisp.net>
http://hocwp.free.fr
_______________________________________________
clfswm-announce mailing list
clfswm-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/clfswm-announce
For the record, both tarballs have been updated. I could confirm that
the Excel example works again on my machine.
_______________________________________________
rdnzl-announce mailing list
rdnzl-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce
Hi all,
After some exchange with Cyrille Thouvenin I started to rewrite some
parts of clfswm.
The main major change is that there is no more references to
workspaces, all is a group. There is a root group and there childs.
A child can be a group or an application window.
Here is the old data structure:
--------------------------------------------------
(defstruct workspace number group-list)
(defstruct group x y width height window-list fullscreenp)
(defparameter *workspace-list* nil)
--------------------------------------------------
Here is the new one:
--------------------------------------------------
(defclass group name number x y w h layout window gc child ...) -simplified-
(defparameter *root-group* nil
"Root of the root - ie the root group")
(defparameter *current-root* nil
"The current fullscreen maximized child")
(defparameter *current-child* nil
"The current child with the focus")
--------------------------------------------------
Now using clfswm is like walking throw a tree of groups and windows.
Here is the current keybinding to navigate throw this tree:
Alt-Tab: circulate throw childs of *current-child* if it is a group.
Alt-Left/Right: circulate throw brother childs (ie: this is like
workspaces)
Alt-Up: select the first child.
Alt-Down: select the father of *current-child*
Alt-Enter: Make the current selected child the current root (ie
maximize it)
Alt+Shift-Enter: Make the father of current root the current root
(ie unmaximize the current child)
There is no workspace but the same effect is obtened by circulating
throw brothers childs.
The advantages:
- you can have workspace in any level.
- there is no need for the pager: _you_are_in_the_pager_!!!
You can find some screenshots here for a better idea:
http://common-lisp.net/project/clfswm/temp/
Others changes are:
* group/window coordinates are in float number between 0 (left) and
1 (right) so we can zoom them. Each group have its own window.
* each group can have its own layout:
no-layout: groups have there size, windows are maximized in the
father group
maximize-layout: groups and windows are maximized
tile-layout: groups and windows are tiled
tile-left/right/...: tile like in larswm/dwm...
... and so on - it's very easy to add a new layout.
* a group is named so you can tell where you want to map a new
window.
* Each time a new window is created each group can do something with
it (nothing, absorbe this window, copy this window, open a new
group and map the window in it, open it in the group named toto...
This is a more general process than the previous control-o (open
next window in a new workspace))
* Chained key binding. Key binding are grouped by action and there is
a little window to present possibles choices (there is no more a
lot of keys to remember).
* Currently I'm trying to have a different focus policy by groups
(I don't know if I'll integrate this by default).
Ouf, here it is :) It's a great change but the code is more simple
(for example there is no more duplicated code with the second mode
and the pager because there is no more pager :)
I'll commited all this changes. So don't be too surprised by the new
cvs content!
Have fun,
Philippe
--
Philippe Brochard <pbrochard(a)common-lisp.net>
http://hocwp.free.fr
_______________________________________________
clfswm-announce mailing list
clfswm-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/clfswm-announce
There are some significant changes in this release, see the News
section of the clouchdb web page for more information about potential
compatibility problems.
_______________________________________________
clouchdb-announce mailing list
clouchdb-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/clouchdb-announce
On Wed, 13 Feb 2008 21:49:55 +0100, "Iver Odin Kvello" <iverodin(a)gmail.com> wrote:
> I tried to muck around with this myself, and discovered the
> Unbox_Any opcode, present from version 2.0 of the framework; and
> this also seems to work (see attached patch). Of course, I don't
> really know what I'm doing, and this isn't present in version 1.0
> and 1.1, but could that work also? It makes the fix a one-liner.
I've now released a new version which hopefully fixes this. Thanks
for your help and thanks to Michael for discovering the bug. A simple
test for callbacks is now included in the examples folder.
As I already announced, the new DLL and the updated C++ code are based
on Visual Studio 2005 now.
Please test!
_______________________________________________
rdnzl-announce mailing list
rdnzl-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce
On Fri, 8 Feb 2008 08:34:41 -0800, Cyrus Harmon <ch-tbnl(a)bobobeach.com> wrote:
> Yes, cl-fad seems like a reasonable approach to me.
See the latest release. Should also hopefully fix the other problem
you reported.
I've chosen to always reply "Not Found" now as I think we don't have
to give the bad guys hints about our directory structure by sometimes
(in the case of folders) saying "Bad Request".
Edi.
_______________________________________________
tbnl-announce site list
tbnl-announce(a)common-lisp.net
http://common-lisp.net/mailman/listinfo/tbnl-announce
On Fri, 8 Feb 2008 18:24:58 +0100, Daniel Janus <daniel(a)sentivision.com> wrote:
> Actually, I found a few more minutes and came up with the attached
> patch, which changes the error to "Don't know what to do with NIL in
> multipart/form-data body.".
That's not entirely correct - you have to check for the CAR, not for
the CDR. But I've now uploaded a version which hopefully has better
error messages for cases like this one (and others as well).
Thanks,
Edi.
_______________________________________________
drakma-announce mailing list
drakma-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce
Hi,
Objective-CL 0.1.1 has been released today.
Quick download:
http://matthias.benkard.de/objective-cl/releases/objective-cl-0.1.1.tar.gz
* What's new?
** CLOS integration
Even though work on supporting the definition of new classes is still
ongoing, Objective-CL now correctly maps Objective-C classes to CLOS
classes. Objective-C metaclasses are likewise mapped to CLOS
metaclasses.
Class and metaclass naming follows the convention introduced by
Clozure CL. For instance, NSMutableDictionary's CLOS name is
NS:NS-MUTABLE-DICTIONARY, while its metaclass' name is
NS:+NS-MUTABLE-DICTIONARY.
There is one wart left in the mapping: +NS-OBJECT's metaclass is a
fake metaclass called ++NS-OBJECT. As far as I can tell, +NS-OBJECT's
metaclass ought to be +NS-OBJECT itself, which the CLOS MOP apparently
makes impossible (CHANGE-CLASS of metaobjects is not allowed).
** Clozure CL compatibility
Clozure CL used to complain about not being able to externalise
pointer wrappers (such as instances of the classes ID and SELECTOR).
This has been fixed by providing a method on MAKE-LOAD-FORM for these
classes.
** GNU CLISP compatibility
Objective-C wrapper object finalisation now takes care of removing
finalised wrappers from the global caching hash tables. This makes
CLISP happy. Therefore, it has stopped crashing upon trying to run
the test suite.
So, what happened to 0.1.0? Well, the short answer is, I tagged a
development version 0.1.0 without running the unit tests first. After
I had realised what I had done, it was too late: I had already pushed
the tag to the repository. As I didn't want anyone to suffer
repository corruption, I decided to simply make the next release
version 0.1.1.
The tag is still there, of course, so if you're extremely curious
about what 0.1.0 would have looked like had it been released, feel
free to take a look. It's not that pretty a sight, though. ;)
Have fun,
Matthias
_______________________________________________
objective-cl-announce mailing list
objective-cl-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/objective-cl-announce