Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
Before you actually shout at me for cheating etc. please worry not, I also despise taking advantage of the game by automating it with an application, however with my growing experience (sadly in unrelated web development) I tried to come up with an idea on how to actually simulate player's control and play a game completely from the outside?
Take any possible game, lets start with Mario.
You can move left and right as well as jump or get into the wells. What library would help us achieve it from the program-side? How will it know when to go right, when to jump, how to avoid the bullets or time out the plants? I am not even getting into trying AI to solve it, I am just concerned with the actual control and analysis of the screen (game output and state).
Long story short:
how to control and analyze what happens on the screen, possibly along with some conditional statements?
Thank y'all!
Okay, I trust you, hope everyone same too.
When I asked your answer, I just ask about game development aspect, I don't ask about security aspect (because I was game developer, not security engineer)
With automation control for testing: You can try with open source Airtest Project from NetEase, or GAutomation from Tencent. Or you can try implement code yourself by unit test hook click, press or touch event.
Or you can use selenium tool for game on web browser.
There are more tools but most of them are cheat tools so I not mention here.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What are some ways including machine learning that I can use in my projects to generate things related to another. Like related apps, related websites, related products, etc.
I've been brainstorming these are strategies...
one way i can think of is show items from same category. But that would be too broad.
2nd way improves upon previous step, it's to keep track of what people click next and promote that item. Meanwhile keep bottom list randomized to let other relevant items show up and get clicked.
3rd way is to use machine learning and provide training data somehow and use that.
I want something simple but smart, as it gets better with time.
Collaborative filtering is designed for solving exactly this problem. The problem with this approach is that produces good results having a lot of data only. I mean... A LOT. And it's not a really simple thing to use. However, any machine learning technique is not simple. There are some node.js packages for CF available, but I have no idea how good are they.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
The Application I am using does not jump infront of everything if I click on it, that means I have to minimize every single window for a clear view. How can I change this?
also the application is just working in "pseudo fullscreen" how do I make it go "real" fullscreen? (I assume this could solve the first problem)
please note I am not the programmer but I am trying to solve this for the original programmer so if you could just give me some code that would be really appreciated.
And Squeak can do multiple host windows since 2006 but nobody has actually done anything with the capability since then.
(Sigh. Supposed to be a reply to Travis' comment)
Have a look at this squeak image.
I am not the original programmer but if you click on the logo then it becomes fullscreen and overlaps the other windows.
The source code can be found in the logo. Please post it if you find it!
Also note that Smalltalk has windows inside the window. I just mean the window of the smalltalk environment.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
It seems that Indexhibit (www.indexhibit.org) is a sort of standard when it comes to building portfolio websites for artists. I just received a mail from an artist asking me whether I use Indexhibit. Beside the issues of the customer poking their nose into technical stuff, I need to know what's so special about Indexhibit?
I took a look at it and saw nothing more then a somewhat original CMS. I have my own system/libraries that I use to build simple websites and prefer sticking to these, but would like to know first... why does Indexhibit have this place among artists... and why do they say "an Indexhibit site" and not "a website built on Indexhibit"... what's the difference between an Indexhibit website and a plain website? Is there any advantage when using Indexhibit?
That's it, you got it, it's just a blank slate that makes it easy to pump out a small portfolio in a short amount of time. It's the helvetica of portfolio web design. Nothing fancy, but it's classic, the art can breath.
I come from a ASP.NET MVC and Django Background, and I've actually been having a bit of fun about working with Indexhibit. I got over my fear of PHP and there is some thing refreshing about just firing a query off, and building html straight out of it. Would never use it for a really custom job, but for things that fit the model, it gets quite out of your way for getting things done.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm sorry if this is a duplicate, but the question search terms are pretty generic.
I work at a small(ish) development firm. I say small, but the company is actually a fair size; however, I'm only the second full-time developer, as most past work has been organized around contractors.
I'm in a position to define internal project process and policy- obvious stuff like SCM and unit-testing. Methodology is outside the scope of the document I'm putting together, but I'd really like to push us in a leaner (and maybe even Agile?) direction.
I feel like I have plenty of good practice recommendations, but not enough solid motivation to make my document the spirit guide I'd like it to be. I've separated the document into "principles" and "recommendations". Recommendations have been easy to come up with. Use SCM, strive for 1-step, regularly scheduled builds, unit test first, document as you go... Listing the principles that are supposed to be informing these recommendations, though, has been rough.
I've come up with "tools work for us; we should never work for tools" and a hazy clause aimed at our QA (which has been overly manual) that I'd like to read "tedium is the root of all evil".
I don't want to miss an opportunity with this document to give us a good in-house start and maybe even push us toward Agile. What principles am I missing?
EDIT 4/15 -
I might have been ambiguous about the scope of this document. For now, it's policy that my co-dev and I plan to follow. So far, we've been given free reign on choice of local tool, source control, etc, and the general process we follow in development (eg build, deploy, whether to use continuous integration...).
Ideally, I'd also like this document to be a model on which to base further process improvements. I'm mostly thinking QA, and maybe nudging our project management towards something lighter and iterative.
The Agile Manifesto and its principles might help with a few more ideas
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Can anyone suggest a set of "commandments" to make everyone operate efficiently during a development project? I am looking for commandments on how Dev and QA and Management should interact. If you lookup Agile or Scrum development models they can explain peoples roles and how things work but it doesn't define a set of bylaws that protect peoples roles from each other.
Micromanagement shouldn't need to occur when rules work properly. QA should have all information they need to test and managment should define what a successful test is. Etc.
If such a set of rules existed and was known to work well, a large industry of consultants would disappear overnight. By the contrapositive, there are no "rules" that meet your qualifications.
All the roles are part of the same team, so everyone share the same goal. People collaborate, meet daily, communicating directly, preferably face-to-face.
Everything is based on trust, there is no need for "protection".
The relationships should all be spelled out pretty well in Agile. Of course, with Agile the point isn't to protect you from each other, it's to eliminate differences between you.
For instance, you are supposed to get rid of the concept of code ownership, if you find broken code you fix it. If you need help, pair with the original author.
QA needs representation in the core team. They don't get left behind because they are in every scrum meeting--as, of course, is the customer.
Management's role (if there is management) in agile is to stay out of the way and provide treats :)
These kind of things weren't just made up for fun, they really are important.
How about the agile manifesto?
http://agilemanifesto.org/
And the 12 priciples, which I'm sure you'll link through to:
http://agilemanifesto.org/principles.html
Edit
Sorry, I misunderstood the question. These are still some good principles!
Just keep communicating and addressing trouble when it comes up.
It's like in marriage: you can't prepare for every contingency beforehand -- you must be willing to deal with every setback that occurs by talking it through with your partners and finding a way to cope with it.