Over the past 12 years, ignition has been developed by me (Axel D?rfler/ pinc Software), and Alexander Bartz, who accompanied me in the first few years, but has left the Amiga a long time ago. Due to limited time, I came to the conclusion that trying to create an open source project around ignition is the best option to ensure its future existence and maintenance. Now, I finally found the time to do so.
I hope that, over time, a few people will find interest in further developing ignition. I plan to stay around, and make sure to answer any questions that pop up, and eventually submit a patch myself.
Oops, yes Capehill is right I wasn't asking Rogue, I just did not pay attention. Of course Rogue has nothing to do with this... Unless he wants to do it in his spare time of course
@Valiant
Ok, so it seems you are interested in doing the OS 4 port aren't you ? Subversion is definitively the best choice has you'll be able to easily track difference against the main repository, which will enable you to do a patch that the author might be able to apply to the main source tree...
Subversion (SVN in short) is really easy to use and is some sort of standard out there, you'll be able to find many tutorials on the Internet. Just a few commands will be needed by you : "svn update" to update your current sandbox against the repository, "svn status" to know which files you have modified "svn diff" (with or without files) to have a diff output of your sandbox against the repository
And that's all, if you would have write access to the repository you'll be able to also use "svn commit" to upload your modifications....
Ok, once it has an OS4 port, then what? Will there be anyone to develop it further? Don't forget that we have other open-source projects like AWeb and JAmiga that have been pretty stagnant for years now. It would be a shame to see the same happen to Ignition.
Fact is that today Ignition has facility to crash under OS4, so at least doing an OS4 port might give us the opportunity to use it. Also a stagnant working project is better than a developped non working project !!
I am sorry, but what does the availability of an OS 4.1 SDK has to do with that?
Just that I don't remember having had that problem when I ran it before, so I presumed the changes from OS4.0 to OS4.1 were something to do with it. rtg.library is a kickstart component, and I just surmised, rightly or wrongly, that compiling with the current SDK might fix the DSI error. Sorry if I was mistaken.
Just that I don't remember having had that problem when I ran it before, so I presumed the changes from OS4.0 to OS4.1 were something to do with it.
Either you or me should not be remembering correctly but for me ignition was a bit unstable before under OS4.0.
Quote:
rtg.library is a kickstart component, and I just surmised, rightly or wrongly, that compiling with the current SDK might fix the DSI error. Sorry if I was mistaken.
IIRC rtg.library is *not* a kickstart component, is it ? If you are trying to run a previously installed version of ignition, please verify if that's not a problem of rtg.library that memorized an old screenmode ID that now under your OS 4.1 install does not exists anymore and thus fails to open (with no error check in the code assuming a screenmode saved will always exists afterward).
IIRC rtg.library is *not* a kickstart component, is it ?
It's in the kickstart drawer, it's not a .kmod file, but it's in there.
Quote:
If you are trying to run a previously installed version of ignition, please verify if that's not a problem of rtg.library that memorized an old screenmode ID that now under your OS 4.1 install does not exists anymore and thus fails to open (with no error check in the code assuming a screenmode saved will always exists afterward).
I am not being thick here but I did not really understand that, but I'll see if ignition is launched on it's own screen or not, and report back.
abalaban wrote: Fact is that today Ignition has facility to crash under OS4, so at least doing an OS4 port might give us the opportunity to use it. Also a stagnant working project is better than a developped non working project !!
It worked for me until I updated to OS4.1. I had to disable the JIT in Compatibility Prefs to get it to go, but it worked fine. Now, with OS4.1 even disabling the JIT doesn't help. It is a shame, it was a good program.
IIRC rtg.library is *not* a kickstart component, is it ?
It's in the kickstart drawer, it's not a .kmod file, but it's in there.
Oh, sorry, never heard about this library before, in fact I mixed with rtgmaster
Quote:
Quote:
If you are trying to run a previously installed version of ignition, please verify if that's not a problem of rtg.library that memorized an old screenmode ID that now under your OS 4.1 install does not exists anymore and thus fails to open (with no error check in the code assuming a screenmode saved will always exists afterward).
I am not being thick here but I did not really understand that, but I'll see if ignition is launched on it's own screen or not, and report back.
What I meant was something I experienced once with a program using rtgmaster.library. This library memorized the screenmode ID in a file in the program's drawer, when I switched to update 4 (or was it final) when screenmode can be configured via monitor's tooltypes all my screenmodes IDs changed, the memorized screenmode wasn't valid anymore and the program was crashing at startup (because the programmer did assume that a memorized screenmode ID would always exist, and he did not bother to check if screen was opened). Anyway as we are not talking about rtgmaster here, I guess there is no point in discussing this... Sorry for my mistake.