| |
|
| |
General Troubleshooting One of the best ways to troubleshoot AJAX and Smart Refresh issues is to recreate the problem with Firebug enabled. Another technique that can be used is to to add a client event handler to the model. You can configure the builder to run a script that displays a ... |
| |
|
| |
When using Smart Refresh (new in WPF 7.0) or Partial Page Refresh in a model that is firing a Portlet Factory or Cooperative Portlet event only the source portlet UI will be refreshed as a result of the action. The event will have been received by the event handler in the target model, but there ... |
| |
|
| |
The basic trick to making a multipage form is to have one variable that will contain all the data, then have several different pages, each with its own Data Page builder, all pointing at the same variable. Then, add a Data Field Modifier to each page, hiding all the fields that you don't want on ... |
| |
|
| |
The most straightforward technique for conditionally deactivating links is to add both Link and Text builders, and use two Visibility Setters to control which one is displayed - the Text for the current page, the Link otherwise. The Conditional Links sample on the WPF Wiki shows this technique in ... |
| |
|
| |
There is a sample of this in samples/datapage/LabelOnLeft.model (and its sister, LabelAbove.model). In those samples, the Phone Number table is what you are looking for. If that sample is not currently in your WPF project, then you will need to add the "Building Models" feature set to the project. ... |
| |
|
| |
The two main ways to do this are to either use the Content Launch Action builder or to invoke an Ajaxlike operation, using a servlet to write the data. The "calculated image" sample in the Ajax Samples package demonstrates the second approach. |
| |
|
| |
The Check Box builder uses a hidden input as the submitted value, using script to copy the appropriate checked/unchecked values into the hidden input as the associated checkbox input changes. Changes to the hidden input also cause an "onchange" event to be fired in this case, and you can use an ... |
| |
|
| |
Probably the easiest way to do this is to use both a Link builder and a Text builder, and include two Visibility Setters which act as an ifelse to display the correct one's output. Please see the Conditional links sample for more details. |
| |
|
| |
Linked Models are primarily intended for data and action re-use, not sharing pages. The easiest way to re-use pages from another model is to use the Model Container builder. If you really must use Linked Model to pull in pages from another model, use an Inserted Page builder to pull each page into ... |
| |
|
| |
The "advanced page location" is a key concept here. While you can very easily target named elements using a page location input widget, Portlet Factory supports a very powerful page location language which you can use to select just about anything on a page. In the case of a typical Portlet ... |