GUI Library name

Hey everyone,

I am going to release a functioning beta of my gui toolkit in a week or so. I want to see if anyone has thought of a good name before. It is currently called LTK but that is sort of boring. Plus, there is a toolkit called FLTK and mine looks too similiar. The L obviously stands for Llama, but it doesn't have to be named after me.

I've been thinking of things such as:
TinyTK
LittleGUI
something with Flex
something begining with P or L

any creative input? The tiny and little names are nice, but they make the system sound less significant. I like the term flex because the Toolkit runs on so much hardware, but I can't find something to pair it with. My first name is Paul so "Paul's __ __" could work. Acronyms are welcome. I also wouldn't mind a pun or something to that effect. Another plus is if it can be abbreviated enough to be placed infront of data types: ltWidget, ltRect, etc..

Anyways, thanks!

Okay I'll post my 2c:

EETK or e2tk (e-squared) "Everything embedded toolkit"

PDK "Paul's Development Kit"

Wunderkit (pun of "wunderkint")

kleiner Werkzeuginstallationssatz (just kidding :) )

I'll post again if I get creative...:rolleyes:

coo thanks. That last one is particularly catchy... and easy to remember

Little GUI => Little GUY => a Troll like a troll not the one used in forums :D
so FlexiTroll

The Llama => Llama Toolkit

Flexible sounds like => FlexiPaul (ok with french pronounciation) then add toolkit behind


well i find FlexiTroll funny between all the garbage i wrote :)

LLTK (Little Llama TK, LLama TK, whatever)
TKPL (getting close to TCL/TKL ...)
FlexTK

You should know LTK is the Lisp Toolkit (http://www.peter-herth.de/ltk/). If you're thinking of PTK that's either the Perl TK (http://www.lns.cornell.edu/~pvhp/ptk/ptkFAQ.html) or this one: http://www.phelios.com/ptk/

So this runs in framebuffer mode, right? Or if it runs in X, it also supports framebuffer mode?

So far I like bus.ch's LLTK (Little Llama Tool Kit) and my Wunderkit...

Thanks for the suggestions. I'm still thinking about it, but I'm not going with LTK anymore (probably not LLTK either but I could). FlexTK and Wunderkit are nice too, but I'll need some sort of 2 or 3 letter prefix for define and macro constructs, some helper functions, etc..

Here is another question. How do you think a rectangle should be measured? Consider the picture. Is the size of the red rectangle 8x6 or 9x7? Is the green one 10x2 or 9x1? The blue- 5x1 or 4x1?

The difference is whether you measure around the rectangle, or on the rectangle. Which one seems more natural? Which one do you think has better implications in a graphical toolkit? I'd tell you how it's been set up but I don't want to influence your remarks.

Take the Gimp in example when you magnify a picture, the considered squares representing pixels works like the green which would be 10 x 2 or blue 5 x 1.
As far i remember, the Degas Elite in 1987 which was working on Atari ST was also using this way of counting, so i think it would be the most natural way as this entered in people's habits...this is only my opinion it doesn't mean it must be like that ;)

Quote:

---

Originally Posted by kraft

Take the Gimp in example when you magnify a picture, the considered squares representing pixels works like the green which would be 10 x 2 or blue 5 x 1.
As far i remember, the Degas Elite in 1987 which was working on Atari ST was also using this way of counting, so i think it would be the most natural way as this entered in people's habits...this is only my opinion it doesn't mean it must be like that ;)

---

Well, that is how the toolkit is coded currently. That seemed most natural to me. When I started to program the X11 Driver for the TK I noticed that the function for drawing rectangles behaved the other way. I'm trying to think of a good reason for doing it that way. In my case it would require adding 1 to all extents before drawing.

At this point in time I am going with WonderKit or FlexTK

I like WonderKit because the only other wonderkit is some wooden construction-kit toy. FlexTK is good, but my problem is the library getting lost if people start calling it flex. FlexTK yields 30+ results in Google, but Flex TK yeilds over a million. Flex API, over 3 mil.

I would personally use LTK or LLTK but I don't like how similar they are to FLTK. WonderKit is almost playful, and that is good! The toolkit is very adaptable and expandable. I like the ideas of Tiny or Little, but it may make the TK seem incapable (and it pretty much is at this point.) More suggestions welcome, as always.