I have already been using
info("formevent") on a couple of my current projects (check out my use in the Variable View file I posted some time ago) and it is a reasonable substitute method to replace …ActivateForm & …OpenForm. The minor downside is that the old auto-procedures handled everything in one procedure rather than in individual form code. I actually like it the new way much better especially if there was some way to incorporate it within the datasheet as well.
If there is no plan for the …CustomAbout or .About procedures or their equivalents then that does not bode well for the future ability to create true stand alone projects based on Panorama X. Any such custom apps running under their own name would add a level of confusion if the About menu was showing another app’s name instead. This would of course be a moot point if a stand alone scheme is never implemented in Panorama X like the old Panorama Engine…ouch!
For me the …CloseDatabase is sorely missed especially with all the auto-save that the current system software incorporates. You never know what exact state Panorama X was last saved in so it might then reopen differently than you would prefer. In Panorama 6 you could have it open every time with no windows and have the .Initialize procedure regenerate the exact conditions you want on startup including a temporary custom startup form.
As you can see my biggest concern is in regard to being able to use Panorama X for creating independent apps. If the app is a freeware product the cost for the developer to ProVUE should be minimal as it was in the past. Commercial apps could be a one time charge as before or set up with a royalty scheme where the app developer and ProVUE partner in the commercialization, possibly even via the App Store. Don’t mean to proselytize but keeping my fingers crossed.