For internal part numbers, are you wanting to assign internal part numbers for components (like connectors, etc.) used in an assembly or an internal part number to the assembly itself?
An internal part number for the assembly is coming soon, but the internal part numbers for individual components is not something that's planned right now.
Currently, all wires in a bundle (all wires between the same two connectors are part of a bundle) are forced to have the same length. Do you want to override that?
The connector graphics are not currently exported to WireViz YAML, so you'd have to re-link them manually with your own image file. The ability to download a zip with the graphics included is in the works.
I really, really want to like Vivaldi, but it's just so slow for me on Windows. It has a similar problem on Linux, though a restart a few times a day solves it.
In most cases convenience. Sometimes, you may need to share a password one-off (ex. https://support.1password.com/share-items/) with a coworker or a friend. Setting up something like that with keepass is not really possible.
If you want to manage passwords amongst family members, it's easier to set them up with one of the cloud services compared to Keepass. You also get some level of customer support, and don't have to worry as much about when your password breaks.
I personally have set up KeePass, made sure it's backed up regularly, and even set up a WEBDAV server to access it remotely. It works great for me, but I know how everything is set up. Strongbox for mobile access is the main reason I can actually use this, and this is a paid application that not everyone is willing to pay for. Experience-wise, other mobile applications for KeePass have not compared, and I have no idea how apps for Android compare, since I set up everyone with iOS devices. Sometimes, the connection to the server gets disrupted, and I have to reconnect.
Not everyone wants to do this, and can have less confidence in the other supporting infrastructure.
As much as attack vectors exist, the biggest risk is you losing access to your own passwords (there's been enough lost crypto wallets you can read about on the internet). Compared to that, a cloud based service is better for a large group of people.
Evoluent Vertical Mouse. Mouse lasted for about 4 years (the middle scroll wheel stopped working), and replacement mouse purchased is still going strong.
Honestly, I find that in many cases I would trust an anonymous random Joe more than a company because they can be more mission driven and limited in their ambition than a growth driven tech company. Firefox keeps trying to push advertising while keeping it private, trying to get people to subscribe to a VPN subscription. Google actively undermines adblocking extensions with Manifest v3 and Web Integrity API. Edge tries to monetize your browsing data by trying to randomly sign your browser in your Microsoft account and sync your bookmarks, history, and passwords to their cloud and keep trying to get you to use their chatbot. There are several more examples.
> Honestly, I find that in many cases I would trust an anonymous random Joe more than a company because they can be more mission driven and limited in their ambition than a growth driven tech company.
If it is a random Joe and not, say, a malicious effort of a major government posing as one. That's the problem.
Otherwise, your next best bet would be to add a notes file or folder with all your TODOs and notes that refer to lines in the source code and keep that in gitignore.
Our interfaces are simpler and bespoke compared to others. We create a document showing different components, how the components should be dimensioned, and also detailing of different interaction, theming, and animation conventions to be implemented. We try to provide enough detail so that a developer can reimplement in their tool of choice, and will schedule several meetings or screencasts with feedback as they proceed through their adaptation of what is documented. This document guides us in creation and modification of existing components. In several cases, need for new components can drive a complete rethinking of the system.
In separate document, we put the application screens, and navigation between screens only. We try to detail out all possible states of the application, elaborating them in writing in the file.
Finally, we have one more page showing variations of the interface to illustrate all conventions.
Biggest benefit is that all design assets can be exported in SVG format and used in actual application so the app is as close to the Figma as well.
Once you have working prototypes, I strongly suggest including videos of the actual implementation for reference and accommodations for limits of the tech stack used, because it may not match perfectly with the Figma.
Is there a way to add our own internal part numbers corresponding to manufacture's part number?
Can individual wires have different wire lengths?
Are there any features if when used won't render properly in wireviz?