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.
Kofi, I made a few minor changes which you may want to consider:
- [ Keyword list tag ] Enabled 'Prefix mode' in the 3rd group of keywords (the ones for HTML). this allows all tags to be highlighted even when there are no separators among them .
- [Comment & Number ] Checked 'Treat keyword as symbol' in the comment line section. This allows highlighting of comments even when there is no space separating -* or $.
- [ Operators ] Removed '/' from activated operators as it was stopping highlighting on HTML closing tags. In the same section, I also defined " and ' as boundary delimiters and set the color to Blue so character strings (including those in HEADING, SUBFOOT, etc.) are treated similarly as in Dev.Studio.
You did a great job at including most of the keywords we regularly use. I haven't looked at the masterfile section yet but I'm sure it's also great.
I do this get rid of association MS do for MAS particular!! I hate
It's funny you said that as I dislike it too .
That thing actually caused me trouble a while ago after I installed MS Access in my desktop. Suddenly, Dev Studio could no longer open .mas files as that extension was being interpreted as a MS Access file instead of a WebFOCUS synonym. I never understood why Dev Studio did not recognize properly its own peers regardless of whatever Windows said
It does not seem to be a problem anymore ... or maybe it's because the last time around I installed Dev Studio *after* MS Office Anyway, as now I know where to go to in case I need to fix this it does not bother me anymore.This message has been edited. Last edited by: njsden,
You can copy objects on the Design tab and then the tool adjusts the code behind those objects accordingly.
Except in the case of composer's Radio Button control. I copied and pasted a Radio group, and the tool failed to adjust the NAME attribute -- so effectively I wound up with one radio group of 10 entries (spread over two tabs), rather than the expected two independent groups of 5 each. Nasty.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
You can copy objects between pages. You should always check that the resulting name and id is unique for the page though. The tool will handle that, but a check is always best. We do not copy event handlers nor population though.
Dialog Manager variables do not have a format per se, In HTML Composer, if a variable has the same name as a field, we will treat that variable as having the same format as the field.
Reset: If you have a Reset button on the page, it will reset all the controls, including any double-list controls. Is that not good enough? What would a Reset button on a double-list control do? As far as the "ALL" value issue goes, we will address that. If you open a case, you will be notified when it is resolved.
In addition to the search control on an individual control, there is a global search and paging control and that one has the case sensitivity options.
The !IBI.AMP.label issue: I am suggesting that you pass in a value that has quotes and pass the quotes in with it.
The Unbound Parameters box: I cannot reproduce what you are saying. Please open a case and provide a reproduction.
Multi-column Radio Button: I cannot reproduce what you are saying. Please open a case and provide a reproduction.
Form Document and Non-Form Document 768 and 769+: Please provide an example.
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
Actually... There's a help page that tells you about adding document classes etc in textpad. Yes, you'll need to associate the file types you're editing with the SYN file...
How to Create a New Document Class There are three basic steps required:
Create the document class. Specify which files are members of that class. Optionally, specify which syntax definition file is required. These steps can be performed for you with the New Document Class wizard, using the command on the Configure menu, or as explained below.
For example, for Perl files, first create the document class: Close any open documents, even blank ones. From the Configure menu, choose Preferences. Select Document Classes. Click the empty box at the bottom of the list of classes. Type the name "Perl" and press Enter. Click Apply. Click the "+" next to Document Classes. Select the new entry for Perl. Change any properties, such as "Create new files as UNIX", if the defaults are not appropriate. Click Apply. Second, specify which files are members of this class: Click the empty box at the end of the list of class members. Type "*.pl" and press Enter. Click Apply. Finally, specify which syntax definition file is required (optional): Click the "+" next to the Perl document class. Select "Syntax". Check "Enable syntax highlighting". From the list of syntax definition files, choose "Perl.syn". Click OK. Now, open a file with extension ".pl" and it should be syntax highlighted.
If you don't see a suitable syntax definition file in the list, check if one is available from the free add-ons page on our web site. If you still can't see the one you need, you can create your own, as described in Reference Information: Syntax Definition Files, and taking an existing ".SYN" file as an example. However, do not use TEXT.SYN, nor start the file with "TEXT=1", as that is only intended for highlighting URLs in simple text files.
Click: Start -> Control Panel -> Default Programs -> Associate a file type or protocol with a Program.
Select ".fex" / ".htm" from the list, click "Change program..." and choose your editor of choice. If not listed, one can use "Browse ..." to pick any other, finish the process and voilà.
Odd. I seem to have lost my DevStudio connection to EditPlus. Start -> Control Panel -> Default Programs -> Associate a file type or protocol with a Program > .fex is set to EditPlus, but in DevStudio, even though the icon is EditPlus and the file type is EditPlus WebFOCUS Program, fexes open in Notepad.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
- Since largely ceasing and desisting from the use of HTML Composer I have developed Javascript that allows me to transfer launch pages between test and production domains with the change of one variable. The domain, folder, dir, etc variables are defined once, near the top of the page, for each location, and one variable determines which location is referenced. I love it!
Could you provide me with a code sample or direction on how you did this? It sounds very useful. Thanks
WebFOCUS Server 8.1.05 Windows 2008 Server WebFOCUS AppStudio 8.1.05 Windows 7 Professional IE 11 and Chrome Version 43.0.2357.124 m. Mostly HTML, PDF, Excel, and AHTML
Well, I am afraid I must be the nay sayer in this little discussion. If you use the tool the way it is designed to work, the HTML Composer workes just fine. Here are a few simple rules I follow:
1) have the report that is to be launched finished and TESTED before you even think about the launch page.
2) ALWAYS add parameter related components by clicking on the hyperlink properties of the button to be used to launch the report. Any new amper variables can be associated with the new control right there.
3) Then and only then , style the new components, and work on the functionality.
Just for the record, I just finished an 8 tab html page with 24 reports and 35 graphs. Once the reports / graphs were done and ready, the application tabs took about 2 hours each. Never looked at the HTML once.
Two weeks ago a 2 tab application with over 50 possible parameter controls, and 17 reports. The only time I opened the text view was to write the javascript to set default values or hide inappropriate controls for the report they had selected from a dropdown list.
Francis, IMHO your mistake was trying to copy the HTML code from one page to the other. My suggestion would be to:
a) Use the 'hyperlink properties' technique above to create the control in each of the four. This also handles all that pesky XML at the bottom of the apge.
b) Style / place the first control
c) Copy JUST the STYLE code from the first one to the rest.
Just my 2 cents
Robert F. Bowley Jr. Owner TaRa Solutions, LLC
In WebFOCUS since 2001
Posts: 132 | Location: Gadsden, Al | Registered: July 22, 2005
Re-usable code/modules and easily replicated appearance and functionality are the hallmarks of a good development environment. HTML Composter is great for creating one-off launch pages/dash boards and for tweaking existing ones (created with the same version!). But in most corporate environments, logos, color schemes, and key data elements (i.e., input variables) never change. Having to recreate these non-changing aspects from scratch for every launch page/dash board is a terrible waste of resources. And this is exactly the kind of work HTML Composter is unable to do without significant manual intervention: take a copy of an existing Composter-generated page and modify portions of it to create a new launch page/dash board. The last time I had to write a job-related focexec from scratch was probably in 1983.This message has been edited. Last edited by: Dan Satchell,
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
There's also the issue that often requirements change once a report is in use. That often means that new parameters are added to the report and need to be selectable on the launch page. Just adding a few new parameters to a launch page isn't usually a problem, but if the required behaviour changes (different data selections, different interoperability, etc.) you're in for some pain!
I've only been working with WebFOCUS since 2010, but even I rarely write a focexec from scratch. We have a bunch of standard procedures that do the work of most of our styling, whatever the output format is. It'd be nice to be able to automate that some more, in their current state they still involve some copy/pasting to apply them to reports. It's still a work in progress - I can't imagine what that would look like after 29 years!
I also can't imagine how IBI would ever be able to write a tool that would generate the correct code in such an environment. Perhaps with a code base that evolved, the best approach is to see if you can also generate the (admittedly rather complicated) embedded XML fragments that you need in your launch-pages. I do hope they documented how that works.
I'm not saying that there isn't room for improvement in the tools! There is. IMHO, the first thing that needs fixing though is the attitude of tech support to such problems; too often the reply is that "it's working as designed" - design flaws are flaws too!
For example, if the auto-prompter prompts me for variables that are in unreachable code, then something is wrong. If the cursor position indicator in Dev Studio disappears after using the HTML Composter while errors refer to such line numbers, that ought to be fixed. Those are real issues, whether they were designed that way or not.
Right, I'll get off my soap box now.
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 :
Yes Dan Satchell is correctand so is WEP5622, there is no way to create ones own templates to leverage a consistent apperance and branding However my request to be able to find a way to develop my own templates was rejected. See below
"Dear Geoffrey,
After further review by Product Managment, the feature request to customize or modify RIA templates used within the HTML Composer has been declined by Product management.
The recommendations I had provided earlier, which I have copied again below, will be the solutions.
Previously provided suggetions: ------------------------------- Currently there isn't a way to create RIA templates for the HTML composer. Right now the recommendation is to apply styling on top of the RIA Theme selected in HTML Composer using the dialogs in the tool. The other option is to create a cascading stylesheet, .css and place it in the Other Files folder of a Domain. The HTML Composer tool can then select that stylesheet for use"
I other words create your own stylesheet whch does not address the inflexibility of the templates in 7703.
Creation of templates is planned for a future release although not RIA templates because RIA templates are an extremely involved thing. You can save your own CSS on top of our themes and you can read the documentation to learn how to do that. In testing the releases, we always open pages created in prior releases and add new content to them as well as change interactivity previously created. So if you have a problem with doing that, you need to open a case with Support.
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
Originally posted by njsden: No prying eyes allowed?
No! - No, primarily I realized that I'd never put together an organized set of instructions on how to do what I'm doing, so I didn't want to put Version 1.0 out for the whole world to stumble over if I missed something!
We'll see what I can do here. . . :-)
Rob
WebFocus 8201m on Windows; App Studio 8201; Procedures: WebFocus with SQL; HTML Parameter Pages & Dashboard; Output: Excel, HTML, & PDF.
Posts: 88 | Location: MI | Registered: July 23, 2009
- Since largely ceasing and desisting from the use of HTML Composer I have developed Javascript that allows me to transfer launch pages between test and production domains with the change of one variable. The domain, folder, dir, etc variables are defined once, near the top of the page, for each location, and one variable determines which location is referenced. I love it!
As requested, here is a link to some basic documentation. I scarcely ever go through the rigamarole of adding this code to an existing page, since most of my new pages are generated by copying and modifying an existing page that already has the code.
WebFOCUS Server 8.1.05 Windows 2008 Server WebFOCUS AppStudio 8.1.05 Windows 7 Professional IE 11 and Chrome Version 43.0.2357.124 m. Mostly HTML, PDF, Excel, and AHTML
This thread has certainly lost it's original intent! All the input on text editors and version control is great but they shouldn't be necessary to begin with. Here's my latest addition to the tales of woe.
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
I write all my own html source and code directly to the servlet jsp. It is wicked simple. Once you get a couple of basic concepts down you'll never go back to the html composer again.
J.
John, can you point me in the direction of learning how to do this? Thanks!
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
I start with a base and generally hand code everything else. I had read through IBIRLS2 when it was around and got a good understanding of what it did. Then IBIRLS3 cam along with all the included XML within the code which knocked me back immensely Picked myself up and started to try and understand the interaction between the components (JS,XML,HTML) and am now in a place where I can achieve most of what I used to without having to venture into composer.
There are still times when I use composer but it is generally to get the base. I still use a form to contain the controls, get rid of the submit button and replace it with my own (actually I mostly change TYPE=SUBMIT to TYPE=BUTTON). I finally ensure that the value for the hidden input control named IBIF_ex is the fex that I want targetted and IBIAPP_app is the app(s) that I need in an app path. If the target is MRE then the parms are different of course but I still develop in apps and then move.
There are times when I have to use composer - when showing Customers "how to" - but these tend to be simplistic offerings.
Suggestions? Take the time to keep abreast of the HTML changes at W3C, learn JavaScript as best you can and bookmark those useful sites that you find when you google something like "javascript regualar expression"!!
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