32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
* Store feeds in kEnqueueFeeds/etc messages as paths? hmm
|
|
* This way, if the user edits the feed after it is enqueued but before
|
|
processing, the changes will be applied.
|
|
* Support for clearing queue
|
|
* Revamp configuration
|
|
* Fix saving, etc.
|
|
* Show progress
|
|
* With progress bar
|
|
* Ran into a slight problem when trying to set the maxValue and
|
|
value when in MainWindow::MessageReceived (kProgress)-- it would
|
|
crash every time, without fail. Even with float constants that
|
|
work when used in MainWindow::_InitInterface. Weird, idk
|
|
* With indicator in the feeds list
|
|
* Configurations
|
|
* Remove unnecessary `new`-- make sure to delete everything
|
|
* Check if arg is a file or not (treat appropriately)
|
|
* No hardcoded paths
|
|
* Default column layouts for ~/feeds and ~/config/settings/Pogger/Subscriptions
|
|
* Show in desktray
|
|
* Make archivable
|
|
* Get menu working
|
|
* Proper scripting support
|
|
* Multiple downloads at once?
|
|
* Array of thread_ids for multiple DL threads?
|
|
* In which case, it'd probably make sense to only spin them
|
|
up as necessary, and kill when everything's done.
|
|
* That'd require a proper queue system, instead of just
|
|
spamming data to the download thread lol
|
|
* Using a proper queue list would give faster
|
|
results to Notifer about how many feeds are
|
|
enqueued (so things *feel* faster)
|