Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] STYLE question

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] STYLE question
 Login/Join
 
j.gross
Virtuoso
posted
Is there any practical difference whether report-wide settings appear in a "global" delaration (one not qualified by a "TYPE=" clause), or in a REPORT declaration (one opening with TYPE=REPORT)?

The GUI editor generates both. I wondered whether that's a matter of style or of necessesity.

This message has been edited. Last edited by: <Kathryn Henning>,


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
MartinY
Virtuoso
posted Hide Post
TYPE=REPORT set the "default" styling for the whole report, where TYPE=xxxx set a specific styling for that section of the report.

So you do need TYPE=REPORT to avoid specifying every section and need TYPE=xxxx to have specific styling per section.


WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF
In Focus since 2007
 
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013Report This Post
susannah
Expert
posted Hide Post
jack, what does a view source of the resulting html look like, in each case? wonder if you can determine from looking there what the differences are , if any, in the < style > bits vs within the < td > bits, or maybe even the < span > bits



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
j.gross
Virtuoso
posted Hide Post
"TYPE=REPORT set the "default" styling for the whole report, where TYPE=xxxx set a specific styling for that section of the report.
"

Martin -- I know that.

I posted, bcs it looks to me as tho, when you park a section-specific setting (such as the top and bottom gaps) upstairs in the global declaration (alongside UNITS and PAPER, stuff that can only be specified once for the whole report) it becomes report-wide "immovable object" setting (i.e., cannot be over-ridden for a specific section) -- whereas in the REPORT section it creates just a report-wide "default" but can be over-ridden on a section-by-section basis.

Has anyone else come to a similar conclusion? And is there any indication of that in the documentation?


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Danny-SRL
Virtuoso
posted Hide Post
Jack,
I did not find anything in the doc.
My experience is that there is also some undocumented feature about the relative position of each styling entry, most of which is not always intuitive.
For example, I have to color code a field according to values. Although the different conditions are disjointed (not overlapping) the order of their appearance has an effect.
Some good old trial-and-trial-again and documentation in the code for future releases differences...


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006Report This Post
j.gross
Virtuoso
posted Hide Post
I found documentation to the effect that REPORT is the default value for TYPE.

A quick test with
...
UNITS=IN, FONT=ARIAL,$
TYPE=REPORT, FONT='COURIER NEW',$
...

shows that values in a TYPE-less global declaration are not treated as immutable -- they can be over-ridden by a subsequent TYPE=REPORT declaration.


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] STYLE question

Copyright © 1996-2020 Information Builders