Adium

Ticket #714 (new enhancement)

Opened 4 years ago

Last modified 7 months ago

Xtras Versioning

Reported by: catfish_man Assigned to: anybody
Priority: normal Milestone: xtras
Component: Xtras Version: 0.82
Severity: normal Keywords:
Cc: Patch: None
Pending: 0

Description

It would be nice if Adium's behavior when attempting to use an out of date Xtra was better than just silently failing or crashing. I'm envisioning something like Firefox's extension versions, or Shapeshifter's handling of themes that haven't been updated for new OS releases. If any Xtras with versions older than the current version attempted to load, a dialog would be displayed listing them, explaining that they might not work, and offering to check for updates (using webinstall, preferably), use anyway, or not load them.

Change History

07/09/2005 04:38:37 PM changed by michael

Yeah this is a good idea, although implementation could break a whole load of xtras, my idea would be to include a compulsary key in the xtra's plist stating which version it was designed for. Something like

<key>TargetVersion</key> <string>0.8x</key>

Then that could be checked against Adium's version number, and rejected if they didn't sync, showing a dialog noting that the xtra may be out of date or improperly written. Just my 2pence.

07/20/2005 11:49:21 AM changed by adamiser

Adium already does display a dialog explaining that addons may not work, with options to disable the addon or load it anyway.

07/20/2005 06:01:14 PM changed by durin42

  • milestone changed from Adium X 0.90 (Old) to Adium X 1.0.

pushing back to 1.0 since I'm guessing this takes some discussion as to implementation, as well as probably an adiumxtra:// type system kind of like the way quicksilver handles it's plugins....

07/20/2005 06:32:18 PM changed by catfish_man

adiumxtra:// links are already implemented in Adium

07/21/2005 08:43:48 PM changed by catfish_man

Blocked by #73

09/18/2005 07:50:48 PM changed by zacw

#73 no longer blocks this

09/18/2005 07:54:17 PM changed by zacw

As a further note, I see two problems with this:

  1. Xtras tend to not need updating in terms of new Adium versions. New features are added, yes, but they tend to not break as with FF.
  2. We'd have, en masse, a large amount of Xtras being updated at a time. This is quite the load for mods, no? All of them would have to be tested, and such.

09/18/2005 08:00:49 PM changed by zacw

Okay, I just thought about this again:

We can make the "designated version" sort of independent of the actual binary uploaded. Here's how: we can have a dropdown list for authors to choose the version which their Xtra works towards. They can then update this field without needing moderator input.

adiumxtra:// can then send some sort of information to Adium involving this sort of information. I'm not sure how we're implementing the download, but it can be something along the lines of an HTTP header which is just "X-Designated-Version" or something along those lines.

09/18/2005 08:05:07 PM changed by zacw

This becomes an issue, of course for:

  • Packages containing multiple different (non-variant) Xtras.
  • Already installed Xtras during an upgrade.

09/17/2006 07:22:54 PM changed by tick

  • milestone changed from Adium X 1.1 to Adium X 1.2.
  • field_haspatch changed.

1.1 is the SoC milestone, so moving to at least 1.2.

12/22/2006 01:26:21 PM changed by tick

  • milestone changed from Adium X 1.2 to Needs dev review.

Moving to needs dev review. When a solid plan can be implemented move to the appropriate milestone.

05/15/2008 08:37:59 AM changed by djmori

06/09/2008 01:12:36 AM changed by Robby

  • patch_status set to None.
  • pending changed.
  • milestone changed from Needs dev review to xtras.