PlayfulGuy wrote:@Philo,
I've been playing with Guideme for months now and have been saving up a list of feature requests and issues. I post it here so others can comment too. Some might already be on your list. Here they are in no particular order.
Very comprehensive
I will try to convert these to issues on github (
https://github.com/guide-me/GuideMe/issues)
I think some may be there already.
Some of the quirks are from making it backward compatible with teaseme.
Some are where people have asked for things in javascript that were not originally considered in the design.
Javascript was originally just meant to give sophisticated game logic and variables, it has evolved to give far more control than originally intended. The more sophisticated stuff works by giving access to the underlying code so where there are multiple objects that allow functions it is because that is how the underlying code works. To change it would also mean changing a lot of the underlying code.
comonFuctions is a good example, I could correct the spelling but it would mean all current teases would stop working and I would need to change it everywhere it was used in the code (besides the second m is redundant and shouldn't be there anyway, your dictionary is probably faulty

)
In settings can you add a "pet name" option. I see sub name as something like "Slave" or "Slut", but would like to have a friendly name like "Sweetie".
Ask d3vi0n to add it to the main download, settings are configured in an xml file not the program, so can be different on different computers. The "default" set are part of the official download
Flags set using set=flag on the page element are not set when the pageload javascript runs. It IS set by the time you leave the page, but not while the page is displayed.
Technically this is correct behaviour, flags are set when the page is viewed so should not be set when pageload runs as the page has not yet been displayed. But I will have a think about whether it would be better to set them before pageload.
Still on the subject of buttons, I would very much prefer to have buttons appear on the page in the order they are listed in the XML instead of in reverse order. It's a pain having to compensate for the fact that they're listed backwards. It's not often there are many buttons on a page, but even with just three or four it's a noticeable strangeness.
I think this is to make it backward compatible with teaseme teases.
If it is I will add a tease setting to allow teases to reverse the sort order
Why are the left html and right html handled differently?
Because originally the left pane was just images and video, html in the left pane was added later and is handled differently by the underlying code.
On the various ones to extend the "teaseme" ifset type stuff, originally I was not intending to change any of that it was just there to be backward compatible with teaseme. Javascript could do any of that stuff.
However I have had various comments from people who find javascript a step too far for what they want, so I have revisited that and tend to agree, so I will be looking at where I can make it easier for people who don't want to use javascript