
I’m sort of working on this typeface from time to time…

I’m sort of working on this typeface from time to time…
This video shows a quick and dirty logo creation process in Flash. I’m starting with a font, breaking it to raw vectors, using Flash’s basic tools working towards the final logo….
I work on the main time line in Flash. From time to time I add a keyframe and move on, thus saving my progress along the way. Finally, that process allow me to a) backtrack in case I feel I’ve lost something, b) make a little video like this…
The final logo, in two variations:





Our company recently moved into a cozy old building in central Copenhagen. As we are a small and young start-up, we can’t afford a whole building, a whole floor nor a whole room for ourselves, so we’re sharing. In fact we’re sharing three floors with 6 – 8 other game developers (depending on how you count).
You could argue that the other companies are our competitors. You could argue that they could steal our know-how, our IP and our honour.
The fact is that yes, in some cases they are, and yes, in some cases they may. But up until that happens we all have a lot to gain from living door to door with the others in terms of sharing problems, ideas, tips, experiences and beer.
The benefits of sharing can however expand far beyond beer.
Small production units don’t need and small start-ups can’t afford much full-time administration and sales staff. Why not share producer, accountant, marketeer and sales resources? Why not in-source publishing?

Recently I’ve been given an interesting challenge that includes creating a complex user interface that should work well for people not familiar with computers [read: Windows] at all. Not only should it work with computer “illiterates” – It should work equally well on three very different continents.
Take India for instance. If you need to take a leak in India and you’re a guy, you apparently shouldn’t be looking for the classic western silhouette of a man indicating that there is a rest room on the other side of the door. You should be looking for something like the above.. (more)
- Who knows what other subtle differences we have here? Ok, I’m not doing a rest room user interface here, so maybe I’m ok…
Ok, no, make that three things.
I don’t get it. How is it even possible to make a machine that emits so much heat and noise and deem it safe for indoor home use? You get a headache and take a lethal chance of burning down your house just after playing for half an hour.
I don’t get it. How is it possible to make a device so incredibly bad at loading and displaying a frickin simple list? Caching is invented as far as I know.
And finally I don’t get the idea of filling up Live Arcade with all that vintage crap. Doom, Marathon, WhateverFighter Something and a bad Galaga port isn’t vintage. It’s just plain waste of space…
I have recently rediscovered Smart Objects in Photoshop partially thanks to a kind reminder from Joen. This is why I think they’re smart, and what I think would be really smart to add.
Smart Objects (SO’s) allow you to define any object in a PhotoShop document as a separate file so to speak. The separate file is then embedded in the document that you are working on. The cool thing is, that you can “compress” really complex objects into one SO in order to keep the main file manageable, while maintaining full control of the “compressed” object. SO’s can be scaled, transformed and filtered without damaging the SO itself.
Before I used SO’s as a way to embed Illustrator objects and similar. And pretty much only this. Now I all of the sudden find myself converting virtually everything into SO’s.
I started out with e.g. a standard button, converted it into an SO and then instanced it wherever I need it. This allow me to work focused on one small commonly used element of e.g. a user interface design at a time, and then flip back to the main comp to see how my changes impact on the overall design.
Next I realized that converting larger isolated areas of a UI design, e.g. the main menu, to an SO with numerous nested SO’s within, really gave a lot of advantages when maintaining one PSD with numerous layer comps of sub-designs in it.
Now I’m just wondering why you aren’t allowed to define a remote location for your Smart Objects, instead of the auto embed? I think it would be absolutely wonderful if I could define an SO in my document, set a remote location for it, and then allow other people in my team to access the same object.
Yes, I know that I can export an SO to a remote location, but I want the remote object to be the master object. Then I could have someone else work on the icons for a UI while I work at the buttons. The icons would update in my document, and the buttons would update in my colleagues document.
… So, when will we see this, Adobe?