> > > > While I may be wrong, I could have sworn that this file, > > "x86-ami-bin.lha" were the x86 developer gcc files to crosscompile > > with (aminet). Heh, proprietary mess.... sounds like my computer > > room! > > I need some proprietary cable tie-backs, velcro and sticky tape for > mine :)
I'm considering large hooks in the ceiling :-P > I haven't looked at Aminet in about 6 months. Maybe there is a tool > for it. Huzzah if there is :) Filename Directory Size Age Description x86-ami-bin.lha dev/gcc 2.8M 17 Binutils v2.9.1 - Amithlon x86 binutils (68k hosted) x86-ami-gcc.lha dev/gcc 3.8M 17 GCC v2.95.3 - Amithlon x86 cross compiler (68k hosted) Thar be tha' files! (shhhh, not mentioning where that was cut 'n pasted from) > Not while we have Amigas and Pegasoses (Pegasii? :) to build with. 8-) > > maybe?) PostScript, now that brings back nightmares of late night > > coding excursions. > > NOOO!!! DON'T MENTION THAT! People will be reminded about the lack > of printing support. Whooops.. maybe that was worse :) Hahaha! Well, before I can complain about V's printing issues, I have to figure out how to get Amithlon to use my USB printer... Some advice: don't use a combination of COBOL and Perl to write a PS interpreter... It causes leperacy. > Well right now I'm wondering how I can improve V's JS without a running > copy of Voyager. There is stuff I half finished and plenty of stupid > and lame missing parts from the JS specs I can implement. It's sitting > and wondering what to do to do it that is the issue. Steal someone else's? 8-) Run UAE for Unix/Linux? you've got me there, I don't see how you do much of the things you do without actually running the stuff on the machine it's designed for! > I would really like to implement one or two cool JS features but then > they'd require someone to walk the code with me and explain where I can > add things. How about "Server-Death-Ray," a built in function that destroys any server that requires one to use IE? What?!!? I don't mean crashing it, or erasing data, but making the thing go "BOOM" :-) Helping with JS is something above my capabilities, ATM. I could write some nifty ARexx tie-ins, but someone would have to have an idea of what a nifty tie-in is. Like, if someone made the page-link (inside the popup) go to a specific ARexx script, I could make the script :-) > > partial to just upping the specs :-) "Are you running V on an ECS > > 8Meg system? Too bad, it's not supported, goodbye." 8-) > > Okay. I have an idea. > > I implement family support. You get nicer looking fonts if you use > ttf.library. Maybe, just maybe, I will implement some kind of mapping > codepages from webpage-specified to browser-default, or maybe let you > specify a font for different encodings (so for instance you could have > ArialPolish for iso-8859-2 - just like a user here does). > > Then that is it. Amiga 68k font support dead. I take it you mean the font system supplied with AmigaOS? You don't mean the processer itself do you? Seems to me the guy with a 75Mhz 060 and a ton of ram could deal with fonts... > The rest is PPC, x86, and whatever-else specific, since it will require > a great deal more snazzy stuff than AmigaOS 3.1 generally runs on. > > Sound good? Oh, I think I see what you mean. To have font support, you must have PPC/x86/etc. That *could* work; however, before jumping off of the deep end... You may want to check with the guy working on the coldfire accl ( http://www.cdtv.org.uk/coldfire/ ). If the thing is slated to be produced, then dropping 68k support may not be a good idea afterall. I don't know if this project is "hopeful," "wishful thinking," or "going to happen." I do not know the validity of this project, but it seems serious. -- -- Regards, Dave 'Targhan' Crawford
