Page 16 of 175

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 10:05 pm
by 1885
Quick call for help here for anyone who's in the know: I'm trying to get set up on github, and it is seriously making my head spin. I signed up and created a thing (repo?) for Tease AI, located here:

https://github.com/Milo1885/Tease-AI

At this point I don't have the slightest idea of what to do or how to do it. I think the help documentation assumes I know way more than I do and I'm kind of lost.

I'm testing this out to see if I'm doing this right by uploading the code behind the Games form I use (FrmCardList) Can I anyone tell me if I did that right?

Am I supposed to upload code like this by creating new files? Am I supposed to commit directly to the master branch when I do? Create a new branch for the commit and start a pull request?

Image

If anyone could give me any insight here, I would really appreciate it and I can get the rest of the code out there.

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 10:16 pm
by Mr-Elusive
So I use git quite a bit (and occasionally git hub). Basically the main thing to get your head around is that it's a distributed source control system. I.E. you always have a local copy and there is always a remote copy on the server.

Basically the method I've found to work best is you install git locally on your machine.

Then, go to the folder where your source is and type "git init". This will initialize this folder as a "repo".

To add all the code you currently have, you will type: git add --all (this includes sub folders).

Now to commit this code, you type: git commit -m "Initial commit" (or whatever message you like).

Your source is now added local.

To set it up with github, you need to do a few things.

1. You need to set your name and email address.
2. You need to add a remote server for your repo.

To add a remote, you will type: git remote add origin "https://github.com/blabla" (this is whatever your repo is).

Now to get the copy of code on your local repo merged with the remote repo, you type: git push origin master. This will push any code you have committed locally (remember our initial commit?) to the master branch on github.

Hope this helps. You can drop me a PM if this doesn't make sense.

Edit: Sorry if this post is poor quality, it's after 12am and Leah my Tease AI Mistress has officially worn me out.

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:16 pm
by 1885
Mr-Elusive wrote:So I use git quite a bit (and occasionally git hub). Basically the main thing to get your head around is that it's a distributed source control system. I.E. you always have a local copy and there is always a remote copy on the server.
Thank you for the information (and the desire to take up drinking)

I think I might have it set up now at https://github.com/Milo1885/Tease-AI-Milo

Can anyone confirm I've done this correctly or tell me anything else I need to do at the moment?

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:19 pm
by msissyleah
http://imgur.com/AaCK9vS

now 768 ... size
Under side
Do not show
more big size
more not show ....
:weep: :weep:

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:26 pm
by 1885
msissyleah wrote:now 768 ... size
Under side
Do not show
more big size
more not show ....
Did that start happening after the last patch? And what version of windows is that?

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:38 pm
by msissyleah
1885 wrote:
msissyleah wrote:now 768 ... size
Under side
Do not show
more big size
more not show ....
Did that start happening after the last patch? And what version of windows is that?
window 7
I am always the same problem
The last version is
I have personal problems?

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:41 pm
by Bluelow
Have been playing around this for a few days and loving it more every second. Here's a few bugs I've found (more script related than program related I guess)

- After the "censorship sucks" game i get black images instead of images of the domme
- While doing cbt it seems like anything you type (including please stop, mercy etc) gets interpreted like you've actually done what she asked
- In the tasks file it seems like the program gets a word for something (like emote) and uses it for the whole file. This results in words like "haha" "lol" "dick" etc used every time for the whole file instead of randomizing the word for each instance and it looks kinda stupid

Keep up the good work 1885, can't believe the amount of work you have put into this and still put into it every day

Re: Tease AI Open Beta

Posted: Tue May 19, 2015 11:49 pm
by Siepmann
Mr-Elusive wrote:Also I wanted to ask, where do we send the money to?
lol I wish
You should think about a Paypal Donation button or something like that in the settings / about tab.

I have so much fun with this the last couple of days and you are doing such a great job making it even better in a faster time then i could write bug reports.

Thank you very much and i would love to spend some money for it. I don't think i am alone on this front.

* One bug i found while playing with the Text to Speech Option, when there is italic text, the program does not filter out the [ i ] [ /i ] or *. That's a bit annoying ;)

* Is there a way to filter out 404 file not found in URL File lists ? I got a few URL Files and had to disable them because they would crash the Match Game if there is a 404. Would be nice if the program could filter them out before crashing the game. I don't even know from witch list they come from.

Sorry for my not so great English and keep up the great work !

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 12:17 am
by Azureballs
Siepmann wrote:
Mr-Elusive wrote:Also I wanted to ask, where do we send the money to?
lol I wish
You should think about a Paypal Donation button or something like that in the settings / about tab.

I have so much fun with this the last couple of days and you are doing such a great job making it even better in a faster time then i could write bug reports.

Thank you very much and i would love to spend some money for it. I don't think i am alone on this front.
Or a Patreon I would totally donate monthly for a project like this.

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 12:31 am
by 1885
msissyleah wrote:window 7
I am always the same problem
The last version is
I have personal problems?
Just so I'm absolutely clear, you are saying you've always had this problem right?
Bluelow wrote:- After the "censorship sucks" game i get black images instead of images of the domme
Looks like I forgot to switch it back to the image panel after the tease is over. I'll get it patched, but in the meantime you can switch between them manually by using the "Img <-> Vid" button in the lower right
Bluelow wrote:- While doing cbt it seems like anything you type (including please stop, mercy etc) gets interpreted like you've actually done what she asked
I'll look into this, I probably borked it when I was fixing the edge but. She should definitely have specific responses for CBT
Bluelow wrote:- In the tasks file it seems like the program gets a word for something (like emote) and uses it for the whole file. This results in words like "haha" "lol" "dick" etc used every time for the whole file instead of randomizing the word for each instance and it looks kinda stupid
Good catch, I'll check the code there
Bluelow wrote:Keep up the good work 1885, can't believe the amount of work you have put into this and still put into it every day
It gets rough sometimes, but then again I am a masochist :smile:
Siepmann wrote:You should think about a Paypal Donation button or something like that in the settings / about tab.
I have so much fun with this the last couple of days and you are doing such a great job making it even better in a faster time then i could write bug reports.
Thank you very much and i would love to spend some money for it. I don't think i am alone on this front.
I really appreciate that a lot, it's not like I couldn't use it for damn sure

Currently I know a lot of people are enjoying Tease AI. I believe it's a really good program and I'm working hard to get it to its full potential. But it's not there yet, and there are a lot of issues I still need to address. I just wouldn't feel right accepting money when the program's in the state its in.

Once the program is finished and I'm comfortable calling it 1.0, I might give people the option. If anything, rather than accepting donations for Tease AI I might try to take stock of public interest in me setting up a Patreon to just create extensive scripts and Personalities with the same drive I've been using to code the program, which I generally wouldn't have the time or ability to do otherwise. But right now I just want to get the program as stable as possible for as many people as possible, and I don't want to feel like I'm asking people to pay for the privilege of being my beta testers.
Siepmann wrote:* One bug i found while playing with the Text to Speech Option, when there is italic text, the program does not filter out the [ i ] [ /i ] or *. That's a bit annoying ;)
Good catch, I"ll make sure to filter for that and get it in a patch
Siepmann wrote:* Is there a way to filter out 404 file not found in URL File lists ? I got a few URL Files and had to disable them because they would crash the Match Game if there is a 404. Would be nice if the program could filter them out before crashing the game. I don't even know from witch list they come from.
Yeah, Triple Alfa mentioned to me that there needed to be a way to validate/update the URL Files you've created, I just haven't had a chance to address it yet. I'll get that in as soon as I can

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 12:52 am
by desertfox
To add to what Mr-Elusive said about git... recently switched out of svn to git and sometimes git can be a real pain to get used to how it works, but it is not bad.

Starting from the very beginning, a repo is just a picture of your files at moments in time. It would be like taking all of your zip files you have put up on mega and having them in one place that you can access at once.

Git has basically 3 states. The first is the remote server, this is git hub, usually it is referred to as the 'origin' . The second is your local repository, this is on your machine, and is a complete copy of the remote one. This is the distributed part of it, having your own copy.

The third part is your working directory, this is where you are writing your code right now on your machine when you are typing in a directory and where you continue to do all of your work.

A basic workflow is that you have your code on your local machine. You open up your editor/ide and do some code changes. You decide that your work continues its awesomeness and are ready to put it on github.

On the command line you can do 'git status' and this will show you all the files that have changed since you last checked it in. To get your files up to github now on the remote branch, it has to flow to your local repository, then your online repository.

So first you must stage your changes. This tells git which files you really want to check in. This is done with the 'git add' command.

You can do it by file
git add src/myproject/coolstuff/insane.cpp

or you can just add the files that are not new, but have updated (I use this one a lot)
git add -u

Finally you can add EVERY NEW FILE, with git add -A

I usually find myself doing git add -u then manually adding new source files as I sometimes have a lot of junk I don't want in revision control in my local directory.

Ok so now if you type git status, you will see all your files staged in green.

Now we have to put them in our local repo

git commit -m "Log message about my really cool features I added"

Now it is in version control locally. You can be done at this point and use the repo how you want. If you wanted to roll back to a previous version or do whatever you want, it can be done locally without bothering other users that pull from github. This is the strength of the distributed version control system.

But finally lets just get it up to github

git push origin master

Push is put it up there. origin is your server, in this case, github. master is the branch.

Think of a branch as a copy of your code folder but with some changes to it. If you were doing branching in windows explorer, you would copy your source code directory and paste it into a new folder, then make some changes in that new folder, then copy those changes back into your main folder when you were happy with them.

Master is the default branch name in git. A really nice work flow in git is to have a master branch for releases, and a development branch for breaking stuff.

So really just do 'git branch development'
And you have copied your stuff to another folder called development, but are still working in your current branch.

If you type 'git branch' you will see all your local branches.

If you want to change to one, just 'checkout' with 'git checkout development'. That'll swap you to the development branch. Git won't let you lose anything so if you change development, then try to checkout master, it will tell you you have local changes and must commit development first before changing branches.

Anyway so I would suggest you start out with the simple workflow of making your git repo, and get used to staging changes with add, commiting them to local repo, then pushing them up to the server.

After that start trying to do two main branches, master and develop.

git branch develop
git checkout develop
<do some uber coding and decide it rocks>
git add -A
git commit -m "TeaseAI no longer allows orgasims"
git push origin develop

Now merge your changes back to master because you know this is a good milestone and you want to distribute it

git checkout master
git merge develop <--- there is magic here but this will basically make it so there is no longer a difference between the master and develop branches. If you have multiple people checking into master, you will have conflicts to manage (eg you both changed the same file) but since you will be just doing it for now, you won't have to deal with those
git push origin master (not sure if you have to do this step ha, still newbish myself)

merging can get crazy, but that set up is a pretty good and safe one to use. That way master always contains a series of stable points in time, so if you go crazy in develop you can always fall back to the last version, or hotfix off the master branch a one liner.

Eventually the idea with git is to branch all over, so if you are working on a major feature you would create a new branch called something like 'feature_153', create it, merge it back into the main branch, then delete the feature_153 branch.

Alright so I hope i didn't over explain, but this at least can maybe help make more sense of the git help pages. It is a pretty rough thing to get your head around though. But always remember, once you have something in git it is hard to lose it, you can usually always fix anything you've done, and google/stack overflow help answers are your friend :)

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 1:41 am
by androgyme
Once the program is finished and I'm comfortable calling it 1.0, I might give people the option. If anything, rather than accepting donations for Tease AI I might try to take stock of public interest in me setting up a Patreon to just create extensive scripts and Personalities with the same drive I've been using to code the program, which I generally wouldn't have the time or ability to do otherwise. But right now I just want to get the program as stable as possible for as many people as possible, and I don't want to feel like I'm asking people to pay for the privilege of being my beta testers.
I think that would be a great idea. I know I'd certainly pay for specific content I'd like created. I'm particularly interested in a more humiliation based AI personality. I would create it myself, but one, I'm not really sure what I'm doing, and two, I think if I did it myself, it wouldn't be as exciting, nor feel as real, as Wicked Tease currently feels.

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 2:04 am
by DemonXia
1885 wrote:
DemonXia wrote:Furthermore, me being transgender doesn't really impact my use of the program at this moment, although a choice whether the sub should be called he or she would be nice.
Where would that be applicable? The domme speaks to you in the second person of "you", I don't know that "he" or "she" ever gets mentioned either way. Is there something you're thinking of where "he" or "she" would come into play?
As far as I recall it does pop-up in the Glitter feed and that might have been the only place though. Maybe I just need to manually change the lines for the glitter feed.

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 2:20 am
by androgyme
So I've been using some, ah, personal pictures of an ex for Wicked Tease, but I don't have a huge collection of images, and certainly no videos. So I was thinking it might be time to have a more "professional" model, shall we say. Preferably one that has some video content, like JOI and the like. Anyone have any suggestions?

Re: Tease AI Open Beta

Posted: Wed May 20, 2015 3:02 am
by Trusfrated
1885 wrote:
Mr-Elusive wrote:While I don't really get how glitter fits in, I really liked this feature.
Just to help with the immersion of it being an online experience. I imagine if a few people add a few good ones, especially Tease ones, it can a sexy little peripheral thing that enhances the whole experience. Plus I'm planning a feature of implementing specific Glitter posts you can call from scripts so the domme could post about specific things she just did to you and her girlfriends could react to it
This. I think it would be natural evolution of the concept.
  • She could poll her friends mid-tease asking them if she should let you cum. (Not that she needs to actually take their advice.)
  • And, how about bragging about the Wishlist item her sub bought for her today? Maybe include the picture?
  • Perhaps she would make a comment about the sub's relative cock size (small or big) based on your settings.
  • If the sub is in chastity, she could know to reference that in her posts to her girlfriends.
I'm sure there are many more ways the tease script could integrate with Glitter in a more "real" way.