{"id":17723,"date":"2015-10-14T05:01:02","date_gmt":"2015-10-13T19:01:02","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=17723"},"modified":"2015-10-14T13:20:21","modified_gmt":"2015-10-14T03:20:21","slug":"image-arc-distortion-via-imagemagick-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/image-arc-distortion-via-imagemagick-primer-tutorial\/","title":{"rendered":"Image Arc Distortion via ImageMagick Primer Tutorial"},"content":{"rendered":"
\"Image<\/a>

Image Arc Distortion via ImageMagick Primer Tutorial<\/p><\/div>\n

ImageMagick<\/a> is a really very very useful PHP class to manipulate image files on a web server, ours at rjmprogramming.com.au being an Apache\/PHP\/MySql web server. That arrangement makes PHP (and the ImageMagick class) a serverside processing constituent. It is most likely if lots of this is new to you, you will still have heard of the phrase “client\/server”<\/a>. And it’s very very likely you’ve heard of Javascript, as it is approachable right up at your own personal computer or device, and manageable and changeable, often (though ever harder with mobile devices), up at your own personal computer or device. PHP, and ASP.Net, and Python, and Perl are more associated with the “server” in “client\/server” … sadly nobody in the world seems to be taking responsibility for the “\/” … but we digress.<\/p>\n

Meanwhile, back at the ranch … when you visit a website and it shows images particular to that website, these image files will be located on that domain’s web server’s file system (ours at rjmprogramming.com.au is a Linux web server file system (and what a world of wonder is Linux, but that is another story)), and a tool like ImageMagick can …<\/p>\n

    \n
  1. read<\/li>\n
  2. write<\/li>\n
  3. update<\/li>\n<\/ol>\n

    … that image, whereas “client” Javascript (and its supervisory HTML) can only, but importantly, just do that first “read” operation … without “read” of course, we wouldn’t even have a test pattern to look at (like in the early days of television).<\/p>\n

    PHP and GD (take a look at PHP GD and Image Functions Primer Tutorial<\/a>) and ImageMagick, amongst others, probably, can involve you in all three modes of use above to enable you to write your own web applications, in our case with PHP, that can do some of those techniques, which may or may not make you gasp, that the traditional image editors like Gimp<\/a> (often under its “Filters”<\/a> menu) or PhotoShop can do, with your web server images. Normally, though, with the involvement of Gimp and PhotoShop types of image editors, it is usual to not do the work on the web server itself, but to do that image manipulation work on a laptop or workstation, that then has ftp<\/a> (or sftp) access to that web server, on which the image files are “uploaded” to sit there waiting for the internet world to come along and “read” (or access) them, perhaps in the form of an HTML img<\/a> tag in a webpage owned by the domain you are accessing in the URL you …<\/p>\n