WebLaunch - Fullscreen browser for web-applications

[twobob]

So... Are we calling this "Done" for now?

I would like to trace the spurious "Unable to launch application error" - do you get that on the touch?

I'm right in the middle of the KUAL testing but will shove this on the "To Test" pile for afterwards if you didn't get that on the touch.

Maybe shove together a few use cases?

[PaulFreund]

Originally Posted by twobob

So... Are we calling this "Done" for now?

Unfortunately we can't right now, the bash addition causes the app to close regulary, but I am looking into this right now.

Originally Posted by twobob

I would like to trace the spurious "Unable to launch application error" - do you get that on the touch?

Nope :X Has it been there all the time or did it come with the last version?

Originally Posted by twobob

I'm right in the middle of the KUAL testing but will shove this on the "To Test" pile for afterwards if you didn't get that on the touch.

Maybe shove together a few use cases?

That would be nice, I think thats a job for when these things are done. One addition I'd also like to make is a horizontal setting

[PaulFreund]

Small addition: I just found out there has to be a way to fetch events from powerd! it is in the file /usr/share/webkit-1.0/pillow/javascripts/simple_alert_config.js I hope I get this soon.

EDIT:

Found out the command and syntax!

nativeBridge.subscribeToEvent(appID, appEvent)

where appID is "com.lab126.powerd" and appEvent is for example "outOfScreenSaver"

Now I only have to find out how to catch this

[twobob]

There the whole time on the PW. I will investigate the logs then when the time comes.
I did mention it I reckon in passing.

I did note it died from Time to Time - good to know you are on that.

Excellent work on the js based event thing. I shall leave it in your capable hands then until such a time as it requires indexing. Or I get this KUAL thing tied down with the team and time becomes available again.

[PaulFreund]

After trying to register an invalid dbus listener the app started to crash on launch for me, maybe it has something to do with the dbus-monitor function. But I hope we won't need it anymore in a couple of minutes, I can already listen to onCharging ;D

[twobob]

ROCK HANDS!

Be glad to see the back of it.

[PaulFreund]

As described here I found out how to receive system messages ! (it's very likely those are from DBUS)

And I now know why your code is working. At least on my Kindle Touch the power goingToScreenSaver doesnt get fired when preventScreenSaver is set to 1. Probably this behaviour is different on the paperWhite. Could you verify this with "dbus-monitor --system" on your PW?

[eureka]

Originally Posted by PaulFreund

As described here I found out how to receive system messages ! (it's very likely those are from DBUS)

Just for clarification: in fact, LIPC subsystem (that custom thing supporting properties and events for interprocess communication) is just a thin wrapper around of D-Bus.

[knc1]

Hmm...
I wonder where they got the name: Lite InterProcess Communications (LIPC) ?
Duh...

[eureka]

I think, L stands for Lab126, but, yeah, IPC is most likely "interprocess communication"

[PaulFreund]

Originally Posted by eureka

Just for clarification: in fact, LIPC subsystem (that custom thing supporting properties and events for interprocess communication) is just a thin wrapper around of D-Bus.

Good to know, didn't occur to me

[PaulFreund]

If somebody wants to test if he gets the goingToScreenSaver event with WebLaunch, include

var appName = 'com.PaulFreund.WebLaunch';

pillowHelper.RequestStatusBarEvent(
	appName, 
	'com.lab126.powerd', 
	'goingToScreenSaver'
);

pillowHelper.RegisterStatusBarEventCallback(
	appName, 
	function(value) 
	{
		document.write(JSON.stringify(value));
	}
);

after

var sessionSettings = settings;

and

return;

after

//-------------------------------------------------------------
// Open application
function openApp(state)
{

and

pillowHelper.UnRegisterStatusBarEventCallback(appName);

after

//-------------------------------------------------------------
// restore status bar on close
function closeApp() 
{

Then all events that are collected by the statusbar will show up and hopefully to goingToScreenSaver event too.
To test please press the power button while preventScreenSaver set to 0 or to 1

[twobob]

If you push that up I'll happily grab a build and abuse it... Err I mean test it.

[PaulFreund]

Originally Posted by twobob

If you push that up I'll happily grab a build and abuse it... Err I mean test it.

Thanks, I pushed the new version to github, or did you mean including the debug changes?

[twobob]

I'll go see what is there.