ElanMan

Welcome to WDF gemini!
I hope you've got more about you than that bloody awful pop duo of the same name who came last in the eurovision!

this line:

var widgetid = jQuery(".star-dropdown").parent().children(".star-widget-id").val();
 
should be:

var widgetid = jQuery(this).parent().children(".star-widget-id").val();
 
In your original code,in the event handler, you're finding all of the selects with a class of 'blah'. Simply put, it means you're working with the first select on the page(no matter what select has changed) You don't want all of the selects with a class of blah, just the one that has the change event fired.
jQuery(this) inside an event handler will refer to the element that was 'clicked', 'changed' etc. This means that when the function traverses the DOM to find the parent etc, it will start from the relevant select, not from the first one on the page.

this line:

var widgetid = jQuery(".star-dropdown").parent().children(".star-widget-id").val();
 
should be:

var widgetid = jQuery(this).parent().children(".star-widget-id").val();
 
In your original code,in the event handler, you're finding all of the selects with a class of 'blah'. Simply put, it means you're working with the first select on the page(no matter what select has changed) You don't want all of the selects with a class of blah, just the one that has the change event fired.
jQuery(this) inside an event handler will refer to the element that was 'clicked', 'changed' etc. This means that when the function traverses the DOM to find the parent etc, it will start from the relevant select, not from the first one on the page.

Have you looked at MediaWiki?
Or am I completely missing what you're after?

Hi Christian,
 
Kree8or has a valid point, technical books with code examples and such can become dated after a while and their content is widely available on the net for free. But saying that, here are some books I've found good and you might want to read if you're an aspiring web designer based on the principles they teach:
 
Designing For The Web
Bulletproof Web Design
Principles Of Beautiful Web Design
Don't Make Me Think
Handcrafted CSS
 
There's the Missing Manual series of books which are technical books but they're supposed to be great books, although I only own the Javascript one, I can vouch for that.
 
Also...
Making websites, just random ones based on your understanding of chaos theory even, is THE thing to do if you want to improve. You can read all the theory you want about being a webdevninja but without practising, failing, fixing, more failing and more fixing (trust me, this'll happen a lot) you wont learn shizz. It's those "eureka" moments that make stuff stick in your head.
 
One last thing...
No amount of reading will do this. Not without doing the latter comment too.
 
Hope this helps mate, best of luck!
~evu.

What about SyntaxHighlighter ?

Funny how we can all read this in a different context;
I assumed he had sent an iPhone in to outerspace for an indeterminate amount of time, eventually had the iPhone returned and found that due to Einstein's twin theory, the phone had gained 1 hour but then then we're all different I suppose...

The rep thingy is the most useless feature on this otherwise excellent forum imo.
However, in the interests of community harmony, luizarios, you have a +1

I was wondering the same, I thought it was something to do with the amount of posts but then I saw someone with a higher reputation than me and just 9 posts :0
 
I just figure out that if you click on the + bellow someone's answer it gives them an extra reputation point, just clicked on yours and now you +3 rather than +2. I've only been clicked once so I only have 1 someone please click mine

Don't do outline: none; or outline 0: as a reset - the outline is important for accessibility

Is this the sort of thing you're looking for?
Revisiting The HTML Image Map

Assuming your form is like this:

<form id="myform" action=""> <p> <input name="myinput" id="myinput" autocomplete="off" type="text" /> <input type="submit" value="Submit" /> </p> </form>
place the following js just before the </body> tag:

<script type="text/javascript"> window.onload = function() { var myform = document.getElementById('myform'); var myinput = document.getElementById('myinput'); myinput.onchange = function() { this.value = this.value.toUpperCase(); }; myform.onsubmit = check; } function check(){ var code = document.getElementById('myinput').value; if (code == "ABC") { window.location = "yes.php"; } else { window.location = "no.php"; } return false; } </script>

CACHING:
 

WP Super Cache WP Minify

I'll chime in...
 
 
 
 
This is untrue, while the official XCode SDK is only available on Mac there are other SDK's you can use. Titanium (Appcelerator) is available on Windows, OSX and Linux, Adobe AIR is available on Windows and OSX.
 
So you have quite a range of choice for SDK's to develop mobile apps on.
 
The one area that does require a Mac is submission to the app store as you use an uploader to submit to the App store which I believe is only available on Mac (I use the uploader on a Mac but I'd be surprised if that's the only way). Google is your friend there.
 
But a Mac is NOT required for development; ONLY if you use the official XCode SDK but like I said there are other SDK options.
 
 
 
The official Android SDK is available on multiple platforms, but as with iOS development there are other SDK's you can use.
 
 
 
Honestly, if you want to develop on 3 platforms I'd choose iOS, Android and Blackberry, most of my clients request any combination of those 3, I have only ever had one client interested in Windows mobile and two interested in Nokia, none of whom actually bothered going ahead on those platforms, they all elected for the big 3.
 
 
 
Like I said, most want Apps for iOS, Android and Blackberry as they are "The Big 3", Nokia doesn't have a very strong smartphone market AND the next generation Nokia devices will be Windows OS and Windows mobile like Nokia don't have such a strong market hold.
 
I believe (it seems to change quite a bit) that Android is currently top selling, but if you provide for iOS, Android and Blackberry your pretty much safe.
 
 
 
 
I believe your correct' date=' the official uploader is OSX but I'd be surprised if there isn't an alternative way, you used to use a web based uploader but that's been dropped. Fundamentally though if you prefer working on a PC you can still develop on the PC and if it is indeed the case that you cannot use anything other than a Mac to upload to the App Store then the simple solution is to pick up a cheap, old Mac and use it just to upload.
 
 
 
 
I'm sorry but I wouldn't entirely agree with that statement... If I may explain.
 
 
If you want to use nothing but official SDK's then you will need to develop the App from scratch in each SDK. So 3 literally develop it 3 times using the official SDK's for iOS, Android and Blackberry. In that sense multi platform can be a lot of work and very expensive; depending on the App.
 
 
If you use 3rd party SDK's its a bit easier as all the 3rd party ones I know of support multiple platform publishing so you can create the app once in the SDK and publish to each platform it supports. HOWEVER there is an issue.
 
 
The two 3rd party SDK's I trust (as in have used and can vouch for) only support iOS and Android Smartphones NOT Blackberry, which means you can build for iOS and Android from one codebase but would need to start from scratch with the Blackberry App.
 
 
The exception being Adobe AIR which does have support for the Blackberry Playbook, so if your making a tablet App the former is not true as AIR can publish to BB Playbook.
 
 
The downside to AIR is that it requires the AIR plugin on Android (native on iOS however) which is only supported on Android 2.2+, however this may not be an issue. All my clients who have elected for Android (official SDK or otherwise) have wanted newer generation (there is a reason for this; I'll cover this in a bit).
 
 
The two SDK's I know are Appcelerator Titanium and Adobe AIR, as an environment I prefer Adobe AIR but you may be different so try both and see what feels best for you.
 
The official SDK's are however very good, the problem is XCode is kind of complicated and the UI designer is I'm afraid, a complete let down. I hate it with a passion, but then that might just be my preferences showing through.
 
 
Also there is another problem, that being new feature support is always going to be in the official SDK's first so it does pay to know the official SDK's unless your ok with potentially turning down work because your 3rd party SDK doesn't support x feature.
 
 
Now onto Android as a platform, you cannot really create the app once and publish to Android per se, this is because of the diverse range of devices that use Android.
 
For example, if you create an App with a beautiful UI on the Desire, how about a Sony mini device with a small screen and low hardware specification?
 
I know from first hand experience you can hit a road block even with the official SDK having to really think about the UI and how it will work as a UI designed for a nice big screen wont always scale down.
 
You also need to consider performance on lower specification devices and support for various features which does vary between devices and the versions of Android they support.
 
Most clients from my experience want latter 2 series and above due to various features but another developers experiences may vary. Now as mobile phones and smart phones are largely disposable devices (I believe Android will show this more than BB and Apple due to lower price devices being available) and its a fast moving space legacy support isn't going to be an issue like it is on regular computers.
 
 
Hope this helps and good luck to you
 
Oh and App development is NOT easy. lol

Is the form submitted via get or post?
You're trying to echo $_POST['RetDate'] but checking for $_GET['RetDate'] ?

As BlueDreamer said, what does the job entail?
 
I can only echo notbanksy's comments.
Chances are you will be interviewed by somebody who hasn't got a clue what you're talking about.
They might present you with a couple of sample web pages (is there a template for these?) and ask you to tell them what you think is wrong with them (really obvious stuff like 'the menu is covering the slideshow' or 'that image is overlapping the footer'.
 
My advice would be , (corny as it sounds), be true to yourself and your knowledge.
Don't say you can do something when you can't.
Try and keep the conversation to things you do know about.
Admit your failings (stuff you're not sure of) but are keen to learn.
 
A few years back, I had an interview for a web dev role. They asked me if I could create a 'calculator' script to do with personal loans. I replied with 'PHP or JavaScript?'
They couldn't answer...
 
I got the job and left three days later because they were sh1te...
 
Just relax and take it in your stride; you've made it this far, they must like you
 
 
Good luck with the job

I think the site is a nice idea but it seems more of a 'linux/unixcommands.co.uk' rather than ssh specific.
i.e the use of cp rather than scp
Is it aimed at just Windows/putty users?
Is it just for using an ssh client or could it also incorporate ssh server configs?
Perhaps a few best practices could be mentioned such as not allowing passwords, rootlogin, using keys etc
Maybe spin off how-tos such as mounting a filesystem with sshfs?
After a quick read, I noticed your 'renaming files' section is inaccurate. Instead of using cp, you would just use mv. i.e

mv file1.txt file2.txt
It's a great idea though and credit to you

I use similar css on my blog:

#skip {text-align:right} #skip a, #skip a:hover, #skip a:visited {position:absolute;width:auto;height:auto;right:0;top:-500px;color:#fff} #skip a:focus {position:static}
Basically, the second line sets the default styles on the tag but positions it absolutely (removed from the document flow) and adds a negative top margin so it isn't seen on the page. Only on :focus does the position change to static (the default positioning for all elements). Now the negative top margin doesn't apply; static positioned elements aren't affected by the 'top' value and the tag is seen on the page.
Hope that makes sense

I'd say you should provide support for non js-enabled users.
From the sounds of it, you've developed the site's functionality to require the use of js and are now thinking of non js-enabled users as an afterthought.
If you'd built the site with progressive enhancement in mind and added features progressively, you possibly wouldn't be having an issue now?
Admittedly, your site's target audience will play an important part in your decision but I don't see why catering for non-js users needs to be a huge amount of work.
YDN posted a couple of articles on catering for non-js users which I tend to agree with.
 
Just my thoughts

Your select element only has a name attribute of item.
Give it an id of monthselect and change spitfire's code to

var month = $("#monthselect").val();

I'm not 'worried about people to lazy to upgrade there browsers' but I'm concerned that you think people with older software shouldn't be allowed on the internet.

really?

I'd say you should provide support for non js-enabled users.
From the sounds of it, you've developed the site's functionality to require the use of js and are now thinking of non js-enabled users as an afterthought.
If you'd built the site with progressive enhancement in mind and added features progressively, you possibly wouldn't be having an issue now?
Admittedly, your site's target audience will play an important part in your decision but I don't see why catering for non-js users needs to be a huge amount of work.
YDN posted a couple of articles on catering for non-js users which I tend to agree with.
 
Just my thoughts

I'm not 'worried about people to lazy to upgrade there browsers' but I'm concerned that you think people with older software shouldn't be allowed on the internet.