FRONTER. aka. "awesome layer hacker" V.1.0.1

[twobob]

I'll make that into a singleton script then that runs whenever fronter is active.

Where the type of click is configurable as 2 7 8 or 9

twobob.fronter.sentinel.sh

I have encountered a few situations/apps already that have required this Double Finger Kill technique.

The ideal evolution would be to pass this to a true/false dialog before triggering the kill.
Happy to take advice on that.

[baf]

Originally Posted by twobob

okay so I get that we are calling

http://www.keplerproject.org/lualogging/manual.html

but... log ("FRONTER Renaming: ".. tostring(str))

err where does that log to?

damned if I can find it.

do I need to manually set/elevate the logging level?

This is a custom function. See lab126_logging.lua.
It goes to /var/log/messages AFAIR. You must raise log level with debugOn.sh though.

[knc1]

Originally Posted by twobob

I'll make that into a singleton script then that runs whenever fronter is active.

Where the type of click is configurable as 2 7 8 or 9

twobob.fronter.sentinel.sh

I have encountered a few situations/apps already that have required this Double Finger Kill technique.

The ideal evolution would be to pass this to a true/false dialog before triggering the kill.
Happy to take advice on that.

Could that be extended to a three finger touch?
For those users all too familar with: ctrl-alt-del

If Linux apps are to replace Windows apps - don't we have to support all of the Windows 'features' ?

[twobob]

Originally Posted by baf

This is a custom function. See lab126_logging.lua.
It goes to /var/log/messages AFAIR. You must raise log level with debugOn.sh though.

Ah thanks.

Makes sense.

I got around it.

Originally Posted by knc1

Could that be extended to a three finger touch?
For those users all too familiar with: ctrl-alt-del

If Linux apps are to replace Windows apps - don't we have to support all of the Windows 'features' ?

heh.

Sadly only two touch points are supported

perhaps the sentinel script can be extended to support keyboard toggling in the very near future...

[baf]

Originally Posted by twobob

perhaps the sentinel script can be extended to support keyboard toggling in the very near future...

You could easily take over KT button for that. In rc.lua it is currently mapped to handleHomeKeyDown and handleHomeKeyUp functions. Replace it with show/hide keyboard function. In the same script there examples how to do that with lipcH:set_string_property() function. You could check the current state of keyboard with keyboard_is_visible() function.

You can also implement your sentinel in functions handling button (touchscreen) presses (in the same rc.lua).

[twobob]

Originally Posted by baf

You could easily take over KT button for that. In rc.lua it is currently mapped to handleHomeKeyDown and handleHomeKeyUp functions. Replace it with show/hide keyboard function. In the same script there examples how to do that with lipcH:set_string_property() function. You could check the current state of keyboard with keyboard_is_visible() function.

You can also implement your sentinel in functions handling button (touchscreen) presses (in the same rc.lua).

excellent points... many thanks

[twobob]

implemented exact-only matching, corner-case cleanup, and reduced logging noise.

+	    if str == nil then
+       		return nil
+ 		end
+
+	if not stringStartsWith(str, "L:") then
+
+-- Debug 		llog.info("WindowManager", "bad-client-name", "winName=" .. tostring(str), "report-untidy")
+		
+-- exact matches only, Ditch the system stuff, this prevents thing like "Gtkboard" matching "kb"
+		
+		if (str == "kb") or (str == "webreader") or (str ==  "pillowd") then
+       	return nil
+
+	       else
+
+-- we made it this far - let tidy up likely corner cases
+-- tidy up spaces and other potentially magic characters
+			str = string.gsub(str, "%s+", "-")
+			str = string.gsub(str, "%%+", "-")
+			str = string.gsub(str, "%^+", "-")
+			str = string.gsub(str, "%$+", "-")
+			str = string.gsub(str, "%(+", "-")
+			str = string.gsub(str, "%)+", "-")
+			str = string.gsub(str, "%[+", "-")
+			str = string.gsub(str, "%]+", "-")
+			str = string.gsub(str, "%*+", "-")
+			str = string.gsub(str, "%?+", "-")
+			str = string.gsub(str, "%++", "-")
+			str = string.gsub(str, "%_+", "-")
+			str = string.gsub(str, "%/+", "-")
+			str = string.gsub(str, "%:+", "-")
+
+-- Debug	 		llog.info("WindowManager", "good-client-name", "winName=" .. tostring(str), "post-tidy")
+	        	str = "L:A_N:application_ID:" .. tostring(str) .. "_O:R_PC:N"
+-- Debug			llog.info("WindowManager", "title", tostring(str) , " ✔")
     end
+end

[baf]

Originally Posted by twobob

+-- we made it this far - let tidy up likely corner cases
+-- tidy up spaces and other potentially magic characters

I wonder if there is any need to struggle with app titles. Couldn't you just assign one generic title for all injected windows. Titles don't have to be unique.

[twobob]

It's a good point.

And one I really should take on board.
I guess it was really more important during the testing phase.

(spent a good hour or so wondering/finding why Gtkboard wouldn't "run")

Once again. excellent input.

[knc1]

Originally Posted by twobob

It's a good point.

And one I really should take on board.
I guess it was really more important during the testing phase.

(spent a good hour or so wondering/finding why Gtkboard wouldn't "run")

Once again. excellent input.

I think this "fix it if you can, toss it if you can't" approach has merit.

At least 'tag' this approach in your local development repo. before making vast changes to it.

(You did remember to do a: git init on this work directory, didn't you?)

[eureka]

Create /var/tmp/root/.config/awesome/rc.lua:

package.path = "/var/tmp/root/.config/awesome/?.lua;" .. package.path
dofile("/etc/xdg/awesome/rc.lua")

Then copy to /var/tmp/root/.config/awesome/ any file from /etc/xdg/awesome, change the copy, reload (restart) awesome. Modified copy will take precedence.

Power of RTFM, baby

[twobob]

sweet work that man.

I believe there was a default keybinding CMD + R (or something) that causes awesome to reload it's configuration while running...

Another gem to be dug up perhaps one day. *makes notes*

[eureka]

Originally Posted by twobob

I believe there was a default keybinding CMD + R (or something) that causes awesome to reload it's configuration while running...

Another gem to be dug up perhaps one day. *makes notes*

It's not default keybinding, it should be set explicitly (to invoke function awesome.restart).

I came to something different but also useful for this case (using overrided rc.lua):

package.path = "/var/tmp/root/.config/awesome/?.lua;" .. package.path
dofile("/etc/xdg/awesome/rc.lua")

local lipcH, errNum, errMsg = lipc.init("com.lab126.winmgr.extra")
if not lipcH then
  log ("!!!!!!!!!!!failed to init lipc " .. tostring(errNum) .. ", " .. errMsg)
else
  lipcH:register_string_property("restart", "w").listener = awesome.restart
  awesome.add_signal("exit", lipcH:close)
end

Then just:

$ lipc-set-prop com.lab126.winmgr.extra restart now

Instead "now" any string value could be used.

Unfortunately, every restart creates additional /bin/sh -c awesome process hanging around. And according to awesome sources, it's by design:

Spoiler:

void
awesome_restart(void)
{
    awesome_atexit(true);
    a_exec(globalconf.argv);
}

void
a_exec(const char *cmd)
{
    static const char *shell = NULL;

    if(!shell && !(shell = getenv("SHELL")))
        shell = "/bin/sh";

    execl(shell, shell, "-c", cmd, NULL);
}

[brianinmaine]

latest fronter 1.0.1 doesn't work for me. I had an earlier version that I just tried and that works fine.

the 1.0.1 version shows the patch fine, then when I run a program like pente or kcheckers, no display. the programs are running (ps -A) and the run script is also running. I'm not quite sure what exactly was changed here between versions? Did you happen to add version numbers in a script anywhere? I'm willing to put on the non-working version again if you tell me what to test?

does the current version work for anyone/everyone else?

[twobob]

Previous version worked via xdotool. new one relies on the internal LUA commands.

I should get one of these touches bumped to 5.3.7 and check nothing major changed...

Also add the evolutional changes outlined by Eureka/Baf above.

But I have several projects cooking at once right now...
Feel free to take over this one. All the notes are on these few pages and the technology used is one copy of "patch" and a lot of fiddling.

Totally transparent.