Daily struggle for a cleaner code
A simple one-liner to convert all JavaScript in a folder to CoffeeScript
First, make sure you have installed “js2coffee” ( and js2coffee.org is real cool for single files too ):
|
1 |
npm install js2coffee |
And then just paste this:
|
1 |
for f in *.js; do js2coffee -it $f > ${f%%.*}.coffee; rm $f; done; |
-it options modifies the spaces to tabs, remove it if you prefer spaces.
Enjoy!
Underscore.js has a lot of great stuff packed in it. One of the functions I love is pick, which lets you input some keys and get a new array from an Array.
So today I wanted to find an alternative to Underscore’s _.pick for PHP, and I didn’t. It’s not a function that would be difficult to write, but that’s where WordPress comes in.
People at WordPress thought that it would be a nice helper for them too, so in WordPress 3.1 they added wp_array_slice_assoc.
The naming is a bit long, but the function is awesome anyway and the naming explains the purpose alright. Slice an array associativley ( that’s a big word ).
Here is how it works.
Imagine we have a some array like this one.
|
1 2 3 4 5 6 7 8 9 10 |
<?php $myray = array( 'john' => 'a name', 'jane' => 'also a name', 'doe' => 'a fake last name', 'duck' => 'an animal', 'goose' => 'an animal', ); ?> |
In this case the array is a mess, your array should never be a mess, but it might happen. In this case, I know I want only John and Jane in my array, so I can do this:
|
1 |
$persons = wp_array_slice_assoc( $myray, array('john', 'jane') ); |
Tara. Now I have a new array “$persons” which has only john and jane.
Well, there are times where you would write something like this:
|
1 2 3 4 |
$john = $myray['john']; $jane = $myray['jane']; $duck = $myray['duck']; $goose = $myray['goose']; |
Which I think of an overkill, especially if you need like 10 variables. Of course you could extract from all of them
|
1 |
extract($myray) |
But what if the array has like 20 items. What happens when they clash? What if someone else modifies your code? I just don’t feel that blindly using extract is the best development pattern.
Along comes wp_array_slice_assoc()
|
1 2 3 4 5 6 7 8 9 10 |
$keys_to_extract = wp_array_slice_assoc( $myray, array( 'john', 'jane', 'duck', 'goose' ) ); extract( $keys_to_extract ); |
Or a slightly more readable (based on preference) variant
|
1 2 3 4 5 6 7 |
$keys_to_extract = array( 'john', 'jane', 'duck', 'goose' ); extract( wp_array_slice_assoc( $myray, $keys_to_extract ) ); |
That’s it.
|
1 |
echo $john; // Echoes: "a name" |
Please, please be careful extracting variables. And when you do, please document them, even if the documentation comes in the form of $keys_to_extract. Recently I had a very difficult time figuring out what is what because the author of a plugin pulled some weird variables out of nowhere and I had to run around var_dump’ing all over the place until I figured out what is what.
Before it was approved.
In fact, we’ve had 2 themes rejected on Themeforest for various reasons and only now will I admit that I was angry. I was mad! Mad at the reviewers, counting clicks they’ve made reviewing my themes. Mad at myself for developing something that isn’t approved. Mad at the universe for putting me in this position ( I could just have found a case full of money instead of all this… ). How much did that help? Zero. It only led to
Self pity. Anger. Frustration. Fear.
I experienced it all, and it seems that the more I felt any of these emotions, the more I got similar ones. I thought I am never going to get out of it.
I quit my job in January with very limited funds in my pocket. Having done that, I had a motivator that basically says “either you’ll learn how to swim or you’ll sink” was pretty motivating, until I had to face rejection. Once it was introduced, it was like having someone at the shore shouting: “Give up! You can’t swim, just let go and drown already”. Not motivating at all. Which caused the (what seemed to be the) endless misery.
I have no idea what did it for me. It may be that I was already expecting that. I wanted to say prepared, but you just can’t be prepared for that sort of thing, and you’re not even going to get what you we’re expecting as well.
So after all the rejection, and having our Acid theme also rejected, I just decided that nothing is going to stop me. I will work on the Acid theme until it is approved.
As it turns out. It’s all that was necessary. I could write a book where I could describe all the advice I’ve accumulated from all the literature I’ve read on the subject, but it all really boils down to the decision not to fail.
By that I mean – If you think you fail, you failed. If you decide not to fail at all, you won’t. Or as Thomas Edison puts it:
I haven’t failed. I’ve just discovered 10’000 ways that won’t work.
It’s a really simple lesson. At least it sounds simple. But there is no way you’ll learn it but through experience.
Here is another really quick snippet.
If you have a page where you’re using Query Posts you’re going to have trouble with Pagination.
Wordpress for some reason likes to use page and paged randomly.
If you assign your page as the “front page”, you’re going to have to get_query_var(‘page’), and if you’re going to assign it elsewhere, it’s going to be paged. This is all fine and dandy, at least when you’re in control, but as soon as someone else starts using your theme, you need something more trustworthy, and that’s what this is.
More
Right now I’m working on a redesign for TexturePlanet.
Up until now I was using Detube theme on TexturePlanet, and it was really more like in an experiment stage to test if people are still looking for textures, and they are.
More
Thanks to WP-SBVTLE I’ve got a nice theme for myself. I will probably make a couple of edits now and then, but finally I feel like writing.
The default WordPress Twenty Twelve (or thirteen) aren’t bad themes, but I just wanted something more like… well – like this.
I’m still in the process of moving, but I’m finally moving from Rackspace to WPEngine. I’ll post about that later on, but so far my experience with WPEngine has been truly amazing! They are awesome!
Well. Previously I didn’t have one, so theoretically it’s not new, but I’ll count it as new. I took the Elephant from The Noun Project, designed by Ted Mitchner.
Yes. This was a short post. I hope to keep writing nice little short posts to get into the habit of writing.
I’d like to think that I’m no different than most of the developers out there. We identify a problem that we encounter and automatically begin thinking of possible solutions.
My problem was a simple one, this time. I wanted to start a side-project ( if you must know – it failed half way through ), but this time, after reading a couple of articles about side-projects, I decided to pay attention to how much time I spend on my side-projects. And I’ve always wanted to know just how much time does something take up exactly. It’s easy to think “ohh it will take me just 3 days”, then spend almost 2 weeks on a project (like when building this application), and finally just loose track of your time completely ( for example now I have no idea how long did it actually take me to build the Progress App ), sure I can do some simple date-hour-calculation “I worked from A date to B date about C hours a day, which means that I worked D hours”, but that is just not good enough, and it gets even worse when you have a very flexible schedule (like I’ve always had), because you manage your own work. I don’t want to repeat the “3 days to 2 weeks” mistake ever again! Without simple time tracking, I know that I will get lost again and again. This just had to stop!
If I would build an application for each problem that I encounter, I would have a lot of problems and close to no solutions. Instead I use the search and gladly buy solutions. My initial search was on the Android Market, because I own a Samsung Galaxy S3 ( we’ll come to the “How did an Android app become an iPhone app?” question later ), and I was confused. Not a single application did that seemingly simple thing. Sure, there are time trackers for all sorts of things, egg timers, running-tracker buddies, freelancer time trackers (like harvest), etc. I didn’t need all that complexity. I wanted a couple of labeled chronometers. Was it too much to ask ? I guess so.
I must admit, that I might have ignored a couple of applications out there. But even if I have, it just means that I reached a certain level of frustration and decided not to bother anymore. Moreover, they probably didn’t fit to my “Simple application” criteria, because really, I was going to give somebody a 1$ for a simple application, nobody wanted my $.
After all the frustration, the defining the solution was easy. A simple application that lets me time my projects/tasks. Emphasis on simple. And of course I should be able to delete tasks, edit the labels and reset their timers.
Right now I’m timing how long does it take me to write this article. I called the timer “Writing Article”. When I’m done with writing, I’ll just stop the timer and see how long did it take me to write all this. The next time I’ll write an article, I’ll reset the timer and see how long is that article going to take. And so on. This was the solution I was looking for.
For the past year I’ve been building applications with Appcelerator Titanium, which has been a very… let’s say “dynamic” experience, but I’ll talk about that another time. For now – all you need to know is that Titanium promises a solution to build cross-platform applications, and because I’m no good in Objective-C (and because I have an Android phone) I decided to build my application in Titanium (with JavaScript). So I did.
What started out as an idea for the Application for my Android phone had just shifted into an iOS Application idea. How? It’s simple, really.
From my experience Android market is a poor place (in comparison with Apple App Store). Applications just don’t sell, users are dissatisfied a lot more, and paid applications aren’t popular. Even further (I know I said I wouldn’t talk about it here) Titanium is just no good for Android. All that combined, and I just didn’t see the value of investing another 25$ for a marketplace membership (which isn’t expensive at all, after Apple’s 99$).
Even further. Android applications require a lot more work, not just because of Titanium, but because of Android. Android is a nice, open operating system, but it comes with it’s own set of problems. For example if you think responsive design is hard, try doing responsive apps, that have to account for all the different screen sizes and systems that the application should be run on. I have no idea how real android developers actually get by.
So I had an idea for Android App, I built it for iOS, and I’m using it alone (with 2 other peeps) on my Android, because after all, I wanted to track my time!
My girlfriend is a Designer/Illustrator, so I had it easy. I asked her to make a nice icon/splash screen and the UI Design. We gave the design a lot more thought than I initially anticipated, but in the end, I think we built a nice little application.
At this point, I’m not sure if I am ever going to publish the application on Google Play store, because of (again) Appcelerator Titanium, the application isn’t just as responsive as I’d like it to be (as in – you have to wait a few ms until a tap event is registered) . I believe that the application should provide value if it’s being sold, and I think that the slight lag (that I’m okay with, but I didn’t buy the application from someone else) defeats the feel of the application a bit. But releasing it for free on Android market wouldn’t just be fair to iOS users, so – Android, you lost yet another app.
It took 6 days for App Store to approve my application, so here it is:
Progress App: https://itunes.apple.com/us/app/progress-app/id594906155?ls=1&mt=8
I just uploaded my initial commit to Github with snippets for the Compass Susy Grid system.
This is version 0.00001, which means I have no idea if I’ve made spelling errors or forgot something, but we’ll fix them over time, right ?
I hope that in the future we can add in some auto-completion for Susy variables, etc, but for now, I hope that you’re going to like my Susy Snippets
Why I didn’t use var_dump() for a long time, even though it has very valuable information in it ? You most probably guessed it. It looks terrible. Even when you fix it with adding <pre> tags around it, it’s still ugly.
Consider this code:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
$fruits = array ( "fruits" => array ( "a" => "orange", "b" => "banana", "c" => "apple" ), "numbers" => array ( 1, 2, 3, 4, 5, 6 ), "holes" => array ( "first", 5 => "second", "third" ) ); var_dump($fruits); die(); |
Well it is turned into this:
It’s ugly! It’s so ugly! There are no other words for it.
So I could never talk myself into using it, and because of that for the past few years, I did a print_r(), wrapped in those “pre” tags.
Until I saw a screencast by Jeffrey Way on Laravel, and I saw the single most beautiful var_dump in the history of mankind.
Look at it! It’s so pretty! It’s the same data, but so much has changed!
So I wanted it too. After some googling, I found out, that it is a PHP Extension (that anyone can install) and not a Chrome extension (which was my initial guess). It’s called Xdebug, and you can get it at http://www.xdebug.org and you’ll probably want to read more about the installation ( http://xdebug.org/docs/install )
In addition, I initially thought, that I’d have some difficulties installing and setting Xdebug up, since I’m a MAMP user (I like graphical interfaces and all that good stuff, I just can’t help it, that’s why I am so excited about Xdebug after all). Turns out, that I was wrong (again).
Enabling Xdebug on MAMP (Pro) is as simple as, well – enabling Xdebug on MAMP (Pro). All you really have to do is:
|
1 |
zend_extension="/Applications/MAMP/bin/php/php5.4.4/lib/php/extensions/no-debug-non-zts-20100525/xdebug.so" |
And That’s it! Enjoy!
Was looking for a simple way to write an alternative of PHP’s in_array() function in JavaScript, and since I’m using actually writing CoffeeScript, decided to look there as well. And sure enough. Mind Blown.
|
1 2 3 |
for val,key in values if val in selected_values return "MIND BLOWN." |
Turns into
|
1 2 3 4 5 6 7 8 9 |
var key, val, _i, _len, __indexOf = [].indexOf || function(item) { for (var i = 0, l = this.length; i < l; i++) { if (i in this && this[i] === item) return i; } return -1; }; for (key = _i = 0, _len = values.length; _i < _len; key = ++_i) { val = values[key]; if (__indexOf.call(selected_values, val) >= 0) { return "MIND BLOWN."; } } |