New Basilisk II information page!
Moderators: Cat_7, Ronald P. Regensburg
New Basilisk II information page!
I made a new Basilisk II information page!
Wow!
I wrote a few paragraphs about the emulator. And I fixed up all the broken links to point to archive.org versions.
Anyone have any suggestions? Some new links or some changes to the descriptions?
And I could use:
a copy of marc hoffman's pdf guide to upload
a couple of screenshots
You can email these to me: mgoodine@gmail.com if you want to help...
(more emulator pages coming soon!)
Wow!
I wrote a few paragraphs about the emulator. And I fixed up all the broken links to point to archive.org versions.
Anyone have any suggestions? Some new links or some changes to the descriptions?
And I could use:
a copy of marc hoffman's pdf guide to upload
a couple of screenshots
You can email these to me: mgoodine@gmail.com if you want to help...
(more emulator pages coming soon!)
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
That is in Opera for Windows? On MacOSX it looks the same in Firefox 3.0.1 and Opera 9.51. What is not right in Opera? In Safari 3.1.2 the list of Files does not look right. Can probably be corrected (in the source) by placing a space between "Basilisk II (without JIT)" and "</a>(Dead Link - check the forums)".ClockWise wrote:(PS: doesn't look nice in OPERA. Fuck.)
Edit: Of course I meant a space between ""Basilisk II (without JIT)</a>" and "(Dead Link - check the forums)".
Of course I forgot to post the link so people "not in the know" could find it. It is over here:
http://emaculation.com/basilisk.php
I don't have Opera installed right now, but I was told that the navigation sidebar gets messed up... it shows up at the bottom of the page rather than neatly on the right hand side.
Do you see the sidebar okay?
http://emaculation.com/basilisk.php
I don't have Opera installed right now, but I was told that the navigation sidebar gets messed up... it shows up at the bottom of the page rather than neatly on the right hand side.
Do you see the sidebar okay?
Ps: http://emaculation.com/basilisktest.php
That is a wider version. As soon as I can find some help with the graphics (I need to make that 'pill' that contains the word "Basilisk II" bigger) I will get that online for all the pages.
That is a wider version. As soon as I can find some help with the graphics (I need to make that 'pill' that contains the word "Basilisk II" bigger) I will get that online for all the pages.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Don't see the basilisk build in my e-mail. To which address did you send it?
The file list should look a bit better now. Does it show up nicely in Safari?
I installed Opera on my work machine and the sidebar looks fine. Not sure what was specific about Stephen's setup that made it not work for him.
Going to concentrate now on updating the other pages into the current design. When I get tired of that I will try to make the wider design work visually and put the information into that template.
The file list should look a bit better now. Does it show up nicely in Safari?
I installed Opera on my work machine and the sidebar looks fine. Not sure what was specific about Stephen's setup that made it not work for him.
Going to concentrate now on updating the other pages into the current design. When I get tired of that I will try to make the wider design work visually and put the information into that template.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
In the 'Required Reading' and 'Files' lists (tables really, rather than lists) the separate.gif image is now too short for the new width.
Also, the tables are incorrectly coded with respect to these lines, table cells are inserted outside table rows, between the surrounding table rows:
</TR>
<TD COLSPAN="3"><IMG SRC="images/separate.gif"></TD>
<TR>
should be:
</TR>
<TR>
<TD COLSPAN="3"><IMG SRC="images/separate.gif"></TD>
</TR>
<TR>
In the generated page there are three <body> tags while there should be only one. If the page is generated from different files, only the file that provides the top of the page should contain the <body> tag and only the file that provides the bottom of the page should contain the closing </body> tag.
These are only a few faults I see at first glance, there may be more. Don't you have software that can signal or correct such faults? Although the page looks OK in the browsers I tried, faults like that will inevitably cause display problems in some browsers.
And again: Put a space between ""Basilisk II (without JIT)</a>" and "(Dead Link - check the forums)".
(BTW: I liked the previous narrower version better.)
Also, the tables are incorrectly coded with respect to these lines, table cells are inserted outside table rows, between the surrounding table rows:
</TR>
<TD COLSPAN="3"><IMG SRC="images/separate.gif"></TD>
<TR>
should be:
</TR>
<TR>
<TD COLSPAN="3"><IMG SRC="images/separate.gif"></TD>
</TR>
<TR>
In the generated page there are three <body> tags while there should be only one. If the page is generated from different files, only the file that provides the top of the page should contain the <body> tag and only the file that provides the bottom of the page should contain the closing </body> tag.
These are only a few faults I see at first glance, there may be more. Don't you have software that can signal or correct such faults? Although the page looks OK in the browsers I tried, faults like that will inevitably cause display problems in some browsers.
And again: Put a space between ""Basilisk II (without JIT)</a>" and "(Dead Link - check the forums)".
(BTW: I liked the previous narrower version better.)
Oh yeah. I spent like two minutes making the wider version and haven't looked at it since. I will get back to it sometime, since ocassionally people bug me about how the current version looks on their big monitors.
When I asked for input, I only really meant for the narrow version. That version is live on the main page.
I will fix up those errors that you mentioned in regard to the tables and to the body tags. I don't really have software that can point out errors. I haven't really written any html in about seven years... right now I'm modifying stuff that was written by someone else back in 2003.
When I asked for input, I only really meant for the narrow version. That version is live on the main page.
I will fix up those errors that you mentioned in regard to the tables and to the body tags. I don't really have software that can point out errors. I haven't really written any html in about seven years... right now I'm modifying stuff that was written by someone else back in 2003.
I fixed those two mistakes that you pointed out:
http://emaculation.com/basilisk.php
Do let me know if you see anything else. As I said, I'm sort of picking through some site design that is left-over from long ago...
http://emaculation.com/basilisk.php
Do let me know if you see anything else. As I said, I'm sort of picking through some site design that is left-over from long ago...
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
You are quick, these errors appear to be solved already.ClockWise wrote:I will fix up those errors that you mentioned in regard to the tables and to the body tags.
The page looks fine in Safari.
The html errors probably have been there for years. I never looked at the source before.right now I'm modifying stuff that was written by someone else back in 2003.
Thanks for the tips!
I just ran it through this thing: http://validator.w3.org/ but I don't really understand what it all means. I hope nothing is TOO critical.
I think the problem is that the page was designed for phpnuke back in 2002 and then Wordpress was shoved in a little while later. I don't want to use any content management system for the individual pages.
Anyways. Do let me know if you see anything else I can fix... it IS broken on the older version of Opera that Stephen prefers. I guess that people using old versions of Opera are a subset of a subset, but it's annoying....
I just ran it through this thing: http://validator.w3.org/ but I don't really understand what it all means. I hope nothing is TOO critical.
I think the problem is that the page was designed for phpnuke back in 2002 and then Wordpress was shoved in a little while later. I don't want to use any content management system for the individual pages.
Anyways. Do let me know if you see anything else I can fix... it IS broken on the older version of Opera that Stephen prefers. I guess that people using old versions of Opera are a subset of a subset, but it's annoying....
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
If you throw this page at W3C markup validation service, it reports 84 errors.
Some reported errors are strictly formal with regard to official specifications and will not cause problems, like the missing ALT attributes for IMG elements and BACKGROUND or HEIGHT attributes for TD elements that "do not exist" (which means that they are not part of html specifications) but will still be recognized by most browsers.
But other errors may cause problems, like P and TABLE elements where they are not allowed. Most of these errors are reported multiple times, so they are probably of a similar recurrent nature as the ones you solved with the table cells. I will have a look at it later when I have more time to study the validator report.
Some reported errors are strictly formal with regard to official specifications and will not cause problems, like the missing ALT attributes for IMG elements and BACKGROUND or HEIGHT attributes for TD elements that "do not exist" (which means that they are not part of html specifications) but will still be recognized by most browsers.
But other errors may cause problems, like P and TABLE elements where they are not allowed. Most of these errors are reported multiple times, so they are probably of a similar recurrent nature as the ones you solved with the table cells. I will have a look at it later when I have more time to study the validator report.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Thanks to Ronald Regensburg there is a very very valid Basilisk II info page now online.
http://www.emaculation.com/basilisk.php
The Executor page is cleaned up too. I'm going to try to do the vMac page tomorrow.
http://www.emaculation.com/basilisk.php
The Executor page is cleaned up too. I'm going to try to do the vMac page tomorrow.
-
- Expert User
- Posts: 868
- Joined: Sat Aug 30, 2003 4:15 pm
- Location: UK
- Contact:
I am not usually one for suggesting the use of CSS, but since the site already uses it, maybe we could make a new page with the content on, and then make some style sheets that make the page look like it does now, with the side bar displaying correctly and the 'pill' not appearing at the bottom of the page. Also, maybe use CSS to generate a wider version so the thinner version is default, but the user could switch to a wider version if desired.
I think I will look into how to make style sheets.
I think I will look into how to make style sheets.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
The site already uses CSS in a stylesheet for some aspects of its appearance.
Removing the "pill" at the bottom is easy. I left it there because I thought it was meant to be there.
I am fairly experienced in building websites that use a stylesheet only for lay-out and appearance. Rebuilding this site using xhtml strict and CSS only while keeping its present appearance would demand a more than average knowledge of CSS. I could probably do it, but I do not want to spend the amount of time and effort that it would take.
I demonstrated to ClockWise how to do a quick clean-up of the code to resolve the large amount of syntax errors. But the cleaned pages still contain a lot of non-functional code debris and some 'original' solutions to achieve a specific result.
An intermediate solution would be to maintain the table lay-out, get rid of most attributes and replace them with styles in the stylesheet (font styles, paragraph styles, body width, margins, paddings, table sizes, cell backgrounds and borders, etc. etc.). Still a considerable task.
Removing the "pill" at the bottom is easy. I left it there because I thought it was meant to be there.
I am fairly experienced in building websites that use a stylesheet only for lay-out and appearance. Rebuilding this site using xhtml strict and CSS only while keeping its present appearance would demand a more than average knowledge of CSS. I could probably do it, but I do not want to spend the amount of time and effort that it would take.
I demonstrated to ClockWise how to do a quick clean-up of the code to resolve the large amount of syntax errors. But the cleaned pages still contain a lot of non-functional code debris and some 'original' solutions to achieve a specific result.
An intermediate solution would be to maintain the table lay-out, get rid of most attributes and replace them with styles in the stylesheet (font styles, paragraph styles, body width, margins, paddings, table sizes, cell backgrounds and borders, etc. etc.). Still a considerable task.
-
- Expert User
- Posts: 868
- Joined: Sat Aug 30, 2003 4:15 pm
- Location: UK
- Contact:
I think the pill appears at the bottom because of the code for the sidebar. The menu code is obviously copied from the homepage and the version of the pill is the one with the little bit attached to the bottom which provides the space for a date, and is thus used on the homepage.
Maybe if we made use of the file which provides the sidebar to the homepage: http://www.emaculation.com/wp-content/t ... idebar.php
rather than just copying code from the homepage.
Edit: Making the pill longer would be quite easy to do.
Maybe if we made use of the file which provides the sidebar to the homepage: http://www.emaculation.com/wp-content/t ... idebar.php
rather than just copying code from the homepage.
Edit: Making the pill longer would be quite easy to do.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
The bubble below the pill can also easily removed.
ClockWise asked me to investigate deeper the way the pages, and especially the index page, are built. Somehow other pages appear to have been pasted together instead of generated like the index page. Better not make any lay-out changes till I have finished my investigation.
ClockWise asked me to investigate deeper the way the pages, and especially the index page, are built. Somehow other pages appear to have been pasted together instead of generated like the index page. Better not make any lay-out changes till I have finished my investigation.
I notice some of these older versions are missing from the new Basilisk II page at http://www.emaculation.com/doku.php/basilisk_ii .
I think I have a few older versions you might be missing, too. In particular, there was a "build 143" patch that was introduced to allow build 142 to run Escape Velocity. I also think I have an old JIT build that would run under Win9x.
I think I have a few older versions you might be missing, too. In particular, there was a "build 143" patch that was introduced to allow build 142 to run Escape Velocity. I also think I have an old JIT build that would run under Win9x.