Thread View: comp.mail.pegasus-mail.ms-windows
9 messages
9 total messages
Started by Han van den Bogaerde
Mon, 25 Dec 2000 09:48
Pegasus Mail v4.0 - a roadmap [long].
Author: Han van den Bogaerde
Date: Mon, 25 Dec 2000 09:48
Date: Mon, 25 Dec 2000 09:48
193 lines
11847 bytes
11847 bytes
David Harris wrote:
There has been considerable interest in the changes Pegasus Mail v4.0
is going to have when it is released, and also in *when* it is likely
to be released. This message is intended to provide an overview and to
explain why it's so difficult for me to estimate a release date.
The primary design aims in v4.0 are to enhance the existing
functionality, and to provide new functionality that many people have
requested - *but*, to do so in a way that is familiar and consistent
with the standards Pegasus Mail has set in its eleven year life. Some
people have tried to tell me that I should abandon the Pegasus Mail
user interface and make one that looks like Outlook, but this seems
pointless to me. It is clear that while many people like the approach
taken by Outlook, not everyone does:
Pegasus Mail's interface has proven itself a viable and worthy
alternative over the course of a long, user-driven life, and I am not
about to flag that away. Having said that, I will be making some
concessions to people who want a "more-Outlook-like" feel in v4.0.
So, without further ado, here is the core list of what are planning to
do in v4.0. This list is not in any specific order.
* Overhauled message reader.
V4.0 has exactly one message reader window, which can present all
types of data. The window has multiple tabs, one each for the body and
headers, for attachments, for annotations, and for a totally raw view.
Splitting attachments to their own tab has allowed us to improve
attachment handling beyond recognition - you can now forward or reply
to individual sections or groups of sections of multipart messages,
and the view of the attachments is much more like what users are used
to seeing in Windows Explorer. The new reader is the most visibly
different thing in v4.0, and most users may find it takes a short
period of adaptation to get used to it; but we believe it provides the
best possible balance between usability and functionality. It's also
very fast.
* Improved handling of HTML.
HTML mail is an absolute can of worms, as everyone surely knows by
now. Pegasus Mail v4.0 attempts to provide improved display of HTML
mail while preserving its current complete insulation from HTML
nasties such as viruses and image bugs. We now support HTML messages
with inline graphics (provided those graphics are encapsulated in the
message, in line with MHTML conventions), and v4.0 can also generate
safe, reliable HTML messages including tables, lines, graphics and
other fancy features - all guaranteed virus and trojan-free.
* Improved forwarding.
Forwarding mail, especially when it has attachments, is an area where
Pegasus Mail has traditionally been slightly weak: not in v4.0. We
have completely rewritten the forwarding support for v4.0 to correct
the weaknesses our users have told us about. I believe that v4.0's
handling of mail forwarding will meet or exceed the expectations of
any user.
* New addressbook.
The Pegasus Mail v3.x addressbook format has served faithfully for
seven years, but it's no longer able to cope with the wider range of
needs people now have. V4.0 incorporates an addressbook that we want
to be the best in the industry: v4.0 Addressbook entries allow you to
tailor all mail settings for the messages you send using them; they
also allow you to keep unlimited notes of any size, including
pictures, formatting and more, to keep comprehensive history of the
mail you've sent using the entry, to set dates and alarms, even to
store mail messages of interest as part of the entry itself. As well
as this, you will be able to create your own addressbook fields either
on an entry-by-entry basis, or as common fields for the entire
addressbook. Sizes will be practically unlimited in addressbook
entries - you want to have 1,000 e-mail addresses in a single
v4.0 addressbook entry? No problem. The v3.x addressbook format will
remain supported in v4.0, and it will be easy to import v3.x
addressbooks into the v4.0 format. We will be providing a Mercury
protocol module to allow remote management and access to addressbooks:
combining this with IMAP will allow Pegasus Mail to be run in a
completely remote manner.
* Outlook-style "preview mode".
V4.0 will support an optional folder view similar to that used by
Outlook and other mail packages. In this view, one large window will
contain your folder list, the contents of a selected folder, and a
preview of the selected message in that folder. This preview mode will
be an option that can be turned on and off and will thus complement
the separate-window model Pegasus Mail currently uses.
* Calendaring and task management.
The subject of many requests, this... Pegasus Mail v4.0 will finally
include a comprehensive calendaring module with alarms, events and
actions, allied with a powerful task manager that will allow you to
plan and manage complex tasks. The task manager is something like a
cross between a to- do list and a project manager - more capable than
the former, and less complex than the latter. The initial version of
the calendaring/task management code will be a personal
implementation, but the hooks are in place to allow simple group
scheduling via a Mercury protocol module, which will follow sometime
reasonably soon after the v4.0 initial release. The same Mercury
module will allow remote access to your scheduling information.
* PIM integration.
One of the primary design issues in both the calendaring module and
the addressbook is to allow integration with PIM devices, such as the
Palm Pilot. At the very least we will provide simple import/export
between our formats and the Palm, and our aim is to provide full
synchronization facilities. We understand how important it is for us
to get this part of the equation right, and will be doing our very
best to provide the most seamless levels of integration possible.
* Secure folders / compressed folders.
V4.0 will support a new folder model which will allow you to password-
protect and encrypt your folders, and optionally compress the data
they contain. With this folder format in place, it finally becomes
sensible to allow password-controlled access to the program at
startup, so we'll be adding that as well.
* Total overhaul of the IMAP code.
We are completely rewriting the Pegasus Mail IMAP client code to make
it faster, more efficient, and more usable in a wider variety of
scenarios. With the recent release into public testing of our Mercury
IMAP server, we expect IMAP to become increasingly important to both
organizations and individuals alike, and we are committed to providing
client code in Pegasus Mail that reflects this importance. As an
example, it will be possible to use v4.0 as an IMAP-only mail program
- one without local folders. IMAP performance should typically be
anything from 100% to 500% faster in v4.0, depending on configuration.
* Total overhaul of the POP3/SMTP code.
Pegasus Mail has supported multiple POP3 accounts for years, but I
think we can do it even better. V4 will allow you to create multiple
POP3 accounts for each identity you use, and there will be lots of new
options, like settable poll times (you can have some POP3 accounts
polled less often than others, for example), server-side filtering
prior to download, and more.
* Python scripting language.
Pegasus Mail has a completely new object-oriented interface for use by
extensions and plugins. We have taken advantage of this interface to
provide a special plugin layer for the Python scripting language, a
widely- used Open Source scripting engine. Using this, it will be
possible to develop your own scripts to do just about anything, and
integrate them into Pegasus Mail. And yes, we will be making sure that
we don't fall into the same traps as Microsoft regarding problems with
scripts executed by mail.
* 32-bit only.
This isn't exactly a feature, but I decided I had to mention it. There
will not be a 16-bit version of Pegasus Mail v4.0 - I can no longer
get updates for most of the tools I use for 16-bit development, and
with the quality of the Novell Client libraries now being very good,
there's really no longer any valid reason for a site to use the 16-bit
version in preference to the 32-bit version. The 16-bit v3.12 version
will remain available and will be given occasional bug fixes, but
there will be no further major 16-bit development of Pegasus Mail.
--
These are the most notable changes planned for v4.0, but there is also
a myriad of other improvements, like faster startup, an improved
filtering interface with new rules/actions, customizable toolbars,
auto-correction in the editor, changes in encryption to provide hooks
for things like S/MIME and MIME/PGP - and more and more.
It should be clear from this feature list that v4.0 is a genuinely
major step forward for the program - easily the most major since the
v3.0 release two years ago. Unfortunately, it takes time to write this
much code, especially when a lot of it involves extensive internal
changes, and it takes a long time to test it, too. As a result, I
simply can't tell you when v4.0 might be released: it might be late in
January, or it might be late in February; if everything goes wrong, it
might even be later, although naturally I hope it doesn't come to
that. Estimating deadlines has got me into all kinds of trouble in the
past, so I'm deeply hesitant about doing it now - I just hope you will
accommodate me on this. Suffice it to say that I am writing this with
v4.0 beta 6, and that I expect we may have as many as 25 beta rounds
prior to release. At present, I have all the beta testers I can
manage, but if I need more at any point, I will make that fact known.
I'm very excited about Pegasus Mail v4.0 - I've put an enormous amount
of planning and preparation into its development over the course of
the year 2000, and I believe it will be well worth the wait - I hope
this summary allows you to share some of my excitement; I'm just sorry
I can't do more to allay your impatience... :-)
Cheers!
-- David --
------------------ David Harris -+- Pegasus Mail
----------------------
Box 5451, Dunedin, New Zealand | e-mail: David.Harris@pmail.gen.nz
Phone: +64 3 453-6880 | Fax: +64 3 453-6612
Real newspaper headlines from US Papers:
"Nicaragua sets goal to wipe out literacy".
Re: Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Han van den Bogaerde
Date: Tue, 26 Dec 2000 22:20
Date: Tue, 26 Dec 2000 22:20
30 lines
2615 bytes
2615 bytes
In bit.listserv.pmail on Tue, 26 Dec 2000 14:27:59 -0000, Andrew Hodgson <andrew@hodgsons.freeserve.co.uk> wrote: >In article <qn5e4tg21pd9vkba7iee4h3b4vokeel1d4@4ax.com> > j.a.a.v.d.bogaerde@caiw.nl wrote: > >> * Secure folders / compressed folders. >> V4.0 will support a new folder model which will allow you to password- >> protect and encrypt your folders, and optionally compress the data >> they contain. With this folder format in place, it finally becomes >> sensible to allow password-controlled access to the program at >> startup, so we'll be adding that as wel > >Question: Does the current release of Mercury allow for these new folder >types, or will it be necessary to have an update of Mercury to accomodate >the protected folders? >> It's still under development. Mercury MTA (except for the IMAP4 module) only uses the new-mail folder, which is currently no folder at all, but a view on files with a *.cnm extension. This issue has not been discussed yet. -- Han van den Bogaerde - jaabogae@caiw.nl Member of the Pegasus Mail Support Group My own Pegasus Mail related web information: http://surf.to/HanPegasusMail
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Sergey Vasil'ev
Date: Tue, 26 Dec 2000 22:48
Date: Tue, 26 Dec 2000 22:48
11 lines
1349 bytes
1349 bytes
"Han van den Bogaerde" <j.a.a.v.d.bogaerde@caiw.nl> wrote in message news:qn5e4tg21pd9vkba7iee4h3b4vokeel1d4@4ax.com... > David Harris wrote: > and no words about different codepages support in new version of PM :((( -- Sergey Vasil'ev
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: N.D. van Bochove
Date: Wed, 27 Dec 2000 17:10
Date: Wed, 27 Dec 2000 17:10
6 lines
1387 bytes
1387 bytes
Thank you for keeping us informed. Yes, it's difficult to wait, but I like the idea of finishing the software before the release..... And with this kind of messages, the waiting is less difficult. Diederik van Bochove
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Evertjan
Date: Thu, 28 Dec 2000 14:49
Date: Thu, 28 Dec 2000 14:49
9 lines
1432 bytes
1432 bytes
N.D. van Bochove wrote on 27 Dec 2000 in bit.listserv.pmail: >Thank you for keeping us informed. Yes, it's difficult to wait, but I like >the idea of finishing the software before the release..... Never done before by MSoft............ -- Evertjan. (Please change the x'es to dots in my emailaddress)
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Paul Moore
Date: Thu, 28 Dec 2000 23:12
Date: Thu, 28 Dec 2000 23:12
90 lines
5232 bytes
5232 bytes
On Mon, 25 Dec 2000 10:48:58 +0100, Han van den Bogaerde <j.a.a.v.d.bogaerde@caiw.nl> wrote: >David Harris wrote: > >There has been considerable interest in the changes Pegasus Mail v4.0 >is going to have when it is released, and also in *when* it is likely >to be released. This message is intended to provide an overview and to >explain why it's so difficult for me to estimate a release date. Thanks for this. I have been very interested in what will be in version 4.0, but couldn't find any information on the subject... First of all, let me say that I find Pegasus to be an incredibly powerful mail program, with lots of "hidden gems" in the form of features which offer incredible power, but are often not obvious from the documentation. But there have long been two *major* issues which have stopped me switching completely to Pegasus - they are silly cosmetic issues, but they really annoy me. I can find no direct mention of them in the list of 4.0 features, but they may be covered anyway - I would love to get some information one way of the other. The first issue is with the reader window. I know this is being overhauled, so this may be covered, but I'll ask anyway. I like to read mail with my mouse pointer pointed at the "delete" button, and I then simply browse with the PgDown/PgUp keys, and when I am finished simply hit the mouse button (without moving the mouse!) to delete. With the current reader window, the "delete" button moves when a message with an attachment appears, wrecking this mode of working. I'd love it if this was likely to change... (This could either be by careful design such that the button positions didn't change, or be allowing customisation of the toolbar layout, I guess). The second issue is the folder views. They simply don't support display views (notably threading) adequately for me. I'd like * Multi-level sorting * Ability to highlight (un)read messages in a different colour * User-specified definitions of threading * A tree-style view for threading The next-to-last item is an issue with mailing lists which prepend things like [list-name] to the subject, which can destroy detection of "Re:" type headers - also there are issues with foreign language readers which (say) use "Aw:" rather than "Re:". The last item basically means that I would like to be able to display the second and subsequent messages in a thread in a different way - maybe with the subject replaced by a simple "..." or indented based on response level, or something like this. I don't really need a fully fledged tree view, with collapsible nodes etc. >Having said that, I will be making some >concessions to people who want a "more-Outlook-like" feel in v4.0. I don't particularly want an Outlook-style view, but it does generally feel better at dealing with threading compared to Pegasus' current approach. I'd like the ideas to be considered, more than the user interface... >* Overhauled message reader. >V4.0 has exactly one message reader window, which can present all >types of data. This sounds wonderful (and probably covers my first point above). I can't wait to see it! >* Calendaring and task management. >* PIM integration. I can't see this as being important to me (Will the Psion devices be included, or is this likely to be Palm-only?) but that's not a problem as I can simply ignore it... >* Secure folders / compressed folders. I'd like to be able to read Unix mbox-format folders directly. Many mailing lists supply archives in this format, and being able to browse them in Pegasus would be nice (a simple "browse MBOX file" which gives a read-only mode is entirely adequate for this, and shouldn't be too far from the current capabilities, as Pegasus uses mbox format as one option at present). >* Python scripting language. Ooh, wow! This sounds really interesting! I can't wait to hear more details! Thanks, Paul Moore
Re: Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Han van den Bogaerde
Date: Fri, 29 Dec 2000 08:24
Date: Fri, 29 Dec 2000 08:24
34 lines
2773 bytes
2773 bytes
In bit.listserv.pmail on Fri, 29 Dec 2000 09:58:38 +0800, David Baker <david@baker.pc.my> wrote: >On Thu, 28 Dec 2000 23:12:05 +0000, Paul Moore ><gustav@morpheus.demon.co.uk> wrote: > >>The first issue is with the reader window. I know this is being >>overhauled, so this may be covered, but I'll ask anyway. I like to >>read mail with my mouse pointer pointed at the "delete" button, and I >>then simply browse with the PgDown/PgUp keys, and when I am finished >>simply hit the mouse button (without moving the mouse!) to delete. > >This used to annoy the hell out of me too! Someone else noted that you >can press the 'D' key to delete the message instead. Now I just have >one hand for PgUp/PgDn & the other for the D key & I can zip through >the messages quite fast. I could never understand why the reader >window wanted to jump around all over the place, especially when there >was a setting to "save window size" - it did only save the size, not >the position... > >Dave This is by design.... like it or not, but this is the only way you can have multiple windows open (one of the big advantages above other mailers) and access the windows. Just counted, I have 6 windows open, right now. -- Han van den Bogaerde - jaabogae@caiw.nl Member of the Pegasus Mail Support Group My own Pegasus Mail related web information: http://surf.to/HanPegasusMail
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Gary Stark
Date: Fri, 29 Dec 2000 12:35
Date: Fri, 29 Dec 2000 12:35
27 lines
2154 bytes
2154 bytes
David, David Baker wrote: > the messages quite fast. I could never understand why the reader > window wanted to jump around all over the place, especially when there > was a setting to "save window size" - it did only save the size, not > the position... > Oh, that this were only the case. I like to have my windows maximised, but only within the Pegasus shell. To me, this means that if I have the save window size setting set on, then the windows should always remain maximised within that context. Alas, such is not the case, and every time I create a new message, Pegasus resets all of its windows to a normalised, rather than maximised, view. -- g. Gary Stark gstark@RedbacksWeb.com http://RedbacksWeb.com
Re: Pegasus Mail v4.0 - a roadmap [long].
Author: Gary Stark
Date: Fri, 29 Dec 2000 12:41
Date: Fri, 29 Dec 2000 12:41
46 lines
3135 bytes
3135 bytes
Han, Han van den Bogaerde wrote: > >This used to annoy the hell out of me too! Someone else noted that you > >can press the 'D' key to delete the message instead. Now I just have > >one hand for PgUp/PgDn & the other for the D key & I can zip through > >the messages quite fast. I could never understand why the reader > >window wanted to jump around all over the place, especially when there > >was a setting to "save window size" - it did only save the size, not > >the position... > > > >Dave > > This is by design.... like it or not, but this is the only way you can > have multiple windows open (one of the big advantages above other > mailers) and access the windows. > It is? Then I need to tell the applications that I write that the multiple windows that they display, in the locations I designate, that they're doing something wrong. <g> Seriously, yes, there is some default Windoze behaviour that provides a default window location, but that can always be overridden by the programmer in his or code when he or she creates that window. While I can make no claims at all about what the design goals are and were for Pegasus, and/or regarding the development tools used in its creation, I can assure you that it is dead easy for me, in applications that I write, to place windows anywhere on the screen when I wish to display them. > > Just counted, I have 6 windows open, right now. > > -- > Han van den Bogaerde - jaabogae@caiw.nl > Member of the Pegasus Mail Support Group > My own Pegasus Mail related web information: > http://surf.to/HanPegasusMail -- g. Gary Stark gstark@RedbacksWeb.com http://RedbacksWeb.com
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads