Looks good. Ok, save locally and use USB stick for manual loading on the RS. However, just because we are off-line to the internet should NOT mean that we are not given the option to send the file to the RS on our personal LAN (local area network, either hardwired Ethernet or WiFi ( I think the RS is WiFi only, but not sure). We should now go back and ask Heygears to give us the option to send the file over our LAN to the RS. No reason that can’t be done easily by Heygears!
@ Thanks! Since I have your attention, allow me to pass along my thoughts on this whole matter (how I see it): 1) As a “consumer” or “company”, we would prefer software to perform its primary function “offline” as the default mode. We would like to establish an initial “log in” and “authentication” (choice of “password only” or add “two-factor authentication” for both “password and 6-digit code sent by text to a phone number, that is then entered into the software for confirmation” for more-secure log-in. After initial log-in the first time, this is established so Heygears can provide “automatic notifications of new Blueprint software updates and Reflex machine firmware updates” that show up in our current Blueprint software on our PCs or Macs. We (the users) should choose when to download and install these software and firmware updates, and it makes sense for Heygears to ask for our login and authentication info before the download and installation occurs. (2) Other than initial login and authentication, “internet access to Heygears backend servers and support” should be optional. Heygears should provide a “button” in Blueprint to enable access to Heygears backend servers and support-by-internet, if, for example, users want access to “support chat services” or other “services located on Heygears servers” that Heygears wants to offer (free or paid). (3) Regardless of internet access, user login/authentication to Heygears servers, users should always be able to use the full features of Blueprint software and either save output files locally (for USB stick or later send to all networked Reflex machines) or in Blueprint just send the output files directly to any chosen networked Reflex machine (4) Have a “file system” on each Reflex machine so users can access one of several recently-loaded “output slice files”, in case a user wants to reprint these files. (5) I have other thoughts, but this message is long, so I’ll stop here.
Looks good. Ok, save locally and use USB stick for manual loading on the RS. However, just because we are off-line to the internet should NOT mean that we are not given the option to send the file to the RS on our personal LAN (local area network, either hardwired Ethernet or WiFi ( I think the RS is WiFi only, but not sure). We should now go back and ask Heygears to give us the option to send the file over our LAN to the RS. No reason that can’t be done easily by Heygears!
Don't worry, we are working on the LAN transfer 😎💫
@ Thanks! Since I have your attention, allow me to pass along my thoughts on this whole matter (how I see it): 1) As a “consumer” or “company”, we would prefer software to perform its primary function “offline” as the default mode. We would like to establish an initial “log in” and “authentication” (choice of “password only” or add “two-factor authentication” for both “password and 6-digit code sent by text to a phone number, that is then entered into the software for confirmation” for more-secure log-in. After initial log-in the first time, this is established so Heygears can provide “automatic notifications of new Blueprint software updates and Reflex machine firmware updates” that show up in our current Blueprint software on our PCs or Macs. We (the users) should choose when to download and install these software and firmware updates, and it makes sense for Heygears to ask for our login and authentication info before the download and installation occurs. (2) Other than initial login and authentication, “internet access to Heygears backend servers and support” should be optional. Heygears should provide a “button” in Blueprint to enable access to Heygears backend servers and support-by-internet, if, for example, users want access to “support chat services” or other “services located on Heygears servers” that Heygears wants to offer (free or paid). (3) Regardless of internet access, user login/authentication to Heygears servers, users should always be able to use the full features of Blueprint software and either save output files locally (for USB stick or later send to all networked Reflex machines) or in Blueprint just send the output files directly to any chosen networked Reflex machine (4) Have a “file system” on each Reflex machine so users can access one of several recently-loaded “output slice files”, in case a user wants to reprint these files. (5) I have other thoughts, but this message is long, so I’ll stop here.