RomRaider

Alright, looks like we're about ready for another release. Its been a while! First off, I want to make sure there's nothing left unfinished that'll hold us up. I'll also need a list of features to add to the release notes from each developer who has contributed since the last release. Finally, if you can help me out with which libraries have been added/changed and any OS sensitivities so I can make the appropriate changes to the izPack installer.

I don't know if Drees has had a chance to look at the memory leak but it is still pretty significant. Same issue - refreshing rom or open/close rom. On my machine (1 gig of ram), with the latest test release (v747) I can refresh a rom 14 times before it slows to a crawl.

I'm not saying this isn't an issue, as I agree it needs to be sorted out before too long, but the problem is much improved since the previous release and RomRaider is still officially in beta. Basically I don't think it should be a showstopper which prevents us from making a release.

No offense to any of the other developers, but with the exception of the logger and the definition releases, general development on RomRaider has slowed significantly over the last 3-6 months. We need to get a release out to promote interest again and hopefully rejuvenate RomRaider's progression towards world domination

Just figured that if maybe it was an easy fix it could be looked at. If not, then go ahead with the release.

Alright, I just talked with drees and he said he made some fixes but some new leaks are showing up in the latest test releases. He said its at least no worse than 0.4.1 though, so we should be good (enough) on that front.

Hmmm...a sample bash script and instructions on how to modify it for your environment would be a nice addition for me and the two other people who use linux with RomRaider. An absolute pathed tarball, deb/rpm/ebuild/etc would make life easier for us folks too. I can write up instructions if you like, and at least make a deb package...maybe get RomRaider added to gutsy universe?

BTW, I wanted to start poking around the code and see if I can make any useful additions...any good places to point a java newb on getting started (I do know a few other languages, some even object oriented!)? My brother in law is a CDE bug fixer (yes, some people still use it) at Sun Mircosystems, but he doesn't seem to know much outside of C, so you would think that would be a big help with learning Java, but it isn't.

-Rich

I'll say it again, for the hundredth time.. hell.. probably thousandth time. I've got a framework for the new GUI ready to be worked on. UTEC support is very close. I need someone to implement the existing ROM map editing functionality in the new framework. I need that same person to help look over and modify said framework!

Someone agreed to start the ECU manager for the realtime maps. Where is he? Same person was to also help use and define GUI framework.

Linux dev and mac dev? We might need someone dedicated for each OS. I can do mac, linux is no longer my laptop OS.

List goes on....

Who is driving all the new development? I don't have time to coordinate things. I'll continue holding off on new development until we get a roadmap define and buy in from all the devs. There hasn't been much dev coordination or community lately.




Its time to make this a real project.

Lets get those bugs defined and assigned:
http://www.bugzilla.org/

Hows about a issue tracker and software lifecycle suite?
http://www.redmine.org/

Whos going to drive this?

<end soapbox>

I've never seen redmine.org. If its not blocked at work I should have time to look in to it today.

I may have another update of the ecu definitions here soon, so you may want to hold off on the new release for just a little bit. I'm developing a tool to compare the ecu definitions against what is called for in each individual rom (axis size/number of elements/data type, map type (16bit), static step/start values, relative positions of similar 1d parameters, tables not defined in the base, etc.). This should reveal any errors, to the degree possible, in the definitions. Hopefully should wrap things up this week.

If it weren't for work, this stuff would be done

Yea, I'm still on the "EcuManager". It turns out that I really need the ECU I/O solid which means a common mechanism that coordinates the requests. Though I could probably just assume that calls will be made serially, I would rather not. Thus, I'm introducing a "DataSource" interface that will serve as the mediator for ECU I/O. My current implementations are completely thread-safe and when I'm finished with the manager, we should be able to log at the same time we set values if we were so inclined. The main reason I feel this is necessary is because RomRaider hasn't before needed to patch the ECU and I imagine features in the future will incrementally rely on a solid I/O foundation. I can offer more details upon request.

All of this is parallel to the GUI development. The way the UI will consume the "DataSource" piece is something like the following:

byte[] data = SerialPortDataSource.getInstance().read(new FragmentDescription(0x020000, 16));

So you can see it doesn't have any UI dependencies. That's what I meant when I said we could plug this into any UI with minimal intrusion. I would estimate that it would take only a few hours to plug it into the existing UI.

If no one has yet talked about stepping up to the task of the new UI, then I think it's safe to assume that you could work on it w/o duplicating any effort. If I didn't have the RamTune stuff, I'd be on it.

J

^^ Awesome, and don't take my bitch session as a lack of thanks for what you're doing. You've really thought things through. NICE!

I've just commited an additional small fix for the memory leak which should help it some more - not sure if it's gone yet though.

Here are the release details for my part:

Added jars: log4j-1.2.14.jar

Added dirs: /plugins

Editor Changes:
* Colorize performance fixes
* Auto-update table colorization on Copy and paste
* Window location/size bug fixes
* RamTune test application added for testing RAM reads and writes and ecu inits

Logger Changes:
* Start/stop file logging button added
* LC-1 integration
* Alpha quality AEM UEGO integration
* Logger command line launcher
* Window location/size bug fixes
* Improved plugin connection handling
* Reset ECU
* Improved debug logging
* Improved graphing including combined graph

There's probably more that I can't think of at the moment.

double post...

Alright, tomorrow I'll take some time to update the izPack installer and hopefully get a test build ready. Tgui, can you take a look at the izPack stuff and maybe make some shortcuts for Linux users?

I've been working on an anonymous ftp uploads that integrate with the current attachment. Once its finished you can just upload via ftp and select the file from a list when you go to post it. This way we'll be able to upload bigger files without phpbb and http in general being finnicky. I'm about half done now but I'm a bit stuck at the moment.

sorry to bug about this, but will this release have launch control?