About damn time, really.
The old site was brown and more brown, combined with a ginormous font file resulting in some terrible behavior.
I shall say no more. Those dark times are past.
I’ve been working on the redesign for a while, and I hate that it took so long, but I’m pretty happy with the results. Still kept the dark feel, but moved away from the monochrome look.
Continue reading The Charon Sheet: A Facelift
So I’ve been working on the next major release of the D20 Spell Lists app, and have found myself in a code and UI reorganization/refactoring jungle as I’ve refined my feature set and how I want to handle things.
One of the common-enough cases that the current version doesn’t handle well that I think needs to be is multiple spellcaster classes. If I’m a Druid 5/Bard 6, I’m going to want to keep separate spell lists, and will have different DCs, spells known, and spells per day to contend with. With the current version, the best solution is probably to have two different character files, each with its own spell lists.
My attempts to smooth that out have resulted in a lot of UI revisions as I tried to find good ways for displaying and updating all this info without slowing down the UI to uselessness (buh-bye, Table Layout Panel). Here’s what I’m sitting with now:
It’s not pretty, and there are more tweaks in the queue (like just putting the DCs/per days right with each class, probably), although for the moment it works well enough (read: stuff doesn’t end up hidden and inaccessible) that I can get functionality working again.
Like that 0 modifier for a Wisdom of 15. >_>
Continue reading The Contortions of a Spell List
Downloadable from The Charon Sheet. (Also, I’m currently reading The Principles of Beautiful Web Design so’s I can make TCS less sucky and more purdy. Expect design changes there as I learn how to do this crap from scratch.)
Only two issues fixed, but they were kinda show-stoppers for the affected folks. Details on the issues fixed.
So I’m in a D&D 3.5 campaign now. And I’m playing a Druid, which is kinda exciting–it’s the first time I’ve played a Druid at a high enough level that I can shapeshift, and I just tipped 5th level on Sunday. (Campaigns always fizzle out early…)
Anyway, the campaign is a hodgepodge of standard D&D and Sandstorm, and summoning restrictions by the GM mean that my spell list involves a fair bit of swapping out that’s a little annoying to manage. For instance, I’m using Sandstorm’s “Desiccate” instead of “Summon Nature’s Ally II”, since I can’t summon.
Since Druids are the type to prepare a few spells per day from a large list of available spells, I needed a quick way to see all of my available options without flipping through two sourcebooks and my swap list at the table. Then I wanted to avoid having the jotted down short-hand description of the spell that I refresh every “day” as I try out new spells.
Pain in the ass.
A bit of Googling lead me to conclude that with the advent of D&D 4e, many of the 3.5e resources… disappeared. And by disappeared, I mean:
All files withdrawn at the request of Wizards of the Coast.
Continue reading d20 3.5 SRD Spell Lists: First Beta
Talk about taking a large bite.
In the interests of pushing my .NET knowledge, I began migrating the Geist character sheet project that I’d started in Django to .NET MVC 3. I hadn’t done MVC in .NET since MVC 1 was beta’d, but hey, MVC is MVC is MVC. Right?
So in the interests of making things more interesting and more testable, I decided to dive into the Entity Framework 4. My beginning read of POJOs in Action, along with my previous experience with .netTears–I mean, .netTiers–had me generally familiar with the concepts of entities, contexts, and repositories.
Kicker is, POJOs is just a book (and one I’ve barely dived into), and .netTears uses code generation, meaning I could get away with treating it as just a very hefty ORM in the applications it was in. Generate and go.
Getting my fingers in it was a whole ‘nother experience.
Continue reading Brain Twist: .NET MVC 3, Entity Framework 4.1, and TDD