This is more of a techy breakdown of how the app works. If you are more interested in learning more about it in terms of how it works for a user, check out this page
This software was originally written and submitted to a competition on Challenge Post titled “re invent the selfie”. Originally I planned to make a timelapse of my entire day into an animated gif capturing a snapshot from the webcam every 30 minutes or so during my work day. I decided that was a little niche so I reduced the capture time down to a few seconds to add just a little extra to the moment of capturing a selfie.
How it works
The project is a node webkit packaged app for OS X. It opens the users webcam when the app is opened, then when the large “Make it” button is pressed 5 frames are captured from the webcam and converted into the gif image format. Then a save button appears and the user can save the gif to their filesystem for sharing on social networks.
What I learned
This was my first experiment using node webkit packaged apps. My day job is fairly varied and I spend most of my time either writing Spring java applications or using front end web tools such as angular for a large scale chat service. So it was was a different set of concerns for me to take into considering building this tool for desktop users. It could be argued that this tool is much more suited to be a mobile app as it is much easier to capture a moment using a mobile phone than pointing a laptop webcam at a situation. This is true but I wanted to quickly prove the concept on desktop and expand my skills into a more challenging environment for myself before porting to mobile, the desktop is more suited to the original time-lapse idea that the project stemmed from.
What’s next for Animated Selfie Maker for OS X?
Social sharing is my top priority to make it super easy to share your selfie to all the main social networks.
Settings to control how many frames to capture and at what speed – this will allow the quick selfie to be expanded into a timelapse if the user wishes.
Filters – Add Instagram style filters & shapes to the animated selfies to make a more interesting creation.
The technology the app is packaged with make sit easy to release a version for windows and linux so they will be following behind the release of this app shortly. The medium of desktop is interesting to develop for but not realistically the most practical to take a selfie on, so depending on the feedback from this desktop release I may port to mobile.
Probably not, I may add an option to remove the watermarks from the selfies but as my time commitment has been fairly low to get it to this point this 0.1.0 version will always be free. If my plans above take me longer than I originally thought I may add add a paid for version to remove watermarks for a very minimal price.
I recently had an issue with wordpress 3.9.1 short tags not parsing correctly. It would call the appropriate function but not populate any of the appropriate attributes. Infuriatningly the issue was only on my live server and not on my development machine so it was a lot of trial and error to track it down. After investigating the problem in the third party plugin for a while I eventually tracked the problem down to the following regular expressions returning NULL.
When I was upgrading I had both servers setup side by side with nginx running on port 82 and setup a quick lighttpd reverse proxy from lighttpd to nginx so that I could keep all my sites up whilst experimenting with nginx config. When forwarding from lighttpd to nginx at a wordpress install it seemed to get itself into an infinite loop redirecting over and over to the homepage. The problem could be tracked down to the redirect_canonical() function in wp-includes/canonical.php.
The check to see if we were on the canonical version of the url was failing and redirecting to itself. I believe it was because the port in PHPs’ $_SERVER variable were different so the url did not match and WordPress would continue redirecting to the url forever. A quick fix was to remove the redirect_canonical filter with the following filter:
The more permanent solution for me which may not be appropriate for everyone was to have all traffic go directly to nginx and remove the reverse proxy after I had finished testing other areas of the site. Using the filter above amy end up with you having multiple versions of the same page indexed by google if you have several versions of the same page setup for translations etc.
A few days ago I came up with a few goals for this site as I have been a little lazy letting the content become fairly stale. I have preached many times to clients and people around of the importance of high quality content in modern SEO in 2014, so, I thought it was time to practice what I preach a little and see what kind of differences I could make to my own site. So as a software developer I thought the easiest problems to fix with this site first would be the technical performance. A good metric for measuring the technical performance of a site is googles PageSpeed Insights tool. It takes multiple factors into account mostly around the two topics:
Page Speed (Ranked separately for desktop and mobile)
Before I started trying to improve my ranking I was using a wordpress theme that was a few years out of date. It wasn’t responsive so didn’t perform well on mobile at all.
So an easy first step was to update the design. I went with the default wordpress twenty fourteen theme as it performs well on all platforms.
Ok, so that was easy. It has some suggestions for increasing the tap areas on the category and tag links but as this is a free off the shelf wordpress theme I am not too interested in that (for the time being). Interestingly my google analytics stats showed that before I changed this theme my visitors were 97% desktop and the remaining 3% mobile / tablet. The main factor for this is undoubtedly that the content is mainly discovered my developers looking for WordPress plugins, but maybe I am being penalised by google for not having a mobile friendly site. I will keep an eye on these numbers in the coming months to see if they improve.
Since January 1st 2014 the average page load time has been around 6.98 seconds (slow) and average page load time 2.70 seconds. A quick first load test with firebug on the homepage of www.mattyl.co.uk shows 23 requests, 636kb transfer and 3.26 seconds load time.
The PageSpeed Insights tool didn’t score too much higher either with a mobile speed score of 64/100
To Install I had to recompile nginx with the page speed module (Instructions here). There are filters for each of the different options and match fairly closely to the issues that the PageSpeed Insights tool will give you. The complete list of filters are all documented but the config below is what worked for me to achieve a 100% speed ranking with the PageSpeed Insights tool. I added this config to a pagespeed.conf file and I include it for each virtualhost on my web server
The tool runs in the background so not every rule will be satisfied on the first page load with the new config turned on. Some processes such as the recompression of images and fetching / inlining of css scripts will only be served to the browser once the external process has completed. It would be a bit of an anti-pattern for a page speed module to make a request slower whilst it finishes its compression.
With all of those filters I was able to achieve a page speed rating of 100/100 for bot mobile and desktop
The module runs as a cpu bounded process so it should not overload your server. This makes it not play terribly well with some caching tools as they can cache too early before the page or all assets has been fully optimised. There are experimental features for configuring a downstream cache with varnish but I have not yet implemented this.
Hopefully this will help if you are struggling to make sense of or make some of the improvements suggested by the the PageSpeed Insights tool. The nginx module certainly took a lot of the manual pain away fro me in reaching my speed goals. I will update in a few weeks time when I have more user data via google analytics if the changes have made a significant affect to real world users.
UPDATE 14/03/2014: Version 0.3.1 has been released on wordpress.org get it using the download above. It removes all duplicates and has compatibility with WPML plugin as well as testing up to wordpress 3.8.1 and woocommerce 2.1.5
The default install of woocommerce does not come with any searching capabilities based on the tags that can be assigned to each product.
I have written this plugin to add this capability to the search on both the front end of your woocommerce site and in the wordpress admin site. There is no extra config apart from installation and activation of the plugin.
You can search by multiple tags by splitting your search with a comma. For example to search for all products tagged with toys and helicopter enter into the search box: “toys, helicopter” and all products with those tags will be returned in the search.
The search functionality in woocommerce doesn’t search by product tags by default. This simple plugin adds this functionality to both the admin site and regular search. It is very useful if you want to add some extra meta information to a product that will increase the discoverability on certain products.
If you have any issues or feedback feel free to leave a comment on this post and I will try and sort is as soon as possible
Disclaimer: This plugin does a mysql query with several joins upon each search. If you have an extremely large store (Eg 20, 000 products) you may be better off using a more generic search solution that builds its own optimised indexes for more speedy searching. If however you own a comparatively small store (less than 5, 000 products) this plugin will probably suit you better.
I recently completed a project that had a requirement for site users to be able to search for woocommerce products by the SKU (Stock keeping Unit). I looked at using relevanssi search but the configuration was a headache and seemed a little overkill to add the search for something very specific.
Plugin Description: The search functionality in woocommerce doesn’t search by sku by default. This simple plugin adds this functionality to both the admin site and regular search. If a product variation is matched the parent is returned otherwise it will try and match on a regular product stock keeping unit.
I don’t have any plans to extend the functionality to search any other aspects of wooommerce apart from the sku but feel free to use the plugin as a base for your own woocommerce search plugins – a link to this blog post would be appreciated though.
Better compatibility with Relevanssi search plugin
Minor release functionally – Major release development wise
Compatibility with Woocommerce layered nav widget!
Fix issue with search results appearing in strange places.
Compatibility with Woocommerce Price filter widget!
Fix issue with incorrect result count.
This is probably the most significant release of the plugin so far as it addresses most of the issues previously raised, so please keep all bug reports / enhancement suggestions coming
Improved support for sites running wpml for translations in woocommerce
OK, Yes I know it sounds mental, but consider the latest email that came from apple selling tickets for their WWDC tickets today. When it arrived in my inbox today it looked like this:
When you enable images it looks like this:
It’s nicer but wouldn’t it be nicer if there was a better in-between stage before the ‘display images’ button was pushed. What if there was a way to display the nice image as a html table so it could be sent in an email and look half decent before ‘display images’ is pressed.
I decided to knock up a quick tool that does exactly that. I wanted a completely client side solution so I used the FileReader api. This does mean that browser compatibility is not wide and the tool doesn’t do any degradation, if your browser doesn’t support it the error console is probably the best place to tell it hasn’t worked. You can also use the sample image if you run in to problems using your own. When I feed the apple artwork through the tool and replace the image the email now looks like this:
Also: view it in your browser. Once the image data has been accessed using the FileReader api it loads the data into a canvas element it samples the image at user defined intervals to get the rgb values. Each of the samples it takes is a <td> in the table with a individual colour. Use firebug / browser developer tools to view the tables output.
As seen in countless TV adverts and movies. If you drag the button to your bookmark menu and click it whilst on a youtube video it will make your hitcount start growing really fast. If it needs to be said this is just an effect and doesn’t actually increase the amount of views your video has according to youtube its just a effect in your browser.