maclyn / curveball Goto Github PK

Doesn't look nice on 480x800 (can solve with outRect.width).

Add more events.

Some widgets don't size correctly (not enough space).

The two page dialog sequence no longer cuts it. Add a real tutorial.

Go material. The half-transparent theme is more Kitkat.

The dock... is not very good. Needs a modern implementation; one of the last "high-effort need-to-dos".

Horizontal A-Z scroller at the bottom of the screen. Essentially a horizontal re-implementation of the old vertical scroller (see FastScroller.java); shouldn't be too much new work.

Lots of nonsense references to smartbars and other things in the apps that need renaming.

On Kitkat and below, the recent apps view is broken. Fix it.

As was reasonably pointed out to me, being able to drag a thing up to expand it and not being able to just drag it down to collapse it is... sub-optimal. Do the thing.

Use folders instead of headers. The preference menu is getting overfilled.

Because this is important.

Drawables, while retrieved in the background, aren't always decoded into bitmaps in the background. Furthermore, many Drawables could be shared across components, but they aren't yet (even if Android is helping keep resource consumption reasonable by doing its own sharing). To resolve this, creation of a memory cache for drawables is important.

Attributions don't reference api.met.no, the new Google Fonts, or Climaicons.

Track CPU usage when in HomeActivity, and preemptively cache bitmaps so we get fewer "white dots" while we load bitmaps into the IconCache. Since we fixed #1, we have this issue since we do drawable grabbing in the background, so it's not always available for use (still much better than UI thread drawable management, but it leads to some ugliness).

On widget bar. Try Calendar.

Currently, we execute IconCache requests on the default executor, which limits us to a single thread. We should throw this work across multiple CPUs to improve performance.

Fetch bitmaps for ShortcutGestureView after loading in the view. It'll slow down things, but it's a good stop-gap until we figure out how to do #5, which is much more involved.

Hasn't been checked in a while -- everything minSdkVersion is fine (no fancy new classes), but there's likely some theme stuff that's off now.

Slightly offset up.

Currently, everything's in one package. Distribute classes into reasonable package names.