Sunday, April 3, 2011

Working on Dungeon Roller

I began work on Dungeon Roller (working title) tonight. I'm using the blog tutorial from rubyonrails.org as a guide. The idea is pretty similar and the functionality seems like it will overlap enough that I can just edit the code where needed.

So here's what I'm working with so far: I've generated the main Character model and I want other models to be associated with it and displayed when viewing a Character, but I want them to remain separately editable. Under the Character model, I've got strings for Name, Class and Level and Text for Background and Description. These should be fairly static, but users will still be able to edit as needed.

I plan to make separate models for Stats, Skills and Equipment, all of which will be visible from the Character model, but remain separately editable. Am I making sense here?

Some questions:

So far, I don't require creating an account/username before creating characters. This is definitely something I'll want in the future, but for developing purposes it seems too clunky to add now. How easy is this to add later? Should I even be worried about that right now?

When generating a model, how difficult is it to add or delete multiple items from that model? I'm assuming there's a command for it, but haven't run into it yet.

I'm pretty excited about this project. It feels good to have a concept and to figure out ways to make it work!

3 comments:

  1. User login is very easy to add later, and we do it this way sometimes. That said, make sure you don't shoot yourself in the foot. It may be easier to identify these issues once your foot is pretty well shot up.

    Deleting is very easy. There are a couple approaches specific to different goals but searching for delete/destroy in documentation should get you there.

    ReplyDelete
  2. Yeah, I'll just leave user login and css for later. Right now I've got enough core functionality to work on.

    Last night I was working with adding columns to a table, then writing a migration and editing the relevant model files to reflect the change. Is there an easier way to display changes, or will I have to edit those files every time?

    I had to force myself not to go back to coding right before bed because I knew I wouldn't get any sleep if I kept working. Awesome!

    ReplyDelete
  3. You should use the basic tools for a few weeks at least before trying some of the easier solutions, but their definitely are easier ways to go about it.

    ReplyDelete