• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
  • entries
    68
  • comments
    177
  • views
    81163

LittleBugz update

Sign in to follow this  
Followers 0
capn_midnight

242 views

In starting this journal entry, I'm considering the scope of the LittleBugz project. This journal entry is then a brain storming session on my behalf. Over the course of the entry, I had changed my mind on the scope of the proejct, but I left the process of coming to that decision in the entry.

I'm thinking LittleBugz will support multiple modes of operation. It could have a wizard interface to ask the user questions about how they are going to use LittleBugz, and then it will select a mode of operation based on that.

Modes will cover different combinations of features:

Single user versus multi user
user authentication versus no auth
user roles versus no user roles
XML file versus database store

Here's how I expect them to be used:

Single User, no auth, no roles, XML file store:
An organized todo list for an hobbyist working on personal projects

Multi user, authenticated, no roles, XML file store:
A small team (3-5) of hobbyists, probably close friends, working on a project together. They already have source control, probably something like SVN, and the XML store file will be in that source control. Everyone has full control over the bug list. Authentication is merely for accounting, not security.

Multi user, authenticated, roles, database store:
A medium sized team (10 - 20) of hobbyist developers (probably OSS), with a designated project lead.


At this point, I really don't have much interest in being useful for anything larger than a small team of hobbyists who are also friends and thusly trust each other. There are plenty of bug tracking solutions for medium sized OSS teams (in particular, Bugzilla comes to mind). The scope of this project is specifically to be a simple bug tracking system. A medium sized team will need more bug tracking features than I intend to include in this project. For that reason, I doubt few medium sized teams will use LittleBugz, even if I provide the User authentication, roles, and database support that they would need.

Up to this point, I had been building LittleBugz on top of SQL Server 2005. I think that's too much of an obfuscation now. I don't expect beginners to be able to handle setting up SQL Server 2005 Express Edition with the proper security settings. As far as databases go, it's not that difficult to do, but as far as beginners go, it's really a chore. For a single-man team, it offers nothing, and for a small team it doesn't offer anything that could not be achieved in other ways. By elliminating support for a database store, I will simplify the project significantly.

Project and Bug definitions will be stored in an XML file. The developers will be free to figure out their own strategy for sharing that XML file. The suggested method will be to add the XML file to source control and to use file merging to stay up to date on bugs created by individual developers. Bugs and projects will be ID'd with GUIDs to ensure there are no collisions between new bugs during file merges.

Roles have no use to a single-man team. I don't think a small team of friends are going to worry about project roles. Of all the small teams I've been involved in, control over work items hasn't been an issue. The only time a concept of "project role" came in to play was during decisions involving project features and project scope. That's merely a political distinction at that point, and up to being handled by the team itself.

Authentication has no use to a single-man team. Because of the trust level between a small team, authorization has no use in a smal team. Authentication, however, is desirable, to keep a record of changes. The project can then assume that authorization is handled de facto by the source control system. If a user has access to the source code, why not give them access to the bug list, too? At this point in time, LittleBugz has full authentication with hashed passwords. Passwords are going to be removed, they just aren't necessary.

Okay, there we go. This will greatly simplify the use of the project. I can elliminate any need for a "use mode" wizard now. When the application starts for the first time, the user will enter their name. This name will then be automatically added to every bug that that user creates. Since the multi-user aspect is essentially handled by external tools, their really is no need to even track users at all -- it just becomes an extra field on the Bug itself.

Should have done this from the start.

0
Sign in to follow this  
Followers 0


0 Comments


There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now