Never create multiple instances of a controller that generates the same view, cause you're event's registrations will be duplicated over and over again!
Wednesday, December 5, 2012
Wednesday, September 26, 2012
Just noticed this method available from API 11 only, so you should find another implementation to avoid unexpected behaviour.
Or don't call the execute method, why? If you'll check documentation you'll see that in some versions of android all tasks will run synchronouslly on the same background thread and on some versions it'll run on a pool of threads. Always use the executeOnExecutor option for consistent behaviour between platform version and avoid unexpected behaviour.
Friday, August 31, 2012
Sunday, July 8, 2012
A few months ago I discovered this new stuff called coffee script, and thought to myself, "this is awesome I'll write less and do more" Today, I tried to continue a development of a pretty fat client side and tried to find myself in the 1000 lines of code I wrote so far (not so many). It was pretty hard, and I'm the only programmer for now, can't imagine how a new programmer would enter to this project.
coffee-script is java-script that look better, no other benefits, and if you plan to write a little more than 200 lines of code, consider using some strongly typed language(that can generate debugable java script) with good IDE that'll help you maintain your code.
Saturday, July 7, 2012
Tuesday, June 12, 2012
Wednesday, March 28, 2012
After a few hours of fighting with google I decided to write it all here:
*This post is more relevant for windows users but can help others.
What do you need to have:
First you need to have ruby 1.9.2+
then you need rails 3+
then u need the bundler gem
then go to getting started with mongoid
then install mongo locally
then check it all good
then add acoount in heroku
then create app
then add your key
Saturday, February 18, 2012
Saturday, January 7, 2012
If you do stuff like put instances of classes inside a session and expect to call methods of this classes later, you must put the session start after you include the classes definitions.
But I suggest not to do this kind of stuff.
Friday, January 6, 2012
The probability that the problem you experiencing is the same is very low.
So here is what my little (and very annoying) google journey came up to:
- You must call session_start(); on each page
- If you use the header('Location: blabla'); you should use relative url to keep preserve session
- some people say before using the header action you need to call session_write_close(); - I'm not using it.
- session_write_close(); could be the reason to your problems, cause after calling it you can't modify the session (in the current http context), that was my problem.
- on php docs, they say that "Session ID is not passed with Location header even if session.use_trans_sid is enabled. It must by passed manually using SID constant."