Hiding the status bar? (for a home automation project)

[jnjitkoff]

Originally Posted by aditya3098

@jnjitkoff: You are not using the latest firmware, right? 5.0 or 5.1 maybe, althought 5.0.x is best for wafs. 5.1.x has some memory management crap and 5.3 does not even use waf (mesquite, is that how it's spelled?)

I have 6 Kindle Touches, and the farthest they've updated is to 5.1.2.
I assume the webkit version is basically the same in any version (I use websockets to keep everything sync'd).

Would it be worth me downgrading them to 5.0.x?

[eureka]

Originally Posted by jnjitkoff

Would it be worth me downgrading them to 5.0.x?

I guess, nobody, who really worked with complex WAFs (I mean, silver18), would recommend you downgrade for better WAF experience.

[silver18]

As regards WAFs (or mesquites), every firmware is just "good".
Every problem is related to upgrades: so, on the other hand, it makes sense to not upgrade your firmware!

[silver18]

Originally Posted by eureka

Nice picture. Specially for you, (not only) titlebar switch commands:

# lipc-set-prop com.lab126.pillow disableEnablePillow disable
# lipc-set-prop com.lab126.pillow disableEnablePillow enable

This is super awesome!!
It will be really helpful in next release of komic!
Just need to figure out how to execute a script when Komic is closed (as it seems I can't use the onpause or onclose....)
Need to study....

[jnjitkoff]

One of the things I was particularly interested in doing was being able to do sounds and tts feedback for actions (via calls to aplay, etc). If I recall, one of the releases had a waf api that let you call arbitrary shell scripts (though on another thread someone has found a similar technique using a background daemon and the logging calls).

Will I regret it if I choose to downgrade to that 5.0.X release to get at that api??

[eureka]

Originally Posted by jnjitkoff

One of the things I was particularly interested in doing was being able to do sounds and tts feedback for actions (via calls to aplay, etc). If I recall, one of the releases had a waf api that let you call arbitrary shell scripts (though on another thread someone has found a similar technique using a background daemon and the logging calls).

Will I regret it if I choose to downgrade to that 5.0.X release to get at that api??

Of course, because there was no such API for WAF apps in any firmware up to (and including) current 5.3.2.1. WAF apps are essentially sandboxed and stock sandbox relaxing facets ("features") didn't and doesn't include process launching.

I've answered you in WAF hints thread about how you could take silver18's way for communication with outside and change it in try to trick system daemon to execute arbitrary shell script.

[silver18]

Originally Posted by eureka

Nice picture. Specially for you, (not only) titlebar switch commands:

# lipc-set-prop com.lab126.pillow disableEnablePillow disable
# lipc-set-prop com.lab126.pillow disableEnablePillow enable

Tried this yesterday: AWESOME!

Komic has now a new option to hide the status bar.
BTW, I need to fix a few things:
- when enabling pillow, the status bar has only time and wifi icon. You need to write on it again!
- I need to catch the closing of Komic to enable again pillow! I could use window.onunload but I had a few problems (I can solve them, I just need some spare time)

[Dr. Drib]

Moderator Notice

Please take a few moments to read our Posting Guidelines, in particular the part about the maximum image size allowed (600x600 pixels). Images that violate those guidelines may be deleted.

It is every member's responsibility to read our Posting Guidelines and follow them.

Thanks.

[knc1]

Originally Posted by Dr. Drib

Please take a few moments to read our Posting Guidelines, in particular the part about the maximum image size allowed (600x600 pixels). Images that violate those guidelines may be deleted.

It is every member's responsibility to read our Posting Guidelines and follow them.

Thanks.

Can't something that has been here for four years be grandfathered?

[JSWolf]

Originally Posted by knc1

Can't something that has been here for four years be grandfathered?

I agree that it's a bit much to remove the image after about 4 years. If nobody's complained about it, then I see nothing wrong with it.

I think the image guidelines are draconian and need to be repealed and replaced.

[knc1]

Plus, the poster has not visited this site since June, 2013.
Somehow I think he will not see the big green message.
So what is the point?

[JSWolf]

Originally Posted by knc1

Plus, the poster has not visited this site since June, 2013.
Somehow I think he will not see the big green message.
So what is the point?

I've stared a thread in the Feedback forum. Please feel free to join the thread. I'd like your opinion. Thanks.

[kdusr]

tried both version on KV,
# lipc-set-prop com.lab126.pillow disableEnablePillow disable
# lipc-set-prop com.lab126.pillow disableEnablePillow enable
and
wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,1'
wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,1'

wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,30'

but they do not work, kv has different key-value of lipc-set-prop com.lab126.pillow ?????

[knc1]

Originally Posted by kdusr

tried both version on KV,
# lipc-set-prop com.lab126.pillow disableEnablePillow disable
# lipc-set-prop com.lab126.pillow disableEnablePillow enable
and
wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,1'
wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,1'

wmctrl -r L:C_N:titleBar_ID:system -e '0,0,0,600,30'

but they do not work, kv has different key-value of lipc-set-prop com.lab126.pillow ?????

You are bumping a four year old thread, I do not think the author will see your question.
It would be best if you started a new thread for your problem, rather than bump one of only historical interest.

Plus, you did not mention what firmware version you are doing those trials on.