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.

Changes between Version 1 and Version 2 of rekkanoryo


Ignore:
Timestamp:
Aug 7, 2007, 5:14:15 PM (17 years ago)
Author:
John Bailey
Comment:

Some tweaks to my page, as well as the addition of a new idea.

Legend:

Unmodified
Added
Removed
Modified
  • rekkanoryo

    v1 v2  
    77== Ideas ==
    88 * Migrate the C Plugin Howto to the wiki?  Asked about in the XMPP conference.
     9   * This is in progress (strike-through formatting as each area is completed):
     10     * ~~CHowTo/BasicPluginHowto~~
     11     * ~~CHowTo/PluginActionsHowTo~~
     12     * ~~CHowTo/ChoosingPluginIds~~
     13     * ~~CHowTo/DebugAPIHowTo~~
     14     * CHowTo/RequestAPIHowTo
     15     * CHowTo/NotifyAPIHowTo
     16     * CHowTo/SignalsHowTo
     17   * We need people who can do How-To's for Perl, Tcl, and Mono plugins.
    918 * ~~Include a Plugins wiki page that can be edited and show third-party plugins.~~  Done.
     19 * New structure within .purple for UI and plugin benefit:
     20   * `pixmaps` subdirectory - Allow plugins installed to .purple to have a standardized pixmap location
     21   * `themes` subdirectory - Standardized location for smiley themes (obviously we need a migration path here), notification themes (for when Guifications 2.x gets absorbed into Pidgin), status icon themes, message themes/styles, and sound themes (which make sense given other existing and intended theme support).
     22      * `themes/notifications` for Guifications themes
     23      * `themes/sounds` for sound themes
     24      * `themes/smileys` for smiley themes
     25      * `themes/messages` for message styles/themes.
     26   * Some related API within libpurple:
     27     * Make the list of each type of themes available to UIs and plugins.
     28     * Make the contents of each theme available, perhaps via GList or hash table.
     29     * Both of the above make any UI or plugin wishing to do so to take advantage of a standardized theme format with a well thought-out and implemented access system already pre-made for them.
     30   * Standardize theme formats (would need buy-in from Adium, I suspect) such that we have a standard XML format that we could easily include a theme editor plugin or standalone application for.
     31     * Let's go ahead and change the Guifications themes to match the new status API.  There are a lot of deficiencies in that theme format since it was based on the old status system and hasn't yet been updated to take advantage of the new system.
     32     * Let's change the smiley theme format, too.  We can maintain backwards compatibility with the existing format if desired.
     33     * We can provide a Theme Migrator plugin to update themes to the new formats where practical and possible.
    1034
    1135----
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!