Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

fawtytoo

Members
  • Content count

    51
  • Joined

  • Last visited

About fawtytoo

  • Rank
    Mini-Member
  1. fawtytoo

    A new port: Omega

    It seems you guys have better things to talk about. I won't be posting to this thread any further. For those that are interested, watch the website.
  2. fawtytoo

    A new port: Omega

    That's very intuitive of you. I have no wish to stay a bus driver for the rest of my life, but it currently pays better than being a programmer. I'm not a mainstream kind of guy. Not because I'm stubborn, but I won't learn anything if I do it the "easy way", or using "what's already there". Hell, if I was going to do it the easy way, I wouldn't be creating this port. There's plenty already out there. I have many reasons why I'm doing it the way I am. I just didn't realise I have to explain it.
  3. fawtytoo

    A new port: Omega

    The way you read "religiously" is not quite right. Manual? I don't have a problem with that. Time consuming? A couple of minutes, which I can live with. Human error? I don't jump straight in to a new version. I have plenty of backups, including on my website. There's a copy of everything somewhere. Offended? No. Annoyed that the thread was derailed? Yes. But there are plenty of comments (not just fraggle) here also that show an assuming attitude. Assuming that I'm not using version control. Assuming I'm not backing up. Now. Back to the port.
  4. fawtytoo

    A new port: Omega

    Thanks. I'm thinking of doing 2 separate ports as the temptation to add new stuff is overwhelming. One is to continue adding new features/support and create as I see fit/ others suggestions. The other will be a fixed linuxdoom. "Fixed" defined here is: coding bugs/errors without breaking/changing the gameplay/demos, improving the code for efficiency/better methods, and to add missing features present in the DOS versions.
  5. fawtytoo

    A new port: Omega

    For the umpteenth time (or maybe the first depending on how you view it): My code is not a bunch of files that I occasionally make backups of. I religiously make a copy of the project and make changes to that copy only. That copy gets a revision number. When I wish to make more changes, I make another copy and repeat the process. I have separate copies of my project for each revision. Hence, the patch files: they show the difference between, not just each revision, but each revision copy. It's not random or occasional, it's religiously done. There may be little evidence on my web site of this, but I am using version control. I can track every change to a revision easily, using both the changelog and the patch files. If someone gave me a patch for a specific revision, I can keep it with that revision only. Same with branching. My system is crude, perhaps a bit time consuming, but it does have version control. Perhaps you are not the only one who is explaining poorly. But the reason I'm not changing is because I'm already doing it. Just not some where you can see.
  6. fawtytoo

    A new port: Omega

    See? These are the digs I was referring to.
  7. fawtytoo

    A new port: Omega

    Shame you feel that way. A programmers merit is also based on their work. It's not like I'm not tracking it at all, or have no backups.
  8. fawtytoo

    A new port: Omega

    I've already done that. My original idea stands, but now I'll maintain 2 ports. One: simply a fixed linuxdoom, and two: my own port that I can do whatever I want with.
  9. fawtytoo

    A new port: Omega

    How do you know I'm not making backups or diffs? I've been doing exactly that from the start. But who benefits from using Git or SVN? Me or you? I wouldn't.
  10. fawtytoo

    A new port: Omega

    The original idea was not necessarily to create a new port, but to provide a 'fixed' linuxdoom source code. Apart from bug fixing, things like midi doesn't work. Some of the command line parameters are a little difficult to use or didn't work properly/as expected. 24 bit colour support. 64 bit architecture support. It's not so much brainstorming as describing it.
  11. fawtytoo

    A new port: Omega

    Yes, I think that's what I meant to say. The point was to simply bring the original Doom source code 'up to date'. By that, I mean to fix any obvious bugs/error messages, and to create something more flexible, which is where the GAMEID and '.lmp=' comes in. Might make a better base for others to use. Just to take the guess work out of what wad you're using. Open to improvement. That's very specific. Would you have a use for that? Perhaps an example? And wouldn't that create a very long command line? I don't want to over-complicate things.
  12. fawtytoo

    A new port: Omega

    Out of all the feedback thus far, hardly anything encouraging about the game. Just one big dig at the web site and version control. Here's me trying to make a go at this, and give others a new Doom port, and all you've done is patronize me.
  13. fawtytoo

    A new port: Omega

    Because: I'm also learning PHP. This is the perfect excuse to see what I can do. And, I already said this web site is paid for. But not specially for this. It has a generic use, even if you can't see it. Plus, it gives me something to do. I don't consider it a hassle.
  14. fawtytoo

    A new port: Omega

    I could improve the layout so it's easier to follow. Add a means to browse the code, and download. And improve readability of revisions showing associated patches. The web site is written in PHP, so making it more interactive can be done.
  15. fawtytoo

    A new port: Omega

    I drive a bus without a seatbelt. And yeah, shit happens. But I'm still doing it. Why can't I host it myself? If you have suggestions to improve the site or version control, please do. But I don't see why I MUST use Git or SVN. I have plenty of copies of every single revision backed up. It's all safe.
×