Time for a complete re-write or start over with v2 of DWC
-
@oliof It sounds like @deckingman may have an ethernet board rather than one using WiFi. My experience (with a Duet2 Ethernet based board), is that wired connections to Duet boards are significantly slower than WiFi based ones....
But for most people I'd guess that speed is not really a big deal. I'd say some of the UI issues are more important.
-
@gloomyandy his ethernet board is still about 60% faster than my STM RRF board on wifi. I agree the UI aspects are worth discussing, but this thread was about speed originally, so I am trying to stick to that topic.
-
I've no idea if any of this is relevant, especially as I'm not too concerned about the speed of DWC but I'll throw it out there anyway as people were commenting about board types and wired vs wifi etc.
Uploading a circa 40 MB gcode file from my aged wifi connected laptop to the printer via DWC takes around 58 seconds at a reported transfer speed of around 750kbits/sec. Uploading the same file via my desktop Ethernet connected PC takes about half that time at a reported speed of roughly 1.6Mbits/sec. Transferring that same file from my Desktop (Ethernet) PC to my aged (WiFi) laptop takes around 3 seconds (no idea what speed that was because it happened too quickly for me to catch it).
All that means is that transferring a file to my printer SD card is about 10 times slower than transferring the same file, from the same machine, to a (aged and slow) Laptop, but it probably proves nothing. It's not my field of expertise by any means but I guess there area number of things at play here, not least of which would be the write speed of the SD card and/or the size of any cache files? It probably has nothing to do with DWC.
-
@fcwilt that's a big part of it. Panel Due leaves a lot to be desired, doesn't it makes sense it SHOULD work on a tablet or mobile just fine?
-
@owend true, but it was written with a framework that is very hard to cone up to speed on for the sake of a hobby.
-
Thanks for the discussion. To clear up some, the point of my post wasn't entirely about speed and certainly not about speed on the desktop.
I ran out of steam and couldn't really get to the mobile device timings. I was hoping to make my point about performance through comparison using the desktop and then implying just how much more burdensome it is on mobile.
There are other points in the post besides performance, if you have the time to read the whole post, please do.
I'm happy to try do more requirements gatherings if interested.
-
@gnydick both the klipper interfaces (fluidd and mainsail) are also written in Vue and Javascript and both actually have their origins in DWC and they seem to do pretty well in terms of features etc.
Hopefully in the future we see DWC getting some more love -
@jay_s_uk yeah, it's totally possible. I have a Voron 0.1 and suspected the heritage. These interfaces are swifter but do also suffer from the interactivity issues, some are worse.
-
@gnydick said in Time for a complete re-write or start over with v2 of DWC:
@fcwilt that's a big part of it. Panel Due leaves a lot to be desired, doesn't it makes sense it SHOULD work on a tablet or mobile just fine?
I'm not a big user of my cell phone for other than calls nor my tablet.
But I know from my programming history that each of those requires a "dedicated" interface design to provide the best user experience. The interface designed for a large computer screen cannot simply be re-used on those smaller screens.
I have noticed many times that web sites I visit using my computer often have very poor implementations for cell phones in particular.
Frederick
-
@fcwilt it's not the differences between desktop and mobile designs, they're actually the same. It's the difficulty in using it with your finger. It's not very touch friendly in the way the controls respond.
For example, I'm scared to death to tap a dialog popup to dismiss it for fear of accidentally tapping whatever is underneath it. Head crash anyone?
The popups should not auto disappear, nor should they be modal.
-
@gnydick said in Time for a complete re-write or start over with v2 of DWC:
@fcwilt it's not the differences between desktop and mobile designs, they're actually the same. It's the difficulty in using it with your finger. It's not very touch friendly in the way the controls respond.
I've done both desktop and mobile designs and for anything complex, like the DWC, they needed to be quite different to be user friendly. At least my idea of user friendly.
Android phones and Apple phones can need different code. Android tablets and iPads can need different code. Apply computers and Windows computers can need different code.
It's not fun and I don't do it any more.
I have not tried to connect to DWC via anything other than my computer. I know I would find it an frustrating experience.
Thanks for the feedback.
Frederick
-
@fcwilt yeah, I was using a different meaning. I was referring to layout using css so you build one page and if you're on mobile it looks one way and on desktop, another.
-
@gnydick said in Time for a complete re-write or start over with v2 of DWC:
@fcwilt yeah, I was using a different meaning. I was referring to layout using css so you build one page and if you're on mobile it looks one way and on desktop, another.
Vue.js has a mode already to decide from sreen resolution and orientation how to display elements, e.g. for a wide tablet screen left-right and mobile top-down.
But this doesn't solve the problem that if there are too much elements, to show
them on one page. IMHO a solution is to add a configuration setting page (and the setting being persisted) where the user decides how to solve it: all details, but only one parameter. Or all details and all parameters, but without spacings, as dense as possible. Another setting could be as much information as possible on one page, or using the tabs and navigation. Or a button "show details". The configuration setting can store the order and position of the personal preference where to see which details also. My wish is to add a "lock all dangerous buttons" button for usage while printing. Another example is, someone with lower eyesight wishes bigger fonts at cost of less information, another user maximum information with small fonts.The disadvantage of individual settings is that help becomes more difficult, but this is a common problem of individual versus standard solutions.
