Re: Updater
Quote:
|
Re: Updater
Quote:
The plan was to have a plugin that handles several repository-sources, much like /etc/apt/sources.list. It would contain a repo-name + url to an updater config. The config would contain several trees (or to be precise: their package-lists) that repository provides and update them using Updater --> Part 1 is done, you have self-updating packagelists. The same/Another plugin would then parse these package-lists, which basically contain all packages (as in plugins/extensions) in that tree and an URL to their updater config. It would hook itself into the admin menu and allow you to select packages you'd want to install by feeding the url from the package-info to Updater_AddPlugin(). -> Part 2 is done. Second thought: I'll start with a question: Is the same plugin allowed to call Updater_AddPlugin() several times? Then this might be a non-problem, as i only care about installing those packages in the first place and all "new" files could be considered as belonging to the Installer-Plugin. Or does it unload itself when downloading starts or sth? |
Re: Updater
Quote:
PHP Code:
PHP Code:
|
Re: Updater
Quote:
Quote:
Quote:
All of Updater's natives/fowards are only meant to interact with the single plugin that's being updated. The reason for it is to prevent plugins from conflicting with each others' updates. What would happen if you added an external plugin to Updater, and then that plugin itself included Updater support? It sounds like you're looking for natives like these: Code:
|
Re: Updater
Quote:
PHP Code:
|
Re: Updater
After taking a peek at the code, it would indeed be tedious to implement what i'm trying to achieve without changing the whole concept.
Basically i would like to use the downloading+parsing but without the forced plugin relation. I don't want to reinvent (the axis of) the wheel, any chance you could remove the plugin-specific stuff from your download-queue + parsing stuff and expose them as natives? I might have missed something here because i only skimmed through, sorry if thats the case ;) E.g.: Create a function that takes an updater-url and downloads it. Create another function to parse it for version information etc. Create another function to download all files it mentioned. Use these functions yourself, re-adding any plugin-relations you had before outside of their scope. Expose these functions. -> Both of our ideas should be doable then, using the same core. |
Re: Updater
|
Re: Updater
Quote:
|
Re: Updater
Maybe this?
|
Re: Updater
That explains a lot, thanks. lol
Figured it was your plugin since it started to happen right after your last update. lol |
All times are GMT -4. The time now is 19:40. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.