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.
In Dev and App Studio, I can create a new HTML page, add a form, and add a control onto that form. I am then able to use % values for position properties, like 35% from the top, and 5% from the left, which arranges the control within the form based on the size of the browser window. If the browser window is restored, it scrunches the controls closer together, or if it is maximized, it spreads it out and gives users room to stretch out. This works very well with list boxes, as you can grow the list box height based on the browser window size (super useful for high resolutions).
The issue I have is with calendar controls. If I dynamically position the calendar, and it works when the report first runs. However, if I change the browser window size, the control input moves, but the calendar image remains behind. This is obviously not idea.
The calendar image is not in the properties, nor is it selectable. I read an old post that said the calendar is drawn at page load by javascript, so that could be why it's not staying with the input control.
Does anyone have a way to force a re-draw of the calendar, or move it with the control using a jquery animation? I'd even take some custom javascript, although I prefer to configure through GUIs.
Cheers,
JoeyThis message has been edited. Last edited by: Moogle,
-WebFOCUS 8.2.01 on Windows
Posts: 318 | Location: Los Angeles, CA | Registered: November 15, 2005
I've just tried this (on App Studio 8.0.08 and 8.1.03) and the image is positioned correctly when rendered in my browser.
In Dev Studio 8.0.08 it behaves as you describe, and from distant memories the image is positioned before the associated calendar text input control, with absolute left and top attributes.
Do you also set the width and height of the form in percentage terms (as well as left and top)? The only time that I tend to use percentage positioning is when I have multiple iframes and never normally on a form for the contained controls.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
I did set the width and height of the form, plus the controls within the form. I was unable to resolve the calendar issue, so I reverted back to a static form. This is unfortunate, from a multiple resolution supporting perspective. Oh well.
Cheers,
Joey
-WebFOCUS 8.2.01 on Windows
Posts: 318 | Location: Los Angeles, CA | Registered: November 15, 2005
In App Studio the calendar control is a jQuery control and you maybe able to affect the location and size of the popup with CSS. You will have to search google for "datepicker jquery" and you can change the properties for the calendar popup.
I hope this helps...
Thanks Barry
WebFOCUS 8103, Windows, App Studio
Posts: 80 | Location: NYC | Registered: November 13, 2008
I'm a long ago believer in building only within the product's configurable properties. The furthest down the customization path I'll go is to use the IBCompose functions, because I trust that they will be continually supported. That being said, I was "victim" to some cose tightening with one of the functions on our last upgrade. That really just proves my stance, though. I feel like I get more benefit from easily staying current on WF version versus tweaking my pages just so, and then having to potentially upgrade each of them on upgrade.
That's my reason for not doing too much custom coding.
Cheers,
Joey
-WebFOCUS 8.2.01 on Windows
Posts: 318 | Location: Los Angeles, CA | Registered: November 15, 2005