What I'd like to do is a series on how to go about solving problems. If you read the forums you will see many instances of questions being asked, then the answer being something like "It's fixed in the next release, so update".
Not all of the code in this series will always be current as better ways of doing things always come up.
What I want to look at here is the base process that you, me or anyone goes through in order to solve a problem.
I'm hoping it will help developers new to Jamroom or new to developing start to get some patterns that they can use to solve their own problems. Which would lead to developing neat stuff.
So here goes:
First thing to remember is: It's not the problem in particular that we're looking at, but rather the methods we use to solve the problem .
Second thing to remember is: There is always more than one way to solve a problem .
Nice video Michael!
Wanted to add that for developers, Jamroom has a few functions that are really helpful when it comes to URL encoding and Entity encoding:
jrCore_url_string() - use this in place of urlencode() as it handles a wider variety of languages correctly.
jrCore_entity_string() - use in place of htmlentities(), for the same reason
Cool video!
@b360 Cheers mate. All credit to you for the subject matter. Help me find some other topics too.