Fortsätt till huvudinnehåll

Hey, there's a framework for that

Remember the iPhone 3G commercial "There's an app for that"? I got a similar feeling yesterday when I discussed my current mini-project "The Record Collector" with an old collegue of mine. Just after giving him the summary he said "Oh, so you are using Play?". Play, I thought, what is that?

Well, it turns out that Play is a framework that "makes it easy to build web applications Java & Scala". I haven't thought of The Record Collector as a web application, but maybe it should be... Need to sleep on it.

Kommentarer

  1. Spännande med Play! Får kolla in det :)

    SvaraRadera
    Svar
    1. Loggan är lite väl lik SVT Play ;).
      Grejar du med något på fritiden nu? Kanske är fullt upp med hus och barn?

      Radera
    2. Listan på grejer som jag skulle vilja göra är lång... men inget som görs för tillfället. Ganska fullt upp med hus och barn...

      Radera

Skicka en kommentar

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i