My neither, looks cool do, i "think" i just send you something there. No idea what a pull request is do
If i manage to figure this out.. i could put a working ajax example there. Its easier to decide what to do when you can see it in the working. I would go for ajax instead of iframe since its much more flexible and kind of easier to code with.
You should see it as a iframe, but the iframe not being a iframe but a simple div or span with a class or id if that makes sense
And feel free to have a look round... Its a shame it doesn't look like we can work on the same file (unless it's because I had relatively large changes pending and had added stuff while accepting your push? (anyone good with github? ) ) All fixed now though, I think.
I have no idea if this is at all doable but would it be possible to add tags to tasks, punishments and rewards and allow people to somehow configure their virtual mistress using those ?
For example, a "cum and eat your load" reward or task could be tagged "forced orgasm" and "cum eating". A sub unchecking the "cum eating" tag in the config menu wouldnt get it at all.
Another idea regarding tasks, punishment and reward. Could it be done to add a way to inject custom package ? Like one could create a whole bunch of those, tag them as explained before and users could inject them after downloading it.
Those feature could make ghe program very popular in no time as you d get a dom of your choosing and a somehow never ending amount of task and stuff through easy community sharing.
Custom packages could be done using auto-includes. For example a punishments folder with a main script that auto loads the other scripts in that folder (easy to program).
However to not force people to write actual php code a xml interpreter might be a better idea.. (so having a main script that loads content from xml files).. This xml files could be easy make i assume, maybe with a simple c++ program or something like that (don't know how to program c++ do, put im sure someone here does).... Then it would be a mather of ... open editor, save and done :)
Tags cool be really useful as well (especially in combination with tasks).
To make the VM look more real desires could be added.
This would probably consist of a list of desires (that would trigger a task containing a specific tag, if exists)
These desires would increment over time and when reaching a certain level would trigger a task.
The amount of incrementation could be changed based on mood (wish in turn could change based on user actions like failing a task etc), user preference etc.
On a side note, if you dont want to get XAMPP a alternative is https://code.google.com/p/phpdesktop/. DB, java seems to work fine to me. (i recommend the chrome version)
For the tags, I plan to do this for the sessions (so that, for example, if the creator wanted to do a lit with anal, they'd check to see whether anal was a limit first and if it was, just do something like "This tease will probably be unsuitable for you." else just get on with it.
Sam could probably be done with tasks/punishments/rewards using a number based system (1 for like, 2 for dislike, 3 for limit), a task will be 1 or 2, a reward 1 etc.) and the contributor choosing the tag for their task/punishment/reward (probably only 1 due to complexity at the moment).
Very good idea, having the user download streams of punihsments etc.. I think we may be able to build it into an offline version to download the appropriate tasks/punishments/etc. from the main web database. Just use the highest ID and select all higher than that from the main DB or just select them from a tag.
I thought about using XML for the sessions... It could work for the tasks and stuff but I'm trying to make them simple-ish for now.
Desires could be added as part of the sessions (with tags, not sure how though :) ) so that if a desire is stronger a session with a similar tag would be shown.
Will try out the PHPDesktop.
Will have to add all of these into GitHub (might use issues with an 'idea' tag) or a wiki page.
In this kind of project, one would need to discuss the use of files vs. database.
From a programming point of view, database seems better, more performant and flexible. XML could be used as a way to import/export things, but the (web) app shouldn't actually rely on it.
Aside from what type of punishment/task it is (good suggestion about tagging), you should also add at least requirements (e.g. butt plug). Another variable should be severity. For some users, wearing a butt plug for 1 hour could be long, for others, it's a piece of cake.
So basically, before you even start a project like this, one would need to consider a lot of 'default' variables.
* personality: your name, name of the main Mistress character, date of birth (rather than age), ...
* interests, limits: most likely a sort of 'checklist' with a score, ranging from 0 to 10 for example
* a common list of toy groups ('anal'), subgroups ('butt plugs'), subitems ('butt plug', 'inflatable butt plug'). A user could add very specific groups and subgroups, but it's a good practice to at least have a proper overview to start with for everyone, to avoid e.g. creator X writing 'buttplug' and creator Y going for 'butt plug'.
Think big, even for example optional 'financial domination'. The user could enter a monthly budget, decide first how much of it he is willing to spend, and then he could get a task to buy a butt plug at some point to buy a new toy, or just go to the score to buy a cucumber, lube, condoms. All depending on likes.
But the more of these variables you have by default, the easier it is for others to create new content which takes the entire situation of the user into account, without having conflicts with other content.
---
About CyberMistress, 2005-2011
The CM software is my intellectual property and no one is allowed to distribute it. Use it at your own risk, no support whatsoever. I do not mind the sharing of content which was created for it by 3rd party. My content however is not to be shared.
I agree with you, the fact we haven't really got a large range of details is one of the reasons why it's not yet online. Thanks for your input though. I'll add the items when I get round to doing the user CP and will try to make the list comprehensive (categories could include... clamps, chastity, anal, vaginal/anal, spanking, clothes ( panties/boxers/briefs/bras/dresses etc. ) ). I think financial could be a good idea (although they, of course, would have to agree that we couldn't be held responsible, and that they can stop if they really want when they first state they want it.
I'm not sure how user added items would work because of the nature of the site and the number of possible spellings, names etc.
Feel free to suggest stuff in the issues section on GitHub (please tag appropriately so we can prioritise issues from sugesstions from questions) or on this thread. Also anyone who wants to help out can by cloning and then sending a pull request with the updated code
I'm missing some personal status and location awareness.
status: free (to serve), busy (really can't), could do small things which don't take a lot of time....
location
- permission to share or not (by default, location's not shared with anyone)
- xy: where is the user now (e.g. if he's using the applicatoin from a mobile phone)
- xyHome (imagine coming home, immediately getting a notification on your phone that your Mistress expects you to undress and insert a butt plug or something. The phone could detect this, but it first needs to learn your location)
- xyWork (another setting should indicate whether it's okay to be given certain assignments while at work)
- ...?
---
About CyberMistress, 2005-2011
The CM software is my intellectual property and no one is allowed to distribute it. Use it at your own risk, no support whatsoever. I do not mind the sharing of content which was created for it by 3rd party. My content however is not to be shared.
Ummm... really interesting idea. Will add it to the list of things to add after we've got a comprehensive site (and possibly implement real Ds). I suppose you could implement this in a mobile app which keeps track of the locations without it being in the database (I wouldn't want to store too much personal info because it's open source and therefore, in theory, easier to hack even with protections) and the app can 'ask' the website whether there are any tasks that should be done at home, work etc. when the user gets there and also check in every 10 minutes or so (when on mobile data) or every minute (when on wifi) (This will almost certainly generate lots of traffic though) unless the users asleep or in quiet hours or something.
Would probably also work well when desires are implemented, if a desire is really high then (s)he'll send a notification when at work or out and about and if it's relatively low she'll only send them when at home. I think this may be good, although it'd have to use the tags (not implemented yet) to make sure (s)he wasn't breaking a limit like public.
Interesting, although personally I can't write apps I'm sure someone on here probably can. If no-one has taken it on when we get closer I might have a go.
Also like the idea about a user being busy, perhaps set a time limit to sessions so they can't overrun (would probably use a cookie with the timeout and then rely on creators checking it, and if they fail (havent figured this bit out yet) then they'd only be penalised if the timer hadn't run out). Also handy for the real Ds stuff too.
It's no hard at all, for most devices you just need to confirm you want to share your location. But the webpage (or app, just generated from the web page) would have to be open nearly constantly to process things. Which it would most likely be anyhow if the user actually wants to be dominated;
---
About CyberMistress, 2005-2011
The CM software is my intellectual property and no one is allowed to distribute it. Use it at your own risk, no support whatsoever. I do not mind the sharing of content which was created for it by 3rd party. My content however is not to be shared.
Traffic should not be a issue since the checking is client side (GPS could suck your battery dry do, but that's a other mater :P).
The location data it self should not be stored on the server but remain on the client "only". The client will tag a location with home, work, etc.. and simply send that to the server. (hey server, im home, hey server im at work).
What location points to what place can be stored with localStorage and processed with javascript.
