Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)



Ken Tilton wrote:


Michael wrote:

On 2007-01-29 18:40:37 -0500, Ken Tilton <kentilton@xxxxxxxxx> said:

Ah, someone else just reported that. My apologies (and a warning that I do not use ASDF day to day so those files do not get maintained).

Just eliminate the cl-ftgl dependency. The ASD has been recommited, along with slight mods for the movie widget.



I tried out celtk. A few comments/questons.

1. Are tile and togl required? I'm used to ltk and it
works on a stock tcl/tk. Installing tile and togl
is easy enough, just wanted to know if it is a hard
requirement.


<cough> yesd and no. No in principle, but maybe yes in fact because I think I hardcode the damn thing to append ttk:: to all the widgets Tile duplicates. You would just have to search on the string "TTK::" and remove that.

really what should be done is simply offer new Celtk widgets like ttk-button. Hang on. I do have a tile? attribute which I would have defaulted to t for this experiment. Maybe track /that/ down and change to nil and the engine will not stick in the TTK:: (or you can tweak it not to).

Anyway, as I was saying, The Right Way probably lets people use non-Tile versions, just because it is so easy to do so and maybe they would have a reason for it, so err on the side of more.

Ah, here is what I did (tho modified now from what you would find):

(defmethod tk-class :around ((self widget))
(conc$ (when (tile? self) "TTK::") (call-next-method)))

And the Tk default (the initform) for tile? is t, and widgets tile does not support have a defaultinitarg of nil.

So if you make a button, you get a Tile button unless you specify:

:tile? nil

Just change the tk-object tile? initform to nil (and disable the package require) and you should be able to avoid Tile.

kt
.

Quantcast