GSOC: Chat Log

Nader Morshed morshed.nader at gmail.com
Wed Apr 17 12:58:46 EDT 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> However, the UI have to be totally unaware of underlying database (for
> example, to make it possible switching to something else in the
> future). This approach also reduces code complexity and makes things
> better considered. That's why I believe, this project is way harder
> than it looks like and it's easy to screw it up. Here are some of
> difficulties:
> - frontend and backend totally splitted, connected via *external* API
> - all routines should be (have to be?) asynchronous

For what it's worth, my branch is still lying around with this mostly
done: http://hg.pidgin.im/cpw/nader/asynclogging/

I don't know if he'll care for my implementation or choice to mirror
the GIO API, but it's there if he wants to hack it up. I'm happy to
explain the code, too, though it's been a while.

> - avoiding huge API - for example: conversation context should
> probably use the same routines that log viewer uses
> - long-lasting operations should provide a method to track them on
> progress bar
> - figuring out good way to maintain inline images (this can be tricky
> and may require devastating half of current API) -> remember, that
> such messages will re-appear as conversation context on next Pidgin
> start
> - thinking forward: making it possible to use external log, or even
> implement it (as a plugin?)

The original plan was to add another PurpleLogger backend. It's not
terribly difficult, but the original prerequisite was having a stable
asynchronous API to keep the client from hanging while network traffic
was ongoing.

> I hope, this project will be fulfilled honestly, because these
> features are the ones which I mostly wait for.
> 
> Tomek

- --
Nader Morshed <morshed.nader at gmail.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQIcBAEBAgAGBQJRbtTIAAoJEKfs8q3oqdgMhV4QAKuXfcyX+AMmN0WO0foVftH6
ccfAL/hvbGCZZ9R03z2gBRGfYZG1YxsxZDrqWu7055mTwL2dJg8fus/P5c1M6u9L
y/m6EuClMDHIiRCuwzSbXjW1sLZ+CiVpbOtsLhACEEL8Cg6CQOosMkqD7Ksf0O9w
GD1op4BiVVrdl6jW2mjVImoiy67wQxJCfE7xqxogxX8Rbq0GXfqNu1tqYC/kbeH9
WJg83xU2OHZyraVLd+Tq2WOmbaZKzqM2yIOE2EcUyscxBeqS8+FU/ZL0yHPUex83
5BvgEnmIX1jJpEgbgZ/Pfdda10fAllD+K1Pmi2kCAFHKnxXNC49lODgI6t+ynBk8
PpZOU8R3cjYH+M/qqd7yWqs7a1WgtxK91+4SocwrRxX8Zp/ohrTrODhvvOxvN9Kr
GpAEsnlyv1MUfy9FJ5dDMuJ3IVydUXhRAeY7rb6WFapUw42/XlVL8DWlSAoImta2
kP4kVbt60tDl8PlR7DEx64vzlz4+kG+DlMNfwkwiLVb09VbMFaJjnVEKbXcjWJc1
M6tAybt72SH389aJSumbgVO7hTQXrQxwGyd1ycqWiPIHaNoeglmyfVIuwV89/3aA
ZSLq22HYqMDyK4fBa8IelyqgL7CCrIF/+mGA1Brawo8NalwTpklUbNke1Q30EVlC
D1IejMT5O3x4oujCALmT
=DVGa
-----END PGP SIGNATURE-----




More information about the Devel mailing list