rr- / malgraph4 Goto Github PK

Now:

1. Visit new user.
2. Receive error.

Wanted:

1. Visit new user.
2. Receive friendly message.

It's pretty slow right now, rendering user page can take up to a few seconds (spacecowboy exceeded 30 seconds).

I have to do something about it.

Perhaps new table?

Implement profile page design posted in #15.

"Not yet aired" icon introduced in #36 is the same as "Dropped" icon in /list section. It is very confusing, especially after introduction of new "Hide suggestion" icon (see #41).

Note that we don't necessarily need combined "not yet aired" + "planned" icon -- "planned" could overwrite "not yet aired".

Describe how mechanism described in #26 should look like.

Profile page in Mg3 looks fugly and bloated and needs change.

Right now every change done to config goes to repo.
There should be mechanism that allows to change config locally without producing any diff in the actual code.

Think of a good spot to put simple controls in. Headers seem like a good place, but cluttering them is not too welcome.

Drop PDO and use proper ORM solution; RedBeanPHP seems to be a good choice.

• Database.php should be removed.
• Processor classes should use RRP instead of PDO.
• Retriever class should be removed.
• Methods from Retriever should be implemented in some kind of Model classes.
• DataUtilities should be renamed to ModelUtils.

Right now, every page title defaults to MALgraph. This, along with description and keywords in <meta>, should be made specific to each page.

This concerns both recommendations and missing titles section.

Add a fourth column to /list, with label Diff, sortable.

For each row, it shows the difference between user's rating and entry's mean score on MAL (Diff = UserScore - MALscore). If user's rating is higher, it shows e.g. +1.41, if lower then -0.12, and 0 if they're equal. If user hasn't rated the given title, it shows -, just like in the rating column.

The items on this column could have a tooltip containing MAL's score, but that's not required.

After implementing ORM framework for dealing with SQL, cron went somewhat slow (6s for one user). I suspect that it has to do with removal of AbstractSubProcessor::update() in favor of R::store(). Investigate the problem and remove bottlenecks.

Right now, cron downloads all a/m whenever user is download, regardless of last download.

It should look at time of last download.

• Content box in the center of the screen
• The width of main header should be the same as the content, not content+menu
• What about mobile layouts?

Applies to anime, manga and users. Related: #2

Right now, navigation menu on user-specific pages looks ugly, it takes a lot of space and distracts user with big picture. It should probably be changed to look nicer.

• Retrieval of cool users
• Evaluating similarity
• Retrieval of all entries
• Filter out blacklisted genres from entries
• Checking what entries are cool
• Adding static entries
• Presentation

Right now:

• left side displays everything user has on its list,
• right side displays everything user hasn't on its list.

What about planned titles?
What about titles that are still publishing?

Please provide detailed logic flowchart what kind of entries should be shown in what sections of the table along with list of users I can test implementation on.

Right now, user menu is displayed in layout.

Layout shouldn't be responsible for drawing anything controller-specific, especially it shouldn't contain such big code cluster like user menu code.

When tab is switched, menu rearranges by 1px due to active item border.

Reference: #43
Remember to scale down "on hold" icon.

Need a design where these icons could be put.

Right now, we have make-db.php script that nukes whole database.
What I'd like to have is a mechanism that would allow to purge everything related to media: genres, relations, ..., leaving users and everything related to them alone.

Currently they say something like "Got 420, next level at 200". It should say "Previous level" for levels other than the highest one achieved.

What to do about user settings?

1. To keep consistency across all icons, the ones in menu should be a bit thicker, namely Ratings and History - these are too thin compared to other icons.
   
   In the corner is the resultant icon scaled down to around 20x20. The arrow head could be a bit more visible, though.
2. Remove half-opaque parts of List icon (icons should be as clear as possible, and this one doesn't need antialiasing since it consists of straight lines).
3. Replace Achievements icon with a less round one:
   

When I browse through suggestions or anything that isn't profile... I don't see my nickname, thus when I go back to MALgraph after few ctrl+tab I ask myself whose page am I viewing.

This is design fallacy and it should be fixed. Nickname has to be shown somewhere.

Right now front page is just a placeholder.

Have a look at front pages of greatest-looking sites in the Internet and design a layout for MALgraph.

Inb4, Google is not greatest-looking.

No further comment necessary.

Right now there are lots of switches and string mappings regarding user modules (profile, list, ratings, ...):

• one in layout.phtml in order to create links for each module,
• one in UserController in order to understand links,
• second one in UserController to dispatch links to proper methods,
• the methods in UserController,
• finally -- UserModuleEnum.

Make new class: UserControllerModule. Each module should derive from that. This leads to nested structure but no switches should be necessary thanks to reflection. Method like UserController::getModules() probably will be necessary.

When refactoring, do have in mind that profile is going to be unrelated to media. Although it should be treated specially in general (for example, it doesn't appear in a/m menus), rather than implementing profile-specific hacks, an universal mechanism that would allow modules to be media-specific (think module that appears only in manga submenu) should be implemented .