Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Apr 1, 2013, 8:04:03 AM (11 years ago)
- Author:
-
MarkDoliner
- Comment:
-
A few really minor updates. Half grammatical, half content.
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v86
|
v87
|
|
| 46 | 46 | |
| 47 | 47 | == Rewrite chat log backend and frontend == |
| 48 | | Our current chat log storage and viewer has only limited functionality. A proposal for this project idea should include plans to implement new backend and frontend (both, but backend is more important, because frontend relies on it): |
| | 48 | Our current chat log storage and viewer has only limited functionality. A proposal for this project idea should include plans to implement new backend and frontend (both, but backend is more important because frontend relies on it): |
| 49 | 49 | * New chat log backend features: |
| 50 | | * use single file (or anything less than thousands of files like now), like SQLite database |
| 51 | | * allow marking messages as unread, so they could be re-opened after Pidgin's restart, until user actually reads it |
| | 50 | * use single file (or anything less than one-file-per-conversation), like SQLite database |
| | 51 | * flag messages as unread until the user actually reads it, so unread messages can be re-opened after Pidgin restarts |
| 52 | 52 | * conversation context |
| 53 | | * inline images (and custom emoticons maybe?) storage |
| 54 | | * import from old chat log formats |
| | 53 | * inline image (and custom emoticon maybe?) storage |
| | 54 | * backward compatibility with old log format (possible one-time migration from old log format to new log format) |
| 55 | 55 | * (optional) remote log storage support |
| 56 | 56 | * Brand new frontend (chat log viewer - note, that it's pointless to do it without backend upgrade): |
| 57 | 57 | * browsing by meta-contacts - tree view, like in buddy list |
| 58 | | * responsiveness while searching, maybe some progress bar |
| | 58 | * sorting by name, last message date, conversation frequency, amount of exchanged messages |
| | 59 | * search capability (with UI remaining responsive, possibly with a progress bar displayed) |
| 59 | 60 | * (optional) typing name in search box could do real-time contacts filtering, like in buddy list |
| 60 | | * sorting by name, last message date, conversation frequency, amount of exchanged messages |
| 61 | 61 | * (optional) fuzzy search option |
| 62 | 62 | * (optional) showing new messages in real time |
| 63 | | * (optional) manual import/export for old formats (note, that import from old format should be anyway done automatically on first run) |
| | 63 | * (optional) manual import/export for old formats |
| 64 | 64 | Here are two mockups: [http://i.imgur.com/XczYG.png like a current one] [http://i.imgur.com/dTFtV.png better one]. |
| 65 | 65 | |
| … |
… |
|
| 76 | 76 | == Emoticon cache == |
| 77 | 77 | (Note: There is some concern that this project is not large enough to justify an entire project.) |
| | 78 | |
| 78 | 79 | Currently Pidgin does nothing with received emoticons. It could save a lot of bandwidth if a cache of received emoticons existed. It could also be merged with local custom smileys so we have a unified way to manage these files. The cache can be done per session, per conversation, per account, or as a global permanent cache (just as buddy icons). The preferred method is a permanent cache so emoticons could be fetched only once. |
| 79 | 80 | |
| … |
… |
|
| 108 | 109 | * Implement Language auto-selection (via browser "Accept-Language" header) |
| 109 | 110 | * Use statically generated pages to avoid unnecessary server load and overhead (in other words, avoid pulling in the strings every time the page loads; only when they need to be regenerated) |
| 110 | | * Make use of existing technology such as gettext or similar web projects to allow translators to submit translations easily |
| | 111 | * Make use of existing technology such as gettext or and Transifex to allow translators to submit translations easily |
| 111 | 112 | * Find a way to generate a translation template, identify or tag strings within pages. |
| 112 | 113 | * Consider ways to provide translated versions of images and screen shots |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!