| Electronics > Projects, Designs, and Technical Stuff |
| uSupply Firmware Released |
| << < (9/11) > >> |
| Gonzy78:
Dear Dave, Will it be open hardware ? I am quite interested you detail the input USB-C part of the schematic. This is neat stuff. USB BC V1.2 is way much easier than type C PD ... About what we have seen so far, the design looks interesting. I didn't read all about on the forum, is there an official topic ? I can't see any battery to fit inside. A supply with embbeded battery would be a killer. You can take your gadget in the meeting room, or on your desk without taking the heavy supply from the lab and wires ... If you need, I made a custom size lipo this year with my team. I know how to do this, manufacturers, import, certifications, quality control, ... Plenty of work but worth every cents. The dream would be with banana and usb output. The usb output would be killer feature, it would able negociate with the sink. You choose what kind of charger/protocol you want test with your new fashion gadget. Maybe you didn't thought about that. It's a free idea ;) I hope see that in the shop soon. It's on my wishlist for santa. We all hope more videos about your work on this project. Thanks for reading the comments Dave ;) |
| MiroS:
--- Quote from: Dave on May 27, 2020, 10:14:58 pm ---You linked in an ancient project coded in FORTRAN (I only know this because I actually searched for the SPICE wiki). I can't possibly comment on a programming language which I don't know and have never used. If the language does allow for splitting the code into multiple files, then 18k lines in a single file is in fact terrible coding practice. --- End quote --- It is not matter of used language. That FORTRAN pice of code is still in use and formed the foundation for modern electronics, so there is nothing to comment on this from your end, but there is a lot to learn from for everyone who is going to write the code - how to write it to let others use it , modify , improve , document , enapsculate , reuse , maintain ... |
| diyaudio:
Dave and David thank you for contributing to the open source initiative, I learned a few things I didn't know about CMAkE could do like the integration with visual studio code which is my Editor/IDE of choice. :-+ |
| wizard69:
--- Quote from: NivagSwerdna on May 26, 2020, 07:58:23 am --- --- Code: --- const char * volatile current{ []() -> const char * { --- End code --- I'm pretty sure it is Klingon. Live long and prosper. --- End quote --- One of the reasons for my love/hate of C++ is this very cryptic syntax if you are not involved in C++ full time. We need something better than C but what that might be is unknown at the moment. I actually think Apples Swift could have a lot of potential once it is fully fledged out as a language. The problem with C++ is that you have to mentally parse every statement instead of simply reading it. I can write something in Python and read tte code 5 years latter, write something in C++ and you may spend a considerable amount of time just figuring out what is going on even if it was written 5 weeks ago. Of course with discipline C++ can be made idiomatic but that means leaving modern features behind. |
| wizard69:
--- Quote from: EEVblog on May 26, 2020, 11:14:55 pm --- --- Quote from: ataradov on May 26, 2020, 09:52:07 pm ---And yes, this C++ heavy code is very hard to read, and the whole functionality could be implemented in a much-much smaller code. --- End quote --- Not a comparison because the features aren't even remotely the same, but for those interested, previous versions of my uSupply written by me are 389 lines and 479 lines for two of the design variants. That's everything, including comments, UI code, control code etc. Not sure I'd like to guess how many lines this version of the uSupply would have taken me in "Dave C", but yes, it would been vastly different to the way David writes his code. I just let him do it the way he wanted, we have vastly different styles. But he writes games engines in his spare time for fun, and I wouldn't know C++ if it bit me on the arse. --- End quote --- I think most people here are pointing out the general difficulty one can have in reading somebody else's C++ code. Dave may have a good solution here but for a third party reading the code it might take hours to understand the structure. That is just one of the issues with C++, but I do wonder how long it would take Dave to grasp this code 5 years down the road with no refresh in between. In the end the only thing the code needs to do is work correctly. The good code organization is a positive indicator here so I'm not worried. Frankly I'm waiting for you guys to ship. |
| Navigation |
| Message Index |
| Next page |
| Previous page |