In jaPBe, a project is a list of files saved as .pbfl file.Q*bert wrote:1) Can someone explain jaPBe projects to me?
a) Do you reopen a project by opening the .pbfl file?
b) Are there other advantages to using projects beyond (a)
If your project only has one file, saving as .pb is enough.
PureFORM is still in development.Q*bert wrote:2) What is the best way to use the PureForm plugin to maintain forms within jaPBe projects?
a) Should I create a separate .pbf file, use "Save as code" to create a separate .pb file and add it to the jaPBe project, or use the code windows "Copy code to jaPBe"?
b) If I later modify the window/gadget code, do I always need to use "Translate from source" to get the changes recognized in PureForm, or is there some way to have PureForm rescan the code automatically?
Currently, to update a source, I maximize the CodeView window, then copy and paste the code changes in my source, and then minimize the CodeView.
The "Translate from source" feature is convenient to import forms from sources not created with PureFORM, but not to update an existing form, as you will loose some information (not all PureFORM features are implemented in the import routine).
I am working on an 'automatic' source update feature, but I am still not sure how to do it. PureFORM will probably have to add some 'code tags' as comments in the generated code and update the code in your source between the code tags. I will probably also add some 'code inject' feature.
But this is WIP ...