Question about API for Spools

[rich-dobbs-13440]

I'm writing a plugin to integrate the Chromatofore Filament Exchanger that I'm developing with OctoPi. I'd like to let the end-user to be able to use SpoolManager to to keep track of spools of filament that are loaded into the exchanger, rather than the minimally featured database that I'll provide. It seems like the API has just been developed to implement the front end, and its not documented for use by other plugins.

As such, its not obvious how to get the information that I need from the API. If somebody could tell me how to fetch the databaseId, displayName, color, and colorName for the spools and selected spools that would be great!

Also, would it be possible create a stable API for changing the spools loaded into tools, and getting back the spool library in a cleaner, well documented process?

[mdziekon]

@rich-dobbs-13440 I'm not the original author of this plugin, so in the requested topic, I know just about as much as you do. You can try extracting necessary information by reading the code of the plugin, I don't think there's anything much better than that.

---

As for the "stable API" feature request - as I've stated in the main description:

For now, I do not plan to continue any "planned features" work from the original maintainer's backlog (such as remote database support), but focus on bug fixing, code refactoring & minor UX improvements.

Therefore, I'm not planning to implement that myself. However I'm always open to any outside pull requests that would implement this feature. So I'll leave it open and mark as "help wanted".

[rich-dobbs-13440]

Hi Michal, Thanks for your reply. Looking at this, I'll probably eventually implement a good-enough spool manager myself, since the existing spool manager hasn't gathered either a sufficient body of users or support so that I can get by on just using an existing plugin. At this point in time, I'm being stymied by not being able to retract filament and form a good tip for reloading the filament. In my early manual tests, I seemed to be able to do this okay, but the automated tests that I've done recently resulted in a plug that after a short time resulted in the Bowden tube being deformed, resulting in a failure after a handful of filament exchanges. So my project is going slowly, with the plugin coding getting little attention. Frankly, the plugin architecture using Knockout is unpleasant and unmotivating. Best regards, Rich Dobbs

…

On Tue, Dec 19, 2023 at 4:23 PM Michal Dziekonski (mdz) < ***@***.***> wrote: @rich-dobbs-13440 <https://github.com/rich-dobbs-13440> I'm not the original author of this plugin, so in the requested topic, I know just about as much as you do. You can try extracting necessary information by reading the code of the plugin, I don't think there's anything much better than that. ------------------------------ As for the "stable API" feature request - as I've stated in the main description: For now, I do not plan to continue any "planned features" work from the original maintainer's backlog (such as remote database support), but focus on bug fixing, code refactoring & minor UX improvements. Therefore, I'm not planning to implement that myself. However I'm always open to any outside pull requests that would implement this feature. So I'll leave it open and mark as "help wanted". — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEBYTOFVYVSPLSUZUOGZV4TYKIOXHAVCNFSM6AAAAAA46TB6ICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRTGYYDQMZZGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>