Moises' handwriting
it is a little on the small side though. and ugly. i would totally be psychoanalyzed as "suicidal" by any graphologist.
made with www.fontcapture.com
Thursday, October 29, 2009
free font!
Moises' handwriting
Monday, September 7, 2009
it does have a point...
i was looking for a way to run "Balance of Power 1990 Edition" on my Vista 64 bit machine, so I checked google to see if Wine was available for vista. I typed "wine" into google, and this came up:
nice one. i don't like wine either. and especially not with cheese. cold beers work just fine.
UPDATE: i accessed the page september 4th, but now it seems they've corrected the error. is there some way for us to browse google's cache?
here's a link to the full-screen capture.
Saturday, August 22, 2009
How to make deadlines
I just came upon this great article from gamasutra: http://www.gamasutra.com/view/feature/4111/dirty_coding_tricks.php?page=4
This one takes the cake, though:
The Programming Antihero
I was fresh out of college, still wet behind the ears, and about to enter the beta phase of my first professional game project -- a late-90s PC title. It had been an exciting rollercoaster ride, as projects often are. All the content was in and the game was looking good. There was one problem though: We were way over our memory budget.
Since most memory was taken up by models and textures, we worked with the artists to reduce the memory footprint of the game as much as possible. We scaled down images, decimated models, and compressed textures. Sometimes we did this with the support of the artists, and sometimes over their dead bodies.
We cut megabyte after megabyte, and after a few days of frantic activity, we reached a point where we felt there was nothing else we could do. Unless we cut some major content, there was no way we could free up any more memory. Exhausted, we evaluated our current memory usage. We were still 1.5 MB over the memory limit!
At this point one of the most experienced programmers in the team, one who had survived many years of development in the "good old days," decided to take matters into his own hands. He called me into his office, and we set out upon what I imagined would be another exhausting session of freeing up memory.
Instead, he brought up a source file and pointed to this line:
static char buffer[1024*1024*2];
"See this?" he said. And then deleted it with a single keystroke. Done!
He probably saw the horror in my eyes, so he explained to me that he had put aside those two megabytes of memory early in the development cycle. He knew from experience that it was always impossible to cut content down to memory budgets, and that many projects had come close to failing because of it. So now, as a regular practice, he always put aside a nice block of memory to free up when it's really needed.
He walked out of the office and announced he had reduced the memory footprint to within budget constraints -- he was toasted as the hero of the project.
As horrified as I was back then about such a "barbaric" practice, I have to admit that I'm warming up to it. I haven't gotten into the frame of mind where I can put it to use yet, but I can see how sometimes, when you're up against the wall, having a bit of memory tucked away for a rainy day can really make a difference. Funny how time and experience changes everything.
- Noel Llopis
This one takes the cake, though:
The Programming Antihero
I was fresh out of college, still wet behind the ears, and about to enter the beta phase of my first professional game project -- a late-90s PC title. It had been an exciting rollercoaster ride, as projects often are. All the content was in and the game was looking good. There was one problem though: We were way over our memory budget.
Since most memory was taken up by models and textures, we worked with the artists to reduce the memory footprint of the game as much as possible. We scaled down images, decimated models, and compressed textures. Sometimes we did this with the support of the artists, and sometimes over their dead bodies.
We cut megabyte after megabyte, and after a few days of frantic activity, we reached a point where we felt there was nothing else we could do. Unless we cut some major content, there was no way we could free up any more memory. Exhausted, we evaluated our current memory usage. We were still 1.5 MB over the memory limit!
At this point one of the most experienced programmers in the team, one who had survived many years of development in the "good old days," decided to take matters into his own hands. He called me into his office, and we set out upon what I imagined would be another exhausting session of freeing up memory.
Instead, he brought up a source file and pointed to this line:
static char buffer[1024*1024*2];
"See this?" he said. And then deleted it with a single keystroke. Done!
He probably saw the horror in my eyes, so he explained to me that he had put aside those two megabytes of memory early in the development cycle. He knew from experience that it was always impossible to cut content down to memory budgets, and that many projects had come close to failing because of it. So now, as a regular practice, he always put aside a nice block of memory to free up when it's really needed.
He walked out of the office and announced he had reduced the memory footprint to within budget constraints -- he was toasted as the hero of the project.
As horrified as I was back then about such a "barbaric" practice, I have to admit that I'm warming up to it. I haven't gotten into the frame of mind where I can put it to use yet, but I can see how sometimes, when you're up against the wall, having a bit of memory tucked away for a rainy day can really make a difference. Funny how time and experience changes everything.
- Noel Llopis
Tuesday, April 14, 2009
PocketTweet
PocketTweet is a small Windows Mobile application that lets you log-in to and update your Twitter account using an active data connection.
Screenshots:
PocketTweet version 0.1(Download Here):
http://www.mediafire.com/?zilgxyoyyx2
Requirements:
- Windows Mobile (2003 and later)
- .NET Compact Framework 2.0
To Do:
- Skinnable interface
- Direct messaging
- twitpic support
- saving tweets.
- friend view
- replies
- account settings
Screenshots:
PocketTweet version 0.1(Download Here):
http://www.mediafire.com/?zilgxyoyyx2
Requirements:
- Windows Mobile (2003 and later)
- .NET Compact Framework 2.0
To Do:
- Skinnable interface
- Direct messaging
- twitpic support
- saving tweets.
- friend view
- replies
- account settings
Thursday, April 2, 2009
gsmGPS
gsmGPS is a Windows Mobile application that approximates your current location without a GPS. It does this by "triangulation". Since all data is in a local datafile, you do not need WiFi or GPRS or EDGE access - it works offline.
Update (v0.3): I have finally found out how to access the current directory in Windows Mobile. Thanks for the feedback. For the latest version, you can just extract the archive to a directory of your choice (can be on a Storage Card). This new version still has data from OpenCellId.
Thanks for the feedback!
Latest version: 0.3
Download gsmGPS 0.3 from here:
http://www.mediafire.com/?223kanimwdn
Instructions:
To install this version, just extract it to a directory of your choice.
Requirement: Windows Mobile with .NET Compact Framework 2.0
The output is a file, mapdata.kml (can be found in the same directory as the executable). This file can be opened in Google Earth:
Note: If you start the program, it deletes the mapdata.kml and creates a new one, so before starting the program, copy the mapdata.kml file in another location.
To do:
- create a version that runs as a "service"
- emulate a GPS device (so you can use it as a GPS device with other programs, i.e. Google Maps)
Old versions:
version 0.2:
http://www.mediafire.com/?yiqyjyzml2j
the one without the opencellid data, version 0.1:
http://www.mediafire.com/?fzyzndgtmfm
Update (v0.3): I have finally found out how to access the current directory in Windows Mobile. Thanks for the feedback. For the latest version, you can just extract the archive to a directory of your choice (can be on a Storage Card). This new version still has data from OpenCellId.
Thanks for the feedback!
Latest version: 0.3
Download gsmGPS 0.3 from here:
http://www.mediafire.com/?223kanimwdn
Instructions:
To install this version, just extract it to a directory of your choice.
Requirement: Windows Mobile with .NET Compact Framework 2.0
The output is a file, mapdata.kml (can be found in the same directory as the executable). This file can be opened in Google Earth:
Note: If you start the program, it deletes the mapdata.kml and creates a new one, so before starting the program, copy the mapdata.kml file in another location.
To do:
- create a version that runs as a "service"
- emulate a GPS device (so you can use it as a GPS device with other programs, i.e. Google Maps)
Old versions:
version 0.2:
http://www.mediafire.com/?yiqyjyzml2j
the one without the opencellid data, version 0.1:
http://www.mediafire.com/?fzyzndgtmfm
Wednesday, April 1, 2009
first post!
welcome to my blog! i created this blog mainly to have a place to put up some of my projects. watch this space for some free software!
Subscribe to:
Posts (Atom)
