Updating the compiler is on my 6.1 list. This doesn’t necessarily mean that it won’t happen until 6.1, it just isn’t necessary to be completed before shipping an initial release of 6.0.
In other words, it is on my short list
This is a project that I would love to see get started. It seems like we could make an open source module that wraps up Eto functionality and exposes it in an easy to use in a ‘pythonic’ way. Docking dialogs specifically are going to be tricky and will require some changes in Rhino first.
I’ve mentioned this in the past, but it’s probably worth repeating now that this the Python functions are being addressed. Can we have the various listbox windows remember their previous locations? If I recall correctly, PropertyListBox is the only one that will open in the last place it was closed. All of the rest revert back to the top left side of the screen.
I would like to see rhinoscriptsyntax functions for splitting and trimming surfaces using a curve (or curves) on the surface (instead of using a brep as is used in the SplitBrep() and TrimBrep() functions). The functions could be something like:
Where surface_id is the guid of the surface to be split/trimmed, curve_id is the guid (or list of guids) for the cutting curve(s), and point is a 3d point on the surface indicating which portion to delete during trimming. The SplitSurfaceByCurve function wouldn’t have to be much more than a wrapper around the RhinoCommon Brep.Split method, but would hopefully be easier to use for those who aren’t as familiar with RhinoCommon.