Dear Kieran,
I would like to request for the new memory map frontend code to be made open source and published to GitHub so that the community can contribute features and fixes to it.
Sincerely,
ExE Boss
P.S.: I’m attaching the relevant Discord Server logs and quoting the relevant posts from the Memory Map Announcement Thread that led to the creation of this forum post (I would put them inside a <details>
element, but the forum doesn’t allow HTML5 ):
Mod edit: Moved the discord logs to pastebin.
Looks and feels pretty good, but why is the layout* handled using tables instead of CSS like my website or the VWF Dialogues Patch V1.2 Readme?
*Note: When I say layout, I mean why does <body>
contain a single <table>
element which is then used to lay out the entire page? It’s terrible for responsive design.
List of reasons why using <table>
s for design is terrible:
- css - Why not use tables for layout in HTML? - Stack Overflow
- Why you shouldn’t use tables for layout. Ever. – David Ball's blog
- Table Layouts vs. Div Layouts: From Hell to... Hell? — Smashing Magazine
- Why tables for layout is stupid: problems defined, solutions offered: Everything on one page)
- Don't use tables for website layout at DuckDuckGo
P.S.: I can try to fix that <table>
mess if the source is available on GitHub.
If you take a closer look at the source code, most of the layout is directly copy-pasted from SMW Central and uses a mostly unmodified version of rain.css, which is the Rain scheme you can select from Edit Profile. Doing it properly would make no sense in this case because I'd either need to convert it into tables or make custom CSS for every possible site scheme.
As for why SMW Central uses a table-based design, it's because it was created years ago, back when Internet Explorer 6 was the standard browser and tables were pretty much the only way to position anything. Today, it looks quite dated, but still works.
By the way, I wouldn't need help to create anything without using tables. After all, most web designers can do that.