ConfigWiz

[Michael]

Each release of Creo contains many new and removed configs. PTC provides a list of them in csv format. That got me thinking,,,

ConfigWiz is a web-based tool for managing Creo Parametric configuration files. It lets you clean, search, and organize configuration options across versions, with an intuitive interface for browsing by category with detailed descriptions.

I hope it’s useful, and I’m looking to improve it. It’s an open source project. Feedback and suggestions are welcome.

Give it a try and let me know what you think. 

ConfigWiz

 

[DavidBigelow]

BAD ASS!  Very cool!

One suggestion - don't use pulldowns for "yes" or "no" options - make them a thumbs-up/down icon or something that is more obvious to select and understand the state - avoid the pulldown selections for simple things.

Also - the text entry fields - if they have limited options for entry... then it should show the available options.

You need the ability to import a config.pro and show an overview of what areas of the configuration options are active and allow editing there.

Are you covering the "hidden" configuration options?

Dave 

[Michael]

Thanks. I like your suggestions and will implement. 

You can already upload a config file and it tells you what was illegal and you can keep editing from there. Though currently I strip out mapkeys. I’m going to add this capability. 

No I don’t allow hidden configs right now. They are technically unsupported configs. 

[DavidBigelow]

Might also be good to have pre-defined common configuration defaults for specific use cases that can be quickly selected, modified, and downloaded.  Performance vs Pretty.  Or specific configurations for specific use cases.

[Michael]

That’s great idea and on my list to add. Thanks.  

[tbraxton]

When a config file is uploaded to the site, how is the data handled and what can be done with the upload?

Suggestions:

Add an FAQ section that explains what the purpose/capability of the tools are.

Configurations set up for different drawing and tolerancing standards (ANSI/ISO). The drawing setup files would also need to be offered along with the config options specific to different standards. This would probably also apply to MBD setup as well.

[Michael]

Great thanks. Great ideas. I’ll add these soon.  

[DavidBigelow]

Since there are so many options by section…. You might consider search filtering similar to what I did for function browsing in CREOSON.

http://www.creoson.com/functions.html

This could be adapted for filter the screen to show only relevant content vs reading every block to try to find them.

Fell free to lift and adapt the scripts and widgets to implement in your end if you see value.

Hope this helps!

Dave

[Michael]

Thanks. I’ve used this great library - big fan!. I’ve added your suggestion - it’s a good and easy implement. 

thanks 

[ProFeature]

Hi @Michael 

Some definitions are repeated more than once. For example:

preferred_save_as_type Shrinkwrap
preferred_save_as_type step
preferred_save_as_type Stereolithography
preferred_save_as_type 3mf
preferred_save_as_type Wavefront

It recommends including the ability to use multiple lines for the same definition.

[Michael]

Thank you so much for pointing this out - I had completely forgotten that configuration options can indeed contain multiple lines and values. I’m going to fix that this weekend. Thank you!

These seem to be the configuration options that allow multiple lines and values:

1. preferred_save_as_type
• Allows multiple definitions for different file types (e.g., Shrinkwrap, STEP, Stereolithography, 3MF, Wavefront, etc)
2. search_path
• Multiple paths can be defined for locating models.
3. search_path_file
• Points to files containing multiple search paths.
4. protkdat
• Multiple entries specify different Pro/TOOLKIT application configurations.
5. loadpoint_path
• Allows multiple locations for external libraries or configurations.
6. web_browser_homepage
• Can be defined multiple times for different homepages depending on the context.
7. template_solidpart and template_solidassembly
• Multiple definitions specify various default templates.
8. modelcheck_dir
• Allows multiple directories for ModelCHECK configurations.
9. trail_dir
• Multiple directories for storing trail files.
10. alias_map_path
• Multiple entries enable mapping different alias configurations.
11. custom_palette_path
• Allows defining multiple color palettes.
12. dtl_setup_dir
• Allows multiple directories for drawing setup files.
13. mapkeys
• Supports multiple custom-defined mapkeys.
14. pro_font_dir
• Multiple font directories can be specified.
15. import_profiles_dir
• Allows multiple directories for import profiles.
16. export_profiles_dir
• Allows multiple directories for export profiles.
17. ui_customization_path
• Allows multiple UI customization paths.
18. material_library_path
• Multiple material library paths can be set.
19. symbol_instance_palette_file
• Multiple locations for symbol instance palettes.
20. layer_tree_cfg_file
• Multiple definitions for custom layer tree configurations.
21. bomber_output_format
• Can be defined multiple times to specify different output formats.
22. bom_report_format
• Allows multiple BOM report formats.
23. windchill_default_server
• Multiple servers can be specified.
24. rep_format_path
• Multiple directories for representation format files.

Did I miss any?

[pausob]

linear_tol
angular_tol