As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Has IBI enabled the Layer feature in Maintain to work at runtime, so one could do something like:
"Winform Set Form1.Layer1.Visible to Yes/No;" ??
I have used the 'Layer' feature of the MDE Form Editor to help build dynamic forms. But to do so, I've had to write some large Cases to show and hide the form controls for the different display situations. This is OK for small records, with only a few controls and labels, but it can get to be a real big pain with more complex screens.
Specifically, I'm thinking of trying to implement a tabbed interface on a Maintain Form, with a background layer and a separate layer for each tab, and controlling the visibility of the layers with simple syntax, instead of a lot of fussy coding that's difficult to write and maintain.
This would enable Maintain to deal with a lot of data fields gracefully, without a lot of bouncing from form to form, and add some modern UI techniques to the product. I don't think it would be that difficult a problem for the Maintain programmers, if it is not already available in a newer release them my 7.6.8
I agree it would be an effective addition to the Forms to be able to Tab different forms. And whilst I also think that it would be relatively easy to implement, it would be nice to hear from the programmers themselves. Mark?
In the meanwhile I have utilised the HTML Painter Tabs to mimic this behaviour. Not ideal but it does work, albeit not as smoothly as I would like, persistence is not available and each tab has to have it's own commit / rollback, and there are multiple forms. Actually sounds like everything you are trying to avoid!
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007
There is no new feature to allow for layering. Even in 7.7 you have to Show / Hide each individual object on a form. I will speak to proggramming about it. A new feature request from a customer is the best way for something like this to get considered.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
Basically create a Maintain with multiple forms. When calling the maintain, allow for parameters to process one section of code and call a form.
In the HTML painter create a tab for each form, and call the maintain with parameters to display each form.
Use javascript for x-iframe scripting to pick up any navigation parameters from one page to another. So as an example, if you select an employee in tab1, in the background run the maintain in tab2 to pick up the education for that employee, so selecting tab2 already has the correct information.
You can make it easier to use by saving changes to all the tab forms by issuing one save and more scripting.
Does that make more sense? If you need support for NFR, I can help.
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007
Thanks for the explanation. I get what you are doing, and it is very clever, but it seems to involve a lot of patches between WF, Maintain, HTML and Javascript. Not something I would want to do on a regular basis
Hopefully the NFR will come to pass, and we can do it an easier way !
Mark,
I have submitted the NFR on Case # 62282555. Any help moving it along would be appreciated.