Date   

Re: Proposal to rationalise VDU variables

R NBW
 

Richard

I think what you intend is sensible. 

In progressing any programming language, you will come to a point where there well be incompatibilities in older programs and they will break.  If this want the case then we would still be using the old Microsoft Basic, complete with lunge numbers, GOTO and GOSUB.

Provided that you make it clear in your documentation what you have done and why, I think it is then the responsibility of the programmer to modify their code.

What use propose is logical and should stand the test of time.

Ray



On 21 Feb 2020, at 5:10 pm, Richard Russell <news@...> wrote:
I'm contemplating doing something drastic: making an incompatible change to BB4W (and indeed to BBCSDL subsequently)! I'd appreciate people's views on whether such an exceptional step can be justified.

Because of the way BBC BASIC's capabilities have grown over the years, anomalies have arisen in respect of the location of some 'system' variables. Specifically the 'cursor movement' flag (set using VDU 23,16...) and the 'line thickness' value (set using VDU 23,23...), which should both logically be part of the VDU variables structure @vdu{}, aren't. The cursor movement flag is currently at ?444 and the line thickness value at @vdu%?248 (in BB4W).

Apart from being 'illogical', not being part of the VDU variables structure has the practical consequence that in programs which deliberately save and restore this structure (e.g. banner.bbc, Ceefax.bbc, telstar.bbc and multiwin.bbc) these variables are not automatically saved as they should be. Some (but not all) of these programs deliberately save and restore the cursor movement flag separately, but none currently saves the line thickness value. Moving them into the VDU structure would fix this.

I have reluctantly accepted this situation in BB4W to date because of the compatibility implications of moving them. But BBCSDL has already set a precedent for moving the line thickness value (it is no longer at @vdu%!248, and indeed isn't even in the same place in 32-bit and 64-bit editions), and updating BB4W to v6.13a provides what might be the last ever opportunity for putting this anomaly 'right'.

So what are your views? If I don't fix this now, there will forever be frustration at the anomalies. But if I do there will definitely be programs that break (I know for sure that some programs set the line thickness using @vdu%!248=n because once upon a time it was the only way). Most likely the consequence will only be 'cosmetic' but it could be important, and such programs will need to be modified.

If I do make this change I will at least ensure that ?444 and @vdu%!248 become 'unused' locations, so that if any unmodified program does write to them no harm will be done.


Re: Proposal to rationalise VDU variables

 

Richard,

 

I am confident you will decide upon the better option.

 

However, I am aware you prefer acknowledgement.

 

Whilst I freely admit my knowledge of such intricacies is non-existent, I personally feel I would prefer no change was made.

 

Regards,

 

Bob.

 

 

From: Richard Russell
Sent: 21 February 2020 17:15
To: bb4w@groups.io
Subject: [Special] [bb4w] Proposal ro rationalise VDU variables

 

I'm contemplating doing something drastic: making an incompatible change to BB4W (and indeed to BBCSDL subsequently)! I'd appreciate people's views on whether such an exceptional step can be justified.

Because of the way BBC BASIC's capabilities have grown over the years, anomalies have arisen in respect of the location of some 'system' variables. Specifically the 'cursor movement' flag (set using VDU 23,16...) and the 'line thickness' value (set using VDU 23,23...), which should both logically be part of the VDU variables structure @vdu{}, aren't. The cursor movement flag is currently at ?444 and the line thickness value at @vdu%?248 (in BB4W).


Apart from being 'illogical', not being part of the VDU variables structure has the practical consequence that in programs which deliberately save and restore this structure (e.g. banner.bbc, Ceefax.bbc, telstar.bbc and multiwin.bbc) these variables are not automatically saved as they should be. Some (but not all) of these programs deliberately save and restore the cursor movement flag separately, but none currently saves the line thickness value. Moving them into the VDU structure would fix this.


I have reluctantly accepted this situation in BB4W to date because of the compatibility implications of moving them. But BBCSDL has already set a precedent for moving the line thickness value (it is no longer at @vdu%!248, and indeed isn't even in the same place in 32-bit and 64-bit editions), and updating BB4W to v6.13a provides what might be the last ever opportunity for putting this anomaly 'right'.


So what are your views? If I don't fix this now, there will forever be frustration at the anomalies. But if I do there will definitely be programs that break (I know for sure that some programs set the line thickness using @vdu%!248=n because once upon a time it was the only way). Most likely the consequence will only be 'cosmetic' but it could be important, and such programs will need to be modified.

If I do make this change I will at least ensure that ?444 and @vdu%!248 become 'unused' locations, so that if any unmodified program does write to them no harm will be done.

 


Proposal to rationalise VDU variables

Richard Russell
 

I'm contemplating doing something drastic: making an incompatible change to BB4W (and indeed to BBCSDL subsequently)! I'd appreciate people's views on whether such an exceptional step can be justified.

Because of the way BBC BASIC's capabilities have grown over the years, anomalies have arisen in respect of the location of some 'system' variables. Specifically the 'cursor movement' flag (set using VDU 23,16...) and the 'line thickness' value (set using VDU 23,23...), which should both logically be part of the VDU variables structure @vdu{}, aren't. The cursor movement flag is currently at ?444 and the line thickness value at @vdu%?248 (in BB4W).

Apart from being 'illogical', not being part of the VDU variables structure has the practical consequence that in programs which deliberately save and restore this structure (e.g. banner.bbc, Ceefax.bbc, telstar.bbc and multiwin.bbc) these variables are not automatically saved as they should be. Some (but not all) of these programs deliberately save and restore the cursor movement flag separately, but none currently saves the line thickness value. Moving them into the VDU structure would fix this.

I have reluctantly accepted this situation in BB4W to date because of the compatibility implications of moving them. But BBCSDL has already set a precedent for moving the line thickness value (it is no longer at @vdu%!248, and indeed isn't even in the same place in 32-bit and 64-bit editions), and updating BB4W to v6.13a provides what might be the last ever opportunity for putting this anomaly 'right'.

So what are your views? If I don't fix this now, there will forever be frustration at the anomalies. But if I do there will definitely be programs that break (I know for sure that some programs set the line thickness using @vdu%!248=n because once upon a time it was the only way). Most likely the consequence will only be 'cosmetic' but it could be important, and such programs will need to be modified.

If I do make this change I will at least ensure that ?444 and @vdu%!248 become 'unused' locations, so that if any unmodified program does write to them no harm will be done.


Re: New files uploaded to bb4w@groups.io

Storer, Darren
 

As soon as I open my big mouth, I soon regret it. I seem to have done David a bit of a disservice, as he has a wonderful new web site, which includes support for BBC Basic SDL :-)

http://www.proggies.uk/

(Sorry David)

Darren


On Mon, 10 Feb 2020 at 00:47, Storer, Darren <darren.storer@...> wrote:
Unfortunately, the excellent bb4wgames site is no longer available but you can take a look at the archives by following this link:

http://tinyurl.com/bb4wgames

...you should find some examples of how to make use of BOX2DGFX, which is designed to be used with BB4W.

Hope this helps

Darren

On Sun, 9 Feb 2020 at 21:24, <mclout@...> wrote:
Will this work for BBC Basic for SDL, and if so can you point to where I can learn how to use libraries like this.  Thank you.


Re: New files uploaded to bb4w@groups.io

Storer, Darren
 

PS. The Box2D documentation can be found by following the link below:



On Mon, 10 Feb 2020 at 00:48, Storer, Darren via Groups.Io <darren.storer=gmail.com@groups.io> wrote:
Unfortunately, the excellent bb4wgames site is no longer available but you can take a look at the archives by following this link:

http://tinyurl.com/bb4wgames

...you should find some examples of how to make use of BOX2DGFX, which is designed to be used with BB4W.

Hope this helps

Darren

On Sun, 9 Feb 2020 at 21:24, <mclout@...> wrote:
Will this work for BBC Basic for SDL, and if so can you point to where I can learn how to use libraries like this.  Thank you.


Re: New files uploaded to bb4w@groups.io

Storer, Darren
 

Unfortunately, the excellent bb4wgames site is no longer available but you can take a look at the archives by following this link:

http://tinyurl.com/bb4wgames

...you should find some examples of how to make use of BOX2DGFX, which is designed to be used with BB4W.

Hope this helps

Darren

On Sun, 9 Feb 2020 at 21:24, <mclout@...> wrote:
Will this work for BBC Basic for SDL, and if so can you point to where I can learn how to use libraries like this.  Thank you.


Re: New files uploaded to bb4w@groups.io

mclout@...
 

Will this work for BBC Basic for SDL, and if so can you point to where I can learn how to use libraries like this.  Thank you.


Re: New files uploaded to bb4w@groups.io

Jerónimo Luis Dalla Via
 

Great!

Thank you very much! 

El sáb., 8 de febrero de 2020 14:00, bb4w@groups.io Notification <bb4w+notification@groups.io> escribió:

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the bb4w@groups.io group.

Uploaded By: Richard Russell <news@...>

Description:
Box2D physics engine (BOX2DGFX updated)

Cheers,
The Groups.io Team


New files uploaded to bb4w@groups.io

bb4w@groups.io Notification <bb4w+notification@...>
 

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the bb4w@groups.io group.

Uploaded By: Richard Russell <news@...>

Description:
Box2D physics engine (BOX2DGFX updated)

Cheers,
The Groups.io Team


BBCSDL for Windows (ARM64)

Mohsen Alyafei
 

Hi Richard,

As there any moves on BBCSDL to work in native mode under Windows 10 on ARM. There are many laptops and tablets being released running Windows 10 on ARM64.

It would be nice to see BBCSDL running under Windows 10 (ARM64) native rather than using BB4W under the 32-bit x86 emulation mode.

https://docs.microsoft.com/en-us/windows/arm/
https://www.zdnet.com/article/windows-10-on-arm-what-you-need-to-know-before-you-buy-a-surface-pro-x/

Thanks


Re: v1.08a

 

Thank you for your patience and explanations.

With no real computer knowledge, I usually achieve an end result by simply

trying l(sometimes literally) hundreds of permutations. I do generally attain my goal but

trained programmers would be tearing their hair out. Hence, not always able to replicate

a result due to lack of notes.

Anyway, I have taken your comments on board and am grateful for your kind assistance.

 

At least, the elementary action of installing direct to my phone won’t ever be forgotten!

 

Regards,

 

Bob.

 

 

 

 

From: Jeremy Nicoll
Sent: 02 December 2019 12:50
To: bb4w@groups.io
Subject: Re: [bb4w] v1.08a

 

On Sun, 1 Dec 2019, at 23:44, The Famous Cash via Groups.Io wrote:

 

> I thought I had been navigating (through my PC with phone on USB) but

> Ray Would has pointed out I should have Downloaded using my phone.

 

You're misunderstanding.  When your phone is connected to a PC via a USB

cable the PC just sees it as a USB-attached disk, so you can use the PC to

put files on parts of the phone's disk-like storage.

 

You can also transfer files to the phone's storage by using the phone to

download the file, or wifi or (as someone-else suggests a cloud-storage

app like Dropbox) etc.

 

The end result is the .apk file is sitting somewhere on your phone.

 

 

You then use the phone's OS to navigate to (ie find) the .apk file, and you

run it.  That's to say, it is run ON THE PHONE.  Android opens the .apk

file, seeks your permission (maybe*) to install whatever is inside the .apk

file, and sets up the new application.

 

  * - in some versions of Android you have to alter something in Settings

  to allow .apk files not-downloaded-by-the-phone (or maybe, not from

  the Android App store) to be run like this,   but in others I think you are

  asked as Android starts to run the file

 

You can't run an .apk file /on a PC/ expecting it to install an app on a phone.

 

> Anyway, like most of my “insurmountable” tasks, the elementary use of

> the actual phone for the download solbved the problem.

 

If that's so it implies that as soon as your phone downloads an .apk file

it automatically then runs the just-downloaded .apk file.   Arguably that

is dangerous as it means if you unknowingly download an .apk file it will

start to install without you necessarily realising.    

 

 

But .apk files that arive on a phone some other way need to be found and

run manually.

 

 

 

--

Jeremy Nicoll - my opinions are my own.

 

 

 


Re: v1.08a

 

On Sun, 1 Dec 2019, at 23:44, The Famous Cash via Groups.Io wrote:

I thought I had been navigating (through my PC with phone on USB) but
Ray Would has pointed out I should have Downloaded using my phone.
You're misunderstanding. When your phone is connected to a PC via a USB
cable the PC just sees it as a USB-attached disk, so you can use the PC to
put files on parts of the phone's disk-like storage.

You can also transfer files to the phone's storage by using the phone to
download the file, or wifi or (as someone-else suggests a cloud-storage
app like Dropbox) etc.

The end result is the .apk file is sitting somewhere on your phone.


You then use the phone's OS to navigate to (ie find) the .apk file, and you
run it. That's to say, it is run ON THE PHONE. Android opens the .apk
file, seeks your permission (maybe*) to install whatever is inside the .apk
file, and sets up the new application.

* - in some versions of Android you have to alter something in Settings
to allow .apk files not-downloaded-by-the-phone (or maybe, not from
the Android App store) to be run like this, but in others I think you are
asked as Android starts to run the file

You can't run an .apk file /on a PC/ expecting it to install an app on a phone.


Anyway, like most of my “insurmountable” tasks, the elementary use of
the actual phone for the download solbved the problem.
If that's so it implies that as soon as your phone downloads an .apk file
it automatically then runs the just-downloaded .apk file. Arguably that
is dangerous as it means if you unknowingly download an .apk file it will
start to install without you necessarily realising.


But .apk files that arive on a phone some other way need to be found and
run manually.



--
Jeremy Nicoll - my opinions are my own.


Re: v1.08a

 

I’m still getting over the shock and frustration I spent months trying to use my PC to install to the phone!

I did get it working somehow though. . .

I am pleased with many of the programs I have written.  Remember, I know zero about “proper” programming and have sold quite a number to varied businesses.

When it comes to using wireless transfer, I would not know where to begin.  I daresay it’s easy but it’s beyond me at the moment.

I remember emailing Richard many years ago asking if it would ever be possible to program a phone. . . I reckoned there was a great commercial opportunity there.

I am now beginning to explore the potential.

I know I tried to compile one of my programs (SDL PC) and ended up with zipped files in the “exe” folder.  Not a clue what to do with them.

Now when I try to compile, I get “Internal error 254”.

I’ll get there eventually as always but it sure is frustrating when I spend so long trying to solve elementary problems which computer-literate folk would laugh at.

I really appreciate your guidance earlier, even though it makes me feel like a dimwit.

 

Regards,

Bob.

 

 

 

From: Ray Would via Groups.Io
Sent: 02 December 2019 00:15
To: bb4w@groups.io
Subject: Re: [bb4w] v1.08a

 

I frequently write on my PC and transfer to my Android device. Have you tried using wireless transfer rather than USB, or using Dropbox as a means of transfer.  The latter is useful in that you can provide a link to a document or program to make it accessible to others.

RNBW

On 1 Dec 2019, at 11:45 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:

Thank you for your help.

 

I was so convinced at the very start the program would have to be generated by my PC, I never contemplated the obvious download using the actual phone!

 

Of course it was easy now it was spelled out to me.  Thank you so much.

 

Out of interest, I was surprised I can run quite substantial programs on my phone but I would never be comfortabletrying to write or edit on the phone.

 

It is simple to do on PC then simply transfer by USB.

 

Regards,

 

Bob.

 

 

From: Ray Would via Groups.Io
Sent: 01 December 2019 21:00
To: bb4w@groups.io
Subject: Re: [bb4w] v1.08a

 

Hi

You are going about it all wrong. You don't need to use a usb transfer.

On your android device, go to www.bbcbasic.co.uk/bbcsdl.  Scroll down and you will find a list out install links for different platforms. Click on the Android Edition and download it. Click on the downloaded file. You will need to temporarily allow the installation from external programs. Don't worry, you will be guided through this.  You will probably be asked how you want to install the apk.  Choose Package Installer. This will install the apk for you together with the BBCBasicSDL launch icon.

You will then be able to write, edit and save your programs using the inbuilt editor.

RNBW

On 1 Dec 2019, at 6:41 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:

I have thought long and hard before posting this as it shows my ignorance of some pretty basic concepts.
However, in order to continue writing programs, I really would appreciate some input. . .
I actually took many months of toil to simply manage to be able to transfer SDL programs written on PC to my android phone.
It took so long, I have no clue how I actually managed it in the end but it did eventually work and I have a few programs now working on my phone.
Now, I tried to incorporate today's update to v1,08a.  I eventually managed to get it on my PC after a struggle
I cannot see how to get the new version on my phone..
I know it's easy for computer literate folk but I am not such.
I have no clue what to do with APK file.  I cam "open" it with Notepad which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone.  (I see  BBCBasic-1.apk, BBCBasic-2.apk,  BBCBasic-3.apk from my previous attempts and today's BBCBasic (2).apk.  I also copied it to the file folder where my working programs are stored.
When I tap the BBC Basic icon, v1.07a still comes up.
Any help, please.
Whilst I am displaying my lack of ability, I throw these in for good measure. .. 
When I compiled a program a few weeks ago, I obtained a zip file in "exe" folder but did not manage to get it working.
Now, when I try to compile, I get "Internal error 254" message.
My programs are really good but, as far as "real" computing goes, I have little clue.  Any help appreciated with thanks.

 

 


Re: v1.08a

 

I frequently write on my PC and transfer to my Android device. Have you tried using wireless transfer rather than USB, or using Dropbox as a means of transfer.  The latter is useful in that you can provide a link to a document or program to make it accessible to others.

RNBW

On 1 Dec 2019, at 11:45 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:

Thank you for your help.

 

I was so convinced at the very start the program would have to be generated by my PC, I never contemplated the obvious download using the actual phone!

 

Of course it was easy now it was spelled out to me.  Thank you so much.

 

Out of interest, I was surprised I can run quite substantial programs on my phone but I would never be comfortabletrying to write or edit on the phone.

 

It is simple to do on PC then simply transfer by USB.

 

Regards,

 

Bob.

 

 

From: Ray Would via Groups.Io
Sent: 01 December 2019 21:00
To: bb4w@groups.io
Subject: Re: [bb4w] v1.08a

 

Hi

You are going about it all wrong. You don't need to use a usb transfer.

On your android device, go to www.bbcbasic.co.uk/bbcsdl.  Scroll down and you will find a list out install links for different platforms. Click on the Android Edition and download it. Click on the downloaded file. You will need to temporarily allow the installation from external programs. Don't worry, you will be guided through this.  You will probably be asked how you want to install the apk.  Choose Package Installer. This will install the apk for you together with the BBCBasicSDL launch icon.

You will then be able to write, edit and save your programs using the inbuilt editor.

RNBW

On 1 Dec 2019, at 6:41 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:

I have thought long and hard before posting this as it shows my ignorance of some pretty basic concepts.
However, in order to continue writing programs, I really would appreciate some input. . .
I actually took many months of toil to simply manage to be able to transfer SDL programs written on PC to my android phone.
It took so long, I have no clue how I actually managed it in the end but it did eventually work and I have a few programs now working on my phone.
Now, I tried to incorporate today's update to v1,08a.  I eventually managed to get it on my PC after a struggle
I cannot see how to get the new version on my phone..
I know it's easy for computer literate folk but I am not such.
I have no clue what to do with APK file.  I cam "open" it with Notepad which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone.  (I see  BBCBasic-1.apk, BBCBasic-2.apk,  BBCBasic-3.apk from my previous attempts and today's BBCBasic (2).apk.  I also copied it to the file folder where my working programs are stored.
When I tap the BBC Basic icon, v1.07a still comes up.
Any help, please.
Whilst I am displaying my lack of ability, I throw these in for good measure. .. 
When I compiled a program a few weeks ago, I obtained a zip file in "exe" folder but did not manage to get it working.
Now, when I try to compile, I get "Internal error 254" message.
My programs are really good but, as far as "real" computing goes, I have little clue.  Any help appreciated with thanks.

 


Re: v1.08a

 

Thank you for your help.

 

I was so convinced at the very start the program would have to be generated by my PC, I never contemplated the obvious download using the actual phone!

 

Of course it was easy now it was spelled out to me.  Thank you so much.

 

Out of interest, I was surprised I can run quite substantial programs on my phone but I would never be comfortabletrying to write or edit on the phone.

 

It is simple to do on PC then simply transfer by USB.

 

Regards,

 

Bob.

 

 

From: Ray Would via Groups.Io
Sent: 01 December 2019 21:00
To: bb4w@groups.io
Subject: Re: [bb4w] v1.08a

 

Hi

You are going about it all wrong. You don't need to use a usb transfer.

On your android device, go to www.bbcbasic.co.uk/bbcsdl.  Scroll down and you will find a list out install links for different platforms. Click on the Android Edition and download it. Click on the downloaded file. You will need to temporarily allow the installation from external programs. Don't worry, you will be guided through this.  You will probably be asked how you want to install the apk.  Choose Package Installer. This will install the apk for you together with the BBCBasicSDL launch icon.

You will then be able to write, edit and save your programs using the inbuilt editor.

RNBW

On 1 Dec 2019, at 6:41 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:

I have thought long and hard before posting this as it shows my ignorance of some pretty basic concepts.
However, in order to continue writing programs, I really would appreciate some input. . .
I actually took many months of toil to simply manage to be able to transfer SDL programs written on PC to my android phone.
It took so long, I have no clue how I actually managed it in the end but it did eventually work and I have a few programs now working on my phone.
Now, I tried to incorporate today's update to v1,08a.  I eventually managed to get it on my PC after a struggle
I cannot see how to get the new version on my phone..
I know it's easy for computer literate folk but I am not such.
I have no clue what to do with APK file.  I cam "open" it with Notepad which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone.  (I see  BBCBasic-1.apk, BBCBasic-2.apk,  BBCBasic-3.apk from my previous attempts and today's BBCBasic (2).apk.  I also copied it to the file folder where my working programs are stored.
When I tap the BBC Basic icon, v1.07a still comes up.
Any help, please.
Whilst I am displaying my lack of ability, I throw these in for good measure. .. 
When I compiled a program a few weeks ago, I obtained a zip file in "exe" folder but did not manage to get it working.
Now, when I try to compile, I get "Internal error 254" message.
My programs are really good but, as far as "real" computing goes, I have little clue.  Any help appreciated with thanks.

 


Re: v1.08a

 

 

Many thanks for your help.

 

I thought I had been navigating (through my PC with phone on USB) but Ray Would has pointed out I should have Downloaded using my phone.

 

Sounds obvious now but I was stuck in trying to achieve that by USB.  (I did get it to work eventually before as I said).

 

On the point of note-keeping.  I normally do know what stage I am at but, having tried every possible combination I could think of,

I was just continually banging my head on the wall for moths.  Literally hundreds of attempts.

 

Anyway, like most of my “insurmountable” tasks, the elementary use of the actual phone for the download solbved the problem.

 

Thanks again.

 

Regards,

 

Bob.

 

 

 

 

From: Jeremy Nicoll
Sent: 01 December 2019 21:05
To: bb4w@groups.io
Cc: thefamouscash@...
Subject: Re: [bb4w] v1.08a

 

On Sun, 1 Dec 2019, at 18:41, The Famous Cash via Groups.Io wrote:

 

> I have no clue what to do with APK file. I cam "open" it with Notepad

> which is obviously of no use but don't see what I can else do with it.

 

> I copied it through USB cable to "Download" in android phone. (I see

> BBCBasic-1.apk, BBCBasic-2.apk, BBCBasic-3.apk from my previous

> attempts and today's BBCBasic (2).apk. I also copied it to the file

> folder where my working programs are stored.

 

It is the installer for BBC Basic.  You need to navigate to it using your

phone's file manager and then run it.   I suppose you really also need

to know where the current version's .apk file is, in case you want to

return to using it, if the newest version doesn't work for you.

 

Surely that is what you will have done to install the previous version?

 

Why did you not keep notes on how you installed that?

 

--

Jeremy Nicoll - my opinions are my own.

 

 

 


Re: v1.08a

 

On Sun, 1 Dec 2019, at 18:41, The Famous Cash via Groups.Io wrote:

I have no clue what to do with APK file. I cam "open" it with Notepad
which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone. (I see
BBCBasic-1.apk, BBCBasic-2.apk, BBCBasic-3.apk from my previous
attempts and today's BBCBasic (2).apk. I also copied it to the file
folder where my working programs are stored.
It is the installer for BBC Basic. You need to navigate to it using your
phone's file manager and then run it. I suppose you really also need
to know where the current version's .apk file is, in case you want to
return to using it, if the newest version doesn't work for you.

Surely that is what you will have done to install the previous version?

Why did you not keep notes on how you installed that?

--
Jeremy Nicoll - my opinions are my own.


Re: v1.08a

 

Hi
You are going about it all wrong. You don't need to use a usb transfer.

On your android device, go to www.bbcbasic.co.uk/bbcsdl.  Scroll down and you will find a list out install links for different platforms. Click on the Android Edition and download it. Click on the downloaded file. You will need to temporarily allow the installation from external programs. Don't worry, you will be guided through this.  You will probably be asked how you want to install the apk.  Choose Package Installer. This will install the apk for you together with the BBCBasicSDL launch icon.

You will then be able to write, edit and save your programs using the inbuilt editor.

RNBW


On 1 Dec 2019, at 6:41 pm, "The Famous Cash via Groups.Io" <blueyonder.co.uk@groups.io target=_blank>thefamouscash=blueyonder.co.uk@groups.io> wrote:
I have thought long and hard before posting this as it shows my ignorance of some pretty basic concepts.
However, in order to continue writing programs, I really would appreciate some input. . .
I actually took many months of toil to simply manage to be able to transfer SDL programs written on PC to my android phone.
It took so long, I have no clue how I actually managed it in the end but it did eventually work and I have a few programs now working on my phone.
Now, I tried to incorporate today's update to v1,08a.  I eventually managed to get it on my PC after a struggle
I cannot see how to get the new version on my phone..
I know it's easy for computer literate folk but I am not such.
I have no clue what to do with APK file.  I cam "open" it with Notepad which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone.  (I see  BBCBasic-1.apk, BBCBasic-2.apk,  BBCBasic-3.apk from my previous attempts and today's BBCBasic (2).apk.  I also copied it to the file folder where my working programs are stored.
When I tap the BBC Basic icon, v1.07a still comes up.
Any help, please.
Whilst I am displaying my lack of ability, I throw these in for good measure. .. 
When I compiled a program a few weeks ago, I obtained a zip file in "exe" folder but did not manage to get it working.
Now, when I try to compile, I get "Internal error 254" message.
My programs are really good but, as far as "real" computing goes, I have little clue.  Any help appreciated with thanks.


v1.08a

 

I have thought long and hard before posting this as it shows my ignorance of some pretty basic concepts.
However, in order to continue writing programs, I really would appreciate some input. . .
I actually took many months of toil to simply manage to be able to transfer SDL programs written on PC to my android phone.
It took so long, I have no clue how I actually managed it in the end but it did eventually work and I have a few programs now working on my phone.
Now, I tried to incorporate today's update to v1,08a.  I eventually managed to get it on my PC after a struggle
I cannot see how to get the new version on my phone..
I know it's easy for computer literate folk but I am not such.
I have no clue what to do with APK file.  I cam "open" it with Notepad which is obviously of no use but don't see what I can else do with it.
I copied it through USB cable to "Download" in android phone.  (I see  BBCBasic-1.apk, BBCBasic-2.apk,  BBCBasic-3.apk from my previous attempts and today's BBCBasic (2).apk.  I also copied it to the file folder where my working programs are stored.
When I tap the BBC Basic icon, v1.07a still comes up.
Any help, please.
Whilst I am displaying my lack of ability, I throw these in for good measure. .. 
When I compiled a program a few weeks ago, I obtained a zip file in "exe" folder but did not manage to get it working.
Now, when I try to compile, I get "Internal error 254" message.
My programs are really good but, as far as "real" computing goes, I have little clue.  Any help appreciated with thanks.


Re: Moving Prog to a MAC

Martin
 

I suggest that you first get the BBC SDL version for Windows, and try to move the code to that. Depending on how much Windows-specific code you have, that may be easy or not. But that will identify what changes you need to make from BBC4W to BBCSDL.

Then install BBC SDL for Mac - you will need access to a Mac! Move your SDL code over to the Mac, and try it. You may find things that do not work (due to Windows/Mac differences), and you may need some code to detect which machine you are on so code can be slightly different on the two machines (and so the code can still be common). Then you can 'compile' it to a dmg file (which can only be done on a Mac) and pass that file on to your friends who own Macs.

All perfectly possible, with a little time & effort. I am currently testing a 80k+ source program on Windows that will run on a Mac ... but it has been developed over several years! (and indeed started as a RISC OS program!).

Martin

On 18/11/2019 20:38, Storer, Darren wrote:
Hi Stephen,
Oops! Trust me to open my big mouth without digging further...
In the Mac version of the BBC Basic SDL IDE, there is a toolbar with an
icon that looks like two cogs; click this icon and you can "create an
application bundle" in the form of a Mac .dmg file. This function should be
perfect to "compile" your program for use on a Mac.
Apologies for the earlier misinformation
Darren
On Mon, 18 Nov 2019 at 16:22, Storer, Darren <darren.storer@...>
wrote:

Hi Stephen,

Depending on how which features of BB4W your program uses, you can usually
port directly to BBC Basic SDL, for a number of platforms, including Mac;
I'm using it on Mac OS (Catalina) with no problems.

You can find all the BBC Basic SDL downloads here:

http://www.bbcbasic.co.uk/bbcsdl/

...and amazingly, they are FREE!

However, I'm not aware of a compile option for Mac, I've only seen BBC
Basic SDL produce .apk files for Android.

Hope this helps

Darren


On Mon, 18 Nov 2019 at 07:50, R.E. <hatch@...> wrote:

Hi
I wrote a small program in BBC Basic on windows a year or so ago, and
several friends have asked me if I can move it to their Mac computers.
I've not done this in the past so I'm guessing that if I get a copy of
BBC basic for Mac
then I can move my code to the Mac and have it compile a version for Mac
computers.
Is that right? And can I still get a copy of BBC basic for the Mac? If
so--where?
Is this what I need to do?
Any help would sure be appreciated. Thank you.
Stephen Hatch


Hi Stephen,
Oops! Trust me to open my big mouth without digging further...
In the Mac version of the BBC Basic SDL IDE, there is a toolbar with an icon that looks like two cogs; click this icon and you can "create an application bundle" in the form of a Mac .dmg file. This function should be perfect to "compile" your program for use on a Mac.
Apologies for the earlier misinformation
Darren
On Mon, 18 Nov 2019 at 16:22, Storer, Darren <darren.storer@... <mailto:darren.storer@...>> wrote:
Hi Stephen,
Depending on how which features of BB4W your program uses, you can
usually port directly to BBC Basic SDL, for a number of platforms,
including Mac; I'm using it on Mac OS (Catalina) with no problems.
You can find all the BBC Basic SDL downloads here:
http://www.bbcbasic.co.uk/bbcsdl/
...and amazingly, they are FREE!
However, I'm not aware of a compile option for Mac, I've only seen
BBC Basic SDL produce .apk files for Android.
Hope this helps
Darren
On Mon, 18 Nov 2019 at 07:50, R.E. <hatch@...
<mailto:hatch@...>> wrote:
Hi
 I wrote a small program in BBC Basic on windows a year or so
ago, and
several friends have asked me if I can move it to their Mac
computers.
  I've not done this in the past so I'm guessing that if I get
a copy of BBC basic for Mac
then I can move my code to the Mac and have it compile a version
for Mac computers.
 Is that right?  And can I still get a copy of BBC basic for
the Mac?  If so--where?
Is this what I need to do?
Any help would sure be appreciated.  Thank you.
Stephen Hatch