Hi McNeel Team, Bugs with Disclaimer: this is a real horror movie. A non-comedy of errors. A mistaken identity of a rough WIP with any level of production software: Thanks goodness I only needed this to make some Holiday custom pint glasses, not for something actually important. Do …

[image] RIL: I understand the frustration. But it’s not so simple to “test everything”. You don’t. And you don’t “fix that which isn’t broken”. Until you know it’s broken, that is. Thanks for your input Rolf, you bring up some really good points, yet I would like to challenge the approach you…

[image] gustojunk: QA is a thing. I’m an ol’ QA consultant. (that’s where I got that “you tested only what you tested, nothing more”. :wink: I won’t debate with you about the most critical functionality you depend on in your daily (as for me I mostly crunch terribly bad meshes from MRI & CT …

[image] RIL: Anyway, software development is still a bit of black magic I know you know this Rolf, but for others’ benefit: There’s a heck of a lot of science that can be applied to it these days. One piece of science involves making testing the primary focus of your effort rather than an a…

[image] jeremy5: I know you know this Rolf, but for others’ benefit: There’s a heck of a lot of science that can be applied to it these days. TDD is and sounds ideal. But, the basic problem remains - namely no matter what strategy or concept you are following - you are still testing only tha…

I’m open to change. Any suggestions on how to improve our development processes are appreciated. Here’s our process for fixing bugs and adding features. I’m going to strictly refer to requests made by users here on discourse. Features and bugs are gathered from many other sources, but for the sake …

[image] jeremy5: In this culture a piece of software cannot be released at any time when one or more test fails. Therefore a new release cannot break something that previously worked. TDD dates back to the late 90’s (embodying much earlier concepts). We do employ TDD, but we could do a lot b…

[image] stevebaer: I’m open to change. Any suggestions on how to improve our development processes are appreciated. Hi Steve, I want to write this as respectfully as possible. You know just about all Rhino users appreciate the hard work you and the rest of the development team do to bring us…

[image] stevebaer: We definitely can do a lot better here for more cases in these areas, but I don’t know of good ways to set up TDD for user interface adjustment which would be for things like the boxedit UI. Hi Steve, I’ve been thinking more about this. I think we have enough historical da…

== NUANCED PRIDE == [image] gustojunk: you git used to just expect us to be the ones asking you to clean the register belt. And just because it seems normal to you, let em assure you thing: it’s not normal, at all. Hm. Let me add some nuances here, about “mature businesses” etc. I’m with you…

[image] gustojunk: I think we need to agree on a basic level of respect to customers where the most mundane stuff that hundreds of thousands of users use every day can’t just simply be that carelessly broken. I want them to take this 10X more seriously. And I think it’s perfectly reasonable. …

The horror the horror of exporting to pdf and illustrator

Serengeti (Rhino WIP)

brian (Brian Gillespie) January 12, 2022, 4:12pm 36

RH-44145 is fixed in the latest WIP

Topic		Replies	Views
Rhino 8 release - too early? Rhino windows	70	4207	March 22, 2024
Where is Rhino 6? Serengeti (Rhino WIP)	87	9161	August 14, 2015
Love for McNeel Meta	93	8230	September 22, 2024
Rhino: developing too slowly Rhino for Windows	82	8390	February 27, 2017
What are we paying for? Frustrations with Rhino vs. Open Source Rhino for Mac mac	22	5444	March 29, 2023

The horror the horror of exporting to pdf and illustrator

Related topics