I haven’t written up the documentation for blueprints yet. Basically this feature allows you to convert the entire database into text files — all of the settings, preferences, field definitions, form objects, everything. Kind of like freeze drying. Then later you can “reanimate” to create the database again.
The primary reason I invented blueprints was for use with source control systems like git. These systems allow programmers to track the exact changes made to a program over time. Then if something winds up broken, you can see exactly what was changed and when. I use git to track all changes made to Panorama X, including the code written in Xcode and everything in Panorama’s libraries and wizards. The latter are exported as blueprints which git tracks.
At some point perhaps I’ll teach a class on how to use git with Panorama, but git itself is a pretty big topic.
By the way, if you simply want to make a copy of a form in a procedure, it’s probably easier to use the exportform( function and the importform statement. That’s what the View Organizer wizard uses. For example, if you have a variable that contains the name of a form in the current database, this line of code will make a copy of it.
importform exportform(formname),”name”,formname+” copy”
At this point, you have to choose one or the other. Either use the print statement for the dialog, but then you have no control over the options, or use the printtopdf statement but then you can only control the options provided. Perhsps someday there will be a way to use the print dialog but supply default options, but that is not something that is likely in the short term.