Converting XML to JSON (new tease)

[JBK]

Hi all,
I am writing an E-stim tease (nearly finished). As I'm not a big fan of the EOS editor, I wrote the whole thing in XML to work with GuideMe. Is there an option to convert the XML to a working webtease on this site (which I'm assuming needs to be in JSON)? I would like the tease to be accessible to everyone instead of only the ones using GuideMe.

[Trusfrated]

You might have better luck in the Teasing Software forum.

That said, Philo created an Offline Editor years ago. If your XML tease works in GuideMe and isn't too exotic, theoretically you could use that editor to generate Nyx code for a new Flash tease. (This is how I wrote my teases offline.) There isn't an offline editor for EOS yet, as far as I know.

[JBK]

I tried the editor. I can't seem to generate Nyx with it.. All the online XML=>JSON translators I found translate the XML to wrong tags which is probably a familiar problem on this forum.
Other tips are welcome. In the meantime I'll just keep working on the tease :)

[Thamrill]

I tried the editor. I can't seem to generate Nyx with it.. All the online XML=>JSON translators I found translate the XML to wrong tags which is probably a familiar problem on this forum.
Other tips are welcome. In the meantime I'll just keep working on the tease :)

NYX scripts are not JSONs and you can't load them in EOS, if that's what you're trying to do; NYX editor requires flash (I just checked) so you can't create a new flash tease to let EOS convert it to its own format, unless you still have a pc with flash on.

If you manage to have a machine with flash try uploading pictures and code here: https://milovana.com/nyx/ to see if Milovana still allows creating flash teases, and if the newly created tease is automatically opened in EOS once published.

Good luck

[JBK]

I tried the editor. I can't seem to generate Nyx with it.. All the online XML=>JSON translators I found translate the XML to wrong tags which is probably a familiar problem on this forum.
Other tips are welcome. In the meantime I'll just keep working on the tease :)

NYX scripts are not JSONs and you can't load them in EOS, if that's what you're trying to do; NYX editor requires flash (I just checked) so you can't create a new flash tease to let EOS convert it to its own format, unless you still have a pc with flash on.

If you manage to have a machine with flash try uploading pictures and code here: https://milovana.com/nyx/ to see if Milovana still allows creating flash teases, and if the newly created tease is automatically opened in EOS once published.

Good luck

The flash thing was a workaround I tried. What I really want to do is to convert GuideMe XML code to a JSON file that works in EOS so I can share the tease on Milovana. Is that possible?

[fapnip]

The flash thing was a workaround I tried. What I really want to do is to convert GuideMe XML code to a JSON file that works in EOS so I can share the tease on Milovana. Is that possible?

I was experimenting with writing a tool to convert NYX to editable EOS, but the differences in layout, and lack of free time, put it on hold. The main issue, IIRC, is having to emulate NXY buttons with a bunch of notifications, as EOS choice options wouldn't work in all cases -- but many stacked notification buttons take up way more real-estate, and have much less room to begin with, in EOS.

If there's enough interest, and ideas on how to work-around some limitations like the aforementioned, it's possible I could be convinced to take another stab at it.

[Thamrill]

The flash thing was a workaround I tried. What I really want to do is to convert GuideMe XML code to a JSON file that works in EOS so I can share the tease on Milovana. Is that possible?

I was experimenting with writing a tool to convert NYX to editable EOS, but the differences in layout, and lack of free time, put it on hold. The main issue, IIRC, is having to emulate NXY buttons with a bunch of notifications, as EOS choice options wouldn't work in all cases -- but many stacked notification buttons take up way more real-estate, and have much less room to begin with, in EOS.

If there's enough interest, and ideas on how to work-around some limitations like the aforementioned, it's possible I could be convinced to take another stab at it.

Can you please elaborate on the issue with buttons? I can try to provide some help

[fapnip]

Can you please elaborate on the issue with buttons? I can try to provide some help

Basically, in NYX, all buttons are on the right (as far as I can tell), and some teases have a good number of them. If you put the buttons below the text, like EOS choice options, it very well could scroll any prompting text from view, since the tease author didn't need to accommodate for buttons when developing the tease. If I put them on the right, I'd need to use EOS notifications buttons, and those very well could take up too much space if you go over just a few buttons. (In addition, EOS notification buttons overlap the image, so that may not be desirable in some cases.)

I didn't look far enough into NYX teases to see if its buttons could be used asynchronously (text/images could change while waiting for a click), but if they can, that would require use of EOS notification buttons to emulate, since EOS choice options are blocking. (Only timer expiration, audio end event resulting in goto, option select, notification button click, etc., can be used to un-block EOS choice options.)

[Thamrill]

I didn't look far enough into NYX teases to see if its buttons could be used asynchronously (text/images could change while waiting for a click), but if they can, that would require use of EOS notification buttons to emulate, since EOS choice options are blocking. (Only timer expiration, audio end event resulting in goto, option select, notification button click, etc., can be used to un-block EOS choice options.)

From what I can remember, in nyx button are blocking, in a sense. The content of the pages is picture, buttons and timers, and ll got instantiated when getting on the page. EOS introduced the concept of actions, beforehand pages were static

Setting the say action before the buttons to pause, the user would have to press to make buttons appear, having time to read the text before showing the buttons.

[fapnip]

Setting the say action before the buttons to pause, the user would have to press to make buttons appear, having time to read the text before showing the buttons.

Or I suppose even a skippable auto-play for the say action would do the trick for most teases. I'll have to take another shot next time I have some free time.

How to get the GuideMe XML/images into Milovana as a valid NYX tease would be another hurdle -- but once it's there, I could take the JSON Milovana outputs for NYX teases and convert that to EOS compliant JSON that could be imported into a new tease.

[JBK]

Holy crap that sounds complicated...

[Thamrill]

Holy crap that sounds complicated...

I don't think it would be too complex, provided that some requirements are imposed on the input guides. Would have to take a look into a couple sintaxes (I don't know what is the plural of syntax in English ) . If I were in a better state of mind I would try to create such converter, but currently I don't feel that motivated, sorry

[PlayfulGuy]

Hi all,
I am writing an E-stim tease (nearly finished). As I'm not a big fan of the EOS editor, I wrote the whole thing in XML to work with GuideMe. Is there an option to convert the XML to a working webtease on this site (which I'm assuming needs to be in JSON)? I would like the tease to be accessible to everyone instead of only the ones using GuideMe.

For several months I've been working on an EOS downloader for Guideme and It's very close to release. Having been working on that project for this long I can say pretty cerrtainly that what you are looking for is possible, but by no means trivial, and will probably never be perfect.

I've actually considered the idea of adapting my code to do exactly what you are looking for, but the reality is it's not particularly likely at this stage.

I was experimenting with writing a tool to convert NYX to editable EOS, but the differences in layout, and lack of free time, put it on hold. The main issue, IIRC, is having to emulate NXY buttons with a bunch of notifications, as EOS choice options wouldn't work in all cases -- but many stacked notification buttons take up way more real-estate, and have much less room to begin with, in EOS.

If there's enough interest, and ideas on how to work-around some limitations like the aforementioned, it's possible I could be convinced to take another stab at it.

The downloader I'm working on actually downloads Classic, Flash and EOS teases. All of the old flash teases can be downloaded as a JSON script very similar to EOS. Based on my experience converting all these to GuideMe, converting Flash to EOS is probably easier than going from Guideme to EOS. The code I have could probably be adapted to that task, but it will be some time before I can even think about it. After I "finish" this downloader (like these things are ever really finished :) I was hoping to dig into the Guideme code and try helping out with development on it, but...

Can you please elaborate on the issue with buttons? I can try to provide some help

Basically, in NYX, all buttons are on the right (as far as I can tell), and some teases have a good number of them. If you put the buttons below the text, like EOS choice options, it very well could scroll any prompting text from view, since the tease author didn't need to accommodate for buttons when developing the tease. If I put them on the right, I'd need to use EOS notifications buttons, and those very well could take up too much space if you go over just a few buttons. (In addition, EOS notification buttons overlap the image, so that may not be desirable in some cases.)

I didn't look far enough into NYX teases to see if its buttons could be used asynchronously (text/images could change while waiting for a click), but if they can, that would require use of EOS notification buttons to emulate, since EOS choice options are blocking. (Only timer expiration, audio end event resulting in goto, option select, notification button click, etc., can be used to un-block EOS choice options.)

EOS notifications are really not the same as Nyx buttons, and I don't think you could really substitute them. And really, the majority of flash teases only have a small number of buttons per page and converting them to choices is the most direct equivalent, and fairly straightforward.

Flash/Nyx is a little simpler than EOS. Only a button or timer expiration would "un-block" a page. I don't think it was even possible for an audio event to trigger a page change.

Or I suppose even a skippable auto-play for the say action would do the trick for most teases. I'll have to take another shot next time I have some free time.

How to get the GuideMe XML/images into Milovana as a valid NYX tease would be another hurdle -- but once it's there, I could take the JSON Milovana outputs for NYX teases and convert that to EOS compliant JSON that could be imported into a new tease.

Yeah, from what I've seen the images are a bigger hurdle. From my limited experience with EOS the image names are basically all sequential numbers. Like you upload the image, EOS assigns it a number, and then you link the image to a page in your tease (or vice versa).

Is it even possible to upload an image with a name that you choose, and use that name in your EOS tease? All the EOS code I've seen just uses numbers for the image names.

I think a skippable auto-say is a reasonable option for those cases where there are a lot of buttons and a lot of text on the same page.

[PlayfulGuy]

Hi all,
I am writing an E-stim tease (nearly finished). As I'm not a big fan of the EOS editor, I wrote the whole thing in XML to work with GuideMe. Is there an option to convert the XML to a working webtease on this site (which I'm assuming needs to be in JSON)? I would like the tease to be accessible to everyone instead of only the ones using GuideMe.

How much javascript do you use in your tease? The biggest challenge I have had converting EOS to Guideme is converting javascript to work. The two platforms have different interfaces and libraries available and some need for translation is inevitable.

Though EOS is a better environment in some ways, so it may actually be easier to translate from Guideme to EOS.

PG

[PlayfulGuy]

** Deleted accidental double post - don't know how I even did that!!