Decided to go ahead and ignore the UX issue for the moment. Now the initial "get the primary and size" returns a DTO (Data Transfer Object) that contains the size size (ia, II, etc), type (F, G, etc) and the stellar zones ID so we can get the inner, habitable and outer orbits. Not really much of an update, and without data it will always return null as no records match. I'll probably scaffold out basic CRUD for that table, but it really belongs in the editor for star type or size, maybe both views via a shared partial view. I know what should probably be there, but this is a case where a project manager or someone looking at it from the outside in would be helpful Sort of how I feel T5 was done: it really needed a 3rd party editor to pull a lot of that stuff together a bit better. We are all blinded by our own stuff (another reason I really actually like code reviews that take the time to actually review the code. Sadly, my current work has none of that, so I got spoiled by the last couple of jobs where we realized that code review really does pay off).
Anyway, no screenshots as nothing new - just a few lines of code in the service, a new repository & interface for that repo. Though I also really need to come up with a better landing page. Currently all the options are just a list across the top of the screen. Works for my widescreen but really looks funny on smaller screens.
I am also rethinking the entire repository thing: the ORM (Object Relationship Mapper) is basically a repository anyway. I'm just adding another layer on top of that for dependency injection basically. It does have some benefits even for a small application like this, but sometimes it also feels like it gets in the way. There are a lot of discussions on this for developers. As developers have a plethora of opinions and software has many ways of doing the same thing.
Our Saturday game got cancelled, so I painted a Minotaur instead. Fairly happy with it - it is from the Archon Caves KS, Donn the Minotaur.
No comments:
Post a Comment