|
|
|
| LIB SDL and ClanLIB |
|
Oscar Giner
Member #2,207
April 2002
 |
Quote: The problem with mailing lists is not only are they annoying as all heck, they have the tendency to be so unreadable, so unintuitive, you spend more time looking for infromation that getting the information you want!
You just need a proper mail client. I use Pegasus Mail, and it can order the messages like in a forum. I attach an small screenshot so you can see -- |
|
Carrus85
Member #2,633
August 2002
 |
Hmm... interesting Oscar. Maybe there is value on mailing lists! I'm dumb!. Okay, if plucky insists on finding a team, lets start the team! I'm in. Anyone else going to take up this charge?
|
|
Rash
Member #2,374
May 2002
 |
Quote: Then you nominate a leader and set up a vote or something. In the meantime, we'll be making a wishlist, thank you. That doesn't change the fact that you need to set up some kind of Allegro development "government" as soon as possible. |
|
X-G
Member #856
December 2000
 |
Plucky: My point is that it's too early to do code. We hardly even have a wishlist or a new dictator; this is no time to discuss implementation or actual code. Anyway, I'd help out, but not if that means I have to start digging through mailing lists. -- |
|
Carrus85
Member #2,633
August 2002
|
Personally, I say screw the mailing lists. We have tons of information in this thread on what we want. Lets just get a diagram/design document going so we know where we are headed before we jump the gun and go. The mailing lists may be a good place to start for "ideas," But they are by no means where we should be turning for every little detail, judging by the number of people that dislike them. Lets start by starting simple: Figure out a portable way that we are going to use file input, that will handle endian-ness, and maybe VFS... I have a dia diagram of what I was thinking of, sorta...
|
|
Plucky
Member #1,346
May 2001
 |
I never said "start coding", though I used "coding" as an example of doing real work. I did say you need a team of sorts before you get started with anything. Of course the team could consist of one person. Though we should be wary of those giving advice/suggestions when those people (like me) have little or no stake in the project, I'll suggest: Note that there should be a lot of learning first before the team gets started even with a design document (unless the team members are already quite knowledgeable.) This is a very difficult undertaking. Which is why I have no interest in helping out other than to give suspect advice. |
|
Carrus85
Member #2,633
August 2002
|
okay, so first things first, get the team going. I'll join, although I don't know what I will do as of yet. Maybe someone could start up a new thread to see some of the interest and to form a list of who is going to help? EDIT: fixed some grammer crap
|
|
Kitty Cat
Member #2,815
October 2002
 |
You do realize, of course, that since it's a completely new project, the code you start with, will be redone later, right? There's already been some design decision on the sound API, as well as some basic design stuff on the system API. Start with that, and as things progress, change it. The code you write now is not going to be set in stone for goodness sake, so why fear you'll screw it up? -- |
|
Billybob
Member #3,136
January 2003
|
Is this the longest thread ever? I mean, it's on page 12. It jumped like 3 pages today.(for default settings, btw).
|
|
23yrold3yrold
Member #1,134
March 2001
 |
Yes. Can we hit 300 before a) it gets locked or b) someone actually puts their code where their mouth is? -- |
|
X-G
Member #856
December 2000
|
Don't threads get auto-locked or something? Or is it just the Hand of God/Our Benevolent Leader that does that? Anyway, if we're going to coordinate things we'd better start by finding out what we've got already. Can someone more familiar with current A5 development sum things up for us? I'm talking code-wise, design-wise, and who-does-what-wise. -- |
|
Bob
Free Market Evangelist
September 2000
 |
Quote: Anyway, if we're going to coordinate things we'd better start by finding out what we've got already. Can someone more familiar with current A5 development sum things up for us? I'm talking code-wise, design-wise, and who-does-what-wise. I will. I'll start a new thread on that. -- |
|
MiquelFire
Member #3,110
January 2003
 |
Matt closes them. Mostly because according to his logic, by the time a thread hits that points, it's gone way off topic (Then again... Allegro 5 is off topic here if you think about it --- |
|
nonnus29
Member #2,606
August 2002
 |
Quote: This is a very difficult undertaking. Which is why I have no interest in helping out other than to give suspect advice. I'll second that. I was thinking a good learning exercise/thought experiment would be to consider this question: Quote: If I were making an Allegro like game library from scratch, where would I start? What would I do? This is what I came up with: 1. Learn how to handle windowing/fullscreen on multiple platforms (Linux,Win,MacosX) That would get you a start on a crossplatform game library. |
|
|
|
