[Kindle] Unified Application Launcher. KUAL

[twobob]

Hmm yeah. and what...monitor for the poweroff event?

or perhaps we should just disable screensavers.... ???

I like the sound of that more...

[twobob]

Originally Posted by knc1

One of the most powerful things that could be imagined on a *nix machine -
...

For the author - nearly as simple - in your file manager just click the file and pick "sign" then pick the key you are using for this purpose.

Whilst I agree this has no extra power than the previous incarnation.
But "Yes," we probably should adopt a signing policy for the nervy.

[knc1]

Originally Posted by twobob

Whilst I agree this has no extra power than the previous incarnation.
But "Yes," we probably should adopt a signing policy for the nervy.

It is a brand new launcher - -
A good time to establish a brand new policy on executable postings.

I know you made a "full disclosure" in the top post -
But since this is a "time of change" anyway . . . . .

[DuckieTigger]

Originally Posted by twobob

Hmm yeah. and what...monitor for the poweroff event?

or perhaps we should just disable screensavers.... ???

I like the sound of that more...

Disable screensaver? HELL NO. Right now that is the only way to get out of stuck programs that refuse to exit. But a cleanup button, that will kill everything that has been started would be sufficient, imo. Or a button to focus again on the code that was run.

[briant1234]

omg twobob <3 will test soon

i can't even karma you more

[twobob]

Originally Posted by briant1234

omg twobob <3 will test soon

i can't even karma you more

Credits.
This is mainly the work of Ixtab.

but you're most welcome.

[twobob]

Originally Posted by DuckieTigger

Disable screensaver? HELL NO. Right now that is the only way to get out of stuck programs that refuse to exit. But a cleanup button, that will kill everything that has been started would be sufficient, imo. Or a button to focus again on the code that was run.

hmm...

having trouble envisioning how this could know what was subsequently run in the resulting scripts. PID children perhaps

It smells like a job for a human rather than a machine... as-in a bodge script.

[knc1]

Originally Posted by twobob

hmm...

having trouble envisioning how this could know what was subsequently run in the resulting scripts. PID children perhaps

It smells like a job for a human rather than a machine... as-in a bodge script.

Ah - how about a script that does a "ps ..." then edits the result to only include the list of program names that the launcher already knows about?

Not me. Let DT code it for us.

- - - -

3193 looks pretty - will try to stop now.
Most of this is chatroom stuff anyway.

[silver18]

Originally Posted by twobob

Whilst I agree this has no extra power than the previous incarnation.
But "Yes," we probably should adopt a signing policy for the nervy.

I'm definitely not into this kind of thing, but I agree with Twobob: the GUI launcher has the same power of this!
Moreover, users (like me) download and install things at their risk.
BTW, I'm more than happy to provide this signing policy for Komic (but I need to understand it first!).

[DuckieTigger]

Originally Posted by knc1

Ah - how about a script that does a "ps ..." then edits the result to only include the list of program names that the launcher already knows about?

Not me. Let DT code it for us.

- - - -

3193 looks pretty - will try to stop now.
Most of this is chatroom stuff anyway.

Already did code it. Well in my head. I will wrap my kterm call in a shell script and kill all leftovers first, then run it. When working will post that script here.

[twobob]

Okay... so to enable a bodge script. easily. I made a trimmed down version of System!k

Called "Helper".

Will attach to top post. just add your improvements to the kill-kterm.sh in there.

Pictured... (when I attach it) done.

[DuckieTigger]

Originally Posted by twobob

Okay... so to enable a bodge script. easily. I made a trimmed down version of System!k

Called "Helper".

Will attach to top post. just add your improvements to the kill-kterm.sh in there.

Pictured... (when I attach it) done.

Oh that will work. Will test it out. Since I already need to hack into the WakeupFromScreenSaver event for my lightoff, I will try to instead of running my script to run a script that will run all /mnt/us/extensions/runatwakeup. And you can customize what happens when you wake up from screensaver.

As for nested menus - is that supported? That would be a great thing.

[twobob]

Whilst the results are TreeMap thus sortable? they currently are processed out as-is.

one for the "nice to have" pile - usability on all devices to be addressed

[DuckieTigger]

Originally Posted by twobob

Whilst the results are TreeMap thus sortable? they currently are processed out as-is.

one for the "nice to have" pile - usability on all devices to be addressed

Ok, got it. Helper is broke. Listen to your own advice: Run your dosending2unixending on your own stuff before tgzing or ziping. Both have dos ending.

Update: here is how kill-kterm.sh should look like:

#!/bin/sh
kill -9 `pidof kterm`
kill -9 `pidof matchbox-keyboard`

Or alternatively if you like killall:

#!/bin/sh
killall -9 kterm
killall -9 matchbox-keyboard

AFAIK, killall only accepts process names, not pids.

[twobob]

now irrelevant