Solved a problem for myself with an extension but not sure how to share the script

Hi everyone,

I’ve been a longtime pyRevit user, but I just used AI to build my first extension. It solves a problem I’ve ran into many times, and now that it’s working so well, I’d love to share it with everyone. The catch is, I’m an architect, not a developer, so I’m not sure about the best way to do that.

My extension searches for all the textures in a project and relinks them, even if they’re in different folders. It works extremely well and is incredibly fast, and I’d be surprised if I’m the only one who has ever dealt with this issue!

So, I have two main questions for the community:

  1. Would anyone be willing to look over the code and make sure it’s good enough to share? (After all, it was created with the help of AI!)

  2. Could you point me in the right direction on how to best share it (e.g., a zip file, GitHub)?

Thank you!

1 Like

Hi, Welcome,

  1. Bring it on, here
  2. Who do you want to share it with? Team, general public, as a pyrevit tool in the main toolset, as separate extension but listed in the list of extensions available within pyrevit?
1 Like

Here it is :GitHub - Swichllc/Texture-Relink: Find and automatically relink all missing textures for your Revit project
And sharing in the most easy way for most users, I really don’t have a preference, just want to spread it to hopefully help other users with the same annoying issue of missing textures.
Im working on making a quick demo video to add to the repo

1 Like

Here is the demo - https://youtu.be/Ao4t1zupCVU

2 Likes

Pretty cool vid and tool
Allow a couple of days before I can have a look and review.
First thing I may propose us review the UI UX, having a single window and no need to reopen the tool

2 Likes

Thank you,
Yes, the need to reopen the tool was a sacrifice I couldn’t solve, since I used AI to build it, and it kept having issue with 2 functions one button, I decided to concentrate on the functionality of the tool, and not continue struggling with the UI/UX - it does only take another second after all.
But Yes, if anyone care to improve it, I do not have any objection.
Im just happy it saved me so much time, and hopefully Im not the only one who this can help to.
And I cant wait to build more tools to solve more annoying issues

1 Like

I think this could be part of the base tools of pyRevit.
I don’t know how much you are familiar with the whole PR/github shabang, if not I could make the PR for you.

Im assuming you are talking about adding it to the pyRevit repo,(I might be completely off), but I know how to create pull request for my own projects, sending it from my IDE to github, not sure how to create it in a project I dont own - but since I want to try and make more contributions, I should probably learn.
In the meantime, yes, if you could create it for me that would be great.
Thank you

In my experience the simplest way to do is using a server / cloud drive where everyone could have access.

I use de server of the company to store the extension folder, then all the user map this folder on their pyRevit config.

In my machine I have a local folder where I test the tools, when ready I move the tools to the server folder.

Not the most fanciest way but it works and no need of Git / CLI knowledge.

Hope it helps.

Hi @AntonioRojas01
I’ve been using all kind of methods, but it was never working perfectly, your method is not always great if you go meet a client in their location for example, so there is also an option to use same folder path and add that path to Revit’s settings, but that also doesnt work every time.
This plugin doesn’t require any git/cli knowledge - as it is right now - its just dropping the files in the right folder and reload pyRevit - and it relink everything even if the textures are in a different folder.
As I said, it solved a problem for me, not for everyone, and Im just sharing it

ok, if you know how to basically create a PR, easy:

  1. clone the pyrevit repo locally using github desktop for example
  2. open the folder containing the pyrevit code in your code editor
  3. add your tool somewhere logical in the pyrevit ui
  4. make the commit and then the PR
2 Likes

I will give it a shot, thank you

Thank you for sharing your ideas.

Fun fact, most people in this community are architects, engineers and Design technologists. That’s the point of pyrevit as a RAD tool where it makes software improvements for revit more open and accessible to the community.

Also most of us uses AI but then we are continuously trying to learn in parallel.

Looking forward to see your contributions more here. and on Github.

This is great to hear, making this journey much less scary.

There is definitely a learning curve, I’ve seen all the comments on the PR and I’m using that to learn too..

Can’t wait to finish with this one and try to contribute with more scripts…

Thank you

1 Like