@johanvos Definitely interested, especially interested in cross platform building. Have been using javafxports. Have been away from newest dev too long
@carldea@FinancialAKB So, Having #JavaFX14 webview on #JDK11 running the mobile site from the #PiDome server (in development). The site is a #VueJS front-end with REST. On the left firefox, right JavaFX (I need to check the icons). LTR: Add peripheral, Login sesisons, Websockets!!!, Premises edit
Technical: Currently busy to move out the internal pidome module dependencies out of the main project and putting them into their own respective dedicated projects. All automated builds will fail until this is done, hopefully in the next couple of hours.
Another milestone, all retired project repositories have been cleaned up, except the original server and the downloads. These stay until @Bitbucket deletes the mercurial repositories which we have been using for all projects. New repos will be created ASAP during development
Almost done with the first additional supported database next to H2 which is MySQL. This means you could simply try out #PiDome with an in memory, without additional installation a local H2 or networked with a MySQL database (currently testing with 8.0).
New blog post: "JMetro Version 11.6.8 And 8.6.8 Released" - https://t.co/nKWG3XuvUe
Some updates and also updated the JMetro documentation page. If you're using JMetro you'd probably should check it out: https://t.co/ZjAJisfmqz
#JMetro#Java#Javafx#FluentDesign
@rahulsaini07@trisha_gee@brunoborges@venkat_s I believe it depends on context. I personally follow this:
- When a collection is returned return an empty collection,
- When it is legal to return nothing in cases, use an optional,
And depending on the severity use a null return or throw an exception
The upcoming version deprecates SQLite and will be replaced with H2 and various other databases. This requires a big change in database update strategies. For this we are moving to @liquibase which will be integrated in the server.
Discovery now changed to the possibility to create a device definition directly from the discovery of a new device. Just tap "Or create a new device" in the device selection. You will be provided with the options of that specific discovered device ( https://t.co/FlRUahDqTI )
When a device type is unknown, but is able to do different things with the same signal (Like KlikAanKlikUit where motion detection is same as button on/off on a remote). Just choose the type in a list of provided controls. Yes,The new device builder supports pre-defined controls
And, how does this look from a developer's perspective, how to create a form with these options: https://t.co/FlRUahDqTI. The screenshot shows how you could possibly provide your end user with pre-defined controls. Just set some defaults yourself, pidome does the rest
When a device type is unknown, but is able to do different things with the same signal (Like KlikAanKlikUit where motion detection is same as button on/off on a remote). Just choose the type in a list of provided controls. Yes,The new device builder supports pre-defined controls
When a device type is unknown, but is able to do different things with the same signal (Like KlikAanKlikUit where motion detection is same as button on/off on a remote). Just choose the type in a list of provided controls. Yes,The new device builder supports pre-defined controls
New milestone in the rewrite, devices controlled by RFXCom (KlikAanKlikUit). Now starting to finish up features not yet fully implemented like premises, multidatabase support, user management (guests and persistent) and module updates without restarting.
Had a really nice and productive evening with @GeertjanW , Catching up, talked technology, #Chess game, #PiDome, #NetBeans, #JavaFX and #OracleJet. He's really a inspiring and energetic person. I'm having too many good ideas now.
On Bitbucket there is a Project named "Retired". This project is getting less and less repositories. If looking for a specific repo, and it's not there it is being or has been migrated to the rewrite. Look in Platform, Drivers, Clients or Modules.
Original server has nashorn implementation for creating drivers (https://t.co/H4Rh6yh85k). With the rewrite i'm wondering if this feature is a must or a could have. This affects the development timeline and will depend on graaljs usability in the JDK (research required).
Some advanced features are being added to the rewrite, one of these is the ability to create a cluster of installations. This allows assigning a dedicated install for heavy duty tasks, assign dedicated premises when you have a LOT of devices and a dedicated event handler, etc...
Some random user details screenshots of work in progress in the minimal mobile web interface.
- Real time password hints,
- User personal connections with external services
- Generic UI and geofencing settings
Initial screen of a data driven form. Section for grouping, DisplayField for label en text, SelectField<Enum> for the dropdowns with default values selected. Thinking of it. Possibly develop a CollapsibleSection which one could name "Advanced" (for DTR/CTR, etc..)