Le ven. 2 déc. 2022 à 03:01, Kurt Jacobson <kurtcjacob...@gmail.com> a écrit :
> > I have been busy starting a family so have been completely out of the > LinuxCNC loop lately,glad to see most of the old familiar names still > active, as well as the new ones! > "Starting a family" ? Good one ! This never, ever ends LOL Very glad to have you back on the field Kurt :) I have not thoroughly read this thread, but I have read enough to be > discouraged by some of the things said. > Don't, please. We are, for once, discussing big matters in a handful of threads, and that is good ! We may have diverging visions, contradictory opinions and incompatible plans, but at least we are putting them on the table. And we all know what a traitor e-mail communication can be... at least I, as a hot-headed, irreverent, chatty Mediterranean, have paid that price often enough :-/ Lets good willingly receive fears and (fair, well-argued) criticisms, and welcome ideas be they old reborn, new or even "disruptive" as they say ;-) As far as I know, we are all here for the fun of a good mental > challenge and to enjoy some time away for the usual stress of work > and life. I don't think anybody is trying to compete in any but a > constructive > manner or "steal market share" from any other GUI project. > To the fun and mental challenge, I'd add the great will of Open Source: making the world a better place. This is an important point as its consideration may heavily impact the project vision from a garage tinkerer software, to a world class project FOSS project for users, developers, education and professionals. > IIUC, @hazzy had a "control agnostic UI" vision in the beginning. That > > could explain why the project was created outside LinuxCNC. > > But others may have better knowledge of the whys and hows... > > > > You are 100% correct. I'm not sure where the rather obvious bitterness > over > the QtPyVCP project originated, but I can explain why I chose to start a > seperate Qt based VCP toolkit. > Let me try an explanation... the developers' loneliness and frustration to see someone start something new instead of joining forces whereas they already painfully lack of it ? Push that into communication traps... And here we are Here is a quick history of the origins of QtPyVCP which may prove helpful. Thank you so much for writing this down ! 🙏 This part _must_ be copy-pasted in the "About" section of QtPyVCP's doc, as this gives the missing contextual understanding of the project that is the bond with LinuxCNC While QtPyVCP has remained much closer tied to LinuxCNC-only than I > originally hoped, I believe it has been successful at lowering the > barrier to > creating and sharing custom user interfaces. > True, and I believe QtVCP, the nice UIs built with it, and its extensive (learned it to my expense 😅) documentation does the same. Anyway, they are the modern toolkits rocking the stage nowadays, with people behind them, ideas to develop and will to go forward... Let's focus on that and walk along ! Important question is, does QtPyVCP vision still holds that control agnostic strategy, how deep, and to what end ? From that essentially may depend the soundness of the project joining LinuxCNC's. > Indeed, considering the success of QtPyVCP, as an outsider, it doesn't > seem > > to impede its development and progress ! > > I think the very fact that it is a seperate project is what has made it so > successful. It is much less intimidating for a new user to contribute to > a small > focussed project, than a massive sprawling code base like LinucCNC has > become, and this is why I believe QtPyVCP should remain at least in a > separate repo. > Can't agree more ! I'm surely not advocating main repository split to invite QtPyVCP to an additional big merge 😅 This is also exactly the point I was making some time ago: subprojects buried into main repo get their lifecycle slowed by the necessarily long one of the core, as well as their overly tight (vs intimate, which is good) link with the code base, tests, docs and build system is holding back their evolution (or withdrawal !). > > > I'm sure neither project wants their years of work trampled on. > > As I said before, I believe most if not all of us are here for fun and to > enjoy > > working together. > If I Was under the impression somebody thought I was trampling on their > work, I'd move on to a group that encouraged constructive turning up of > the > ground! > In such case, you wouldn't go anywhere alone... TY J _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
