Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Tech docs | Downloads | BBC Micro

Reply to thread


"The resources I mean are the thousands of pounds wich will likely be spent by RISC OS users on Oregano3 instead of on plugins that would work with all RISC OS browsers and might be released as open source software."

Ah, well I would see that more as income rather than resources. As at that point resources have already been spent to produce Oregano 3 and the income will hopefully cover the costs of those resources. At that point its up to the user to decide where to direct their money, and if they want to finance other projects or products then thats up to them (Looking at the Firefox pledges and the Gimp-Print work people already have shown they are willing to do just that.)

Out of interest, what plugins do you think should be ported first?

"My definition of a browser wich works with 'typical sites' is one that works with 99% or more of the websites out there. Firefox on Windows seems to do that, so I don't see why Firefox on RISC OS should not get there as well."

Heh, well that again depends on your definition of works :) Certainly Oregano 3 makes a better job of some sites that Oregano 2 did with regards to the layout, but having a slightly invalid layout doesn't neccessarily stop the user from using the web site. Certainly one of the aims is to get into as many sites as the (non-IE) browsers do under Windows and Linux.

"Also Firefox is growing its market share so quickly, that many website developers are starting to optimise their sites for it. I don't see Oregano ever getting there."

The point about Firefox (and Opera) is that they support certain web standards. If a site is written correctly (i.e. to those standards) then there should be nothing stopping Oregano 3 from also being able to access the site. If, however, a web site is optimised specifically for Firefox then how is that any different from the IE optimised sites that are now causing web standard compliant browsers all sorts of problems today?

"As for TTF and PostScript font support, I would like to see them supported by RISC OS as standard, not as some external third-party module."

I would like to see a lot of things supported by RISC OS as standard. Sprites with alpha support would be nice to have as a standard, but you can only get that support if you buy a specific version of RISC OS that isn't available to users of the top end, ARM based, RISC OS supporting hardware.


 is a RISC OS UserLeo on 26/7/05 10:40AM
[ Reply | Permalink | Report ]

Please login before posting a comment. Use the form on the right to do so or create a free account.

Search the archives

Today's featured article

  • Brush up your ARM coding skills with Matthew Bloch's assembler guide

     Discuss this. Published: 27 Feb 2001

  • Random article

  • Messenger Pro 4.23 does HTML email, Unicode
    <blink>Everyone loves HTML email</blink>
     12 comments, latest by Rien on 17/12/06 10:06PM. Published: 10 Dec 2006

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign

    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "I see Drobe'll suck up any old s*** as news?"
    Page generated in 0.0682 seconds.