Thread:Oioiaussie/@comment-5042346-20120723191744/@comment-5116140-20120724005854

Design of Fusion Reports

I am really glad the questoon of how to best report fusions is being discussed. The key is to make it simple, easy to find current recipes and easy to post sucessful fusions. The current design represents a lot of dedicated work which has definitely helped me get some truly awesome dinos I could not otherwise obtain. Here are some ideas to simplify the fusion reports.

A. There needs to first be an Index Page

It would look like this. * * * * *

Click on the dino you would like to get through fusion or that you would like to report a recent recipe for. They are organized by Tier.

Tier 0: Sorry but tier 0 dinos cannot be obtained by fusion.

Tier 1: Brontosaur

Pterodactyl, Ingridia, etc

Tier 2: Triceratops, etc

Tier 3: Bambiraptor etc. <-- These names are all links to separate pages.



That's all that would be on the index page. A list of links, one for each fusable dino.

B. Now suppose I want an ingridia. First I go to the fusion index page and click on the Ingridia link under Tier 2. There I will find the most recent recipes organized by date.

It might look like this. * * *

INGRIDIA

Report here recent fusions that have produced an Ingridia. Most recent data appears at the top.

Date 3:  Month/Day/Year    Dino 1: Dimetrodon (4)    DIno (2) Dimetrodon (4)

Date 2:  Month/Day/Year    Dino 1: Dimetrodon (4)    DIno (2) Dimetrodon (4)

Date 1:  Month/Day/Year    Dino 1: Dimetrodon (4)    DIno (2) Dimetrodon (4)

That's it. Of course the values might be different.

C. I agree that user name should not be included. It is critical however that the most recent entries appear at the top so users can simply ignore entries far down the list. That makes the list "self correcting" after changes by TinyCo.

D: Advantages.

1. Very simple design. The current tabular design is what software engineers call BRITTLE. It requires a lot of dedicated rework when TinyCO adds new dinos or changes tier levels. The proposed design is simple to the extreme.

2. The fusion reports are self-correcting since the most recent data appear at the top. Simply ignore old data or cull data beyond say 20 reports.

3. No objection if a multiple line gets reduced to one - (with index k counting the number of reports). However, this runs the possibility that one outlier new report could

"revive" outdated reports that really rarly work after TinyCO changes the fusion tables.

Will check back regularly for follow up.

ID: TinyRobinEgg

The design of the fusion results