config parameter

[bcube2]

Not really an issue, rather a question: could the config parameter be added?

[mfo13]

Yes. I think so. If it is just an space to place the name of the config file it is quite easy. On the other hand, perhaps, you are talking about the config tool generating a config file together an html code to call it? It is also possible but will take some time to implement. In this last case the user would have, lets say, a check box to generate the html code or the config file? By the way, just a curiosity, which one has precedence, the config file or the html specifications? Suppose you have bgcolor in both with different values, for example.

[bcube2]

Well, I know nothing about which approach will be easier to implement, but I was think like creating a text area similar to the initmove parameter and labelling it AnimCube.txt (or whatever .txt you like). If that textarea is not empty, the HTML code below the simulator would show "AnimCubeX("id=cube&config=AnimCube.txt&other_parameters") with loading the settings from that AnimCube.txt textarea (or a file which would be created?).

ACJS doc for the config parameter is saying "All values specified in the configuration file can be overwritten by simulator parameters declared in the HTML document (web page). That is, simulator parameters declared in the web page are prioritized over the parameters specified in the configuration file."

[mfo13]

OK. Understood! I'll try to implement your idea after fixing the other bugs. I think it is a very nice idea! The user would type the config parameters in a blank area and the config tool would produce both, the html code as well as the config.txt file text. So the user would just copy and paste both in his/her html file as well as the txt file. Great!

[mfo13]

I think we can start thinking in more detail about this tool. First of all, do you know what commands we can put in the config file? All of them? Even move, for example? Do I need to inspect the code first?

[mfo13]

Take a look at https://mfo13.github.io/index2.html
It is a first trial. What do you think?

[bcube2]

First of all, do you know what commands we can put in the config file? All of them? Even move, for example? Do I need to inspect the code first?

Assuming that by commands you mean parameter settings, yes, the config file should support all of them. Nothing wrong with declaring move=R in the config file.

Take a look at https://mfo13.github.io/index2.html
It is a first trial. What do you think?

Looks like the index.html file only with the Config file box added to me :-)

I would display that Config file box only if the config textarea is not empty. I would insert the config textarea (I would use the same design as for the initmove/initrevmove parameter) into the Cube Settings section just below the frame height option. I would rename "Config file" in the box below the simulator to "AnimCube.txt". The seetings in the AnimCube.txt box should be displayed in this format. If a user clicks on the config parameter option in the Cube Settings section, "AnimCube.txt" label should appear somewhere. One way to do it is typing "AnimCube.txt configuration file, set parameters here." in gray color into that textarea, and when user cliks/taps to that textarea, this message will disappear.

[mfo13]

Yes! We are thinking pretty close the same. I've Just sent you to show it is possible and not so difficult to implement.

[mfo13]

Finished my idea. Take a look: https://mfo13.github.io/index2.html

[bcube2]

Thank you for trying, it's great to see the progress.

I have several suggestions for improving both functionality and design. Let's discuss one thing at a time, ok?

So should I start with functionality or desing suggestion?

[bcube2]

I'll go with this one: in the Cube Settings section, I suggest to hide the config text area by default, just like it is done in case of initmove.

And I'll add another one: I suggest to make that text area as big as in case of initmove, not just a single line.

[bcube2]

Actually, let me first check we are still on the same page and I am not asking for a functionality that can not be made.

Basically, I am asking for the config textarea to act like a .txt configuration file. That´s it, nothing else ;-)

If that´s possible, the AnimCube.txt tab below the simulator is not needed at all (and I will get to it later). I am also thinking about allowing users to upload the .txt configuration file (as an alternative to creating one via the config textarea), but I will get to it later as well.

[mfo13]

Well..., ok, we can make a text area that behaves like a config file, but you did not get my idea... let me explain.
Why should the user produce by himself all the complex commands of the configuration file if he has a configuration tool?? The configuration tool can do that for him! It is what the config tool is doing right now. You have two possible outputs, one is the html code and the other one is the content of the AnimCube.txt file. That's why you have two output tabs now (notice the AnimCube.txt tab is not an input). The line in the cube setting, which is an input, is placed there for the user's config file name if he has one. As stated in the docs, the cofig parameter accepts only a file name, nothing else. OK, I understand your point, a space for the user pasting the parameters of his config file as an input to see what happens, ok, it needs to be implemented, perhaps with an upload as you said instead of a blank area, I think it is better and less confusing. Did you get my point now?

[bcube2]

Oh, wow, thank you for your explanation. Now I get it.

It served as an IQ test and I failed, but with "hints" (placeholder in textarea) or additional/explanatory text it would be more clear what is expected from the user. It is working great.

Yeah, so your idea was to let the config tool create the .txt file for the user, while my idea was to input/paste declared parameters into the textarea and let the config tool process them.

Let me think a bit about which approach is better.

[mfo13]

Why not both?

[bcube2]

I don´t see a way for your approach how to set the same parameter in both the configuration file and the HTML page (config tool in this case). Is it impossible or do I miss something?

example: in the configuration file there is buttonheight=15, in your config tool there is buttonheight=20