luakit - Lightweight web browser

[twobob]

Luakit. latest revision.. (Luakit 039e319)

I will bundle this WITH midori when the time comes. might as well as the libs are so similar, get more bang for our buck on the library space used that way...

(It does not, yet, have a custom libwebkitgtk to handle uploading - which is still cooking)
So WARNING: Choosing to Upload a File will hang it... (Unless you use fronter)

https://dl.dropboxusercontent.com/u/...uakit-KUAL.zip

thanks.

[twobob]

EDIT: So, the keyboard toggling problem is solved...

-- Zooming

"+", "Enlarge text zoom of the current page.",

"-", "Reduce text zom of the current page.",

"=", "Reset zoom level.",

you will want to EDIT the /mnt/us/extensions/luakit/usr/bin/config/binds.lua to remap your favourite functions to keys the amazon keyboard can handle...

It's pretty obvious what to do.

[brianinmaine]

http://developer.coronalabs.com/cont...-and-listeners has lua stuff about touch events...

still looking.

http://docs.coronalabs.com/guide/eve...uch-multitouch

http://www.mindfiresolutions.com/Mov...g-Lua-2219.php

seems you need a function to call the keyboard, then add an eventlistener to listen for touch screen events?? I know nothing of lua!!

http://www.think-techie.com/2011/08/...-keyboard.html

[hawhill]

This is not really about Lua and not about finding keyboard implementations with a Lua API. Luakit just offers a (small, at a first glance) Lua API. What you are searching for is a good point to trigger a keyboard pop-up. I can't see a good point for that in the Lua API, so it's back to C then. Well, probably it's so closely entangled with GTK that the proper point to show up a keyboard is within GTK code anyway.

[twobob]

I don't care where I get it.

All i need is Screen X & Y.

Anything...

And this thing can run any LUA by its very modal nature, windows.lua can be constructed to do ones bidding

Seems like such a simple request... and yet... I'm struggling

[brianinmaine]

"xtestlab126 -d" shows all the touch events... ?? there MUST be something better!

"cat /dev/input/event3" shows garbage on screen when touched?
Oh - thats what evtest is for "evtest /dev/input/event3"

[Aeris]

Originally Posted by twobob

I don't care where I get it.

All i need is Screen X & Y.

Anything...

Don't know if I got exactly what you mean... If you need screen width and height I've found this script on kterm launch one:

#WIDTH=`xwininfo -root|grep Width|cut -d ':' -f 2`
# use wider keyboard layout for screen width greater than 600 px
#if [ ${WIDTH} -gt 600 ]; then
#  PARAM="-l ${EXTENSION}/layouts/keyboard-wide.xml"
#fi

So it would be:

WIDTH=`xwininfo -root|grep Width|cut -d ':' -f 2`
HEIGHT=`xwininfo -root|grep Height|cut -d ':' -f 2`

If you meant the X Y cursor position... ignore this comment xD

[twobob]

ah right, no. perhaps I should have been more specific.
"On click, what is the X and Y location"

I was messing with evtest last night (from geekmasters scripts) and Brian has just reminded me again this morning of it.

I'll hack something out of that.

Thanks

[twobob]

Originally Posted by brianinmaine

"xtestlab126 -d" shows all the touch events... ?? there MUST be something better!

"cat /dev/input/event3" shows garbage on screen when touched?
Oh - thats what evtest is for "evtest /dev/input/event3"

hmm it's event0 on the PW. I'll do a test for the device then first, thus determining the right event#. Then horror-story trace the content.

Thanks

My brain is losing it's flexibility I fear...

[hawhill]

Oh, I misunderstood the question. It is about manual triggering the keyboard... as brianinmaine told, evtest can print parsed output of the touchpad input event devices.

twobob, do you want to trigger the keyboard popup in java code or in another program/script running parallel to luakit?

You might prefer "xev" to "evtest". You can run "xev -root" to get all events, mask events with "-event" or get events for a given window with "-id" or "-name".

[twobob]

ah... Thanks : ) I'll give that a try then. Every time I ran xev in the past it never spitted out what I expected. I'll give it another go then...

I /think/ -name is the name of the xev window itself... but -id could work...
appreciated.

xev -id $(xwininfo -tree -root | awk '/Luakit Browser Framework/ {print $1}') 2> /dev/null | awk '/root/ {print $7} ' | tr -d ')' | cut -d"," -f2 | awk '$0 < 50 {system("/mnt/us/extensions/luakit/usr/bin/toggleKeys close")}' || awk '$0 > 700 {system("/mnt/us/extensions/luakit/usr/bin/toggleKeys open")}' helpful...

[eureka]

hawhill nailed it. Just change the C part of luakit to handle mouse click on this area (because taps are recognized by X application as ordinary click of left button).

It's not possible within Lua (if you're don't want to mess with C part beforehand, exposing click event to Lua part). Top right part of status bar is filled by label widgets, which aren't exposing click events by default.

UPD: oh, I was wrong for it not being possible. That's what I did to test the way on my computer (NOT on Kindle):

1. $ mkdir $HOME/.config/luakit
   $ cp /etc/xdg/luakit/binds.lua $HOME/.config/luakit

2. Add this to my custom binds.lua:

   window.init_funcs["handle click on status bar (except of part filled by selectable lables)"] =
     function (w)
       w.sbar.ebox:add_signal("button-release", function (v, mods, button, context)
         print(button) -- prints 1 for left click
       end)
     end

And it printed 1 to standard output every time when I clicked status bar (except the url part, which handles clicks on its own).

Also:

$ luakit --version
luakit 039e319

[hawhill]

Yeah, that's the clean approach. Grabbing all X server or input events in a separate process is another option, though. A bit messy, since it will need to wade through all events coming in, though.

[twobob]

Originally Posted by eureka

hawhill nailed it. Just change the C part of luakit to handle mouse click on this area (because taps are recognized by X application as ordinary click of left button).

It's not possible within Lua (if you're don't want to mess with C part beforehand, exposing click event to Lua part). Top right part of status bar is filled by label widgets, which aren't exposing click events by default.

I have no "problem with" hacking any part of it... just needing some guidance, or even a little help. Yep - that (exposing/attaching the click events to labels) was what I (and knc1) were working on last night - plumbing the click events in the labels seemed the perfect solution.. after quite a while of not "getting it done" I passed out but recognised that would be the tidiest solution :\

Originally Posted by hawhill

Yeah, that's the clean approach. Grabbing all X server or input events in a separate process is another option, though. A bit messy, since it will need to wade through all events coming in, though.

I can handle messy. "Done" is really all I want at this point...

6 hours sleep in 3 days is hurting my ability to think. At least, that is what I tell myself....

[eureka]

Originally Posted by twobob

I have no "problem with" hacking any part of it... just needing some guidance, or even a little help. Yep - that (exposing/attaching the click events to labels) was what I (and knc1) were working on last night - plumbing the click events in the labels seemed the perfect solution.. after quite a while of not "getting it done" I passed out but recognised that would be the tidiest solution :\

OK. I don't want to participate in hacking of the C part (it's bo-o-ring, ti-i-iring and I ain't even use luakit), but you should look at update in my previous post.

UPD: as keyboard could be invoked through LIPC, information on accessing LIPC from Lua might be useful.