Bitmessage/PyBitmessage-2025-02-19
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Threaded Inbox #283

New Issue
Open
opened 2013-07-03 21:49:16 +02:00 by IvanCool · 8 comments
IvanCool commented 2013-07-03 21:49:16 +02:00 (Migrated from github.com)
Copy Link

I suggest to add some basic support for threaded Inbox, e.g. sorting messages by grouping topics and dates.
I've never had any chance to work with Python before but I managed to make some changes to source code to display Inbox with threads. This is far from the final version but it seems to be much more usable than keeping 2 separate tabs each containing 10 topics with 5-20 messages each topic distributed across the inbox and outbox. Managing big number of messages/topics with Inbox/Outbox scheme is a real pain.

I don't know how to push my changed yet. I'm new to git.

I attach a slightly modified screenshot. I've removed some sensitive info (original titles+contacts) but it still gives a general overview of proposed changes.
bm1

I suggest to add some basic support for threaded Inbox, e.g. sorting messages by grouping topics and dates. I've never had any chance to work with Python before but I managed to make some changes to source code to display Inbox with threads. This is far from the final version but it seems to be much more usable than keeping 2 separate tabs each containing 10 topics with 5-20 messages each topic distributed across the inbox and outbox. Managing big number of messages/topics with Inbox/Outbox scheme is a real pain. I don't know how to push my changed yet. I'm new to git. I attach a slightly modified screenshot. I've removed some sensitive info (original titles+contacts) but it still gives a general overview of proposed changes. ![bm1](https://f.cloud.github.com/assets/4932919/745733/1382e1ba-e419-11e2-91a9-9631fdc0a1d9.png)
ghost commented 2013-07-03 21:55:32 +02:00 (Migrated from github.com)
Copy Link

I agree that a threaded inbox is a good way to go. The more that Bitmessage looks and behaves like other email clients the more likely it is to be widely adopted.

I agree that a threaded inbox is a good way to go. The more that Bitmessage looks and behaves like other email clients the more likely it is to be widely adopted.
IvanCool commented 2013-07-03 22:04:26 +02:00 (Migrated from github.com)
Copy Link

So how do I push my changes then?

So how do I push my changes then?
ghost commented 2013-07-03 22:12:51 +02:00 (Migrated from github.com)
Copy Link

In your branch there's a square green button on the left hand side. Hit that and then give the pull request a title and submit it,

In your branch there's a square green button on the left hand side. Hit that and then give the pull request a title and submit it,
sarchar commented 2013-07-03 22:35:10 +02:00 (Migrated from github.com)
Copy Link

I think it's worth pointing out that E-mail clients already do threaded
messages -- along with attachments, HTML text rendering, Cc & Bcc, etc.

I haven't done any searching (yet) on what the long term goal with
Bitmessage is, however, I do think it may be wise to focus less on the
message composition and more on network performance and stability.

I drafted a prototype today that merges Bitmessage with a barebone
SMTP/POP3 server and have successfully had "threaded" messages delivered
through Bitmessage directly into Thunderbird.

Fixed link - https://github.com/sarchar/PyBitmessage

See screenshot: http://imgur.com/4Rx1c3q

For what it's worth, I'm aware of at least two other projects that
accomplish something similar. The first, a C# project that runs only on
Windows and isn't sufficient for everybody; however, it looks like a
quality project. The second, a standalone "bitmessage wrapper" that
didn't seem as though it were stable enough with the latest Bitmessage
code, but I could be wrong about that.

Feedback? Is this something that I should create a pull request for?

Chuck

On 7/4/2013 3:12 AM, Bob Mottram wrote:

In your branch there's a square green button on the left hand side.
Hit that and then give the pull request a title and submit it,

—
Reply to this email directly or view it on GitHub
https://github.com/Bitmessage/PyBitmessage/issues/283#issuecomment-20442061.

I think it's worth pointing out that E-mail clients already do threaded messages -- along with attachments, HTML text rendering, Cc & Bcc, etc. I haven't done any searching (yet) on what the long term goal with Bitmessage is, however, I do think it may be wise to focus less on the message composition and more on network performance and stability. I drafted a prototype today that merges Bitmessage with a barebone SMTP/POP3 server and have successfully had "threaded" messages delivered through Bitmessage directly into Thunderbird. Fixed link - https://github.com/sarchar/PyBitmessage See screenshot: http://imgur.com/4Rx1c3q For what it's worth, I'm aware of at least two other projects that accomplish something similar. The first, a C# project that runs only on Windows and isn't sufficient for everybody; however, it looks like a quality project. The second, a standalone "bitmessage wrapper" that didn't seem as though it were stable enough with the latest Bitmessage code, but I could be wrong about that. Feedback? Is this something that I should create a pull request for? Chuck On 7/4/2013 3:12 AM, Bob Mottram wrote: > In your branch there's a square green button on the left hand side. > Hit that and then give the pull request a title and submit it, > > — > Reply to this email directly or view it on GitHub > https://github.com/Bitmessage/PyBitmessage/issues/283#issuecomment-20442061.
IvanCool commented 2013-07-03 22:57:15 +02:00 (Migrated from github.com)
Copy Link

I'm sure you should. SMTP/POP3 support will be worth it.

But I still think simple threaded inbox would do much better than separate Inbox/Outbox feature.

I'm sure you should. SMTP/POP3 support will be worth it. But I still think simple threaded inbox would do much better than separate Inbox/Outbox feature.
IvanCool commented 2013-07-03 23:18:27 +02:00 (Migrated from github.com)
Copy Link

Ok, here is some initial work on threaded Inbox - just to test look and feel:
https://github.com/IvanCool/PyBitmessage/tree/ThreadedInbox

A lot more things need to be done though. Do you think it is worth working on?

Ok, here is some initial work on threaded Inbox - just to test look and feel: https://github.com/IvanCool/PyBitmessage/tree/ThreadedInbox A lot more things need to be done though. Do you think it is worth working on?
PeterSurda commented 2015-10-18 11:29:30 +02:00 (Migrated from github.com)
Copy Link

I will look into this and try to integrate it into the new UI.

I will look into this and try to integrate it into the new UI.
PeterSurda commented 2015-11-10 18:38:54 +01:00 (Migrated from github.com)
Copy Link

I'm deprioritising this to post-0.6.

I'm deprioritising this to post-0.6.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
enhancement
Milestone
No items
No Milestone v0.8.0
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-19#283
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?