Creating layered images in C#

I'm currently developing a mobile site for a client. The site is the frontend for a competition that they will be running in 2010.

Part of the project specification requires the user to be able to build an image by choosing a background, foreground, and slogan. The site will then composite these images and enter the result into the competition.

In addition the site will send text messages to the users cellphone informing them of their status and (if they elect to receive it) a "word of the day"

This is probably the closest C# solution to what I was looking for:

public Image LayerImage(Image Current, Image Layer, Int32 LayerOpacity)
{
Bitmap bitmap = new Bitmap(Current);
Bitmap layer = new Bitmap(Layer);
Color pixel = new Color();

for (int x = 0; x < layer.Width; x++)
{
for (int y = 0; y < layer.Height; y++)
{
pixel = layer.GetPixel(x, y);
bitmap.SetPixel(x, y, Color.FromArgb(LayerOpacity, pixel));
}
}

return bitmap;
}

The PHP solution is slightly more easy:

$layers[] = imagecreatefromjpeg("images/example_background.jpg");
$layers[] = imagecreatefromgif("images/example_foreground.gif");
$layers[] = imagecreatefromgif("images/example_motto.gif");
for ($i = 0; $i < count($layers); $i++)
{
imagecopy($image, $layers[$i], 0, 0, 0, 0, 600, 550);
}
header('Content-type: image/jpeg');
imagejpeg($image);

We don't use the .PNG format when coding a .mobi website because not all handsets support this format. Similarly we cannot assume that Javascript will be supported and so we cannot rely on this as a solution. Everything must happen at the server and be sent in the most simple format to the mobile phone.

Further references

http://www.dreamincode.net/forums/showtopic53101.htm
http://msdn.microsoft.com/en-us/library/system.drawing.aspx
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm

Comments

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer. Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted. This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel. A thorough comparison of the patterns is available here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework. It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database. Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its glory in this demo.

Fixing puppet "Exiting; no certificate found and waitforcert is disabled" error

While debugging and setting up Puppet I am still running the agent and master from CLI in --no-daemonize mode. I kept getting an error on my agent - ""Exiting; no certificate found and waitforcert is disabled". The fix was quite simple and a little embarrassing. Firstly I forgot to run my puppet master with root privileges which meant that it was unable to write incoming certificate requests to disk. That's the embarrassing part and after I looked at my shell prompt and noticed this issue fixing it was quite simple. Firstly I got the puppet ssl path by running the command puppet agent --configprint ssldir Then I removed that directory so that my agent no longer had any certificates or requests. On my master side I cleaned the old certificate by running puppet cert clean --all (this would remove all my agent certificates but for now I have just the one so its quicker than tagging it). I started my agent up with the command puppet agent --test whi

Redirecting non-www urls to www and http to https in Nginx web server

Image: Pixabay Although I'm currently playing with Elixir and its HTTP servers like Cowboy at the moment Nginx is still my go-to server for production PHP. If you haven't already swapped your web-server from Apache then you really should consider installing Nginx on a test server and running some stress tests on it. I wrote about stress testing in my book on scaling PHP . Redirecting non-www traffic to www in nginx is best accomplished by using the "return" verb. You could use a rewrite but the Nginx manual suggests that a return is better in the section on " Taxing Rewrites ". Server blocks are cheap in Nginx and I find it's simplest to have two redirects for the person who arrives on the non-secure non-canonical form of my link. I wouldn't expect many people to reach this link because obviously every link that I create will be properly formatted so being redirected twice will only affect a small minority of people. Anyway, here's

Adventures in IT

Search This Blog