mrsaints / historyx Goto Github PK

Related #1

• Handle data through Immutable.js;
• Optimise render() through shouldComponentUpdate().

Related #1

• Migrate all stores, actions, and dispatchers to Alt.js;
• Implement waitFor() to update stores.

If our view limit is 100, and we have exactly 100 historical records, the paginator still shows the next button. This is a bug.

The current version is v1.0.0, although in reality I'd consider it v0.0.0. This thread will cover the "essentials" that needs to be done before a proper release (i.e. app store) can be made.

On a slightly related note, I'm planning on switching away from MDL entirely. It's a great framework, but it's built with too much reliance on its JS libraries (with a bunch of listeners)

I've decided to redo the entire extension, starting with a new CSS framework. It's most likely going to be Bootstrap 4 (Alpha). Rationale is simple: it's widely used, and its new version is fairly lightweight. It works without JS, and it feels a lot more predictable than MDL.

v2.0.0 is committed. Refactored, and reorganised the entire app. It's now using Bootstrap 4 (Alpha). Components, actions, stores, and constants are further compartmentalised, and cleaned up.

This is the roadmap for the next major release v3.0.0.

Scenarios

• Date specific (default):- "DD/MM/YY" | Time
• Query specific:- "Searching: X" | Time and date (same for stale visits)
• Query, and date specific:- "Searching: X on DD/MM/YY" | Time

Completed

• Pagination (???) / Show X results (e.g. All);
• Search ALL (i.e. not date specific - how to best handle this?).

To be added

A separate webpack config should be created for the development environment. The extension also needs an automatic packager / builder (e.g. gulp).

• Settings page: alter date format;
• Deleting single URL;
• Deleting ALL / selected;
• Undo delete (recycle bin?);
• Sorting (e.g. by date, and alphabetical order)
• Grouping (e.g. by hostname);
• Tagging (i.e. custom search);
• Reset;
• About / metainfo page (e.g. version);
• Show full URL.

Under consideration

• omnibox
• Most visited (by date? should this be on a separate page?) | Could use topSites API;
• Statistics or something fancy... (see above)
• Routing (???);
• Custom calendar element (I don't like the current one);
• Star on bookmarks;
• Autoreload.

Issues

• Retrieving real dates / times (for stale links);
• Fix pagination when "ALL" limit is used;
• Button to refresh stale results (possibly the title);
• Reduce font-size?

Perhaps we should use Immutable.js...

The flexbox simply extends to fit the long URL / text.

Cause:

Changes to Chrome to meet spec changes.

Solution:

Setting min-width to 0.

How to search from all history but not just one day?

Is it possible to support more flags? Such as regular expressions? Or "before" / "after" / "during".