lp:~colindean/gwibber/bitly-support-lp439382

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #439382: Provide support for bit.ly

Wishlist

Won't Fix

Link a bug report

Related blueprints

479. By Colin Dean on 2009-10-27

+ added preference for username: shortener_username
+ added username input to preferences dialog (pref_shortener_username)
+ added ability to pass username to shortener if the shortener module requires it
+ made bitly and jmp modules require a login
+ made default login "gwibberuser" - someone should register this username

* It would be really cool if the username input only showed when a module required it, but I don't think there's the architecture in place to handle this
* N.B. that this hasn't even been executed yet to see if it works, as this is a local commit with a push for working across multiple computers

478. By Colin Dean on 2009-10-26

added work on modifying bitly.py
added bitly and jmp stubs
still need to add preferences text input for login and a way to access it

477. By Alexander Sack on 2009-10-25

rename Laconi.ca to StatusNet (UI part) in laconica.py (thx @BUGabundo for testing) - lp:419817

476. By Ken VanDine on 2009-10-22

Serge Matveenko 2009-10-09 Update Russian translation

475. By Ken VanDine on 2009-10-22

* When we quit, shutdown the daemon
* Fixed status icon handling

474. By Ken VanDine on 2009-10-22

Fix to match digg API

473. By Alexander Sack on 2009-10-22

unbreak messages sorting caused by bad flickr time format; use ticks() everywhere

472. By Alexander Sack on 2009-10-22

fix gwibber not starting if font settings use a non-integer value for size (LP: #383759)
- patch by Krzysztof Klinikowski

471. By Alexander Sack on 2009-10-22

also make a lightweight/not-threaded OperationResultHandler

+ after this patch all not-blocking operations in gwibber are processed in glib
  main loop; this should reduce the multi-threading problem to the quite well
  confined OperationThread's run method.
+ use OperationResultHandler.process_opdata as glib idle handler for ops
  produced in OperationThread
+ drop all uses of output_queue
+ pass operation result handler to OperationManager constructor now that it
  schedules the proper callback directly
+ accordingly, do not start the Messages result handler in server.py's Microblog
  constructor; instead directly pass it to OperationManager constructor, which
  then will use it as a glib idle handler to run the code in mainloop thread

470. By Alexander Sack on 2009-10-21

make a lightweight OperationManager without a threaded scheduler
+ drop scheduler loop code (aka run)
+ make a source callback out of process_scheduled_operation
+ use glib.add_timeout_seconds to schedule operations
+ use glib.remove_source to unschedule operations
+ stop starting operationmanager thread in Microblog constructor