Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it,
follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given
their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
PA Programming Thread :: PAdev.net - Need hosting for a service of yours? Check it out.
Posts
Remember that's allowing for a maximum of 512, not starting the VM at 512.
-Xms512m would set it at startup.
And if you do threading -Xss512m would allocte 512 a thread.
We're bolting on i18n to an app waaaay after active development has stopped, and by and large the textual display portion works flawlessly (this is .net 3.5, with a mix of WinForms and WPF). The problem comes when we let the user set display formats for dateTimes and monetary amounts. The preferences control that lets the user set these allows for the user to set the terms in their language. For example, YYYYMMdd becomes AAAAMMdd for Spanish locales.
The problem is our DateTimeHelper class, which converts between these different formats, saves the user-generated formates, and assorted other helper functions, persists the locale-specific version of these strings instead of translating to a locale-independent format before doing the translation.
Similar situation with monetary amounts, in that decimal and comma positions are variant based on locale.
In both cases I was able to fix the problem by splitting up the functionality in the helper classes in separate 'data-facing' and 'user-facing' method chains, where there is one entry point from user-facing to data-facing that always is visited before any data transmutation occurs.
Hooray for not planning on i18n in the first place!
I'm just glad we're not handling Right-To-Left support, because the designers here would flip tables if they had to account for that as well.
I am wondering if I should blog about company and project stuff and what of it. I can't go into a lot of details for a while cause yeah.
The PhalLounge :: Chat board for Phalla discussion and Secret Santas :: PhallAX 2013
Critical Failures IRC! :: #CriticalFailures and #mafia on irc.slashnet.org
(Need a master of C#-fu on staff?)
We have an iPhone/iPad game in development.
The PhalLounge :: Chat board for Phalla discussion and Secret Santas :: PhallAX 2013
Critical Failures IRC! :: #CriticalFailures and #mafia on irc.slashnet.org
Way to waste battery life.
MonoTouch? C#-master? Huh? HUH?! You see where I'm going with this?!
(Seriously though, good luck...it's something I've seriously, seriously considered lately)
He's right, the JVM, even a really good one like Dalvik, is a huge waste of battery life, because it has to do the entire JIT step just to run code. Oh, I know, Android has a Dalvik cache where it stores pre-jitted app images, but still.
I think my g/f's phone lasts about a day of normal use. I can go about 2.
My stupidphone can go roughly a week.
Samsung. Everything I own electronic is Samsung if I can help it..
I stick with sony and toshiba. Pretty much all the big name brands are good. Just replaced an old CRT TV that was probably 15 years old that was Zenith with a sony one.
Objective-C is the sheriff of alien town.
No.
Yes it is.
My major beef still.
What part? You didn't highlight anything.
Sir, we just bolted Smalltalk on to C....what have we done?!
It's alive...IT'S ALLLIIVVVEEEEE.
You are a teller of lies.
It's all that Java. It's gone to his head.
It's true. Too much Java and I get slap happy.
So for instance, if the end user does RegisterAutoGeneric<IList<>>();, any parameter or return value I find that is based on IList, and who's generic parameter is something I can map (either because it's a core type like string or int, or because it's a mapped complex type), I will auto-wrap that generic in a handy dandy type wrapper.
I would encourage end users to auto-generic interfaces when possible, because a single IList<TType> wrapper can encompass every possible implementation of IList<TTYpe> out there...ObjservableCollection, ReadOnlyCollection, regular old List...etc.