Well if you embed worldmap inside your own web page as an iframe (eg using dashboard2) then you have control of the rest of the page and can probably popup whatever you like.
I have always followed your progress about DashBoard2.
Also watched the how-to-first-steps video last week.
This is an amazing piece of module, and one day I'll have to start learning it, how to use it,
but at first view it is too complicated for my basic knowledge about html + css.
@TotallyInformation it is not Your fault, but mine because I'm not a web-developer and seeing the "default template" made me realise: it's an overkill for what I need and that learning process about the whole thing would probably take month if not years to understand how everything works.
I'm also afraid that it would make an extra overhead to the browser, (more memory + CPU consumption), which is not acceptable on a POS PC. (Must be optimised to max 50ms respond time for the user, sometimes on a non-cooled, limited freq 6th gen CPU with 2GB RAM + Win7 running at 45+ °C environment.)
No problem, that post wasn't aimed at anyone in particular. I just like to remind people that not everything is necessarily best in Dashboard and that there is a viable alternative for those who want it.
No, the opposite is true. UIBUILDER driven web sites use significantly LESS resource than Dashboard particularly in the browser while delivering a lot more flexibility. This page has some details.
Admittedly, I've not done direct comparison tests on the server-end but most use of UIBUILDER on the server has minimal impact. The new Markweb features may have a little more impact but only if you have many users using the web site; this is because conversion from Markdown to HTML happens on the server not in the browser. But for standard uibuilder nodes, there is some startup effort that adds a bunch of routes and endpoints to Node-RED's ExpressJS web server but, again, unless you have a lot of end-users hitting your resulting pages rapidly, the overheads should be minimal.
Dashboard 2, on the other hand, has to do a lot of data delivery to the front-end in order for anything to happen at all. In the browser, you have to load multiple heavy-duty libraries and the code as well as data for everything is passed from Node-RED to each client. Not a criticism of D2 by the way, just an observation.
Anyway, not a problem, you need to use whatever is best for you.
I may be able to add some form of dialog as the basics are there for the help panel. But will be a while until I get some time and probably won’t easily styled apart from rewriting the css file
I do not see any difference to, what you have suggested at the first place. (wrapping WM to Dashboard and running ANY kind of JS / HTML etc insice DashB2)
If you are afraid of "extra problem support" that these unallowed scripts would cause, simply deny any help on those.
Why would be a Leaflet pluging a problem, if millions of other people use it daily bases ?
We are the programmers, who write code into those nodes. So basically You are saying: