![]() ![]() ![]() ![]() We simply forgot to include the redistributable. Windows C++ redistributable needs includingĪh, this was an obvious mistake. So far we managed to successfully do this for both macOS and Windows, but Linux is the final challenge (we've done a bit of research into this in the past, and it seemed doable). Our aim is to get it working at the login screen for every OS (again, optional). So, since Synergy 3 now runs as a service on every OS (much like Synergy 2 did), it's essential that our Linux installers create the needed systemd files, to automatically start Synergy on boot (which will be optional, of course). Ok, so the original plan was not to release Alpha 1 for Linux, but at the last minute we decided to see if it was working on Linux and (with typing in an extra command) it worked brilliantly! The service needs to be installed on Linux We're not sure if it's going to be possible to run Synergy at macOS login if you use FileVault, but we'll sure try. However, this only works if you don't have FileVault enabled. Oh, and we also managed to get macOS working on the login screen in Synergy 3, which is brilliant. We may end up doing something like this to improve the UX for our less experienced users. Many apps have solved this by providing a help screen that guides users (or, rather, teaches users) how to use the macOS accessibility security settings. This actually worked OK-ish for Synergy 1, but we still get support tickets about this. The Apple design guidelines say something along the lines of "just prompt the user with the standard dialog" (but the user isn't entirely sure why they need to do this, and it can be a bit scary the first time. So, as the developers of such an app, this means that we need to work hard to create a good UX (user experience) when it comes to adding our app to the macOS accessibility security settings. But, it makes life difficult for users who want to use productivity tools such as keyboard and mouse sharing apps, remote screen viewers, and so on. MacOS Accessibility view in Security & Privacy preferences paneĪpple wants to protect their users from malicious software such as keyloggers, and make sure privacy is protected too from things like malware. The main problems we uncovered (and prioritized) were. But, crucially, those who do need to unlock advanced settings, well it's all there now for them to tinker to their heart's delight ( unlike Synergy 2). ![]() This was the whole design philosophy of Synergy 3 we wanted people who either didn't have time or experience to poke around with settings to be up and running in minutes. A few users managed to install without a hitch, and were going within minutes which is a far cry from what most people experience with Synergy 1. So, how'd the user testing go?įeedback ranged from "it just works", to "I get an error code" which is pretty much what we expected. However, we're going to take a more technical direction with Synergy Classic, since those who will be using it will likely be highly technical individuals. you're not going to be configuring Synergy all the time, so it'll be mostly closed).įor those who really don't want to use Electron (we get it, Electron is quite a heavy framework), we'll be including the old Synergy 1 GUI as Synergy Classic. We're sticking with Electron for the GUI as it's working out great so far, and it's a short-running process (i.e. However, we do have plans to rewrite the service using either Rust or Go (we're pretty close to making a decision on that) since using Node.js for the service is a bit of a memory hog. For our first prototype of the service, we decided to go with Node.js, so. This is actually a web technology, and most of the GUI code is written in JavaScript. The new GUI uses Electron, with React running inside. Our new Electron configuration GUI (graphical user interface) using React.A temporary prototype Node.js service written in TypeScript.The existing Synergy Core (this makes up most of Synergy 1 and is written in C++).How it's all put togetherįirst, a bit of background. ![]()
0 Comments
Leave a Reply. |