Catching system events from mesqute

[PaulFreund]

EDIT:

This code is now included in pillowHelper and should not be used without removing the callback default_status_bar before closing!

Old Statement:

This code ueses the pillowHelper library to communicate with the pillow app default_status_bar. It enables you to receive system events as a message. I'm pretty sure it is able to catch DBUS events, see description why.

PHP Code:

    // Get system events from Mesquite. I am pretty sure these are actually DBUS events!
    // For example I can subscribe to org.freedesktop.DBus - NameOwnerChanged
    // runAsPillow in pillowHelper.js which is located here at: 
    // https://www.mobileread.com/forums/showthread.php?p=2476587#post2476587

    // Hook callback
    kindle.messaging.receiveMessage('persistantCallback', function(message, value) 
    {
        document.write(value);
    });

    // Hooking into statusBar event list - Method 1
    runAsPillow(
        'default_status_bar',
        'com.PaulFreund.WebLaunch',
        function()
        {
            // Create a persistant callback
            document.body.persistantCallback = function(a) 
            {
                // Call the default eventCallback as it will be overwriten
                StatusBar.eventsCallback(a);
                
                // Notify myself about the data
                nativeBridge.setLipcProperty(
                    'com.PaulFreund.WebLaunch',
                    'persistantCallback', 
                    JSON.stringify(a)
                );
            };
                
            // Subscribe to additional events
            nativeBridge.subscribeToEvent('com.lab126.powerd', 'testMsg');
                
            // Overwrite the default eventHandler callback
            nativeBridge.registerEventsWatchCallback(document.body.persistantCallback);
        }
    );

    // Hooking into statusBar event list - Method 2
    // Method 2 is building upon the SubscribedEvents object and its
    // SubscribedEvents.sources array of handlers, but it would require
    // more function proxying if the desired messages already have a handler
    // for more information see: 
    // /usr/share/webkit-1.0/pillow/javascripts/default_status_bar.js 


PS: I think we should rename the WAF tag in the board to Mesquite

[twobob]

PS: I think we should rename the WAF tag in the board to Mesquite

Hmm... But the old ones ARE Wafs.... Perhaps a NEW Tag?

Would that do?

[PaulFreund]

Originally Posted by twobob

PS: I think we should rename the WAF tag in the board to Mesquite

Hmm... But the old ones ARE Wafs.... Perhaps a NEW Tag?

Would that do?

I sometimes forget that vendors don't upgrade their old devices, of course a new tag would be awesome

[twobob]

I have requested the works be undertaken in due course.

I'll happily amend your tags to the correct ones at that time.

[eureka]

Mesquite subsystem is essentially the same old WAF. No changes except renaming. Furthermore, WAF is a general term for Web Application Formats, covering W3C Widgets specification, and Kindle's WAF/Mesquite application is the simple plain W3C widget. So new tag isn't required, IMHO.

[twobob]

Right... But one type references a different set of named instances in the sqlite database.

The WAF ones don't work on the later models and vice versa.

So technical ideals aside, any thoughts on that practical aspect of "It Don't Work on My Device!"... This is more what I was attempting to outline with the new tag.

[PaulFreund]

Originally Posted by eureka

Mesquite subsystem is essentially the same old WAF. No changes except renaming. Furthermore, WAF is a general term for Web Application Formats, covering W3C Widgets specification, and Kindle's WAF/Mesquite application is the simple plain W3C widget. So new tag isn't required, IMHO.

Unfortunately the term WAF is not very wide-spread and as it seems the W3C stopped using it too (old workgroup closed, new one is called WebApps Working Group). Also when there is no reference to WAF on the Kindle ( and old Kindles will die out over the years ) so nobody will know what the term means.

[twobob]

For my money WAF says "Older models supporting WAF naming convention" and MESQUITE says "Newer models supporting MESQUITE naming convention".

The average user won't care that they are the "same" if one doesn't work on the other.

I am taking this from an application end-user viewpoint obviously.
We are already lumbered with a pile of older apps that "Don't Work" for the sake of a simple naming convention alteration...

resisting urge to Amazon bash...