Milovana.com

Quarz wrote: Thu Jun 13, 2019 10:59 pm I'm close to finishing my next tease and I thought about having a few people play it before publishing in order to catch bugs and grammar mistakes.

That brings up the question how to share an Eos tease with someone else before publishing it.
Does sending them the backup file work or would they not be able to load that?
Or is there maybe some even better way to do it?

seraph0x wrote: Fri Jun 14, 2019 6:08 am I added a feature to Eos to allow private sharing of teases. Just go to the new "Share" tab in the Eos editor.

Be warned though, once you share a link, you can't take it back!

Triple Alfa wrote: Sun Apr 07, 2019 10:40 am First, about the preview code and storage. The storage does not get wiped when entering preview mode. What I would do, is for testing create a button on your start page that will reset the values. You create a function like this in your init file:

Code: Select all

function resetValues() {
teaseStorage("newPlayer", 0);
teaseStorage("myOtherValues", "relevant Values);
}

You can then call this from the button by having it do an eval action with:

Code: Select all

resetValues();

Now you can easily reset anything to test the newPlayer/returningPlayer scenarios.

snakelinux wrote: Tue Apr 09, 2019 5:39 am 2) You should give users the ability to reset their stored variables. This is especially useful if there is a bug in your code. Setup a page that when a user clicks the button to reset it runs this function with the variable names changed to your stored variable names.
function refresh() {
teaseStorage.setItem("storedVariable1",undefined);
teaseStorage.setItem("storedVariable2",undefined);
}

var apple = teaseStorage.getItem("i") ||0 
apple++
teaseStorage.setItem("i", apple) 

apple

teaseStorage.setItem("i", 0)

Roblsforbobls wrote: Sat Jun 22, 2019 12:50 am Here's the bug:
I use the Say action and insert an eval tag in it:

Code: Select all

apples+1

When "apples" is equal to 1, this code yields 11 instead of 2. However when I do

Code: Select all

apples-1

it gives 0. Furthermore, you can get around the issue by doing

Code: Select all

apples-0+1

to get the expected value of 2. It follows the same behavior when trying to add two variables as well.

Quarz wrote: Sat Jun 22, 2019 8:06 am I tried this out and get 2 for apples+1 and 0 for apples-1.
Could it be that your apples isn't equal to 1, but equal to '1'? 'cause then I get the behaviour you described. (Which is intended, I think)

• Code Editor - In any page that shows the javascript code editor, the displayed cursor position doesn't match where the actual cursor is. I think there's something wrong with the web font used in the editor. I'm using Firefox 67.0.4. Right now I pretty much have to copy and paste the code into an external editor because the built in editor is unusable in this state.
• Upload to Gallery - Only jpeg allowed, but the file browser opens with *.* filename filter
• Notification - Notification.get behaves strangely. If the notification is not yet added, Notification.get doesn't return an object which is expected. When the notification is added and being displayed, Notification.get returns the notification as expected. However, after the notification has been clicked, and the notification is not longer shown, Notification.get still returns the notification object. That might make sense if there were a Notification.show or Notification.hide and a way to get the current visibility of the notification. As it is now, IMO, it should only return an object when the notification is actually on screen.

• Javscript errors - It's pretty difficult to find code errors without resorting to lots of console.log statements. Right now when a code error occurs the browser console just displays a cryptic error that doesn't pinpoint the cause. It would be good if that could be improved to maybe output the statement where the error occurred.
• Allow .js includes - I have lots of javascript objects and the init script is unwieldy. It would be great to allow uploading .js files to the project and then including them.
• Allow png and gif images.
• Say Action - Create from code (not just the text, but an entire bubble) (font size / color / background color)
• Page Labels - Basically an "Action" on a page that doesn't do anything other than being a placeholder with a unique name. Then you can use pages.goto('pagename:label') to jump to that label within a page.
• Notification - Create/Remove from within code
• Change the background color. Is there a way to currently do this? I didn't see one.
• Allow background image
• Allow changing text position
• Allow changing color of text within Choice buttons. I can add a <span> but style="color:#ff0000;" doesn't change the color.
• Image object - There's a Sound object to play sounds from code, let's have an Image object to change images from code.
• Image Action - Allow eval for image file name
• Image Action - Allow clearing displayed image. I want a help page that can be opened up any time, but want to clear the background to just show text. Now I could use a transparent png, but png images aren't allowed.
• Input Field - Allow different types of validated input (text (min/max length), number (integer/float), range, date, regex, etc. ). Right now you can check the input with code, but you have to jump back to ask for the field again if there was an issue which is kind of kludgey.
• Image Action - Gallery Image - Allow using wildcard for file name
• Input Field - When running a tease, auto set focus on the field so you can start typing immediately. Right now you have to click the mouse within the field to start typing
• Use Web Font that has more Unicode 6.0 symbols such as playing cards U+1F0A0–1F0FF
• Button/Notification Labels - Allow eval within labels
• TeaseStorage - Share saved data between scripts. There could be separate storage areas for the authors scripts, as well as everyone's scripts. Global variables like name, gender, age, etc. would be useful and the user can set them once. These global variables can be managed by EOS and read only for teases.
• Start another tease from within your tease. When the other tease ends, it comes back to your tease where you left off. That way we can have small shared sub-teases for various common tasks.
• Allow multiple images on the screen at the same time
• Image Gallery - Allow users to have their own personal galleries, and a tease can pull images from it (maybe based on tags or some sort of grouping capability)
• Web Speech API (Text to Speech). Most modern browsers have this capability now. See https://developer.mozilla.org/en-US/doc ... Speech_API
• Gallery - Allow adding jpegs from "Files" area (not just uploading new jpegs)
• Webm / Webp support
• Webcam support

Roblsforbobls wrote: Fri Jun 21, 2019 4:43 am

Triple Alfa wrote: Sun Apr 07, 2019 10:40 am First, about the preview code and storage. The storage does not get wiped when entering preview mode. What I would do, is for testing create a button on your start page that will reset the values. You create a function like this in your init file:

Code: Select all

function resetValues() {
teaseStorage("newPlayer", 0);
teaseStorage("myOtherValues", "relevant Values);
}

You can then call this from the button by having it do an eval action with:

Code: Select all

resetValues();

Now you can easily reset anything to test the newPlayer/returningPlayer scenarios.

snakelinux wrote: Tue Apr 09, 2019 5:39 am 2) You should give users the ability to reset their stored variables. This is especially useful if there is a bug in your code. Setup a page that when a user clicks the button to reset it runs this function with the variable names changed to your stored variable names.
function refresh() {
teaseStorage.setItem("storedVariable1",undefined);
teaseStorage.setItem("storedVariable2",undefined);
}

I'm a novice at best when it comes to Java, so I was having the hardest time getting these codes to work to reset my stored variables. Here's my storage code:

Code: Select all

var apple = teaseStorage.getItem("i") ||0 
apple++
teaseStorage.setItem("i", apple) 

I use Say: "apple =

Code: Select all

apple

" to assess that the variable storage is working (it does).

By fiddling around with the solutions from previous comments and struggling to get them to work, I happened upon a working piece of code to refresh and reset stored variables:

Code: Select all

teaseStorage.setItem("i", 0)

Note that I used "i" here because that's what I used in my stored variable code. Hopefully this helps someone!

Lamei wrote: Thu Jul 04, 2019 8:06 am I estimate that I will need approximately 150 variables for the new tease. If someone could advise that would be great as I can't continue making the current tease. Thanks

var money = 0
var time = 0
var x = 0

var money = 0; var time = 0; var x = 0

RemiHiyama wrote: Sun Jun 23, 2019 12:13 am Are eval tags supposed to work in the labels of choice actions? I'm getting some weird behavior, but my best guess is that it's evaluating once and then showing the same thing every time the page is shown after that. Which isn't great since the point of the eval is to have dynamic text on the buttons.