What is best PPC for PocketFrog development?

[BIGBEN]

[HTK]

the e805 could be a good choice, fast beast, and you can try to do some vga stuff.
but your e-125 is not the worst pda for development, I did Infestation using a em-500 and it was good to test the game always on the "worst case scenario", I know that if it runs on that pda it will run equally or better on any other ( apart from sh3 devices ).
My "new" pda is a h1910, it is slow on the default clock, but using it at 300mhz I get the ideal speed to run what I´m development right now ( top-down racing game at 30fps, full screen scrolling, real time rotation for the vehicles, alpha blended particles, hungry things but not as 3d ) so I´m happy with it, at least I´ll not be spoiled to make slow code, I´ll always be afraid of losing the full fps

but on the e-book aspect, i´m seriouly thinking about getting a e805, the libretto I have does not instantly power on like pocket pcs and the 320x240 from my 1910 is not enough in some cases.
I´m sure that e805´s 640x480 will do just fine for every pdf/chm/html I want to read.

there is nothing better than reading a computing book on a computer

[BIGBEN]

[Kzinti]

[BIGBEN]

[fzammetti]

[BIGBEN]

[Kzinti]

[fzammetti]

My suggestion would be the Axim Basic. It's unfortunate that we have to think along these lines, but you really do need to be designing for the lowest common denominator. I think any MediaQ device fits the bill, and since the Axims (the X5's anyway) are quite cheap, why not?

Also, I don't know about anyone else, but I came to a very difficult decision working on my current project: I'm hard-coding the frame rate to 24FPS and designing everything to run at that speed. That's about the highest frame rate I can seem to get consistently throughout the entire game.

As long as it does so on my Axim (running at stock 300MHz), I think I'm OK on every device. Yes, I could do all the time-based frame rate stuff, but it seems like added complexity to me, and I don't like the fact that the game may run smoother on one device vs. another. I'd much rather design it to run the way I see it on my reference device and know that it's going to run that way on any device I put it on.

True enough, there's inherit limitations in working at such a relatively low frame rate, but it's to me the best solution out of a bunch of bad options. Besides, if you know that a given frame rate is giong to be steady, even if it's low, you can design accordingly and get decent results none the less. This is my approach anyway, for better or worse (I just want to get this damned game done already!!)

[BIGBEN]