Mabinogi World Wiki is brought to you by Coty C., 808idiotz, our other patrons, and contributors like you!!
Keep this wiki going by contributing to our Patreon!
Event List
User:Pyrus/Wiki_Home
Yes? No? Discuss.
The server status gets really squished, not to mention, not everyone has widescreens (yet). And, I don't know how you did it, but the general news spans longer than the server updates?
Also, what about when there are no events? Or more events to the point where the table is obnoxiously long? Or repeated events to the point where it spans more than a line of text (multiple hot times)?
A table just doesn't seem right for this kinda thing, unless you can get it to look fitting.
As I said, I'd prefer a bullet list, was just entertaining the idea. And when do we NOT have events anymore? There's always something going on at all times, no matter how boring the events are.
I was thinking we'd just leave out the current events section when there are no events.
I think it belongs between daily missions and server status, but I hate the table idea more than you. I'd have 2 lines for each event; one line for name & link, one for start & end(or dates & time for "hot time"s). Or, since there are usually multiple events with the same start & end times, use the dates as sub-headers grouping the events.
I'm not sure listing start time is necessary for current events on the main page, unless we put upcoming events in the same box.
You should figure out how to make each event only take up one line so there isn't so much wasted whitespace, in my opinion (remove years, maybe remove "Event" from event names, possibly exclude start date since end date is more important in the present time). Also the addition of the table doesn't make the server status itself squished, just the whitespace around it. Regarding widescreen, the min width with the current events table seems to only add about 100px to it. Just some thoughts.
Instead of trying to fit this into the current table by making it span 3x as many columns, It might be beter to just use a nested table spanning both columns of the current one(so the size of whatever is in the top row doesn't mess with column width below), and definitely drop the year, so far, we've never had a 2+ year event.
Using a table for the current event list itself wastes too much space on padding, plain text would be a lot better.
"nested table spanning both columns of the current one"
Can you continue to elaborate on this because I don't understand what you mean.
I don't see why you'd need a nested table.. If you're going to make a row that spans both columns... colspan you'd colspan that new row for the table anyway...
Instead of increasing colspan to a total of 6, leave it as a 2 column table, but merge the daily/status cells, and in the new cell, add a 1 or 2 row, 3 column table for the daily/event/server stuff:
...
|-
|colspan="2"{|
| Daily label
| Event label
| Status label
|-
| Daily Missions table
| Current Events (preferably as plain text)
| Server Status table
|}
...
The way you have it now gets the job done, but it would take more work to make sure it doesn't mess with the width of the cells under it like it does in your current example, and we might have to manually resize every cell on the page again if we ever change the width of anything in that one row. The width of the events section might change if we change our minds about the necessity of listing year or start time, or if there's ever a really long event name.
Switching to the nested table idea would more effectively separate the width cells in this row from those in the next, so it would be easier to avoid what's happening in that next row right now.(I don't know how it looks for you, but Firefox is showing me a page where "General Mabinogi News" is 2x as wide as "Mabinogi Server Updates" for your example, which doesn't seem to be intentional since the source still says 50% width for both).
Edit[edit]
I was over-thinking this.
Since there's nothing above or below that needs to match the width of any of these cells, you can just break up the existing table; put daily/current/status in a 3 column table, then news/updates in a 2 column table, and just put Frontpage1 and newmenu at the top and bottom without tables.
(too bad that doesn't work because I never said I liked his design [and sorry, pyrus, I don't, it creates whitespace issues with widescreens])
Would you mind clarifying what specifically you mean by "issues"? Is it just too much white, or is it the arrangement or something else?
I would like to know these issues too. Also there is some weird vertical whitespace difference in between the bullets.
That's my cue to enter...I suggest we some how code scrolling text with the events names at the top of the home page.
ahh nevermind I forgot that's really difficult to do...we could make a centered list that isn't bulleted. Bullets looks weird. Center the text too.
Welp I see my idea burning in flames now...the only thing I can think of now is separate the notices and make a separate window for event notices. like when it begins and ends.
How about having it on transcluded on the sidebar? That may be prone to vandalism but so is the front page.
everything is prone to vandalism Pyro...everything....
But what would that look like in the side bar?
Speaking of which, I've been busy/lazy with the ranged weapons reform. . . Feel free to do the work for me help me.
For things like "Hot Time", it's not necessary to repeat the month. For "Hot Time" and 2x exp/ap events that only run a few hours a day, I think we should mention the times on the front page too. For example, if there was a "Hot Time" scheduled for 7pm every other day for 10 days starting August 28th, this is how I would suggest we list it in the Current Events box: "August 28th, 30th; September 1st, 3rd, 5th at 7pm".
It might look better if you make the Current Events box narrower; the whitespace would be distributed to the sides of the page a bit, instead of it all being in one big chunk in the center.
I still think we should consider grouping events that have the same end date.
I agree with all of your points but, aside from maybe 2 events per month, almost every event has the same end date (and that includes limited gachapons and pets).
Lets say we do group similar events under one bullet, what then? We make the table taller instead of wider which is the opposite of Kevin's bit?
Okay, then instead of my earlier suggestion of using dates as subheaders, we could just use comma delimited list with the dates at the end.
Though the subheader idea would increase the height less than it would decrease width, and if you decrease the width of the box enough, you could move the daily missions/server status tables closer to the center so the page looks almost the same as it does now.