Community

Serphet wrote:

this isn't the thread for this.

Sure is, the FAQs that need to be answered are:

When will Character Builder be supported on OSX?

Why isn't the Character Builder supported on OSX?

and What kind of brain dead ninny decided to build the character builder as a desktop application instead of a web one in this day and age?

But to those who want to know what to do when WotC refuses to acknowledge the Mac, or linux users in who play D&D* stop paying for DDI and make it clear why you aren't in the feedback form when you disconnect your account. If they won't listen to your voice they may finally start listening to your money (and the lack there of.)

*Considering D&D appeals to geeks, who tend to be 1) more computer savvy, 2) more likely to be more then just windows users you would think they wouldn't make a bone head move like this, but on the other hand that whole knee-jerk idiocy with the pdfs....

Serphet wrote:

I understand why the app is and will probably always be windows only, and Why it wasn't done as a webapp.

So I understand why it will probably always be windows only, that being they made a arbitrary decision to develop on a windows only platform, and not just a windows only platform, but the most recent release of said platform blocking even the few community efforts to make .net work on non-windows. Since that choice was made, and money spent to make it so, your right they are probably never going to rewrite it in a different language now. Too late, so sad... My question is why?

As for why is wasn't done as a webapp? Again I don't see a good reason why not, and actually it is possibly the only possible path forward at this point. As they could make an asp.net front end to the app and not have recode the whole damn thing.

mudbunny wrote:

It is something that will be put in the FAQ that is in development here.

And here is the elf quote:

elf]We mocked up a web app and it wasn't responsive enough, we mocked up a winforms prototype, and it was slow and lacked the ability to do all the things we wanted to do so we ported to WPF which set us back a week but was so worth it.

This is from one of the (ex)-devs on DDI and macs:

So what he is saying is "We mocked up one window proprietary interface, it didn't work so well so we mocked up another windows proprietary interface?"

So the remained of his quote goes on to assume that customers should suck it up and pay 150 for windows just so they can run one piece of software (Or is Hasbro endorsing that we Pirate windows to keep costs down), or wait for Microsoft to build a CLR implementation for OSX? The later is naive, and the former is presumptuous.

At this point they could embrace creating an open API into their system, it would still require individual users to have subscriptions, but then allow third parties to build tools so that avid Mac/Linux users could just build their own wrote:

Oct 20, 2009 -- 5:18PM, Matthiasdmh wrote:

Aside from that issue, however, does anyone know of a way to either save character sheets as images or otherwise move them in a format that I can open and print from a separate computer?

I use a mac, and im so i have not had the opportunity to use the builder. However, it is my experience that most operating platforms (including windows) allow printing to a file of some sort. My mac allows printing to a .pdf, which is basically an image of the file. Windows also support a .pdf format or similar though their document writer printer. Check your available printers in the drop down menu to see if you have access to it. These files are usually fairly small and should be easily transportable... most are small enough to even send in an e-mail attachment. Hope this helps.