Changes between Version 3 and Version 4 of DeveloperSummit2012

Jun 5, 2012, 8:41:56 PM (8 years ago)
Jens Maus

final update to developer summit page


  • DeveloperSummit2012

    v3 v4  
    1010* Future versions of YAM will continue to be released for AmigaOS4/PPC, MorphOS/PPC, AmigaOS3/m68k, AROS/x86, AROS/PPC and AROS/x86_64.
    1111* While all AmigaOS-derived platforms will be supported, maintainers (developers) for MorphOS/PPC and all AROS-based platforms are missing and should be encouraged to join the YAM project.
     12* The introduced multithreading (multiple processes) support in YAM 2.7+ has been proved to work stable. In the course of YAM 2.8/2.9 development the multithreading framework will be take over more tasks like e.g. mail filtering in the background, etc.
    1213* Contributing translators are updating their catalogs on a regular basis which supports the initial decision to open catalog translation for every interested translator rather than solely relying on the nowadays vanishing Amiga Translators' Organization (ATO).
    1314* More translators are required and should be encourage to join the project so that we can support a larger amount of different languages.
    3940== YAM 2.9+ roadmap decisions ==
     42* #77: While there seem to exist binary versions of GnuPG (gpg) on AmiNET ( there are no ports of libgpgme which in our opinion would be required to support GPG in YAM. Therefore we still have to wait and eventually try to port it on our own at some time.
     43* #102: Using a publicly available anti-phishing list seems to be a nice idea. However, this requires a larger amount of changes to YAM and some more evaluation of the google project mentioned.
     44* #104: Direct DKIM support in YAM would be a nice idea. But it requires to have full SSL certification support which is due in YAM 2.8. If that support is finished we could thing about this relately new anti-spam method.
     45* #122: User-definable toolbars requires a large rework on the configuration site of YAM and potentially also some changes to TheBar.mcc. It nevertheless seems to be a task doable but simply has low priority on our list.
     46* #123: User-definable context menus also requires a large amount of changes to the configuration to make it possible to let the user define the context menu entries. While definitly helpful we will hopefully find some time in the course of 2.9 development to implement that.
     47* #125: There is general consensus that the addressbook GUI requires a larger overhaul in YAM. It should be largely synchronized to the possibilities the addressbook in other clients like Thunderbird provide while still keeping the hierarchy based sorting in place.
     48* #126: The current embeded HTML to Text converter does a pretty good job. However, full HTML-Mail support is still a task in YAM. Unfortunately, this requires to have a MCC class available which will allow to display HTML+CSS mails directly in YAM. Such a class is still not publically available and would be best based on the current MUIOWB project. Hopefully such a public mcc class for displaying HTML+CSS pages will be available until YAM 2.9 is scheduled to be released otherwise we have to stick with our HTML2Text converter engine in YAM.
     49* #130: Besides full GPG support S/MIME support should be added. This would allow to sign and encrypt emails with SSL certificates rather than GPG/PGP keys. As soon as full SSL certificate support is integrated in YAM the implementation of S/MIME should be quite straight forward.
     50* #134: A 'Stop' button in the toolbar will be added to abort jobs performed in the background (e.g. filtering) via the multithreading framework.
     51* #137: To increase the parsing speed our flex-based parsers for converting HTML emails to plain text and to color highlight mails will be converted to re2c-based scanners which seem to provide more flexibility and a higher performance.
     52* #142: Similar to the 'about:config' editor in Mozilla projects YAM will get a config editor GUI to directly modify all config items including the hidden options.
     53* #230: A new column in the mail listview will be added which will display information through which mail server a mail had been transfered. This would allow to sort mails by incoming mail servers.
     54* #312: To improve performance and flexibility a prototype will be created to evaluate the possibilities to move the currently index-based mail storing mechanism to a sqlite based approach since binary versions of sqlite3 already exist for various platforms (
     55* #318: A Quick-Reply possibility will be added to the read window/read mail group which will allow to quickly reply without having to open a write window.
     56* #319: The current management of the internal config values/structures is cumbersome and error prone. It will be replaced by a mutator/accessor based approach with functions allowing to modify a certain config option based on a config item string.
     57* #322: The current implementation of the UpdateCheck mechanism will be changed to allow automatic update installation not only update archive downloads.