@idoodler thanks… i changed where the data is used and moved the routines to the node_helper… all good…

i have done some work over the weekend to get my two modules and their helpers working to do the basics…

database access is working, rest api server is working. (scheduler helper)
browser window creation and destruction is working, and image loading (handler helper)

one thing of note, a json object transports from module to helper and back. BUT any data added to the object in the helper (like a browserwindow object), does NOT transport (becomes undefined on receipt.)

@hriereb just checked… nothing free there…

cheapest looked like 400 eu /year

@hriereb i see… i created a new userid and see the same thing… IBM now owns this stuff and has decided not to provide free api access anymore… what a shame…

you can’t install in Desktop… its protected…

use your home folder… then make a shortcut to start the mirror

i got an api key the other day without any trouble. just have to login and go to key settings…

https://www.wunderground.com/weather/api/d/docs

thanks… not a nodejs developer generally, so didn’t know about the npmjs site…

also, i run the MM on an ODROID not PI. a lot faster.

i understand how ws works… i built a custom ws server and interface in front of an api emulation platform to support software testing a couple years ago.

thanks… the image is not shown in the dom, it is shown in a separate ‘browserwindow’, floating over the dom. i just loadUrl the image into the window, after creating and positioning it.
the mirror code doesn’t know the images are there

pictorial calendar reminders.

I have tested that the helper needs to do all this window mgmt

The scheduler module does scheduling (compare db data to calendar entries), start/stop viewer(s), and provide indirect services to load images depending on their source (file, dropbox, google drive, one drive).

The viewer module just walks thru a list of urls (getNext()) and opens a window hidden, loads image, hides old window, shows new window, deletes old window. (avoid dead window during load and, minimize screen flash)

yeh, but all this notification event handling really messes up the code i have which is all angular promise based.

I want to open my own browserwindow (show image), but u can’t do that in a module, only in a helper,
but then the window handle object needs to be stored inside the object which is managing the list of images for this ‘viewer’. that object is stored in the module… so, how do I transport the window handle object to the module… is the object valid in the other context (helper vs module).

see the topic ‘what can i do in a module’. (which u already have)