Laptop running XP
but emulating the QL using QPC2
- Original Message - From: "Malcolm Lear"
To:
Sent: Monday, February 07, 2011 12:41 PM
Subject: Re: [Ql-Users] Approaches to parsing in SuperBASIC
On 07/02/2011 12:14, Lee Privett wrote:
Hey Malcolm, if you want a little bit of
-
From: "Malcolm Lear"
To:
Sent: Monday, February 07, 2011 12:41 PM
Subject: Re: [Ql-Users] Approaches to parsing in SuperBASIC
On 07/02/2011 12:14, Lee Privett wrote:
Hey Malcolm, if you want a little bit of help with conversion, two things
of interest, firstly i know nothi
Evening Tony,
> Well http://sourceforge.net/projects/docbook/ doesn't give the lightest
> clue as to what platform, and neither does the "View all files" link.
> Not a good start.
It's ALL platforms. They are all the same.
Welcome to my nightmare! That's how I got stuck even before I started.
Wh
Norman Dunbar wrote, on 7/Feb/11 10:49 | Feb7:
So, my advice to anyone considering writing documents is simple, do it
in Docbook. Do it once and create many different formats. Unfortunately
the learning curve is not shallow, but it's not steep either!
Well http://sourceforge.net/projects/doc
SVG format by any chance?
Scales beautifully at [almost] any resolution.
Cheers,
Norman.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL
Company Number: 05132767
Sure
Lee Privett
-
Sent from my Laptop running XP
but emulating the QL using QPC2
- Original Message -
From: "Malcolm Lear"
To:
Sent: Monday, February 07, 2011 12:41 PM
Subject: Re: [Ql-Users] Approaches to
On 07/02/2011 12:14, Lee Privett wrote:
Hey Malcolm, if you want a little bit of help with conversion, two
things of interest, firstly i know nothing of ePub formats etc. but if
you have the text file in Microsoft Word, you can get the index
created for you automatically (if you have a sepera
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-
> boun...@lists.q-v-d.com] On Behalf Of Plastic
> Sent: 07 February 2011 10:58
> To: ql-us...@q-v-d.com
> Subject: Re: [Ql-Users] Approaches to parsing in SuperBASIC
>
> On Mon, Feb 7, 2011 at 4:34
Message -
From: "Malcolm Lear"
To:
Sent: Monday, February 07, 2011 11:13 AM
Subject: Re: [Ql-Users] Approaches to parsing in SuperBASIC
On 07/02/2011 11:00, Plastic wrote:
On Mon, Feb 7, 2011 at 4:43 AM, Malcolm Lear wrote:
That would be great, Dave. I'll carry on going t
On 07/02/2011 11:00, Plastic wrote:
On Mon, Feb 7, 2011 at 4:43 AM, Malcolm Lear wrote:
That would be great, Dave. I'll carry on going through the book
concentrating on getting a full text version for you. It would make a good
replacement to the 'Beginners Guide' in the original manual. I've
On 07/02/2011 10:57, Plastic wrote:
On Mon, Feb 7, 2011 at 4:34 AM, Dave Walker wrote:
Just a suggestion - if you are going to work on producing a better version
of the manual then I would suggest that PDF is NOT the best format. It
does not tend to display well on modern ereader type devi
On Mon, Feb 7, 2011 at 4:43 AM, Malcolm Lear wrote:
> That would be great, Dave. I'll carry on going through the book
> concentrating on getting a full text version for you. It would make a good
> replacement to the 'Beginners Guide' in the original manual. I've seen Jan a
> couple of times in Ne
On Mon, Feb 7, 2011 at 4:34 AM, Dave Walker wrote:
> Just a suggestion - if you are going to work on producing a better version
> of the manual then I would suggest that PDF is NOT the best format. It
> does not tend to display well on modern ereader type devices, and does not
> support feature
> I have already made it a project for
> the future to re-do the manual, make it into a searchable website, etc.
Dilwyn supplies the UserGuide in PDF format on his QL On A Stcik system.
It's already searchable.
Cheers,
Norman.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
Thor
Morning all,
On 07/02/11 10:34, Dave Walker wrote:
> Just a suggestion - if you are going to work on producing a better version of
> the manual then I would suggest that PDF is NOT the best format. It does
> not tend to display well on modern ereader type devices, and does not support
> featu
That would be great, Dave. I'll carry on going through the book
concentrating on getting a full text version for you. It would make a
good replacement to the 'Beginners Guide' in the original manual. I've
seen Jan a couple of times in Newmarket and if I have the opportunity
I'll ask her if she'
Just a suggestion - if you are going to work on producing a better version of
the manual then I would suggest that PDF is NOT the best format. It does not
tend to display well on modern ereader type devices, and does not support
features such as text-flow if font sizes are zoomed. I would su
On Mon, Feb 7, 2011 at 1:44 AM, Tobias Fröschle <
tobias.froesc...@t-online.de> wrote:
> Am Sonntag, den 06.02.2011, 17:56 -0600 schrieb Plastic:
> > Let me play with some code and see what I come up with over the next
> couple
> > of days. I think I can be a lot more computationally economical, b
On Mon, Feb 7, 2011 at 3:41 AM, Norman Dunbar wrote:
> On 06/02/11 20:14, Plastic wrote:I bought this book years ago from Quanta,
> and was completely horrified
> by the quality of print. Nothing to do with Quanta of course, just a
> commercial book that looks like it was run off on a dot matrix p
If it helps any, I have a period of 6 months plus of medically-enforced
non-work, so I have LOTS of free time. I would be happy to convert books to
PDFs in the style of the manual, if they are in the public domain or if I
have permission from the rights holder. I have already made it a project for
The download is 2.2 MB, it is not text searchable at all and is pretty
cr4p. However, it's better than nothing! Just!
Cheers,
Norman.
I'm slowly sorting this book out, so it will be searchable. However it's
a bigger job that I first imagined. A version that matches the user
guide format wou
I never felt RIGHT$ was clumsy, because it was easy and as Phoebus will tell
you, I do like to be spoon-fed ;) I do remember missing it so much when I
got my QL.
Hi Dave,
I can't let you go wanting. I've never used RIGHT$ myself, but I guess
this implements it correctly.
10 DEFine FuNction
On 06/02/11 20:14, Plastic wrote:
> I don't have anything - restarting from scratch.
Jan Jones' SuperBasic book is online at
http://www.speccy.org/sinclairql/archivo/docs/books/qlsbtdh.pdf - the
quality of the PDF is about as good as the original print run. :-)
I bought this book years ago from Q
Am Sonntag, den 06.02.2011, 17:56 -0600 schrieb Plastic:
> Let me play with some code and see what I come up with over the next couple
> of days. I think I can be a lot more computationally economical, but my code
> will not flex easily to other cases, whereas your code is applicable in a
> lot of
Am 07.02.2011 02:11, schrieb QL-MyLink (f/fh):
221 lines of code!
Tobias, do have more 'lazy Sunday afternoons', please.
Wish I could have written the same - it's poked some valuable ideas
into my memory. Thank you.
In there however, is a small shadow, specifically regarding your
SELect ON
221 lines of code!
Tobias, do have more 'lazy Sunday afternoons', please.
Wish I could have written the same - it's poked some valuable ideas into my
memory. Thank you.
In there however, is a small shadow, specifically regarding your SELect
ON's. Does your code rely on the additional utili
Wow. You really thought about it. 221 lines of code!
I have this notion that I need to scan through the characters and split the
input into words. I can simplify a lot because the bounds are known and very
limited.
For example, " S " INSTR cmd$ is a very simple case and so is " L " - so for
these
On Sun, Feb 6, 2011 at 11:58 AM, QL-MyLink (f/fh)
wrote:
> Tobias helpfully said -
>
>
> Dave,
> the "manual" is right here and your memory is wrong ;-).
> -
>
> Brave Dave,
> Do you have a copy of Jan Jones?
>
> It's great for *all*
Dave,
had a lazy Sunday afternoon and was thinking about your problem - And,
being a bit challenged and had nothing else to do, wrote a
parser/analyzer for your "Language":
Ended up with quite a bit of code, the problem is not as simple as it
seems (Hope I didn't over-complicate things). But I
Tobias helpfully said -
Dave,
the "manual" is right here and your memory is wrong ;-).
-
Brave Dave,
Do you have a copy of Jan Jones?
It's great for *all* SBasic INSTR-uctions.
John in Wales
___
Tobias Fröschle wrote, on 6/Feb/11 11:36 | Feb6:
Am 06.02.2011 12:19, schrieb Plastic:
Also...
One of the major problems I'm having is the "manual" I downloaded. The
"QPCKeywords V1_02" document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remem
On Sun, Feb 6, 2011 at 5:47 AM, Tobias Fröschle <
tobias.froesc...@t-online.de> wrote:
> Am 06.02.2011 12:10, schrieb Plastic:
>
> For clarity: ABC is the format of the flight number. eg: AAL2123,
>> CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
>> BAA418, etc...
>>
>
Am 06.02.2011 12:10, schrieb Plastic:
For clarity: ABC is the format of the flight number. eg: AAL2123,
CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
BAA418, etc...
I like the way you have the parser call a function to isolate each
component. I have until this point
Tobias, thank you! I have struggled with this for a couple of days. This'll
teach me for having started out on a Commodore PET.
I couldn't find INSTR in this manual because it's in the wrong place. After
IO_PRIORITY. It never crossed my mind to look past the place it would
logically be.
This is h
Am 06.02.2011 12:19, schrieb Plastic:
Also...
One of the major problems I'm having is the "manual" I downloaded. The
"QPCKeywords V1_02" document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remember how to use
them. I would dig in the garage to
Also...
One of the major problems I'm having is the "manual" I downloaded. The
"QPCKeywords V1_02" document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remember how to use
them. I would dig in the garage to find the old printed manual, but it's
FR
For clarity: ABC is the format of the flight number. eg: AAL2123,
CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
BAA418, etc...
I like the way you have the parser call a function to isolate each
component. I have until this point been thinking in terms of... (pseudo-cod
Dave,
ABC C NN - 2 digits is an altitude in thousands of feet
ABC C NN X - the X modifier expedites the altitude change (where
possible/reasonable)
ABC C NNN - 3 digits is a heading in degrees
ABC C NNN L (or R) - where a course change follows the shortest turn, L
or R modifier ma
I'm working on the command parser for my Air Traffic Control sim. I have not
written a parser in this sense before.
The parser takes input from the user, and parses it into meaningful
instructions to pass to an aircraft. It emulates a unified "ear" for the
pilots of all the aircraft.
It deals wit
39 matches
Mail list logo
