Here’s an idea:
You know how dynamo has their own package manager?
what if instead of us suggesting an extension or ask the developer extension we can have our own public access package/registry.
This will take off the main pyrevit developer’s effort to approve a package everytime and have an automatic audit of anyone who suggest a new extension to be added (proper name/description/ file requirements/folder extension etc)
I dont think this would be a hard thing to do would it?
Dynamo packages are comparable to functions or classes. Comparable to pyRevit’s API wrappers. These are core to pyRevit. Such as pyrevit.forms or pyrevit.script. You can of course add to this through the normal course of pyRevit development. You want more forms? Write some and add to the core of pyRevit.
But what you’re more likely wanting is pre-digested functions - code snippets. I don’t think that fits in as well to the development flow of python like it does in dynamo. There arere plenty of good resources on github for good pyRevit code and the extensions are a good way of seeing how others have approached a problem.
Personally, I find dynamo’s package manager the weakest part of the whole dynamo environment. It is heavily dependent on individuals that often change direction or abandon efforts. Or the code becomes no-touch and sealed in the dark. Not really in the full spirit of open source.
Anyone could start a library of functions on github to accomplish what I think you are after. And that might be a good tool for managing these sorts of snippets, functions and classes. It would be more open for collaboration than dynamo packages.
What sorts of things are you looking for?
What Aaron stated
Plus
You don’t want to add something that is doomed to be stale.
The maintainance of a new exposed surface of pyrevit. This is already a monster with very little contributors and maintainers.
The infrastructure necessary: webserver or web service, db, …
And it’s associated cost.
For me it’s a no, but this is just my opinion
