> > Voyager did not. It kinda relies on an Amiga being there for certain > > proprietary tools, includes for custom built tools, assigns.. it's a > > messy mess IMO and it's not worth cleaning it up. And there is no gcc > > cross compiler for x86 Amithlon that runs under AmigaOS or MorphOS. > > 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 haven't looked at Aminet in about 6 months. Maybe there is a tool for it. Huzzah if there is :) > So, cleaning up the needed tools is not worth the effort, at > least for the moment? Not while we have Amigas and Pegasoses (Pegasii? :) to build with. > 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 :) > Heh, a gzillion times :-) Well, the proof is in the pudding, and V's > JS works in far more places that AWeb's or IB's. I don't have access > to IB's new version (beta, alpha, or otherwise), so I cannot compare > with future offerings. 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. 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. > > > Yup, and so does an 8meg AGA/ECS amiga. At least for web-browsing. > > > > That doesn't stop people trying. And whining. > > Well, either the minimum specs have to be upped or a blanket "settings > configuration" needs to be made for those people. Although, I'm still > 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. 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? -- Matt Sealey <[EMAIL PROTECTED]>
