thyrgle / kelleybioinfo Goto Github PK

May clean up some stuff:

https://bootstrap-flask.readthedocs.io/en/latest/

Level change currently prohibits cell selection in web page.

https://metricsgraphicsjs.org/

Match against solution.

There appears to be a lot of redundancy in creating category HTML, maybe Jinja for loops can be used for this somehow?

Currently, the links are white, they can't be seen in the background.

Too many white links, need to make more specific.

User should probably not have a column for points. Just compute from History. Cache a lot somehow?

Not entirely confirmed, possibly utilize cache-busting in some way to prevent this?

Currently doesn't do anything, MetricGraphics library seems broken anyway.

The dynamic forms make it hard to work with Flask-WTF, need to make sure CSRF is being handled correctly.

Could use selectors more effectively, reducing the size of the CSS file and HTML.

Currently gives too many false positives. Possibly refactor the entire algorithm.

Currently looks squished.

app/templates/base.html

img tag needs an alt attribute.

https://moz.com/learn/seo/alt-text

You can cheat at Needleman-Wunsch too easily.

Should only be needed for profile.js atm.

Going to profile from anywhere that isn't the homepage goes to non-existent pages.

Seems to be easier than wtforms. Adds some additional stuff...

Or just use webpack as part of the build process?

Currently CSS doesn't work quite right. It looks good, but it still isn't quite correct. Similarly, this may need to be refactored into a popup page...

https://bootstrap-flask.readthedocs.io/en/latest/macros.html

Pressing "Practice" doesn't change the toggle. It remains on Quiz.

Consider using this boiler plate for the base html template.

Is it possible with the current infrastructure? Refactor to make it possible?

Problems should be registered automatically and should probably all be located in a/the problem folder. There should be no import hell.

• Should https://github.com/ironfroggy/straight.plugin be used?
• Should https://docs.python.org/3/library/pkgutil.html#pkgutil.walk_packages be used?

See https://stackoverflow.com/a/10527478/667648 .

Currently, the needlemanwunsh.py content method requires too much knowledge on the part of the programmer trying to create problems, more work should be delegated to the problems.py using a decorator or something of the sort. Specifically:

1. There is no need to handle post requests.
2. The templates file should not require the problem programmer to import scripts for problem loading, this should be done for them.
3. There might be the need for some matrix helpers to load from HTML? This part of the API is still up in the air... (More specifically, the matrices differ vastly in internal structure, is there a clean way to encapsulate all of them?)

Don't use execute in python, use execute_script write the script in an sql file.

Currently does not do this, makes it impossible to "construct" the new answer.

Consider adding this meta tag

The site should be viewable for mobile devices. Currently font scaling is an issue.

Consider adding media queries to fix this.

Also consider a desktop down approach for media queries.
max-width

Too many script tags are placed at the head tag.

Consider placing them near the bottom where they will not be blocking HTML parsing.

If not that consider using defer or async attributes.

Article below.

https://www.sitepoint.com/a-detailed-breakdown-of-the-script-tag/

How should the matrix translation from server to frontend and back be handled?

Menu items are hard coded, need a way to iterate through the categories and sub problems in Jinja.

/auth/login

Consider using offsets class rather than creating a extra div.

https://getbootstrap.com/docs/4.0/layout/grid/#offsetting-columns