Jump to content

  • Log In with Google      Sign In   
  • Create Account


landagen

Member Since 24 Jan 2007
Offline Last Active May 27 2013 02:48 PM
-----

Posts I've Made

In Topic: Is this a bad programming paradigm?

15 April 2013 - 12:52 PM

I am not sure why you would ever want to do this.  It is like building a car with a brake pedal, but then instead of braking when you press it, the car's check engine light comes on as you barrel through a busy intersection. 


In Topic: What game mechanics do I start coding first?

12 April 2013 - 01:01 PM

I think if you evalute your project closely, you should be able to determine what is best to start with.  Making a game is an iterative process.  It's not like you tackle the fighting system and then move on and never touch it again. You will visit and revisit that piece.  What is next for you?  What can you do that does not have any missing dependencies?  What are some of the biggest questions that need to be answered?  Some questions require experimentation to answer.  If that is the case, then start experimenting as soon as you can so that those questions can be answered.  Always try to find the shortest and clearest route to the destination you are trying to acheive.


In Topic: Classifieds Projects lacking

12 April 2013 - 12:45 PM

I agree that the classifieds is certainly not where I would put it.  I more mean the replacement to the Help Wanted forums is the classifieds and that it is lacking in what I believe is important.  Not to say that the classifieds should be morphed into what I was imagining.  I am glad to hear that there is interest in doing something like that and I hope it comes sooner rather than later.  I believe it can really spur a sense of community here.  The recent articles are definitely a good start to increasing game development information and I hope that it continues that way.   


In Topic: GDNet Official source code repository

12 April 2013 - 12:36 PM

I don't think articles and "source code repository" are mutually exclusive.  As a matter of fact, I was imagining they would work together.  I just don't want to have to copy and paste code and put it all back together in some files from articles.  Plus typically, articles are only going to be written with one language and it is doubtful someone will go back and convert the code to another language.

 

A) As I mentioned, have either multiple repositories (one for each language) or have a folder for each language.  I would imagine that there would be people who would duplicate solutions across multiple languages depending on their language of choice so I don't think that would be a problem.

 

B)  As far as who is in charge of this source code repository I would do something like the Crossbones group that was recently created.  Just get people to volunteer and then eliminate those who are not doing a good job.  Let everyone contribute, but just have a group to review the contributions and commit them. 

 

C)  I don't think anyone can answer that.  How did they answer "Do they have time to write articles?".  You just need to try and see what happens.  What is the worst case scenario?  You had to setup a repository and some permissions and it just sits idle.  Most likely though you will have a repository of solutions that people can study, adapt, and integrate into their own projects.

 

D)  If you are talking about the engine part, then I would say that would have to be investigated to see if there would be any type of benefit.  There may not be.  But I would like to see a simplified engine that doesn't have all of the latest features that is just designed to be kind of a learner engine.  It is designed to learn the concepts and pieces of how an engine can be put together following some emerging and standard concepts.  It should be simple and straightforward providing a lot of code documentation.  Articles themselves can link to the code repository to show an example.  As far as the other code samples/small solutions it would be different because frameworks are all about being totally encompassing.  There are very few frameworks that are out there that are just there to show a certain concept.  Most frameworks and engines are trying to be feature complete and have been tuned for various reasons.  Typically they are also not well documented and there is no articles associated with the different concepts that they implemented.  There is probably no articles on how the SceneManager in Ogre was developed and how it works and why they made the decisions they did.  It is also surrounded by a million other bits of code that someone has to dig through and understand just to understand the SceneManager concept. 

 

E)  Who is to say the recent article writing is going to live long?  Does that mean they should not try?  Again, I believe the repository should be linked to by the articles and that they should complement each other.  I don't believe an article is the only place to keep code snippets as they are doing currently.  I mean look at CodeProject.com.  They have code in the article, but they also include a download of the source code for the concept they covered. 


In Topic: Entity-Component Design Questions

08 April 2013 - 05:57 PM

Okay.  That makes sense.  So for performance critical systems avoid the iterating through entities over and over again while processing them.  Instead, opt to synchronize with an optimized format for that system and use that data instead.  


PARTNERS