| ID: | 5684 |
| From: | rn...@igor2.repo.hu |
| Date: | Thu, 9 Jun 2022 09:01:17 +0200 (CEST) |
| Subject: | [pcb-rnd] RFC: project file considerations |
| replies: | 5695 from rn...@igor2.repo.hu , 5696 from Nicklas SB Karlsson <nk...@nksb.eu> , 5697 from Nicklas SB Karlsson <nk...@nksb.eu> , 5700 from ka...@aspodata.se |
Hi all, this is going to be a thread about comments on a very specific set of proposals being implemented in sch-rnd. I am posting it here because it will affect Ringdove as a whole, including pcb-rnd later. This is NOT a write-only thread: please DO READ ALL MATERIAL BEFORE REPLYING. Please write only if you first invest the time to really understand the topic. (If you can't afford the time to read the material, thats' fine, just don't reply then.) I am not interested in generic opinions about project files, I am interested in comments on details of these specific documents. So please think in the frame of these documents, using the terminology of these documents - that's the only way to contribute to them. Starting some random brainstorming from scratch "because it's related" won't add anything but noise. There are two documents that need review and comments. First, this one explains all the different ways we could related to project files (so it's background theory), within certain assumptions/limitations explained in the abstract: http://repo.hu/cgi-bin/pool.cgi?project=sch-rnd-aux&cmd=show&node=prj_archs Then this one, building on the above, explains the implementation and practical scenarios I am experimenting with in sch-rnd: http://repo.hu/cgi-bin/pool.cgi?project=sch-rnd-aux&cmd=show&node=prj_corners What I am interested in: - if any of these specific ideas would conflict with how you already use your favorite sch editor (in case you consider switching to sch-rnd) - if any of these specific ideas would conflict with how you already use pcb-rnd (in case later I implemnet the same thing pcb-rnd) - if there is any trivial, natural feature/scenario missing from the current design (prj_corners) that _you_ actually need - as always, I am interested in YOUR use cases, not in "whatever you can imagine" or "something that you don't need but could be useful in general or for someone else" Best regards, Igor2
Reply subtree:
5684 [pcb-rnd] RFC: project file considerations from rn...@igor2.repo.hu
5695 Re: [pcb-rnd] RFC: project file considerations from rn...@igor2.repo.hu
5696 Re: [pcb-rnd] RFC: project file considerations from Nicklas SB Karlsson <nk...@nksb.eu>
5697 Re: [pcb-rnd] RFC: project file considerations from Nicklas SB Karlsson <nk...@nksb.eu>
5700 Re: [pcb-rnd] RFC: project file considerations from ka...@aspodata.se
5701 Re: [pcb-rnd] RFC: project file considerations from rn...@igor2.repo.hu
5702 Re: [pcb-rnd] RFC: project file considerations from Nicklas SB Karlsson <nk...@nksb.eu>