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

Reply to thread


re Availability; How about people who write stuff FOC using (say) GCC? Shouldn't they be allowed to see what the Style Guide says - or should they be made to pay in order that they can provide free software?

Coling and JWCR:

re 'Updateability'; Let's make it perfectly clear that I am not talking about changing things for the sake of changing things. I'm talking about updates to cover ommissions in the style guide, and to reflect additional considerations that have come about with the changes that have been made to the OS itself in the 13 years since the style guide was published.

I believe there *are* ommissions in the style guide - the usenet comments have already brought to light that those who criticised Pluto's use of '[field] label' on Style Guide grounds are in error since the Style Guide doesn't insist on 'label [field]' and I'm reasonably sure there are other areas. Where they aren't in error is on the basis that it doesn't make sense in the instances they're used that way in Pluto, which is why the Style Guide should cover it.

I don't think (not going to check right now) that the guide doesn't cover toolbars at all - I don't think I had very many apps that had them back then, but they are common now. In what way should they be covered? Well, the guide provides some very specific information on the sizes that various icons etc should be, and I would suggest that the same level of specific information should be presented for tool bar icons. (I personally think an ideal size is twice the height of the window furniture tool icons).

Changes to the OS? Again, I'm not going to check now, but IIRC the SG as published covers choices, but tells you to contact Acorn because the subject is under discussion. Is it still under discussion at Acorn, or has the matter been resolved. Hmm, let me think - oh yes, it has, it's been resolved so the situation has, in effect, changed - and there is a very good document on the subject published on Justin Fletcher's website. More disparate information. (Along with the additional information on the Iyonix website, as I mentioned yesterday).

The Style Guide needs to be updated so that we have a *single* document containing such things, and it needs to be 'updateable' so that new concepts, new tools, and so on can be covered where necessary.

(I might agree that you had valid arguments if they were that the wiki - where anyone can log in and change it - is not the best solution, but that isn't what you argued).

 is a RISC OS UserVinceH on 24/12/06 11:51AM
[ 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

  • Voting for Best of 2004 Awards open
    Let the people decide - ends 30th Dec
     25 comments, latest by davehigton on 27/12/04 10:34PM. Published: 10 Dec 2004

  • Random article

  • RiscStation laptop progress check

     Discuss this. Published: 19 May 2001

  • 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
    "Drobe won't credit us for breaking stories. Oh well, that's journalism for you."
    Page generated in 0.0665 seconds.