whats this? javscript/ga

Started by
27 comments, last by jpetrie 9 years, 10 months ago

so, anyone?

Sure.

[spoiler]I often feel like "let me Google that for you" links are a little rude, but I think refusing to do any of your own basic research is worse, so I've made an exception this time. Note that if you had done your own basic research but were just having trouble with these concepts I would have been happy to downs quite a bit of time explaining them to you, but you haven't, so I won't. I can't speak for others, but I expect this may be a contributing factor in why you aren't getting more responses.

You might think what you're doing is ok, but it's generally excepted common courtesy when asking for help online that you should do your own basic research first; that is to say, most people feel differently to you, and if you want the best chance of getting help you need to demonstrate the common etiquette that everyone else expects of you.[/spoiler]

(Posted from mobile, please excuse any small formatting or spelling errors.)

- Jason Astle-Adams

Advertisement

so, anyone?

Sure.

[spoiler]I often feel like "let me Google that for you" links are a little rude, but I think refusing to do any of your own basic research is worse, so I've made an exception this time. Note that if you had done your own basic research but were just having trouble with these concepts I would have been happy to downs quite a bit of time explaining them to you, but you haven't, so I won't. I can't speak for others, but I expect this may be a contributing factor in why you aren't getting more responses.

You might think what you're doing is ok, but it's generally excepted common courtesy when asking for help online that you should do your own basic research first; that is to say, most people feel differently to you, and if you want the best chance of getting help you need to demonstrate the common etiquette that everyone else expects of you.[/spoiler]

(Posted from mobile, please excuse any small formatting or spelling errors.)

I was explaining to that this attitude do a reseach first, its just logically wrong - I very often use the metodology of doin research later (or mixed one when doing research and asking in parallel, and i find it quite reasonable)

it is.. depends on situation (often long research can bring you more but sometimes the situation is this kind that you wold like jus a small talk against the heavy research with docs For example in some last thread about android Im very happy with a result of talks - im sorry there is no more such small talks here it could be quite educative IMO

at least in begginers forum it should be okay imo

much worse i find an answers like "google it" - when someone comes with specific question (that can be found but not al begginers are able to find it quick, sometimes it can take so much effort that he drops it down, ) "google it" is of no help and imo trashes the forum - imo stright answer would be much better and welcome

i find it quite reasonable

Almost noone else does though, and there's really nothing objectively more logical about it than the alternative.

Search for how to ask questions online and almost every guide will suggest you do your basic research first.

It's common courtesy, almost everyone else expects it of you, and you simply aren't always going to be able to find the discussion you want to have first if you don't because people will think you are being rude and simply close your topics without responding.


I won't say any more on the topic, but I won't be volunteering any of my valuable free time to help you unless you change your approach and do your own basic research, and I can guarantee you that along with all the earlier members who have told you very similar things there are other members who haven't responded here who feel the same. It's your choice.

Good luck.

- Jason Astle-Adams

i find it quite reasonable

Almost noone else does though, and there's really nothing objectively more logical about it than the alternative.

Search for how to ask questions online and almost every guide will suggest you do your basic research first.

It's common courtesy, almost everyone else expects it of you, and you simply aren't always going to be able to find the discussion you want to have first if you don't because people will think you are being rude and simply close your topics without responding.


I won't say any more on the topic, but I won't be volunteering any of my valuable free time to help you unless you change your approach and do your own basic research, and I can guarantee you that along with all the earlier members who have told you very similar things the are other members who haven't responded here feel the same. It's your choice.

Good luck.

I know its common but I think its wrong.. The opposite, I mean the thing that some fellow just answer you is also present (and i find it okay) As to you feel free not to answer me, nota problem here smile.png

(you already not answering this as you say so it is not realy any change)

Fir, if you only want to talk you should post to the lounge.

I don't know if it is the language barrier playng into this, but your attitude just comes over as rude and condescending. You can't expect other users of this forum spoon feeding you the solutions to problems you encounter while you are programming, when you could have found the answers yourself with half an hour of research.

Instead you are expecting dozens of people to invest their own free time to do the work for you while you sit around and wait for the responses to fly in.

Take your original post for example: If I hadn't known what this code does I would have immediately seen the string "GoogleAnalyticsObject". Put the exact string into google search and the second result is a detailed explanation of what this code does.

Fir, if you only want to talk you should post to the lounge.

I don't know if it is the language barrier playng into this, but your attitude just comes over as rude and condescending. You can't expect other users of this forum spoon feeding you the solutions to problems you encounter while you are programming, when you could have found the answers yourself with half an hour of research.

Instead you are expecting dozens of people to invest their own free time to do the work for you while you sit around and wait for the responses to fly in.

Take your original post for example: If I hadn't known what this code does I would have immediately seen the string "GoogleAnalyticsObject". Put the exact string into google search and the second result is a detailed explanation of what this code does.

disagree, already said why (instead of bore my of this weak pseudo-moralization better answer the technical questions)

let me skip this boring google terrorism

got yet one question

accoriding to this code im trying to understand

and this tutorial here

http://www.playfuljs.com/a-first-person-engine-in-265-lines/

this function probably counts the length of the eye-to-wall

ray casted into wall in some raycaster in js language

function ray(origin) {
var stepX = step(sin, cos, origin.x, origin.y);
var stepY = step(cos, sin, origin.y, origin.x, true);
var nextStep = stepX.length2 < stepY.length2
? inspect(stepX, 1, 0, origin.distance, stepX.y)
: inspect(stepY, 0, 1, origin.distance, stepY.x);
if (nextStep.distance > range) return [origin];
return [origin].concat(ray(nextStep));
}
I got a trouble understanding this
It would be helpfull to hear some explanation , anyone?

this function probably counts the length of the eye-to-wall
ray casted into wall in some raycaster in js language

It does not "count the length of the ... ray". Counting the length of a ray doesn't even make sense to me, so I'm not actually sure what you're asking here.

You're not sure what the function does. Which part of the description (from your link) is unclear? An answer to this might be able to give a answer that will make your problem go away.

Next, we need to check for walls in each ray's path. Our goal is to end up with an array that lists each wall the ray passes through as it moves away from the player.

Starting from the player, we find the nearest horizontal (stepX) and vertical (stepY) gridlines. We move to whichever is closer and check for a wall (inspect). Then we repeat until we've traced the entire length of each ray.
If understanding the goal of the function is not the problem, what is?
If it's none of those things, what is it? Is it something specific about the code you don't understand? If it is, you should post that specific thing, and give as much information about why you don't understand it, and what you think it might be.
Directing you to google is not being rude. It's saving everyone involved time (including you), and you will need to be able to research simple (or even advanced!) things mostly on your own if you want to get anything done. Of course, asking questions if you're stuck is always fine, as long as you've tried on your own first.
You might disagree with this, but this is how this forum (and every other technical forum I've seen) works. If you don't like it and think it's stupid, maybe what you're looking for isn't actually found on this forum? Maybe you're actually looking for someone to mentor you or act as a teacher?

Hello to all my stalkers.

this function probably counts the length of the eye-to-wall
ray casted into wall in some raycaster in js language

It does not "count the length of the ... ray". Counting the length of a ray doesn't even make sense to me, so I'm not actually sure what you're asking here.

You're not sure what the function does. Which part of the description (from your link) is unclear? An answer to this might be able to give a answer that will make your problem go away.

Next, we need to check for walls in each ray's path. Our goal is to end up with an array that lists each wall the ray passes through as it moves away from the player.

Starting from the player, we find the nearest horizontal (stepX) and vertical (stepY) gridlines. We move to whichever is closer and check for a wall (inspect). Then we repeat until we've traced the entire length of each ray.
If understanding the goal of the function is not the problem, what is?

for example I do not understand speciffically

return [origin].concat(ray(nextStep));

but other things in this function are terribly unclear to

for example what this function returns?

I also do not understand "earest horizontal (stepX) and vertical (stepY) gridlines. "

If you have origin of the ray in one tile you move in advance say 1 unit forward to some next tile - what they mean by nearest horizontal or nearest vertical - I dont get it


disagree, already said why

Unfortunately, whether or not your disagree turns out not to have much bearing on reality. You aren't being particularly respectful of the community of people who are trying to help you; you should take the advice they've given you about doing basic research on your own to heart. You can use it to answer your most-recent questions, and if you have follow-up questions you can post them separately (make sure to clearly explain the research you've done on your own), since this topic has strayed far from it's original question.

I am closing this thread now, since it has run its effective course. Have a nice day and good luck with your research.

This topic is closed to new replies.

Advertisement