I need to save a form's current state and restore it while i am navigating between them. I am using FormManager class to navigate between form's. Is it possible to do that with memory handled efficiently?
bada Allows create up to 30 forms per application. You can use Frame::SetCurrentForm to make desired form active. But as i see you want have exactly one physically existing form at the time. Imho common mechanism to saving some state is not exists ( by the way what exactly states you trying to achieve to save? ).
You can try using some own (depends of what exactly you need) user-define format such as some template-based collection from Osp::Base::Collection
Related
Periodically, my database gets slow and I have to create a new database and import all my forms, etc. into the new database. For some reason, all my form control settings (Access Theme, etc.) gets lost and I have to manually go through every control on every form to reset it to the way I like it.
My question is:
Is there a way to keep all my form control properties and settings when I import them into the new database?
If not, how would I use VBA to do this for me automatically... looping through all the controls on all my forms to set all the properties to the way I like it? And, even more specific, I have a Sample Form with one of each control with all the properties set the way I want. So, how could I open this Sample Form and read each control's properties to copy to all the same controls on all my forms?
Performing a "Compact & Repair Database" action under the file tab will speed up your slow database. So you will not have to export and create a new instance of the database.
Microsoft does a good job of explaining
hope this helps
I Compact and Repair all the time.
I found the answer to my question: When I create a new database and import the forms from my old, slow, database, Access asks if I want to import the Themes along with the forms and, when I check this box, it copies all the forms' formatting, colors, etc. I think you have to click the Advanced button (or something like that) to see this option when you're in the Forms tab.
I am creating an application and trying to figure out best way to deal with navigation in it. User can choose different view settings (which content to show and options to filter it). Part of settings is stored in backend in user preferences model. Another part is stored in url and managed by router. But there is more settings I want to keep. The reason: I want to be able to refresh content therefore I need to keep settings somewhere, not update content on user actions and forget how I came to this state. My question is: what is the best place for such settings? Collection object? View object? My own controller?
P.S. to make it more clear, I'm working on rss reader application. And I want, for example, to show last week posts from certain feeds which are starred etc.
Save it in the URL. Thats the only place you can really rely on. If you need more then routes use query parameter like in a classic web application and use them in the view.
I'm working on an application using Play 2.0.4 in Scala, and one of the features I was asked to implement is to build a form that remembers all of the edit history. Basically, there should be a button next to every field that shows the details of every change, because the app users may want to rollback or use the edit history information later.
The first idea pops up in my mind is to assign a hidden div to every field that appends every change, and only shows the div when users click on the corresponding button. This doesn't sound very hard, but I feel like it may make the HTML a mess (since each user has his own record, each record has many fields). Or I could make a copy of the database and store all the changes inside, with the primary keys changed to be both the id of the form, and the edit time.
Thoughts? Am I overthinking the problem? Is there a more elegant way to store all of the edit history? We estimate that there would only be around 200 people in the company using it, so I guess I can let efficiency slide a little...
Thanks in advance.
I would normalize and persist the record in the database. This would allow you to have history on changes by having a history table for each section that they with to rollback.
This would allow manageability of restorations based on sets of data and significant changes can be tracked. Managing each field separately would be very cumbersome and least pragmatic.
I do all development in a single application. when a new version is ready I create a template and give it a version number. this way I can store a history of all previous versions.
the development templates are used to push the new design to many applications via replace design.
Creating manual version number or template names is fine but I am looking for a more automatic way of finding out which build the different applications are inherited from
When I visit the different applications I would like to be able to see which build number each application are inherited from. is this possible?
A simple build time stamp could do, but is there a built in build number that can be used and that can be displayed on the xpage.
e.g Build 2012092712345
Update:
Thank you for all your answers, many good suggestions but it looks like all require manual work.
The best solution would be if there is a way to read (from ssjs) a timestamp from any file within the nsf that is always updated during a build. is this possible?
In classic notes, there was a method to add a shared field with a special name to the application. Cannot remember the details, but have it somewhere on the disk.
Then you can see the build number in the design tab of the application properties. And you can of course display the value in your applikation as well.
But you have to fill the item manually on each build. Or use teamstudio Buildmanager. This tool adds the value automatically.
And I also guess that you can write some code that changes the value whenever you create a new build.
Another option would be to use a versioning system like CVS/SVN. This is possible since 8.5.3.
Source control
I think I know what you are meaning. Your a pushing out design and want to check thru code what version each database has. I usually do this with a Build form. In this form I have computed fields with all the data I want to retrieve. Then I open the database with an agent create a document
and set the form field to "BuildForm" and do a computewithform.
Now I can see all information about this database.
I once wrote a rudimentary build system for "classic" Notes, and had the last part of the build pipeline create a form named _BUILDID_, and put the build id in the $Comment field.
The main reason to create a form instead of a shared field was that I could dynamically fetch the form using NotesDatabase.Forms, and open up the desired field.
I sure hope there are simpler solutions nowadays... :-)
I create a form wherein the user enters some values but I now need to retrieve those values to display in a table. I'm unsure about how to achieve this. I'm working with the intro package and new to the system. I've read some tutorials but nothing about achieving this.
Edit: I should mention that I need to persist these values in a database first before attempting to display it.
Probably, the easiest way is to use Powermail extension, which handles many cases.
You could save the submitted data in dB and show it after with Your extension, or TypoScript configuration.