![]() I don't know why he's not active at the moment though. ![]() He'll than add the components to the database library and merges the pull request. Therefore the contribution to this library is done by adding the components to the relevant libraries and (currently) passing the part number and digikey listing for the parts to Mark. The idea of this library is to have the components in libraries which are under version control by GitHub and a hosted database which links the schematic and footprint libraries together and lists all the relevant parameters for that part. These parameters can be used to filter in altium designer (AD) e.g. Now, I don't know how snapEDA works since I've never used it but, this library has high quality 3D models and a whole lot of parameters listed with each component. Please feel free to ignore these questions, though - I can fully understand how plowing through tons of messages on a public account can become a To come back on the last section of your fist comment. Am I missing something or the "community" update process (like adding new components) is indeed somewhat complicated?Īnd another question: Would you be fine with someone distributing the library using Torrents? Not that I know anyone or am planning to do this, but I believe the deployment process could be done much quicker in this fashion. Are you planning to continue the development of this library, given how popular snapEDA is? If so, I couldn't find an easy way of adding the components to the library from the AD itself, maybe only using things like SVNDBLib, which again I'm not very familiar with. Using the opportunity, I would also like to ask you about the contribution model for the library. The whole idea of local cloning will also help in the long run, if (when) you forget to update the Azure subscription, and generally is better for maintainability. Now, back to the point - if you could add the steps needed for the local installation, I believe that can save some trouble for new people. Besides, I'm not quite keen on Github's fork mechanics that demand users create useless clones of projects that they never intended to host on their page, and that whole process generates needless amounts of fuss. Now normally I would have made this a pull request but I'm not quite sure if the steps I have provided are optimal. Test the connection and follow through with the rest of the installation instructons ![]() Provider=SQLNCLI11.1 Integrated Security=SSPI Persist Security Info=False User ID="" Initial Catalog=altium_library Data Source=localhost Initial File Name="" Server SPN="" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |