https://dsheiko.com/categories/developer-tools/ Recent content in Developer Tools on Dmitry Sheiko's Web Development Blog Hugo -- gohugo.io en-us Wed, 04 Mar 2020 00:00:00 +0000 https://dsheiko.com/weblog/building-a-blog-with-hugo/ Wed, 04 Mar 2020 00:00:00 +0000 https://dsheiko.com/weblog/building-a-blog-with-hugo/ This blog hadn’t a redesign for a decade. It was driven by self-made CMS, which naturally has become, say the least of it, outdated. So some time ago I ripened for a remastering. Instantly I started by looking for a CMS or a headless CMS. Then I realized, the blog is actually static – I don’t have here any forms or services, it’s all about representation of content. Why not to go with a site generator? https://dsheiko.com/weblog/javascript-and-underscore-js-type-methods-in-php/ Thu, 12 Apr 2018 00:00:00 +0000 https://dsheiko.com/weblog/javascript-and-underscore-js-type-methods-in-php/ I’ve been working with PHP since 2000 and with JavaScript even longer. Over last decade JavaScript evolved drastically. It had a promising design from the very beginning and gained its current incredible shape with the shift to ES2015 (Harmony). PHP though didn’t change that much. Apparently it’s doomed always to suffer from its own legacy. It arrived in middle 90s as a simple CGI app to maintain Rasmus Lerdorf’s home page and have been more like spontaneously developing ever since. https://dsheiko.com/weblog/setting-up-dev-environment-with-webpack-3/ Mon, 11 Dec 2017 00:00:00 +0000 https://dsheiko.com/weblog/setting-up-dev-environment-with-webpack-3/ I observe as some people still write ancient ES5 syntax of JavaScript and it’s disheartening. I wonder what keeps them from moving forward. Some must be driven by psychological inertia, but some likely just find it to complex to make their new syntax running in a wide range of browsers. In fact, nowadays we may not fear about it anymore. One can set up a dev environment where tools decide what transformations requires the code and what polyfills to load depending on selected target (list of user agents to support). https://dsheiko.com/weblog/the-client-side-templating-with-commonjs-compiler/ Thu, 27 Mar 2014 00:00:00 +0000 https://dsheiko.com/weblog/the-client-side-templating-with-commonjs-compiler/ In spite of most server-side languages JavaScript was not designed for templates. Yet we have plenty of template engines for client-side JavaScript now. They allow us processing templates, but what about declaring a template? As you know JavaScript doesn’t provide a decent way to assign a multiline text to a variable. Well, you can go with string spitted by back-slashes, but in this case a trailing space would break your JavaScript. https://dsheiko.com/weblog/tooling-live-reload-for-multi-tasked-cycles/ Thu, 25 Jul 2013 00:00:00 +0000 https://dsheiko.com/weblog/tooling-live-reload-for-multi-tasked-cycles/ We all are taught not to repeat ourselves while coding. Nonetheless we keep repeating the same operation over and over – pressing F5/Ctrl-R for browser reload every time we have to examine the results of our last changes. After watching some of Paul Irish screencasts where he was showing the magic of live reload under Sublime Text 2 I wondered if I could employ something alike while keeping working with my beloved NetBeans IDE. https://dsheiko.com/weblog/support-request-tool-like-google-feedback/ Mon, 19 Sep 2011 00:00:00 +0000 https://dsheiko.com/weblog/support-request-tool-like-google-feedback/ Have you ever noticed Google+ has an amazing feature called Google Feedback. You click on feedback highlight an area of the site page and getting screenshot with your marking on it sent to the Google support team. If you wonder of having this tool on your own, just take my code and adapt for your requirements. How to install First of all you have to install server side components for making screenshots ( XServer and CutyCapt). https://dsheiko.com/weblog/source-code-analysis-code-sniffer/ Thu, 20 May 2010 00:00:00 +0000 https://dsheiko.com/weblog/source-code-analysis-code-sniffer/ Choice problem In the previous article we examined the only way of code analysis – PHP tokinizer. But digging deeper you’ll find many of options. Well-known expert of the subject Sebasitan Bergmann points out following Dynamic code analysis -* Xdebug (can be coupled with PHPUnit) -* php-code-coverage Static code analysis -* Token-Level Analysis by ext/tokenizer and PHP_TokenStream -* Syntax-Level Analysis by PHP_Reflection_AST and ext/parse_tree -* Bytecode-Level Analysis by ext/bytekit As far as you see, with such a set of tools you can do whatever you want. https://dsheiko.com/weblog/source-code-analysis-translation-coverage/ Mon, 10 May 2010 00:00:00 +0000 https://dsheiko.com/weblog/source-code-analysis-translation-coverage/ How to Make Translation Term Coverage Report Let’s assume our application has a UI translation module. We created dictionary and use terms from there within the code of application components. Everything is clear so far. But one day we begin to suspect that not all of the terms presented in the dictionary are really used within the application. Besides, probably some of terms which are used in components are not available in the dictionary.