|
Already on the TODO list 
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
When attempting to add a job there is no currency option for "Pounds Sterling" (aka GBP), nor is there an option for Euros. The four options available are a bit of an odd bunch (US, Canadaian, Australian and New Zealand Dollars).
The pins don't look like they are pinned in the correct place. For example, jobs in Toronto look like they are pinned somewhere in southern New York State until you zoom in quite close. I'm guessing that the "centre point" of the pin graphic does not correspond to the tip of the pin to which is the eye is drawn.
|
|
|
|
|
Colin Angus Mackay wrote: When attempting to add a job there is no currency option for "Pounds Sterling" (aka GBP), nor is there an option for Euros. The four options available are a bit of an odd bunch (US, Canadaian, Australian and New Zealand Dollars).
My job listing is unlikely to contain any of these... maybe the currency should be an entry rather than a list?
|
|
|
|
|
Added the missing currencies - sorry about that!
With regards to pins there's not much we can do. We throw them at Google and say 'here's the Lat/Long' and Trust In Google (I know, I know...)
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris,
I've had a thought - forum suggestions.
I've noticed that a lot of posts in the programming forums are generally questions that get asked many times over, such as "How do I do cross form communication in C#?" and similar. I understand these questions as I too had them when I started playing around with C# and it isn't obvious if you don't know; similarly I understand the frustrations of those who try to help and why CP weariness sets in (usually denoted by the "Google is your friend response").
Could we have an intermediary step between a poster asking a question and it appearing on the boards? This brief intermission would be a "We found the following posts and articles which may answer your question. Have a look-see, if none of them seem appropriate, click here to proceed with your post" type affair.
I don't think this would stop all repeat questions, but might help those who don't have English as a first language, those who don't know how the site works, those who are posting out of frustration and those who are pulling their hair out answering the same questions time-upon-time-upon-time.
Cheers,
Me.
|
|
|
|
|
That's a great idea. Probably would need tweaking to get it right, with lots of heuristic code to guess at what the poster is asking.
|
|
|
|
|
Would absolutely love to but we don't - yet - have the database power.
It's possible though.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
I have a hamster you can borrow.
|
|
|
|
|
Ew... a used hamster, no thanks. 
|
|
|
|
|
Getting this (twice) when attempting to post a message.
Error: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.. Ticket: 27952
Edit:
Using IE 7; posting responses (not new messages) in Soapbox; happened during the twenty minutes prior to this post.
Jon
Smith & Wesson: The original point and click interface
|
|
|
|
|
Yep - Just been uploading new code so you would have been viewing and old and a new page between page loads. Should be good now.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
I think you should make an article ineligible for voting until AFTER it has been made publicly available.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: I think you should make an article ineligible for voting until AFTER it has been made publicly available.
I agree. It doesn't make a lot of sense to allow voting on articles before they've been made public, if for no other reason than the majority of them will not see the light of day, so voting is a waste of time; it doesn't affect anything.
People voting should know this, but I think there is some visceral satisfaction for voting 1 on something that the author obviously didn't spend very much time on.
For those articles that eventually get approved, it would be cleaner if they make their debut with no votes. In other words, the voting should begin only when an article goes public. The slate should be clean at that point.
|
|
|
|
|
Article votes are handy pre-publish.
How about we just nuke the votes when an article is accepted?
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: How about we just nuke the votes when an article is accepted?
I think is a good idea.
Regards.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Well, the problem is that people are voting on articles instead of accepting/reporting them, thus moving them out of the queue.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: thus moving them out of the queue.
Huh?
There is at least one article I 1'd and reported that was later allowed through.
I don't want to have to go vote on it again and my opinion of it hasn't changed.
|
|
|
|
|
In the Location column include the "Telecommute" detail so that it is easy to scan down and see if the job is (1) close or (2) telecommutable.
|
|
|
|
|
Good one. Added as a request.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
How about adding whether or not the company would consider relocation/applications from abroad. I've just about had enough of the UK, and would consider upping sticks for the right company.
|
|
|
|
|
You really believe job seekers will listen to it though
I've lost track of how many hundreds of job applications I've had from overseas even though we specifically state we're looking for devs in Toronto
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: You really believe job seekers will listen to it though
It couldn't hurt.
|
|
|
|
|
Chris Maunder wrote: You really believe job seekers will listen to it though
Were they skilled? Last time I was looking I received a ton of applications from people that looked like they had only just heard of computers.
|
|
|
|
|
What about adding 'sort by salary' option?
Giorgi Dalakishvili
#region signature
my articles
#endregion
|
|
|
|
|
added
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
