Opened 9 years ago
Closed 7 years ago
#792 closed enhancement (fixed)
Auto-updating of OO plugins
| Reported by: | dstillman | Owned by: | simon |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | word integration | Version: | |
| Keywords: | helpwanted | Cc: |
Description
Details here: http://api.openoffice.org/docs/DevelopersGuide/Extensions/Extensions.xhtml
From a very quick skim, looks like it should just require putting the version number in the description.xml files with the compiler script, adding a couple lines to the templates to include the update URL, and creating the update XML file itself.
Change History (4)
comment:1 Changed 9 years ago by simon
comment:2 Changed 9 years ago by dstillman
Well, we wouldn't build it automatically from SVN (or, if we did, it wouldn't automatically go live). It would just mean that if we pushed a new version, and someone updated, they'd have to go and update to the latest version of Zotero too. We wouldn't push a version that wasn't compatible with the latest released version of Zotero.
comment:3 Changed 9 years ago by dstillman
- Keywords helpwanted added
comment:4 Changed 7 years ago by simon
- Resolution set to fixed
- Status changed from new to closed
(In [4947]) Integration megacommit, part 2: Zotero code
Closes #884, final period missing when a citation is first added in note styles
Closes #1298, issues with footnotes and citations in OOo
Closes #1069, Use async HTTP calls for integration requests
Closes #1027, User-customizable integration port number
Closes #698, Migration away from VBA
Closes #1085, Migrate VBA plug-in to new XML-based API
Closes #792, Auto-updating of OO plugins
It doesn't look too hard to do, but are we sure we want to do this? What if the plug-in is updated to a version that's incompatible with the current version of Zotero? Or will we only push plug-ins that are backwards compatible?