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.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
I came across this writing on Tech Support, and I'm wondering what you guys make out of it. Are IB implying they are in the process of dropping support for W3C standards and implementing legacy functions?
However in WebFOCUS 7.7.xx and higher, there are exposed functions the HTML Composer makes available for the developer to use. The function: IbComposer_enableHtmlElement('ElementID', true/false);
This function would accomplish the same effect as the above code and should be used if the developer is using WebFOCUS 7.7.xx or higher: Change: document.getElementById('agency_code').disabled = false; To: IbComposer_enableHtmlElement('agency_code',false);
The exposed functions will always work when a new release is available.
Any thoughts?This message has been edited. Last edited by: <Kathryn Henning>,
Change: document.getElementById('agency_code').disabled = false; To: IbComposer_enableHtmlElement('agency_code',false);
Gosh, that's not even correct! The second statement does the opposite of the first...
Anyway, getElementById() will always work, regardless of what IBI says. Personally, I would probably use JQuery's $('#agency_code').prop('disabled', false) instead.
The difference is that IBI's implementation does a couple of things for controls they customized, such as comboboxes and arrays of checkboxes or radio buttons. It also behaves a bit differently for Internet Explorer, I think that has to do with old versions (6 or 7 and older).
I do think it's bad design that HTML uses a property disabled=true instead of enabled=false; inverse logic is confusing. BTW, Microsoft does the same in the Advanced Internet Explorer options - it's a common ailment.This message has been edited. Last edited by: Wep5622,
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
If you don't use our API functions, your code may not work in newer releases and Support will tell you to change to the API functions at that point.
David Glick Director WebFOCUS App Studio and WebFOCUS Developer Studio WebFOCUS Division Information Builders, Inc. Direct (917) 339-5560 Voice Mail (212) 736-6250 x3560 Fax (212) 947-5168 Email david_glick@ibi.com
They are not "legacy" API functions. They are documented in the manual like everything else...
David Glick Director WebFOCUS App Studio and WebFOCUS Developer Studio WebFOCUS Division Information Builders, Inc. Direct (917) 339-5560 Voice Mail (212) 736-6250 x3560 Fax (212) 947-5168 Email david_glick@ibi.com