Re: [Ql-Users] QL wikis and information

[Norman Dunbar via Ql-Users]

Qdosmsq is mine, and is nostly software as I am most definitely not a hardware 
guru, nor do I play one on tv.

I helped convert and set up qlwiki.qlforum.co.uk too. We could create a 
hardware namespace, separate from the existing qlwiki namespace for these 
things?

Comments?


Cheers,
Norm.

On 16 April 2018 20:14:37 BST, pjwitte via Ql-Users  
wrote:
>On 16/04/2018 18:14, Dave Park via Ql-Users, Re: Graphic objects and 
>padding, wrote:
>> It's almost like we need some kind of public "infobase" or
>"programmer's
>> wiki" to make these nuggets easily searchable and reference-able.
>>
>> Where might we find something like that?
>>
>> PS: I offer free web hosting to anyone willing to run it.
>>
>> On Mon, Apr 16, 2018 at 9:47 AM, pjwitte via Ql-Users <
>> ql-users@lists.q-v-d.com> wrote:
>At present there is 
>http://qdosmsq.dunbar-it.co.uk/doku.php?id=qdosmsq:start, which is a 
>technical wiki. There is also 
>http://qlwiki.qlforum.co.uk/doku.php?id=qlwiki:sinclair_ql_home_computer,
>
>which is more "historical".  There is of course lots more info out 
>there, but it is widely spread around.
>
>I had rather hoped the relevant people would pipe up here and trumpet 
>their wares! The above request seems like a timely reminder.
>
>A lot of this passes people by (and as we get older, some of us may 
>need regular refreshers ;-) So it would be great if those of you 
>sitting on valuable information could (re)introduce yourselves and 
>briefly (or not) tell us about the essential hardware and software 
>information you have in custody.
>___
>QL-Users Mailing List

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
QL-Users Mailing List

[Ql-Users] QL wikis and information

[pjwitte via Ql-Users]

On 16/04/2018 18:14, Dave Park via Ql-Users, Re: Graphic objects and 
padding, wrote:

It's almost like we need some kind of public "infobase" or "programmer's
wiki" to make these nuggets easily searchable and reference-able.

Where might we find something like that?

PS: I offer free web hosting to anyone willing to run it.

On Mon, Apr 16, 2018 at 9:47 AM, pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> wrote:
At present there is 
http://qdosmsq.dunbar-it.co.uk/doku.php?id=qdosmsq:start, which is a 
technical wiki. There is also 
http://qlwiki.qlforum.co.uk/doku.php?id=qlwiki:sinclair_ql_home_computer, 
which is more "historical".  There is of course lots more info out 
there, but it is widely spread around.


I had rather hoped the relevant people would pipe up here and trumpet 
their wares! The above request seems like a timely reminder.


A lot of this passes people by (and as we get older, some of us may 
need regular refreshers ;-) So it would be great if those of you 
sitting on valuable information could (re)introduce yourselves and 
briefly (or not) tell us about the essential hardware and software 
information you have in custody.

___
QL-Users Mailing List

Re: [Ql-Users] Graphic objects and padding

[Dave Park via Ql-Users]

It's almost like we need some kind of public "infobase" or "programmer's
wiki" to make these nuggets easily searchable and reference-able.

Where might we find something like that?

PS: I offer free web hosting to anyone willing to run it.

On Mon, Apr 16, 2018 at 9:47 AM, pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> wrote:

> On 14/04/2018 20:01, Marcel Kilgus via Ql-Users wrote:
>
>> pjwitte via Ql-Users wrote:
>>
>>> If those who "wrote the book" on these matters arent able/willing to
>>> pipe up, then we'll have to waste some time R-ingTFBs and doing the
>>> tests ourselves. I'll be back.
>>>
>> "The books" were written so long ago, even the people who wrote them
>> must usually spend some serious time to answer questions like yours.
>>
>> Regarding your question in the forum, the internal save area format
>> always has a "spare" long-word after each line, fuck knows why. So
>> that is why every line is 4 bytes longer, because it just writes out
>> the internal format. But it doesn't matter really, the "increment"
>> field in the file header is what's important, for all it's worth it
>> can be one 65kb per line and should still work, the field must just
>> match the data. If you construct a file yourself, use whatever line
>> increment pleases you.
>>
>> The fog is slowly clearing :) Thanks for your input. I
> assumed anyone "in the know" would just know the answer and
> not have to waste precious hours figuring out what was
> already known, as I did - and presumably many before me.
> Trying to derive the rules  from the various implementors
> proved frought, as it seems that, for pragmatic reasons (or
> perhaps to compensate for other's non-compliance) they
> mostly have their own rules for outputs and acceptable
> inputs. Anyway, once Im certain, Ill write it up, so no one
> needs to ask or answer this again.
>
> Per
> ___
> QL-Users Mailing List




-- 
Dave Park
d...@sinclairql.com
___
QL-Users Mailing List

Re: [Ql-Users] Graphic objects and padding

[pjwitte via Ql-Users]

On 14/04/2018 20:01, Marcel Kilgus via Ql-Users wrote:

pjwitte via Ql-Users wrote:

If those who "wrote the book" on these matters arent able/willing to
pipe up, then we'll have to waste some time R-ingTFBs and doing the
tests ourselves. I'll be back.

"The books" were written so long ago, even the people who wrote them
must usually spend some serious time to answer questions like yours.

Regarding your question in the forum, the internal save area format
always has a "spare" long-word after each line, fuck knows why. So
that is why every line is 4 bytes longer, because it just writes out
the internal format. But it doesn't matter really, the "increment"
field in the file header is what's important, for all it's worth it
can be one 65kb per line and should still work, the field must just
match the data. If you construct a file yourself, use whatever line
increment pleases you.


The fog is slowly clearing :) Thanks for your input. I
assumed anyone "in the know" would just know the answer and
not have to waste precious hours figuring out what was
already known, as I did - and presumably many before me.
Trying to derive the rules  from the various implementors
proved frought, as it seems that, for pragmatic reasons (or
perhaps to compensate for other's non-compliance) they
mostly have their own rules for outputs and acceptable
inputs. Anyway, once Im certain, Ill write it up, so no one
needs to ask or answer this again.

Per
___
QL-Users Mailing List