Voyager

Open Source

Precis

Please read this...

DO NOT download anything unless you understand the rules printed below and agree to them.

I do not, yet, know if Paul Vigay wishes to look after the running of these applications alongside Voyager. So I am writing on the assumption that he does not. If he does, then I'll update this document to reflect that. Don't hassle him about it, he's done wonders in getting Voyager open source to begin with. Give him praise and undying gratitude.

Okay, here goes:

Source code

• The source is not GPL.
  For the purposes of legalities, the code is copyright © Richard Murray. However a project may have been amended by numerous different authors. It is suggested that if you add an entry to the "Versions" file, you add your name in square brackets after your modification.
   
  
• You may not freely distribute your modified code; ie on your website for the general public. Instead, please send your modifications back to myself for inclusion into the main source.
  You may, however, create a page on your site for your trial versions and development code which can be linked to directly from here.
  The reason for this is to minimise the exposure of differing versions of QuickVoy and/or Emily. As far as the end-user is concerned, the normal area on this site is where they can download a tested version of QuickVoy. Emily is not directly available.
   
  
• There is no Revision Control System in operation. In-house rules are that the version number is increased for each day of work. So version 0.45 amended for a big change over two days would become version 0.47. And version 0.74 given a two-minute tweak is then version 0.75.
  As these projects are not commercial, the version numbering does not reflect major or semi-major changes. Ie, ripping out a big chunk of code and redoing it will only up the version by .01, not .10. And the major version number is only updated upon a roll-over or upon such time as the code is either rewritten from scratch or ported to another language; neither of which I view as being likely.
   
  
• You can either send me your code snippets, or the entire affected source (inc. headers if different). As long as it is obvious what you've changed. If you send whole source files back, I'll run a diff against the original.
   
  
• You may not use CC 5.xx or Link 5.xx. If that is all you have, it isn't a big worry as you will be sending me sources back. But if you part-compile, I'll need it to be compatible with:
  • Norcroft C version 4.00 (cc v4.00, link v4.00)
  • objasm version 2.00
  • Nick Roberts' ASM version 4.09
  • BASIC version 1.16, optionally with Darren Salt's ExtBASasm version 1.77.
  • as version 1.21 (Niklas Rojemo)
  • Norcroft Pascal version 4.00
  The libraries used are:
  • DeskLib version 2.30
  • Standard C library, as supplied with Norcroft C version 4.00
    (but not RISC_OSLib)
  
   
  You may mix and match as applicable, so long as...
  • BASIC code: I can StrongBS it and run it.
  • APCS code: I can hit Sh-Ctrl-C in !Zap and it'll build.
  
   
  If you use a different or custom library, please ensure the object file(s) are publically available. It would also be nice if the library source was available, at least here with the sourcecode if not public. But that's an issue between yourself and your conscience.
   
  
• I reserve the right to modify these rules as I see fit, at any time. The new rules WILL come into effect immediately, you have the option of deleting the sources and backing out with no repercissions.
  Basically, the rules are to:
  • Prevent unknowing users installing development code and wondering why it might not be working as it should;
  • To make it obvious that this is not a source code free-for-all. You may happily hack away to your heart's content, but you are expected to contribute your code to the main application. It is a share-and-share alike.
  
   
  
• If you plan to use the common excuse, I don't want anybody to see my code, then grow up. My code I don't feel is a screaming advert for proper coding style, but I am making it available as a gesture of goodwill and to help along those users of Argo's Voyager. Whether it is comprehensible or not is totally by-the-by. :-)
   
  
• Finally, no part of this code may be used in another application without permission of the original author (that's myself) and the author(s) of changes. To make life a little easier, we'll say that the other-authors rule only applies to sections of code > 10 lines (in original source format). Thus, if a routine by me gets trivial-bugfixed by eight different people, you need only ask me, not nine people! But entire functions written by a contributor, you'd need to ask both of us.
  The obvious exception to the rule is if you plan to recycle your own code!
   
  
• Above all else, support the concept of Open Source, share your modifications, help make the projects better, and everybody gets to benefit. Okay?

Executables

• The executables here, or linked from here, are not for free distribution. They are development code, and may require specific resources. They may be complete, or simply patch files.
   
  
• You understand that the code may not have been tested and may have adverse results to the wellbeing of your system. Specifically, it may be a version designed to work with a specific system or piece of hardware, the assumption of which may cause all hell to break loose on your system.
   
  
• Neither myself or any of the 3rd party authors are liable for anything that may go wrong as a result of your use or inability to use this software.
   
  
• For aid in versioning, a version modified by a given author retains the original version number, but instead has their initials suffixed. Upon such time as the changes are integrated into the main source, the version number may be updated.

QuickVoy

Emily

However, the development version 0.34 is available for download by completing the form below. This is the 'package' version, and currently includes no source.

Emily is written in C, and it is my first attempt at something like this, so chunks of code are little more than suck-it-and-see. The internals of the editor don't bear thinking about!