Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
I have a card game programmed in Qt ( And intend to stick with the language ), and it has come time to create the UI. I have almost no idea how to move forward, but some of the things I want to visually achieve are being able to flip a card over, and having it move from one pile to another.
I started thinking though; Card Games are basically two dimentional applications, but if I want those animations, should I really be considering doing its UI in 3D instead? The problem is I that do not have any experience creating 2d or 3d engines and so I have no idea what to expect in terms of work load or future proofing.
- I am concerned that if I do it in 2D, that it may end up being a lot more work to animate the cards in the way I want.
- Similarly I am concerned that 3D is too much, in the way that developing a sudoku game in 3D is overkill.
- I am a one person team, and so this has to be practical for me to achieve, and I just do not know what kind of workload to expect from either approach.
- The game will be similar to Magic the Gather, or Pokemon, and so its mechanics will be a bit more complex.
- Is programming a card game in 3D generally overkill?
- Does programming it in 3D almost certainly guarantee that more work will need to be done?
- What code tends to be more elegant and intuitive to read and follow: 2D or 3D based engines?
- Are any of the common card games, like Solitaire on Windows programmed in 3D?