Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- From: philip.armitage@xxxxxxxxx
- Date: 29 Jan 2007 12:56:41 -0800
On Jan 29, 7:47 pm, Ken Tilton <kentil...@xxxxxxxxx> wrote:
philip.armit...@xxxxxxxxx wrote:
...I'm about a month or so away from releasing a 0.1 build of my
It may be that my performance issues are nothing
to do with wish and more to do with my crappy code. But I find that to
but with SomeOtherTk (Py?) as well) that performance is not an issue
talking to wish. As someone once said, this ain't protein-folding we're
doing. Not sure what to tell you, except, yes, the algorithm is usually
the problem. Otoh, I did not even consider doing OpenGL by sending
Yes it's either that or the shoddy graphics card combined with
somewhat heavy GNOME desktop on my machine at work which is
struggling. It seems reasonable on my home computer. I can tweak this
thing forever but I'd rather get _something_ out there and wait for
the abuse to roll in.
I suppose I'd also be interested in what I lose. With LTk I get pretty
comprehensive docs...PWUAHAHAHAHAHAHAHHAHHAHAA!!!!!!!!!!!
another sucker...er, interested inquirer get involved I think Frank will
adopt Celtk, give it is own c-l.net project, and then /you/ can document
it? Not interested in writing doc? Believe you me, I understand.
It's not that I'm not interested but I still have to write the docs
for my own code.
The good news is that the great thing about Ltk and Celtk is that we
have been careful merely to wrap tcl/Tk, not substitute a new API (the
mistake made by the cl-opengl project). So Tcl/Tk doc is Celtk doc, and
questions/problems can go to comp.lang.tcl as well as celtk-devel
(should it ever exist).
This is very true. In fact I was able to bring a small amount of
Tkinter (Python) experience to my LTk coding too which has helped
immensely. It's reassuring that you and Peter know what you're doing.
... and zero dependencies (well apart from a workingand the frickin source?!), now you do not want to install anything else.
Tcl/Tk installation but I mean no compiling chains of undocumented
Lisp libraries...).What a wuss! First you want doc (what is wrong with dozens of examples
You'd love Cello. Not!
It's not a case of not wanting to though. It's more a case of spending
ages getting nowhere. When you move to a new language having used
others for a couple of decades, you want to dive in and do something
useful rather than write word count programs (even ones that do it
'functionally'...). So it's a fine line between using your programming
knowledge and not spending months trying to get packages to build.
But this is very much my problem and not yours before you pull another
weird tennis analogy on me :-)
Phil
.
- Follow-Ups:
- Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- From: Ken Tilton
- Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- References:
- All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- From: Ken Tilton
- Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- From: philip . armitage
- Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- From: Ken Tilton
- All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- Prev by Date: Re: Array access
- Next by Date: Re: Is there any eq t test in Common Lisp?
- Previous by thread: Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- Next by thread: Re: All Your GUIs Are Belong to Us (Die, McCLIM! Die!!)
- Index(es):