@Paul-Reed Thanks much for pointing out the new chart.js. It looks like this issue has been addressed. Sorry I did not follow the development details. Would love to try out the Alpha release in the near feature.
@Steve-Mcl Yes you are correct that I was referring to the original dashboard.
@kevinGodell It would be great that this feature can be integrated in the future.
1 Like
Don't forget to account for ending authorisation sessions, don't leave them open indefinitely. This is where it gets tricky when using websockets.
Having just released v0.3.0 with some great enhancements such as reordering widgets in the group, in the unlikely event that the developers are sitting round wondering what to implement next, the lack of the Message Pass Through option in the switch and dopdown nodes, and the expected changes to the dropdown node message format, are the two things preventing me from proceeding in migrating my home dashboard across.
1 Like
Still get the blue screen error.
Also, the link from the sidebar is still wrong - it doesn't take into account the httpNodeRoot setting.
Could have sworn that was fixed.
Would you be kind enough to provide details / repro Julian & I will get this fixed.
Sure:
- Change your settings for
httpNodeRootto something other than blank - I always leave it as "nr" on my dev machine because I had so many issues forgetting to include it in the various uibuilder URL's
- Restart Node-RED
- Reload the Editor
- Open the Dashboard 2 sidebar
- Click on the button to open the Dashboard
- Note that it opens
http://127.0.0.1:1880/dashboardinstead ofhttp://127.0.0.1:1880/nr/dashboard
Note that I haven't tested having Node-RED on a different port. I assume that the link is defined with a relative URL, something like :${port}/${RED.settings.httpNodeRoot}/Dashboard? Sorry can't remember the actual prop for the port in settings.
Hmm, actually, I don't think that will work. I think you have to build the full URL including the scheme, IP and port. That's because you are calling the link from the Editor but handing off to the user-facing ExpressJS app. Anyway, some testing doubtless needed to get the right effect so worth changing the root URL for the editor as well as the httpNodeRoot. And trying with Node-RED on a custom port.
1 Like
Thanks Julian. in my head - this is (was) fixed but I will dig into it and will definately be fixed in next release. Issue raised.
1 Like
This issue #142, marked as fixed, does not seem to be working. It should be including mobile web app capable entries into the web page meta data. When I run wget ip:1880/dashboard I see
<!doctype html><html lang=""><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Vue App</title><script defer="defer" src="js/chunk-vendors.e754d3f7.js"></script><script defer="defer" src="js/app.192e57b3.js"></script><link href="css/chunk-vendors.2378ce49.css" rel="stylesheet"><link href="css/app.d69e3f81.css" rel="stylesheet"></head><body><div id="app"></div></body></html>
with no mobile config in meta.
It was only closed yesterday Colin. It may not yet be published. /cc @joepavitt
I took this from the release notes to mean that it should be
- Add mobile meta for easy assignment to mobile app lists by @joepavitt in #159
Just noticed that core-js is in dependencies but does not appear to actually be used? Is it really needed? And if it is, did you see the problems the core-js dev is currently having? Might be worth offering some small funding amount?
Good point, I'd never knowingly added that, will investigate.
Since the notification widget is not available yet, is it trivial for those that know how (which I don't) to achieve a basic OK/Cancel popup using a template node?
Don't worry if it is not trivial, I can wait.
It is actually next on my list. Likely to be next week.
If you do want to build your own, depends on how you want it triggered, if only from a static button, then it's fairly straight forward (examples here). If you want it triggered from injection of a payload, then it's likely to be a little trickier, but if you don't mind waiting a week, I'll have it done.
1 Like
Thanks Joe, I will wait in eager anticipation 
That is the trouble with releasing something early, people play with it and then hassle you to get more done.
4 Likes
1/ my dashboard is in "Layout: Grid" and when I put a button widget in 1x1 it displays it to me in a rectangle. There is no (or not yet) 1x1 widget size setting or have I not seen it?
2/ Have you planned to add display settings for the X axis in hh:mm:ss to the Chart widget? As well as the display duration? Because on my graph I have no idea of the 2. For beginners who want to display a quick curve of a sensor in real time I think it is essential.
1 Like
Do you mean you expect it to be square? If so then the same applies to any size, a 4x1 is not four times longer than high.
A 1x1 button on the old dashboard is square.
Old Dashboard: 1x1 is a square
Yes, like the old dashboard, it would make sense that 1x1 or 2x2... would make a square rather than a rectangle. And 4x1 must be 4x wider than tall.
1/ my dashboard is in "Layout: Grid" and when I put a button widget in 1x1 it displays it to me in a rectangle. There is no (or not yet) 1x1 widget size setting or have I not seen it?
Thanks for the feedback, the layouts were very much put in as temporary placeholders, and their naming is not intuitive to non-CSS developers (will be updating them soon).
Grid is actually utilising a column approach, no matter what the width of the screen there are a set number of columns (defined by width), this makes it more flexible for varying screen widths, but does mean that a 1x1 isn't likely to be square (depending on the screen width a any given point). Flex is meant to be more "fixed" in nature as per Dashboard 1.0, but hasn't had the attention it needs at the moment.
Thanks for the feedback though, we also have a new layout about to be released - Notebook. Which, as things stand also wouldn't provide square 1x1, but know that I am very aware of the preference here and will strive to ensure it's more consistent when I get the chance.
1 Like
2/ Have you planned to add display settings for the X axis in hh:mm:ss to the Chart widget?
As well as the display duration?
Not sure what you mean here?
1 Like
