Scratch

Sperry wrote:

Nevermind my problem, I was using an old version of Panther, with the un-updated file blocks

It turn out it will read the contents of the online text document.

Tags that i would like to use in our code
<TEXT="TEXT">
<BR> line break

what tags would you like?

You got post 1200!!!

sparks wrote:

Sperry wrote:

Nevermind my problem, I was using an old version of Panther, with the un-updated file blocks

It turn out it will read the contents of the online text document.

Tags that i would like to use in our code
<TEXT="TEXT">
<BR> line break

what tags would you like?

really? wow! that's perfect!

<BR> is already used for that in HTML, which might be good, I was thinking that we can make the file easier for Scratch to read if a prompt is only 1 character, e.g [/] could be break, or if all prompts are the same length, it saves the program time working out how long the prompt is.

e.g.

[break]
repeat until letter (count) = ]
set store to join store and letter (count) of file
change count by 1

or

set store to letters (current letter) to (current letter) + 4

much less coding if they're all an expected length

It doesn't really matter how long the tag is, Each letter takes about 1/8 - 1/3 of a second to get.

I will try to make the scripts as short as possible, if that is what you are trying to say.

using the <> holds a similarity to html, and as Panther is open source, other people who want to read the file can understand it more easily. so I think html style coding is a good idea.

how about one file that contains
•version number, so that a project can tell if it will read the file properly, or if the project needs to be updated (in case we make a big change some time)
•number of other files (each paragraph or topic or picture can have a file)
•names of files (so that they can be opened through Panther)

here would be an example of the content of a file called "ref" or something:
*things in brackets are just to explain)
Version1.0Panther Developed
<#files=5>
<header=img> (file name=content type could be used?)
<welcome=spc> a speech bubble file
<message=txt> (main text)

the "ref" (refrence file) would therefore supply file names and how they should be treated and by providing the file name, Panther can open them.

The reason more than one file should be used is 1) to stop them getting too big, and 2) so that the content can be loaded in one go, using the method of text, speech bubble or picture described by the = after the file name.

we could even provide prompts in the ref file that controls the order that the files are loaded into Panther.

markyparky56 wrote:

Is it just me or does the colours tab not work in the newest version? I dont need it but i was just looking around.

it has a problem opening if you load a project that was made using the previous version... it's a big glitch.

markyparky56 wrote:

Is it just me or does the colours tab not work in the newest version? I dont need it but i was just looking around.

It works for me.

MathWizz wrote:

markyparky56 wrote:

sparks wrote:

using the <> holds a similarity to html, and as Panther is open source, other people who want to read the file can understand it more easily. so I think html style coding is a good idea.

how about one file that contains
•version number, so that a project can tell if it will read the file properly, or if the project needs to be updated (in case we make a big change some time)
•number of other files (each paragraph or topic or picture can have a file)
•names of files (so that they can be opened through Panther)

here would be an example of the content of a file called "ref" or something:
*things in brackets are just to explain)
Version1.0Panther Developed
<#files=5>
<header=img> (file name=content type could be used?)
<welcome=spc> a speech bubble file
<message=txt> (main text)

the "ref" (refrence file) would therefore supply file names and how they should be treated and by providing the file name, Panther can open them.

The reason more than one file should be used is 1) to stop them getting too big, and 2) so that the content can be loaded in one go, using the method of text, speech bubble or picture described by the = after the file name.

we could even provide prompts in the ref file that controls the order that the files are loaded into Panther.

This means that they can have online highscore boards? Right?

No, I don't think so. I think we would need some kind of database for that.

So it can't write to files on the internet... makes sense...

Sperry wrote:

sparks wrote:

using the <> holds a similarity to html, and as Panther is open source, other people who want to read the file can understand it more easily. so I think html style coding is a good idea.

how about one file that contains
•version number, so that a project can tell if it will read the file properly, or if the project needs to be updated (in case we make a big change some time)
•number of other files (each paragraph or topic or picture can have a file)
•names of files (so that they can be opened through Panther)

here would be an example of the content of a file called "ref" or something:
*things in brackets are just to explain)
Version1.0Panther Developed
<#files=5>
<header=img> (file name=content type could be used?)
<welcome=spc> a speech bubble file
<message=txt> (main text)

the "ref" (refrence file) would therefore supply file names and how they should be treated and by providing the file name, Panther can open them.

The reason more than one file should be used is 1) to stop them getting too big, and 2) so that the content can be loaded in one go, using the method of text, speech bubble or picture described by the = after the file name.

we could even provide prompts in the ref file that controls the order that the files are loaded into Panther.

Good ideas, very good ideas!

So you'r thinking something like:
if (current version of Panther == 1.0 && docTypePanther == 1.1)
{
  writeToScreen("You need to update your Panther program to get the most out of your experience! Please got to pantherprogramming.weebly.com to get the latest version of Panther!");
}
else
{
   writeDocToScreen;
}

Sorry for the C++ style coding, it's what I use when I'm not on scratch. (I'm a curly bracket lover!  )

GO CURLY BRACKETS!!!!
Anyway. Iv found a glitch, when you open a dialog box in presentation mode it mucks up the screen.

well yeah, If I'm referring to a scratch program, I print out the blocks.
|if<(letters 1-4 of file []) = [v1.1]>
|... continue
|Else:
|open dialogue[oops!] with message [...sorry update etc.]]
|---------------------------------------------------

I've had that.
1) not much works in fullscreen atm anyway
2) it went away after the box closed

well as I said eariler, I'd really like to do that. Hope you don't mind... you wanted to help with the coding, and you have... maybe I make a start and then I send it to you?

oh, here's an example of the ref.txt file:

:info
Iam=reffile
<version=1.0>
<Panther1.0>

:file numbers
<files=n>

:files
<header.txt=img> anything after the > is ignored
<speak_welcome.txt=spc>

the idea is that a line beginnning with : is a "hat" so that Panther can search the file for the section it wants with a keyword.

sparks wrote:

well as I said eariler, I'd really like to do that. Hope you don't mind... you wanted to help with the coding, and you have... maybe I make a start and then I send it to you?

oh, here's an example of the ref.txt file:

:info
Iam=reffile
<version=1.0>
<Panther1.0>

:file numbers
<files=n>

:files
<header.txt=img> anything after the > is ignored
<speak_welcome.txt=spc>

the idea is that a line beginnning with : is a "hat" so that Panther can search the file for the section it wants with a keyword.

I don't mind. You can start. On the weebly site, there is a hidden page called test, if you look at that; that is the page I was working with.

Heres some code that I would suggest:
(I would suggest to keep some things abbreviated to shorten parsing times.)

:INFO <-- Start section INFO
FileType=ref; <-- Set file type to reference
CurrentVer=Panther V1.0; <-- Set latest version to 1.0
UserVerNum=(1.0); <-- Set the users version to 1.0 (Is there a way to determine the users version?)

:FILES <-- Start section FILES
NumOfFiles=NumOfFiles; <-- Set number of files to be used
FilesToParse:(FileA, FileB, e.t.c); <--Enter the file path of all files

:PAGE CODE <-- Start the pages code to be displayed on sceen to user
DisplayText:"Welocme to Panther..........; <--Text and any other functions for things to be displayed

Then it would wait for user interaction and then go to a page that a user specified (by clicking on.

Do you like my ideas?

I do like them. The version of the project can be stored in the project itself, and can be compared against the UserVerNum.

a couple of things:

as Panther can read a line of a file, the codes file type, panther version, project version and suchlike don't need a name before them, as long as the line on which they are placed stays the same in all ref files:

:info
ref
Panther 1.0
1.0

:files
5

:files to parse:
<header.txt=img> (these still need to be in full)

this way it may be harder to read the file and understand, but we save A LOT of space and reading time. As soon as it knows that it is a ref file, the Panther project can tell which lines of the file refer to what.

thoughts?