A couple of changes

[sub]

lol

[dottore]

will you provide something like a skeleton for the plugin-developers? this would make the switch easier and of course faster.

i didn't understand everything in this thread, since it is very technical english, so excuse me if i ask: do you plan to provide basic ui-elements like buttons, checkboxes, lists, numeric steppers and similar?

i had the idea, that one could put the background-composite-image in the BaseSkin.xml and this image could be kind of "extended" in the plugin-skinfiles. so the size and background-image and maybe other elements could be inherited and you could overwrite and add elements. so you could provide list-elements and just add additional information like filesize or tracksize in the plugin-skin-files.

just an idea!

[DaveC]

lol

Always happy to amuse you, Sub ... seriously though ... could these extensions (new methods) not live in IMenuTask? Asking cause I just do not know that much gory detail, not suggesting it is THE way ... likely lots of reasons it would be bad, just do not know ...

[sub]

I've got a mostly written document that describes things the developer should be doing (like keeping button names consistent for skinning etc), but this isnt quite finished. With this I intend to provide a sample plugin that does these things.

i didn't understand everything in this thread, since it is very technical english, so excuse me if i ask: do you plan to provide basic ui-elements like buttons, checkboxes, lists, numeric steppers and similar?

I'll implement screen that uses a checkboxes etc for changing settings, but these will only be for that screen. They wont be generic ui-element for use in other plugins screens. I dont really want to go there. I've only got very limited time I can waste on this kind of stuff, and this isnt something that interests me.

i had the idea, that one could put the background-composite-image in the BaseSkin.xml and this image could be kind of "extended" in the plugin-skinfiles. so the size and background-image and maybe other elements could be inherited and you could overwrite and add elements.

I have been thinking about this type of thing, but I dont intend to do anything more at this stage. Limited time again. I've got way way too much on my plate already.

so you could provide list-elements and just add additional information like filesize or tracksize in the plugin-skin-files.

I probably wouldnt go there. See my comment above about not provide ui-elements for developers.

[sub]

Always happy to amuse you, Sub ... seriously though ... could these extensions (new methods) not live in IMenuTask? Asking cause I just do not know that much gory detail, not suggesting it is THE way ... likely lots of reasons it would be bad, just do not know ...

I dont want to break compatibility with the existing IMenuTask plugins, so I wont be adding these new methods to this interface. By implementing it as a new interface, I can easily tell which plugin support it, and which dont.

[DaveC]

Thanks for the quick and nice answer to a rather stupid question (was thinking the interface could be optional) -- DUH, obviously it would break every plug ... :o

[psycik]

sub, will this document cover things like gettemporarybitmapfromcache and the like to describe the most effective use of memory for plugins??

Not so much a how to, but a how you should??