Introduction
What is RAVE? RAVE is an acronym that describes the different types of web browsers that use web pages. Specifically, it stands for Reader, Adapter, Viewer, and Editor. The purpose of this article is to demonstrate one way to create a web page that can be read by any type of web browsers.
Background.
This is the fifth in a series of articles that discuss the GRML markup language and the web browsers that use it. If you would like further background on the software and technology, see the Related Articles section.
RAVE
As mentioned in the introduction, RAVE consists of four parts. They are:
Readers - load or download a web page or file, parse the data, and prepare the content for display;
Viewers - display the content of the web page or file in a meaningful way (i.e. text view, list view, headline view, grid view, etc.)
Editors - allow content to be edited, modified, and saved.
Adapters - are used to translate data from one format to another, such as HTML to GRML, or vice versa.
Readers.
All GRML web browsers and file viewers come with a reader. In fact, all existing web browsers have an HTML reader. It is this piece that allows the application to read the markup language and use the content meaningfully.
Readers have serialization features to find and load (or download) content. They also include a parser to extract content for use. An application that only is used as a reader would not have a display for showing the available content. It would simply download it and extract the relevant information.
All web browsers have readers.
Viewers. Seeing the contents of a file provides useful information. Depending on the way the content is seen, will determine the user's perspective of that information. This is the function of the viewer. It displays the content that the reader has made available to the application.
An application can have many viewers or one view, but they all depend on the services of a reader. For example, a typical web browser has an HTML reader and a HTML viewer. In some web browsers, such as Pioneer, the web browser can have multiple views. With Pioneer, there is a GRML reader, a GRML list viewer a GRML report viewer, and a GRML text viewer.
The most popular web browsers have at least one viewer.
Editors.
Once the content is displayed, some web browsers allow it to be edited. An editor allows displayed content to be modified, edited, and saved. Modifications can occur by manipulating an image, changing text, including or excluding results, or adding new content.
An example of a web browser editor would be Cavalier. It reads GRML, displays an image view, allows image editing, and saves the changes. Editors are the least common type of web browser.
Adapters.
Not all web browsers are compatible because they use different markup languages. A GRML web page cannot be read by an HTML web browser and vice versa. Thus, the need for adapaters.
Adapters bridge the gap between different markup languages, file formats, and content types. They can be created on the server, within the web browser's internal logic, or as an add-on. For example, an adapter would be used to change a HTML web page into a GRML web page. Or, it could be used within an application to generate a different file format from that of the reader. A GRML web browser could use an adapter to translate GRML into a CSV file, or XML.
Adapters are not web browsers but are used by them, usually as a utlity application, script, or code block (e.g. a class or library). Most web browsers do not use them, but, GRML web browsers and web sites use them often.
Getting started with a simple web page.
Okay, now that we know a little about the types of web browsers that read web pages, let's look at an example.
<code>
<GRML>
<a class=column_13 type=Item>Title</>
<a class=column_13 type=Item>Request</>
<a class=column_13 type=Item>DateTime</>
<a class=rslt_13 type=imagewidth>72</>
<a class=rslt_13 type=Imageheight>72</>
<a class=rslt_13 type=image>http:
<a class=rslt_13 type=Item>Dems want uranium claim probed</>
<a class=rslt_13 type=Item>CNN</>
<a class=rslt_13 type=Item>7/9/2001</>
<a class=rslt_13 type=link>http:
<a class=rslt_13 type=image>http:
<a class=rslt_13 type=Item>PCBs trial a costly marathon</>
<a class=rslt_13 type=Item>CNN</>
<a class=rslt_13 type=Item>7/9/2001</>
<a class=rslt_13 type=link>http:
<a class=rslt_13 type=image>http:
<a class=rslt_13 type=Item>Town braces for Lewis and Clark crowds</>
<a class=rslt_13 type=Item>CNN</>
<a class=rslt_13 type=Item>7/9/2001</>
<a class=rslt_13 type=link>http:
</GRML>
Copy this code into a text editor, launch Pioneer and load the save file. Let's first look at the pictures in the report view, then the list view. You should see the following:
 |
 |
| List view |
Report (picture) view |
 |
|
| Simple text view |
|
In Image Cavalier, you should see the following:
Image Editing view
Following this format allows the web page to be displayed in different types of GRML web browsers.
Conclusion.
Web browsers can be described using the acronym RAVE. Readers, adapters, viewers, and editors describe the abilties of web browsers to use web pages and files.
In future articles, additional tags will be introduced and examples will be demonstrated for use with other GRML web browsers.
Related Articles
Using an image editor with dynamic web pages
An alternative to HTML and current web browsers
HTML, XML, GRML -- making a better markup language for the web
A simple web page format that works with windows and ASP
| You must Sign In to use this message board. |
|
|
 |
|
|
After reading your first few articles I though you were just sadly confused and misguided, but you keep pumping this nonsense.
This time I looked at your website. To quote:
GordonRhodes web browsers are unique business products that increase the value of your website content and services. They offer value that creates user/customer dependence. Your users and customers become locked-in and are unable and unwilling to consider your competitors.
I've updated my impression from misguided to malicious. Get this worthless crap out of here. It is completely doomed in the market anyway, but by your own words you are promoting it for anti-social purposes.
Maybe you can see it to that infomercial fellow who also posts here.
--
-Blake (com/bcdev/blake)
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
It is so hard to find people who tell it like it is. You are not trying to hold anything back, it seems. Also, it betrays a general thoughtfulness to your comments.
You are one of the first to actually have spent some time to develop an informed opinion. Regardless of whether it is positive or negative, your process was not superficial. So often, it is easier to comment now, and investigate and research later.
Once again, thank you for the time and consideration.
|
| Sign In·View Thread·PermaLink | 1.00/5 |
|
|
|
|
|
|
I have to agree with the 'great feeback' you recieved - this series of articles seems to get worse every time. I can't see anything that this technology can do that standardised technologies (HTML/XML/XSLT) cannot - apart from lock end users into a non-standard browser. I'm intrigued as to whether you have had any postive feedback from anyone that may have "spent some time to develop an informed opinion"....
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Toby, I think all this stuff might be a joke but you seem to have put a lot of effort into it. In my time I have spent ages winding people up but I have never even come close to what you have achieved.
If you are being serious then I apologise in advance...
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
but your posts are just blanket condemnations of something you know nothing about.
If you could just make one insightful comment about the capabilities, enhancements, stability, or performance of the software and the technology platform, it might be easier to consider your comments in a professional light.
|
| Sign In·View Thread·PermaLink | 1.00/5 |
|
|
|
|
|
|
