Skip to main content

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
Labels:

Comments

Post a Comment

Popular posts from this blog

Using Fail2Ban to protect a Varnished site from scrapers

I'm using Varnish to cache a fairly busy property site.  Varnish works like a bomb for normal users and has greatly improved our page load speed. For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site. I decided to use fail2ban to block IP's who hit the site too often. The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with. This means setting up varnishncsa.  Add this to your /etc/rc.local file: varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log: /var/log/varnish/*log { create 640 http log compress ...
Post a Comment
Read more

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred.  The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change.   Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal.   One way to decouple your domain logic from both persistence and controller is to use the "repository pattern".   Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...
Post a Comment
Read more

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 ...
Post a Comment
Read more