Lurkers' Retreat
!Oregano 1 Browser for RISC OS systems

What is happening? - A users guide

A short FAQ for the needy
(Rev. Needy will receive all donations)
Go to Contents

1.01 First release (21-Feb-2001)
1.02 Added "What to do/Who am I" sections/fixes (23-Feb-2001)
1.03 Section 2 reorganised, sundry additions (27-Mar-2001)
1.03-05 First HTML version, a few more additions too.
1.04-01 Clean up and yet more additions.
2.00-01 Initial O2 FAQ additions
2.00-02 Error amendments
2.00-03 Code check/site move and O2 note
2.00-04 More updates and revisions (31-Dec-2002)
2.00-05 Contact details changed (18-Jul-2003)
2.00-06 Final version (Oregano 1 superceded)

Introduction

This is a short FAQ for those folks that are forever asking "What is going on with Oregano?" or whatever. It cannot be helped that this question keeps getting repeated, but it is appreciated by most that the good folk at Oregan and Castle cannot be constantly restating their current and proposed position; better leave this to an FAQ and let them carry on the good work. If you see anything missing, or you spot a mistake, please email me at the address above or stick something on the group (if you do this, please observe good netiquette and ONLY post the relevant bit. Folk will not thank you for reposting the entire FAQ just to point out one or two errors!)

Within this FAQ, there are certain sections which may require you to make alterations to certain sections or files within your installation. Please note that you do so at your own risk, bearing in mind the current conditions of sale and warranty on the software and that the writer and/or contributors of this FAQ can accept no responsibility for any damage or loss of use of the software or other system componants resulting from changes made by you. If in doubt, please contact your dealer.

If you wish to submit a change to this FAQ or spot an error, please write to this address, stating clearly what needs changing. This FAQ was written based mainly on Oregano V1.10js, though it also includes Oregano 2 beta additions (thanks to James Wilkinson at Oregan). It will be reposted as required, with copies available upon request.

WARNING: This document applies to Oregano 1. Although some of it may be applicable to Oregano 2, not all of it will be. You should apply to Castle for details and errors concerning Oregano 2.


Contents

1. What is currently being developed
     1.1 And what became of...
          Browse
          Fresco
          ArcWeb
     1.2 If Fresco is dead, then Voyager is dead, right?
2. Oregano bugs and features
     2.1 Oregano bugs
          2.1.1 Inverted graphics when printing
          2.1.2 Inverted graphics when saving graphic
          2.1.3 Main window resizing is erratic
          2.1.4 The browser does not support Acorn/RISC OS fonts
          2.1.5 Web pages cannot be saved as draw files
          2.1.6 There appears to be no native cache to Oregano
          2.1.7 Landscape printing does not work properly
          2.1.8 Oregano leaves no error message when "crashing"
          2.1.9 Use of index marks can be erratic
          2.1.10 Certain sites do not work
               (a) The site is broken
               (b) The site is intentionally broken
               (c) There is a bug in Oregano
          2.1.11 Large data in forms bug
          2.1.12 All items must be loaded before a link can be followed
          2.1.13 Images sometimes do not load fully
          2.1.14 Frame resizing does not work
          2.1.15 RiScript worries (or Adding runnables to Oregano)
          2.1.16 Page gets stuck on a specific date/removing an unwanted cookie
          2.1.17 Form contents
     2.2 Other useful bits
          2.2.1 Faking Netscape/MSIE
          2.2.2 Basic troubleshooting steps
3. Caching
     3.1 Acorn WebServe
          3.1.1 I keep getting "The requested URL could not be retrieved"
          3.1.2 I'm unable to access secure sites
          3.1.3 Can I extract files from the cache?
          3.1.4 Getting WebServe to run automatically
     3.2 Navaho
4 Add Ons
     4.1 The Cyberbit connection
           4.1.1 ...suddenly it doesn't work
     4.2 Skins and hotlists
5. Oregano 2
     Why doesn't O2 make more use of the RISC OS Window Manager ?
     What on earth has happened to the Skins ?
     In more than a year, is that all that's changed ?
     Will I always have to use Oregano(1) to download updates to Oregano2 ?
     Is the GUI script language JavaScript? Why not?
     Can I use JavaScript in Skin windows ?
     What happened to HTTPStream ?
     What happened to XTTFont ?
     Does '*Close' or 'CLOSE#0' still hurt ?
     What is the 'Utils' module ?
     Is there a new demo ?
Acknowledgements
1. What is currently being developed?

Oregano and WebsterXL are now the only browsers being actively developed for the native RISC OS platform. Of the others:-

1.1 And what became of...

Browse This Acorn offering is now in the hands of Pace (though Pace have sold RISC OS to Castle, so this may no longer be the case) and seems to have no future at the moment, although hints were made at the time of Acorn's demise that there could be some movement in the future as a side project. This does not seem to have happened, the last version to be released was V2.07. (Stable, supports plug ins, no Javascript).
Fresco Ant's offering and also part of the latest Voyager kit. Ant pulled out of the market in 2000, Argonet withdrawing support for the Ant Suite at roughly the same time although Paul Vigay has announced ongoing support for the package as time permits. (Paul already has the AntUtils package that supplements the Ant Suite with a number of useful tools, and is also involved in the ongoing support and development of Voyager). The last version released of Fresco was V2.13. (Stable, supports plug ins and Javascript, although some bugs in Javascript side).
ArcWeb This was a freebie that was heavily used early on by Acorn users in the absence of good commercial developments. The author went on to much greater things :) but this browser had a lot in it for what was essentially a lone project. The last version issued was V1.92 (Stable most times, though it still had frame problems, no table support and resizing was a chore, no plug in support and no Javascript).
WebsterXL effectively replaced a number of developments from the same stable, so I shall not go into details here.
Go back

1.2 If Fresco is dead, then Voyager is dead, right?

Wrong! Voyager (the internet agent for Acorn/RISC OS machines from Freedom2/Argonet) still uses Fresco even though it is not being developed now (except where time permits), but it is Ant Ltd. that has withdrawn from the market, not Argo. Should the question of Fresco become a problem in the future, this would be addressed by Argo themselves (but see above section on Fresco about the actual support of the program).

Go back

2. Oregano V1 bugs (Updated 20-Oct-2001)

The list shown here do not include specific URL's, but do show bugs often reported for version V1.10js as well as an initial FAQ for another version which was originally badged as Oregano 2 (I have V2.0.3 beta 1), though this version was discontinued by Oregan. Note that this beta version is not related to the version currently being marketed as Oregano 2. For the FAQ on this version, please see Chapter 5. Note that the errors shown in this chapter refer only to Oregano 1.10js

2.1 Known or reported bugs

Note that some of these bugs may be unsubstantiated but have been reported by user(s). If you can shed some light on one or more bugs, please let me know for future reference.
2.1.1 Inverted graphics when printing

This seems to affect gifs more often than other graphics. This only affects what is printed out directly from Oregano itself. If you snapshot the screen with Paint or use a similar tool, the graphic will show normally when printed.

Go back

2.1.2 Inverted graphic when saving graphic

Related to error 2.1, this occurs if you request the browser to save as a sprite. Save the required graphic in its native form, then convert using ChangeFSI or similar to avoid.

Go back

2.1.3 Main window resizing is erratic

This seems to be most common on framed sites, where a click on the maximise/ minimise frame switch causes the browser to change the box size in an unexpected fashion. The drag frame size box, however, works normally.

Go back

2.1.4 The browser does not support Acorn/RISC OS fonts

Oregano uses TrueType fonts rather than the Acorn outline fonts. This means that there is a degree of flexibility in that some features can be used.

Of course this does mean that Oregano does not support native Acorn fonts. The result is that while it does mean that Oregano can do things such as supporting kanji scripts (and in theory any other Truetype font), the rendering is different to that normally seen on the RISC OS desktop, including aliasing.

This is not necessarily a bug, in that it was necessary to do this to allow this degree of flexibility. Please see section 4 below.

Go back

2.1.5 Web pages cannot be saved as draw files

True. This has a lot to do with points 2.1.4 and 2.1.1, in that to be able to save the screen as a Draw file, first it has to be changed into something that could be saved as a Draw file. The other browsers don't suffer from this problem as they do not represent the web page in the same way as Oregano does.

Go back

2.1.6 There appears to be no native cache to Oregano

True. There is some talk of one being introduced in a couple of revisions' time (the new version of Oregano should have a cache included with it). One freely available cache is Navaho, which can be downloaded from the Oregano upgrade site, another is Webserve, which was available as part of the Browse kit. See section 3. There is also Nutmeg, a commercially available product which can be found at your local dealer, or see section 3 below.

Go back

2.1.7 Landscape printing does not work properly

This fault is nasty in that it can crash your system to the extent that it needs a hard reboot. An error message may not be shown, though if one is shown, then it will usually be something along the lines of "VDU4 not supported by driver" or similar.

Go back

2.1.8 Oregano leaves no error message when "crashing"

It has been reported that this can be alleviated by changing settings within the boot/run obey files, but only as far as getting the program to leave a trace in a log file. One such patch is to alter the <Oregano$Dir>.!Run file to contain:

Run <Oregano$Dir>.Oregano %*0 2> <oregano$dir>.blah
and the error would then be recovered from "blah". There are a number of alternative settings at the end of the Run file in question, which provide a number of error handling alternatives.

Other suggestions received are:-

If you instead uncomment the line:

If "<Oregano$DebugOut>"="" Then Set Oregano$DebugOut <Oregano$Dir>.stderr
Then this will work almost the same as the above suggestion, but with the advantage that Oregano will start up again if it dies without closing the stderr file - the former solution will make Oregano silently fail to run.

(btw, Oregano also logs javascript errors to this file.)

There has also been some comments about the saving of old stderr files (in its normal state, Oregano overwrites this file on each run). Two suggestions came about to change this:-

If you're using the original suggestion, you just need to change the > to a >> and it'll append rather than replace. (Unix users out there will probably be familiar with redirects - > means write/overwrite while >> means write/append.) The following in the !Run file has been working for another user. It keeps a total of three previous incarnations of the file.

Remove <Oregano$Dir>.stderr3
IfThere <Oregano$Dir>.stderr2 Then Rename <Oregano$Dir>.stderr2
<Oregano$Dir>.stderr3
IfThere <Oregano$Dir>.stderr1 Then Rename <Oregano$Dir>.stderr1
<Oregano$Dir>.stderr2
IfThere <Oregano$Dir>.stderr Then Rename <Oregano$Dir>.stderr
<Oregano$Dir>.stderr1
Note that the second parameter of the rename command should be on the same line as the rest of the command, the mail formatting has split each of the last three lines into two portions.
Go back

2.1.9 Use of index marks can be erratic

This could be due to badly written tags, but some users have experienced problems with <A HREF="#name">/<A NAME="name"> tagging.

Go back

2.1.10 Certain sites do not work

There are usually three answers to this.

(a) The site is broken By which I mean that the code used to create the site is not correct. It must be remembered that not all folk are boned up on HTML/Javascript/Flash/Java or whatever and will make mistakes. This does not necessarily mean that Oregano will be the only browser with problems getting onto the site. If you have access to another browser, try that, and see if you can spot the erroneous code. The site's creator might appreciate the help.
(b) The site is deliberately broken By which I mean that the code has been deliberately written to optimise itself on one or two browsers using illegal or non-standard code. Often this is where you will also find those annoying "Upgrade to" buttons. There are only two reasons for this sort of site behaviour; ignorance or stupidity. Whilst ignorance of the existance of a standard can be excused to an extent, the stupidity that prompts users to perpetuate the ongoing browser wars is unforgivable. Luckily for us, these sites are in the minority, and even those that say that they are optimised for PC browsers can often be used by Oregano users. Unluckily for us, a large number of the unreadable sites are corporate bodies that some of us want access to.
(c) There is a bug in Oregano This can only be proven if (a) and (b) are ruled out. As in any coding environment, there are rules that need to be observed, to which the compiler (or in our case the browser) has to adhere. Browsers are unique here in that they can act arbitrarily to ignore errors without compromising other parts of the code, but as the rules become more complex, the browser will have more reasons to give up and say "I quit". Don't for one moment think that by having x, y or z brand or browser that this makes you immune to this problem!

See section 2.2.2 for a run down on how to practically tackle most errors and bugs that you may find.

Go back

2.1.11 Large data in forms bug

Oregano will hang when attempting to post a form if over 4KB (approx) has placed in one of the fields. Oregano cannot be killed when this happens and a reboot is necessary.

Go back

2.1.12 All items must be loaded before a link can be followed

"Why, when I find myself on a page full of images, does Oregano insist on waiting until they have all been loaded before following a link (which I clicked on as soon as the text loaded)? Obviously I could click on the "STOP" button before clicking on the link, to stop the images loading, but I'm sure that most other browsers stop loading the current page when you click on a link." - Hilary Phillips <hmphillips@brookes.ac.uk>

This pretty much explains itself, in that although Oregano does not stop loading the current page when a link is selected, it will if you STOP the load from the top line. However there are certain circumstances where going directly to a link while the page is loading can be a pain as well (for example if the link in question is on the same file but has yet to be loaded).

Go back

2.1.13 Images sometimes do not load fully

This occurs due to a "timeout" (all downloads are subject to a time, the expiry of which is called a "timeout"). To try to reload an image, simply CTRL-select the image concerned.

Go back

2.1.14 Frame resizing does not work

It has been noted that frames set up with moveable frames do not work properly. This is where the NORESIZE tag is omitted from the definition of the frame. Frame borders are also not shown.

Go back

2.1.15 RiScript worries (or Adding Runnables to Oregano)

Some users have asked to be able to load PDF's (portable document format files) directly to RiScript or !pdf from Oregano.

To do this, click on Choices from the icon bar. Click on Media. Add

adf

to the list of runnables. Save. One warning is that these files are stored by Oregano in !Scrap and does not clear them afterwards. You may want to keep an eye on this. (This appears to be an Oregano specific bug).

Go back

2.1.16 Page gets stuck on a specific date/removing an unwanted cookie

This occurred with a specific page that was meant to be updated dynamically yet suddenly froze on a particular date. The fault appeared to be related to a cookie related to that page (in the case of the reported fault, myriscos.co.uk).

To cure this, first quit Oregano, *RMKill HTTPStream, then edit the cookie file (!Boot.Choices.Cookies) to remove the line containing the cookie for the site. Then restart Oregano (Note that you do not need to restart your machine if you have killed HTTPStream first).


Go back

2.1.17 Form contents

According to one report, the contents of check and radio boxes are not initialised in forms. This would require the manual entry of values, which may be a problem if you reload the form for any reason. For now, the only advice is type carefully and check before you click "submit".


2.2 Other useful notes

This section is where you can find any useful notes for Oregano itself. I'll be happy to add sections on addon programs if the demand occurs.

2.2.1 Faking Netscape/MSIE

In the case of (b) above, it is worth remembering that Oregano has the ability to fake responses to browser interrogation, so avoiding some of this behaviour. Go to Choices > Misc from the icon bar, and at the bottom of the screen you will see a field marked "Who am I?" This can be set to one of three settings:

  • Netscape© 4.72 (Mozilla)
  • Internet Explorer™ 4
  • Internet Explorer™ 5

plus it can be set to Oregano (this applies to both 1.10 and beta 2). Obviously it would be nice to make it so that this sort of "faking" would be unnecessary, but again we are at the mercy of the web writers that insist on this type of interrogation.

Go back

2.2.2 Basic Troubleshooting steps

You are getting frustrated trying to grab a page. The following should help you out. Try each of these before tearing your hair out/reporting the fault to the mailing list:-

  • Quit Oregano, reload and retry
  • Quit Oregano, press ƒ12 then enter the commands:-
                                *RMKill HTTPStream
                                *RMKill XTTFont
    
    Press return a second time to re-enter the desktop, then restart and retry (see note below)
  • Try doing it again after you have rebooted
  • If you use Webserve, try turning off Proxying in Oregano (The simplest way to do this is to go to Choices > Network from the icon bar and untick "http".)
  • Experiment Oregano's "Who am I", "Enable Javascript" and "Fake document layers" settings (see 2.2.1 for the "Who am I" setting)
You may well find that the problem is resolved by this process. If so make a note of it, and if it is cure by chaging the settings let the list know. If the problem presists it is then likely to be a genuine failure of Oregano, and you will be providing far more valuable feedback, if you tell us you have done this.

Note:- Sometimes "*RMKill HTTPStream" takes down the machine to an unusable state. I've found it much safer to do "*RMKill MemoryAllocator" before doing the above two *RMKills.

Go back

3. Caching

The following was written before !Cassia and !Nutmeg were released. If you wish to try these, see www.imagesoft.co.uk for details and ordering.

The main function of a cache is to hold items downloaded for the construction of a page so as to make the overall browsing of a site faster. It does this by downloading a single copy of a particular item, such as a graphic, then using this copy to reconstruct a page rather than going back to the net for another copy. This decreases rebuild time for a screen and also can be used to speed up the browsing of a site where common graphics are used for several pages.

Oregano 1.10js does not have a cache of its own. While it can be made to support an online proxy by addressing it, the only way to cache is to use a third party package.

Go back

3.1 Acorn Webserve

This was supplied as part of Browse, the Acorn Web browser, although it may also have versions on various disks, especially if you had access to the Voyager beta versions or if you were a Clan member. It was never marketed on its own, and I have no knowledge of it being made available since, although an Acorn FTP mirror does still exist somewhere.

To install this, you should have the New Boot sequence installed. This was made available in many places, including the Acorn User CD ROMs.

The installation includes a special install routine which, once it sees your boot directory, will then attempt to load the various required parts into the directory. Once loaded, reboot your machine.

First call up the choices page on Webserve and make sure that you have the local port set to 80, tick "Assume connection is already active" (unless you are using Socketeer or other diallers that support Dial on Demand), and untick "Don't allow other machines to connect".

I prefer not to use a remote proxy, so I leave that blank, but otherwise your ISP will give you the necessary address for this if they supply such a beast.

Once that has been done, call up Choices on Oregano and select Network. Tick the HTTP box and enter the following into the field next to the tick box:

                               127.0.0.1:80
SAVE this. Once this is done, you will then be ready to run. Note that this does not mean that the proxy will automatically load when you run Oregano; that needs to be sorted within the !Run file somehow if you want that to happen. Otherwise you must remember to run Webserve before you start browsing.
Go back

3.1.1 I can't browse! I keep getting "The requested URL could not be retrieved"

All this means usually is that you have not loaded the Webserve program. You can either do this manually by double-clicking Webserve (I keep it in AppDock myself) or by scripting. However I do not give a script for it here since this involves changing the code in one of your Oregano files, something for which I shall defer to the programmers at Oregan. (In other words, I ain't takin' the rap for telling anyone to rip their copy. If you want to do it, don't involve me!) Having said that, see section 3.1.4 below.

Go back

3.1.2 I'm unable to access secure sites

Make sure that on Choices > Network, you have ONLY ticked http. Normally, the proxies box should be empty and unticked except for http (this doesn't mean that you cannot tick the other boxes should you need to for other purposes). It is especially important that you both tick the box and enter the address (as shown above) since the address by itself or a tick by itself will not be enough to get the program to use the cache.

Go back

3.1.3 Can I extract files from the cache?

Some folk may wish to do this, especially if they want to get at specific information or graphics. The program CacheFS from David O'Shea allows this. The program is available from http://ocean.ucc.ie/99/oshea/

Go back

3.1.4 Getting WebServe to run automatically

You may want to make it so that WebServe runs automatically when you run Oregano. One solution is to load WebServe into your Choices.Boot.Tasks directory so that it is already there, but if you are tied for memory or you just plain don't like that, the following can be added to get Oregano to load WebServe.

Make sure that you keep backups of the files that are to be worked on, just in case something goes wrong.

First, you must add the following parts to the WebServe.!Run AFTER the last group of RMEnsure commands:-

| So Fresco/Oregano knows it's running
set webserve$running 1
| Configuration set by last run.
IfThere <WebServe$Dir>.!Config Then Obey <WebServe$Dir>.!Config
IfThere Choices:WWW.WebServe Then Obey Choices:WWW.WebServe
|
Wimpslot -max 96K -min 96K
Run <WebServe$Dir>.!RunImage %*0
unset webserve$running
Then add the following parts to the Oregano !Run file just before the last line:-
| Run WebServe
If "<webserve$running>"="" then filer_run <WebServe$Dir>.!Run

Note: The above script is supplied as is, and I can take no responsibility for any errors that you may encounter as a result of adding this code to your copies of the programs. It is always a good idea to keep a copy of the originals so that you can reinstate them should the worst happen, but if you don't, on your own head be it! Please also be aware that you may find that support may be withdrawn for unauthorised changes made to the code (well, Oregano at least - I doubt that anyone at Pace is particularly bothered at this point!)

In other words, you make the above changes at your own risk!

Go back

3.2 Navaho

Navaho is a program that provides a number of server functions. In this case, however, we only want to use it to cache, therefore a fair amount of it will be disabled for our use. In that respect, all that is detailed here is how to get it to work with Oregano as a web cache. For the rest, you will need to go elsewhere for details. Note also that this version of Navaho is a beta version, and while many users have now got this loaded and working, there is no guarantee that it will work on all configurations.

Download the program and unpack it to somewhere where it can be got at. A good place is in the same place as where you have Oregano itself.

Having run it, you may find that you will need to "unlock" it. Click on the iconbar icon and enter the default user name/password (sysman/anasazi).

Select Tools > Quickstart config from the iconbar and tick Dial-Up connection. Leave everything else empty (Country should be "None").

Select Tools > Suite Configuration, then select "Mail". In the SMTP Server box, untick "Enabled". Do the same in the POP Server box and the IMAP server box.

Now click on News and untick NNTP Server "Enabled".

Now click on Proxy, and untick "Enabled" on all the servers in this page EXCEPT http, which must be ticked. You will also need to adjust the Cache management box, which is the last but one box on the Proxy page, including how much space you wish to devote to caching, maximum file size and so on.

The misc section doesn't need to be touched unless you are required to do so.

Now select Web and untick "Enabled" in the HTTP Server box.

Click on Utilities and untick ALL the boxes in the servers box, then enter the IP Address 127.0.0.1 in the Ip Access > Allow box.

Click on SAVE.

Now you need to change Oregano as shown in section 3.1 by changing the Choices > Network > Proxies > HTTP setting to ticked with 127.0.0.1:8080 in the address field and set "Don't proxy" to "local".

You should now reboot your system, then reload your dialler followed by Navaho.

Go back

3.2.1 Mildly scary nag screen removal
  1. SHIFT-Doubleclick on !Navaho
  2. SHIFT-Doubleclick on the !Run file
  3. Scroll down to the bottom of the file
  4. Find the line that reads:
     RMEnsure PPPdriver 0 RMRun <NavahoPPP$Dir>.NavahoPPP 1500
    
  5. Go to the start of the line.
  6. Comment the line out by typing a '|' -this is to the left of the z-key, and is SHIFT-\
  7. Save the file.
  8. Shut down, reboot and run !Navaho again.
Go back

4 Add ons

The following sections concern additions for Oregano 1


4.1 The Cyberbit connection - how to support Japanese sites.

The biggest advantage of using TrueType is that this opens up the use of fonts that have never been openly available for Acorn users. One such is Cyberbit™ which is a do-all font used to display some kanji based text displays such as Japanese.

Of course this does mean that Oregano does not currently support native Acorn fonts. The result is that while it does mean that Oregano can do things such as supporting kanji scripts (and in theory any other Truetype font), the rendering is different to that normally seen on the RISC OS desktop, including aliasing.

To add this, first you have to find a copy of the Cyberbit font as it would be supplied to a PC user. This is becoming increasinly hard to find but a good rifle through the Internet with a search engine (www.google.com for example) will usually turn up a copy.

Using SparkFS or Sparkplug, open up the archive and extract the cyberbit.ttf file from it. Save this into !Boot.Resources.!OreganRes.Fonts as a data file called "Cyberbit". Close !OreganRes and open !Oregano.

PLEASE NOTE THAT YOU ALTER THE CONTENTS OF YOUR COPY AT YOUR OWN RISK.

Open the "Messages" file and find the section headed "# Fallback font for stackable system". Change the variable below it to read as follows:-

                 font.fallback:TrueTypeFont:Cyberbit
Save this file and reboot your system. A good test site for checking that all is working as it should is www.aic-int.com which should show mostly kanji, though accesses to English sites should be unaffected.
Go back

4.1.1 I have the Cyberbit patch installed, but suddenly it doesn't work

The "Messages" file inside !Oregano may well have been overwritten as part of a recent program upgrade. You may need to re-edit the file to allow it to work. Similarly the Cyberbit file may have been removed, so replace it as before.

Go back

4.2 Skins and hotlists

Sendu Bala has created a help page for users interested in creating skins for Oregano 1 and a guide on Hotlists. To read, see http://www.drood68.freeserve.co.uk/Oregano/

Go back

5. Oregano 2 beta

The following was submitted by James Wilkinson of Oregan as an initial FAQ for the Oregano 2 beta browser. Some of the previous chapters will still be appropriate for both versions. If in doubt, please see the Oregano ML. I have left this here for historical reasons alone.

Note that the version discussed below is the now aborted Oregano 2 project. Castle now market a new version to replace it based on a later project. The details below and the programs it relates to should not be taken as an intention of future projected programming for this program. The version that this section relates to is now unlikely to be made public, so if you don't have it, don't bother to ask for it.


Q: Why doesn't O2b make more use of the RISC OS Window Manager ?
A: Oregano2 beta used the RISC OS Window Manager for the top-level windows and each of these contained a 'session' which consisted of multiple Oregano2-windows. The Oregano2 beta windowing system was optimised for Oregano2 beta's purposes and had many key features in development.

Go back

Q: What on earth has happened to the Skins ?
A: Skins in Oregano2 beta were radically different to Oregano(1) - they are very flexible, written in HTML and were platform-independent.

Go back

Q: In more than a year, is that all that's changed ?
A: No - Oregano2 beta was a significant re-design over Oregano(1) and this allowed new features, improved stability, increased performance and easier development. Some of the highlights included a new TrueType font-rendering engine with direct-to-screen fast redraw, JavaScript 1.5 support, improved CSS support, the new GUI mechanism, increased configurability, features for network users, and more.

Go back

Q: Will I always have to use Oregano(1) to download updates to Oregano2 ?
A: This question is no longer relevant since this version has been discontinued.

Go back

Q: Is the GUI script language JavaScript?
A: No.
Q: Why not?
A: JavaScript required a Document-Object-Model (DOM) for each window created. As Oregano2 beta Skins (GUIs) were written in HTML, this would have required a JavaScript DOM for all windows in the Skin. When you multiplied this by the fact that each top-level window used it's own copy of the Skin, memory consumption due to DOM structures soon became unworkable. The GUIScript that was available was JavaScript-like so that it was familiar, but a very simple language.

Go back

Q: Can I use JavaScript in Skin windows ?
A: Yes, but it will use more memory (see previous answer). Check Task Manager for details.

Go back

Q: What happened to HTTPStream ?
A: It was no longer needed. As part of the development of Oregano2, the functionality of HTTPStream was integrated into the core of the browser where it could be extended more easily. Many of the problems with Oregano(1) were related to HTTPStream and were therefore extremely difficult to track down.

Go back

Q: What happened to XTTFont ?
A: It was no longer needed. Oregano2 beta included a new TrueType Font rendering engine that could blend fonts directly onto the screen. It also included caching so that often-used letters were quicker to access. In low-colour screen modes, the font rendering engine would fall back to using RISC OS Sprite mechanisms.

Go back

Q: Does '*Close' or 'CLOSE#0' still hurt ?
A: If a file that Oregano2 beta was using is closed while being used, Oregano2 beta would re-open the file (if possible) otherwise it would fail gracefully.

Go back

Q: What is the 'Utils' module ?
A: This module provided access to some of the low-level features of RISC OS, such as key up/down detection and socket activity notification.

Go back

Q: Is there a new demo ?
A: Not of this version. This version of Oregano2 was discontinued after Oregan decided to change te direction in which they were developing the product, so Oregano2 beta was effectively a dead end. A new program based on the current non-system specific Oregano is to be released by Castle, and a demo should be available for that at some point. Keep watching for more details.

Go back

Written/compiled by chika (Chris Johnson)
Corrections acknowledgements

Many thanks to:-
Nik Gare <nik@cheddarcheese.de>
Stefan Bellon <sbellon@sbellon.de>
Jeremy C B Nicoll <Jeremy@omba.demon.co.uk>
Alex Bach Andersen <alexbach@isa.dknet.dk>
Nick Roberts <tigger@argonet.co.uk>
John Woodthorpe <lists@armlink.co.uk>
Nicholas McGovern <nicholas@mcgivern15.freeserve.co.uk>
Mike Gilbert <mgilbert@tme.co.uk>
James Wilkinson <james.wilkinson@oregan.net>
Tony Van Der Hoff <tony@mk-net.demon.co.uk>
Ray Dawson <rayd@argonet.co.uk>
David Ruck <druck@freeuk.com>
Chris Johnson <C.A.Johnson@hw.ac.uk>*
David Eaton <david.eaton@ukgateway.net>
Roger Horne <roger@number7.demon.co.uk>
Bob Ansell <bob@edweb.co.uk>
Matthew Somerville <matthew.somerville@trinity.oxford.ac.uk>
Sendu Bala <sendu@sbsnet.screaming.net>

* No, these are two different people! To save confusion, I'm known on the net as "Chika", so we'll leave it at that, eh? :)
Go back

Other acknowledgements

MSIE, Internet Explorer TM Microsoft
Netscape, Navigator TM Netscape (AOL)
RiScript TM Cerilica
PDF TM Adobe

and of course...

Oregano © 1998-2003 Oregan Networks Ltd.

...and any other marks I have forgotten to mention. Let me know if you want a specific mention! - Chika

Valid HTML 4.01!