freenode/#clim - IRC Chatlog
Search
23:43:32
nyef`
bugrum: In my own CLIM exploration, I found that there's a lot of "reading between the lines" of the CLIM II specification to figure out how the backend should be structured... and then the "official" CLIM II implementation goes ahead and does something different, and McCLIM probably does something *else* different...
23:44:19
nyef`
So one of the things that went on my list of desiderata for my own CLIM implementation was a backend-writing-guide or similar.
23:45:00
bugrum
I did find a small enough but decent starting point in the guided-tour documentation
23:46:38
bugrum
however I will say that a more thorough document on how to implement different backends might make it easier for folks who want to port CLIM to other platforms say iOS or even Android (it should be possible)
23:47:09
bugrum
The interfaces won't change and CLIM's layered architecture definitely lends itself to the same advantages as Qt's QPA
23:47:26
nyef`
So, the initial things to worry about, AIUI, are event handling, toplevel windows ("frames"), and graphics rendering (anything that goes through a MEDIUM).
23:49:23
nyef`
That much should get a more-or-less-working "generic" port, in that everything is rendered in terms of a CLIM look-and-feel, and then from there you customize your frame manager to use the "adaptive toolkit" stuff to swap in "host" widgets where appropriate for various gadgets and whatnot.
23:52:28
bugrum
okay frames, event handling (I guess careful thought needs to be put here so that it doesn't leak to the command level) and graphics rendering are the bare minimum
23:53:53
bugrum
there isn't anything in CLIM's interfaces that has to be changed to handle things like multi-touch and mobile
23:54:12
whoman
yes, ive done some mobile dev, i can see clim working quite alright with it. especially the many popups, lends well
23:54:14
bugrum
at least I don't think so (I'm still going through tutorials so consider this a naive hypothesis)
0:19:47
nyef`
For mobile, or multi-touch generally, I might expect that there could be a new event class for multi-touch events, but that there would also be a default handler to bounce them to mouse events for the most part, and that the usual pane-realization mechanism could be used to substitute in multi-touch-sensitive widgets as appropriate.
0:28:06
bugrum
yeah I have customize the environment a bit. the default prefix key is... inconvenient
0:28:41
whoman
<p>-k to kill, <p>-w to list all windows. [r]esize, and [q] fullscreen. thats all ive been using
0:29:08
whoman
i set it to my <menu> key, which is only on one side of space, i'd rather it on <win>, but had issues with that
0:29:23
bugrum
it always takes time for me to get an environment setting. was hoping for a quick cheat sheet and some more details on how frames work (I accidentally split to the minimum size and didn't know how to maximum the frame)
0:30:22
whoman
those 8 or so are the only ones i got to know, not sure if i could learn more, took about a week to get it muscle-memory
6:08:44
jackdaniel
I'm fine - in PoznaĆ to meet with some friends. I was a bit sick lately, but it seems it was nothing serious
6:09:30
beach
Fine too, thanks. Things are a bit slow on the Common Lisp front, but lots of social activities instead.
6:09:30
jackdaniel
it's a shame bugrum left, if he'd be still here, I'd tell him that some remarks about backends are in `Developer Guide' section of the manual