On Thu, Dec 15, 2005 at 06:41:06PM -0800, Peter Naulls wrote: > > I've looked over the recent ArcEm work, and I'm quite impressed. I know > there's still a few rough edges, and we need to put together things like > a !Boot sequence that we can distribute with it. I'd therefore like to > do a new release sometime in January. >
I'm not too keen to commit to a specific timeframe at the moment, perhaps it might be more wise to list the things that would be good to complete for the next release, and release when we're ready. This is a list of the things that I would want before a new release, feel free to tack things onto this list. The ones marked * are ones I'm in the middle of 1) Find a RISC OS port maintainer, or failing that let that platform skip this release 2) Port Daniel Clarkes pallette fix to http://cvs.sourceforge.net/viewcvs.py/arcem/arcem/X/DispKbd.c?r1=1.50&r2=1.51 to macos x and windows 3*) Finish off the Windows support for modes larger than 800x600 3a) Hassle mdales to try it for macos :) 4) Verify the (c) on Daniel Clarkes Mouse wheel module and check in to a directory in the support_modules heirachy. Then attempt to add support to the Windows and Macos x builds. 5*) Check in the ArcemModes module to a directory in the support_modules directory. This allows compatibilty with Virtual A5000 larger and higher colour depth screen modes. (1024x768x16cols, 800x600x256cols etc) 6) Update the website to be more welcoming, add a few screenshots so people can easily see that it works, accept bugs, update the manual, make sure a users mailing is setup. 7) Find a src of roms for it, as Peter N mentioned. 8) Create a base HD image, as Peter N mentioned. 9) Test, verify we are at least as compatible as version 1.0 > For the !Boot sequence, I believe Peter has something available that we > can look at - if not, one can easily be created - although perhaps we > ought to clarify the instances under which we can distribute it. > I don't have anything to hand but I'll see if I can knock one up quickly. I'm thinking of a 64 MB ST506 image with the following. Please add more ideas to the list. Also I'll add a version number to the disc image, so if we think of more in future people will know if to update. 1) Risc os 3 universal boot. [1] 2) Castle 32bit shared CLibs and toolbox updates [2] 3) Network parts [3] but not the toolbox or newer bits from 1 or 2 4) Zap or Stronged or both 5) !Elite !!! [1] http://acorn.riscos.com/acornftp.htm [2] http://www.iyonix.com/32bit/ [3] http://www.castle.org.uk/oregano/orgsupp.htm#boot > For the RISC OS 3.1 ROM, I will create a script which will > download and extract it from the support files from !A310Em, thereby > side-stepping copyright issues. This will allow a degree of instant > gratification on Unix systems so people can just type "make" and have it > all work, which will considerably lower the barrier to people trying it > out. > It's a reasonable idea, I've done a bit of prodding and it seems likely the (c) for 3.1 resides not with Castle or ROL but it was an unsold asset of Acorn that currntly resides with the Morgan Stanley Dean Witter holding company that bought Acorn. That's a company with a lot of lawyers but probably no idea that they own it. > For the future, I'm keen to see us use QEMU, perhaps integrating into > it. Its JIT will allow at least RiscPC speed on modern hardware. We'll > have to add 26-bit mode and move the hardware support to QEMU of course > - challenging, but hopefully no more than an engineering exercise. Oh long term plans, how theoretical 8) Peter -- Peter Howkins [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
