When a column parent tag is read, the child tags create the column order. This determines the order of display of columns. When a result parent tag is read, the child tags are added if the attribute exists in the column order.
Each item is added as it is encountered. The top column in the column order displays first. The bottom displays last. This is true for results. The top result with an attribute in the column order displays first. The bottom result with an attribute in the column order displays last.
Below are the combined form and view tags for the two examples.
Example 1.
<grml>
<edit search1>
<Title>Request:
</edit>
<Combo Default>
<Title>Default location
<monster>monster
</combo>
<submit>
<location>GRMLBrowser.com/jobs.asp
</submit>
<column>
<Date Posted>
<Job Title>
<Job Location>
<Company>
<Search>
<DateTime>
<Link>
</column>
<result>
<Date Posted>Jul 28
<Job Title>Sr. Java Software Engineer
<Job Location>US-CA-La Jolla
<Company>Company A
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
<Date Posted>Jul 20
<Job Title>Web Development Analyst
<Job Location>US-WI-La Crosse
<Company>Company B
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
<Date Posted>Aug 2
<Job Title>Software Group Manager
<Job Location>US-CA-La Mirada
<Company>Company C
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
</result>
</grml>
Example 2.
<grml>
<edit search1>
<Title>Request:
</edit>
<Combo Default>
<Title>Default location
</combo>
<Combo Default>
<monster>monster
</combo>
<submit>
<location>GRMLBrowser.com/jobs.asp
</submit>
<column>
<Date Posted>
<Job Title>
<Job Location>
<Company>
<Search>
</column>
<column>
<DateTime>
<Link Location>
</column>
<result>
<Date Posted>Jul 28
<Job Title>Sr. Java Software Engineer
<Job Location>US-CA-La Jolla
<Company>Company A
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
</result>
<result>
<Date Posted>Jul 20
<Job Title>Web Development Analyst
<Job Location>US-WI-La Crosse
<Company>Company B
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
</result>
<result>
<Date Posted>Aug 2
<Job Title>Software Group Manager
<Job Location>US-CA-La Mirada
<Company>Company C
<Search>Java LA
<DateTime>Today
<link>http://127.0.0.1
</result>
</grml>
The above examples demonstrate the different ways to organize GRML. While the tags are in different places, each creates the same input controls, columns, and results.
Scope of use.
Some GRML viewers do not display columns. It may only display images, or links, or partial text. For example, Pioneer Report MDI uses its thumbnail view to display an image and a result item appearing first in the column order. However, all GRML files or web pages require columns, if results are displayed.
Now that it has been shown how GRML uses input controls, columns, and results, it is possible to use the above example to create just about any type of GRML file or web page. There are form tags for handling user input and sending requests. There are view tags to display file or web page columns and results.
The only limitation of the above GRML is it does not demonstrate dimension tags. It is a topic discussed in another article. To respond to a request submitted using input controls, server-side processing is required. A server-side scripting, or programming language, such as ASP, JSP, CGI, .NET or PHP is needed. These techniques are discussed in another article.
Conclusion.
Well, that's it. Remember, all GRML files and web pages consist of two types of tags. One is the form tag, for creating input controls. The other is the view tag for creating columns and results.
A parent tag exists to create input controls. There are the parent tags, column and result. And, there are child tags. These set the attributes of the parent tags. Only parent tags have end tags, while child tags do not.
Knowing the different tags in a GRML file or web page provides the basis for learning other aspects of the markup language. Once familiar with the different tags, the next step is to learn how to use server-side processing with form requests and how to use the dimension tag.
07/11/05. Created this web page from Using GRML.
01/08/05. Updated formatting.
10/26/04. Removed almost all references to Pioneer Report MDI.
10/26/04. Added article text to cover GRML tags.
10/26/04. Updated examples from GRML 1.2 to GRML 2.0.
08/30/04. First published.