An "unwritten" rule of the Forum or of any other Forum is to avoid doing someone's homework. We are here to help people, not to do entirely their job.
Oh dear... I noticed one of your rule type things said to post the HTML code you're working with... I'm not really allowed to do that... I'm just a little intern while the company is using my labor for free... Is that alright still? I tried to ask a pretty specific question...
Originally Posted by Amoranth1
The solution is to duplicate the html with all the sensitive information taken out. We don't care about the specific content, as long as it won't change behavior.
thank you joe kreuz
See some tutorials of all these:
Thanks a lot scragar
But many time I saw if I want any help from existing topic I fail to get it. So I think if you use tagging system for the topics and a search option with that tag.
Then it will help us to find out the solution very fast from the existing topics.
Always include any error message in your post, even if you don't understand its meaning.
It is extremely annoying to be passed a piece of code or URL that generates un-acknowledged errors.
When developing a site, where possible always configure the console to pop-up on error.
If you're using Internet Explorer, click on the yellow triangle at the bottom-left corner of the window.
Last edited by Arty Effem; 11-06-2006 at 12:18 PM.
PM = 'PayPal Mode'
- Bookmark this xul:
- Right click on the bookmarked xul -> Properties -> check "Load this bookmark in the side bar"
A) Great as long as you are 100% sure you know the "right" way.
Originally Posted by thuko135
B) Tone is everything. Suggesting best practices or alternatives can be done without "criticizing". Criticizing someone's code is really a veiled criticism aimed at the author, i.e. "you're stupid", or "you're lazy", or "I don't like you", etc. Why waste your time criticizing; if you don't want to help, don't. Of course, if a poster is disruptive, then a moderator should deal with them.
I'm probably quibbling over the meaning of criticism, but it doesn't sound like a good thing. I'm hoping that every type of question can get some kind of reasonable answer. Nothing wrong with suggesting better code or proven code. But often people want to know why their approach won't work -- it's part of developing code savvy. If someone is willing to take the time to explain why, it is very valuable and instructive to the community.
Wise comment. I also agree that, beside the code itself, we should give the others the possibility to understand the code...
Originally Posted by simonbaker
I'm working on something with Google Maps, and I'm afraid I got in a bit over my head.
I'm trying to add re-sizing controls to the map, and I just can't figure it out. The object is to get the "Size" part of what this guy has done... without all the other stuff.
And nothing I'm trying is working.
Background info on the Google Maps API
Help me understand....
Do you also try to ake a pie with no idea about pastry?
Do you also denouce God without ever having read a bible/koran/torah?
Do you try to install a CD player in your car with no idea about automotive electrical principals?
So why do you try and get us to fix a problem with a menu that we did not write and would never use in a million years?
Why not find out the author (always listed) of the script and ask them?
Oh yeah, I just remembered why....because we can bake a pie while reading the torah and listening to our newly installed CD player in the car.
Design first! Code later!
Let's take it easy a bit. We're here to help and encourage, not tear down and destroy. First of all, the post is three months old. Second, it's off topic anyway and needs to open its own thread.
It's probably time to close the thread anyway.
""Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing ever happened."
" -- Sir Winston Churchill
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)