Would you be interested in a Creo coniguration editor?

This is super cool… It is obvious you are overcoming frustrations and streamlining the process for discovery and configuration.  Looks very focused, practical, intuitive vs the typically disconnected and obtuse UX we suffer across multiple applications (probably designed by people who do not actually use the software).

AI is amazing these days - good judgement is where the game is.. thanks for demonstrating that by example.  #KeepGoing

Dave 

The only question I have is whether it would be possible for this tool to package an installation directory as a drop-in package.

Most supplier packages we install for Creo environments typically require running a setup.exe first, followed by a separate executable that installs the supplier-specific files. From what I've seen, this tool appears to have the ability to browse and work with the configuration folders already in place.

One of our biggest challenges is that storing all Creo files on our network drives results in slow performance, and I don't think our infrastructure will ever consistently provide the speeds needed to make that approach practical.

It would be very helpful if there were a utility that could package an additional local launch package, allowing the necessary files to be installed or cached locally while still maintaining the required configuration and supplier-specific settings.

Another feature that would be extremely valuable is the ability to parse xtop.exe and identify all active configuration options available in each Creo build. Currently, the only person I'm aware of providing this information consistently is Olaf Corten through his Creosite website. While his work is greatly appreciated, it would be beneficial for administrators to have a built-in method of tracking and validating configuration options directly within the tool, rather than relying on a third-party resource to maintain that information. This would make it easier to stay current with changes between releases and improve overall configuration management.

I would definitely be interested in testing this and providing feedback based on real-world use. Whether you decide to implement my suggestions or not, I'd be happy to help evaluate it and identify any issues or opportunities for improvement.

One recommendation I would make is to consider hosting the project on GitHub. Even if you're primarily developing it yourself, making the code available would allow other users with more programming experience to contribute enhancements, submit bug fixes, and help expand the tool's capabilities over time. It would also provide a centralized place for issue tracking, feature requests, and community collaboration, which could help the project mature much faster than relying on a single developer.

There seems to be a genuine need for better Creo administration and deployment tools, and I think there are a lot of users who would be willing to contribute if given the opportunity.

I created something similar called ConfigWiz. But I took it down as it was too hard to maintain. I can share the code and workflow if you like to look. Maybe I should put it back online.