Hi, the new dashboard looks really cool and the new features are also very helpful. Regarding the number of widgets I am sure we will soon have more on the new dashboard than on the old one, since it is really simple to create new ones.
I am currently working on the integration of images into the data explorer stored with the data lake sink as described in STREAMPIPES-75. During the development the question came up how we structure our core modules in the UI. There are currently multiple directories containing shared components and services. I actually like that we prefix those modules with “core” and I would suggest to move the data model from connect to the module core-model since it is used in multiple other modules. Further I will move the components in core-ui into the data-explorer since we have a different widget concept for the new dashboard and cannot re-use them. What are other components we can put into the core-ui directory? (Buttons, …) Philipp > On 19. Feb 2020, at 09:15, Dominik Riemer <[email protected]> wrote: > > Hi all, > > good news, finally a first working version of the new live dashboard is ready! > > It's already merged in dev so that we can test if everything works. > While we have not yet reached full feature-parity with the old dashboard in > terms of available widgets, the new dashboard also has some new features: > - multiple dashboards can be created > - widgets can be moved in a grid system and resized as needed > - widgets can be configured after they have been placed in the dashboard > - widget colors and titles can be flexibly changed > - new widgets can be created easily using a similar configuration approach as > pipeline elements > > It would be great if you could test the new implementation, provide some > feedback and discuss about things you'd like to see! > > Dominik > > -----Original Message----- > From: Dominik Riemer <[email protected]> > Sent: Tuesday, January 21, 2020 9:49 PM > To: [email protected] > Subject: Re: AW: Improving the Live Dashboard > > Hi all, > > following up on this, to give you a quick status: > The good news is, I've started to implement the new dashboard. > The old dashboard will be completely refactored and upgraded to an Angular 2+ > module, and there will be some nice new features that I mentioned in the > corresponding Jira ticket. > So the not-so-good news is that it'll probably take some time as it seems to > be a ton of work ;-) > > I hope to have a first prototype working by the end of the month. > > So if you have any new ideas what to include/improve, I'll be happy to know! > > Dominik > > On 2019/12/03 07:59:33, Christofer Dutz <[email protected]> wrote: >> Hi folks, >> >> One thing I'd enjoy would be to have more than the fixed maximum of 6 rows. >> >> Chris >> ________________________________ >> Von: Philipp Zehnder <[email protected]> >> Gesendet: Dienstag, 3. Dezember 2019 07:16:55 >> An: [email protected] <[email protected]> >> Betreff: Re: Improving the Live Dashboard >> >> Hi, >> >> thanks for creating a first draft. I think it is a very good idea and also >> very useful. >> In the data explorer we already created a prototype of the backend API to >> also read historic values. Additionally there are already two types of >> visualization available with a table and a line chart. We can re-use those >> and extend those. >> Let me know when you have finished the first prototype. Then I can add those >> two. >> >> We could also think about to integrate the asset dashboard as an additional >> visualization. What do you think about that? >> >> Cheers, >> Philipp >> >> On 2019/12/02 21:54:45, "Dominik Riemer" <[email protected]> wrote: >>> Hi all,> >>> >>>> >>> >>> the Live Dashboard we use to display real-time charts of sensor >>> values can> be improved in terms of usability. Some issues we >>> currently have are:> >>> >>> - Users can change the order of dashboard widgets, but modified> >>> layouts are not persisted> >>> >>> - Changes to widgets are not persisted, e.g., the order of table> >>> columns as Chris mentioned in a previous mail> >>> >>> - Created visualizations cannot be modified> >>> >>> - Currently, only a single dashboard can be created, but it would be> >>> nice to create multiple dashboards (e.g., to visualize the state of >>> multiple> >>> assets) > >>> >>>> >>> >>> So I think it would be great to refactor the dashboard, and at the >>> same> time, migrate the current implementation to Angular 7 (for >>> those of you who> are new, the UI currently uses both Angular 1 and >>> 7 components and we are> gradually upgrading old Angular 1 >>> components to 7). I'd volunteer to create> a first prototype of the >>> new dashboard.> >>> >>>> >>> >>> In general, I think the dashboard should be rather simple (we >>> shouldn't> probably compete with some very good visualization tools >>> that already> exist), but some things I'd like to see are:> >>> >>> - Having the opportunity to create standalone dashboards (some> >>> companies we've talked to already mentioned that they would like to >>> have> individual, configurable dashboards that can be used to >>> display condition> data at the shop floor level)> >>> >>> - Such dashboards could be shared / implemented as web components to> >>> be integrated into other systems> >>> >>> - Read-only mode> >>> >>> - A very fluent way to modify the layout of widgets and the >>> dashboard> >>> itself> >>> >>>> >>> >>> So what do you think? Which features would you like to see in a >>> real-time> dashboard to monitor IIoT data?> >>> >>>> >>> >>> Dominik> >>> >>>> >>> >>> >> >> >> >
