Updating a skin

[Matt]

If anyone has troubles updatings your plugin or skin let me know. I received a couple emails from the website regarding upload errors.

if you are able to update no problem, also let me know.

thx

[drewkeller]

it won't let me upload the skin file although it let me update the description text and the graphic. the error field was blank. i'll email the skin file to you.

apparently there is a 100k limit on the graphic size? i had a bmp that was actually smaller than 225x225 and i got the 100k limit error. perhaps the limit should be added to the criteria

[Matt]

I fixed some bugs and now updating works in Firebird as well as all other browsers.

[drewkeller]

I fixed some bugs and now updating works in Firebird as well as all other browsers. working nicely in FB :)

except there is a field for version info on the page AFTER submitting the skin and there is not an input box on the submission form

also, it would be nice to be able to "preview" the queued skin to make sure i got the right graphic uploaded etc.

perhaps also a message showing how many skins are in front of yours in the queue (does the database know?)

just a few lines of code, right? ;)

[Young Twig]

http://beta.quinnware.com/skins.php?skin=12

Whoa. The skin was made 11/15/2003 and updated on 11/12/2003...

:confused:

[Matt]

http://beta.quinnware.com/skins.php?skin=12

Whoa. The skin was made 11/15/2003 and updated on 11/12/2003...

:confused:

i was wondering if anyone would pick up on that. I'll get around to fixing that little issue.

[Young Twig]

I updated GVB to support resizing of extensions. It was in queue... I saw it. It never got updated. It is no longer in queue. :confused:

[Paul]

I updated GVB to support resizing of extensions. It was in queue... I saw it. It never got updated. It is no longer in queue. :confused:
Your submission was not passed because only skins for the current release are to be posted. You can post your skin for development versions under the Development Builds forum.
You should have received an automatic email about the failed submission.

[Young Twig]

Your submission was not passed because only skins for the current release are to be posted. You can post your skin for development versions under the Development Builds forum.
You should have received an automatic email about the failed submission.
Oh poop. My bad. :(

[Zayoos]

If anyone has troubles updatings your plugin or skin let me know. I received a couple emails from the website regarding upload errors.

if you are able to update no problem, also let me know.

thx
I have problem with upload plugin (update and new plugin) in Opera. I'm geting notification:
"The following problems occured with your upload:
UPLOAD FILE: invalid file type (must be a zip compressed file).
Please fix the problem on the form below."
I'm creating the file with "QCD Plug-in Installer" (September 6, 2003).

With IE i had no problems, my update was successful.

[Xymantix]

Your submission was not passed because only skins for the current release are to be posted. You can post your skin for development versions under the Development Builds forum.

Just out of curiosity, will this affect your release process at all? In the past we'd have development builds for months on end, and a full release a couple of times per year. During that time, we could submit skins that relied on development features, and they were still available via QCD's built-in skin browser in versions of the player that supported them. If devbuild skins aren't available from the internal skin browser anymore, or from the web site's skin section, it seems like there's little incentive to release a skin until the version of QCD that supports the features is released. That's not a bad thing necessarily, but if the active skinners always include new features and the official releases only occur once or twice a year, it seems like the skin submissions would be few and far between as well.

[Paul]

Just out of curiosity, will this affect your release process at all? In the past we'd have development builds for months on end, and a full release a couple of times per year. During that time, we could submit skins that relied on development features, and they were still available via QCD's built-in skin browser in versions of the player that supported them. If devbuild skins aren't available from the internal skin browser anymore, or from the web site's skin section, it seems like there's little incentive to release a skin until the version of QCD that supports the features is released. That's not a bad thing necessarily, but if the active skinners always include new features and the official releases only occur once or twice a year, it seems like the skin submissions would be few and far between as well.
I hear you. But this time there is the difference of having the skins on the website. I don't want to mix skins that will work for some player versions and not others (just a support issue).

Possibly for next beta, Matt can setup the site to send skins that depend on beta features to the player's downloader but not have them list on the site.

[Xymantix]

Yeah, I completely understand the issue raised by mixing skins. I was halfway hoping that it meant more frequent official releases, since the 4.x series of releases has been more regular than the 3.x.

[Young Twig]

Possibly for next beta, Matt can setup the site to send skins that depend on beta features to the player's downloader but not have them list on the site.

That is exactly what I was going to suggest. Just add a note to the skins section about development skins only being available from the internal browser... :)

[Young Twig]

Just out of curiosity, will this affect your release process at all? In the past we'd have development builds for months on end, and a full release a couple of times per year. During that time, we could submit skins that relied on development features, and they were still available via QCD's built-in skin browser in versions of the player that supported them. If devbuild skins aren't available from the internal skin browser anymore, or from the web site's skin section, it seems like there's little incentive to release a skin until the version of QCD that supports the features is released. That's not a bad thing necessarily, but if the active skinners always include new features and the official releases only occur once or twice a year, it seems like the skin submissions would be few and far between as well.
Heh... Yeah. Paul would you be planning on coming out with a release between now and the 23rd? Because I'd like to have the smaller, better GVB up there and I don't want to have to make a not resizable version of Snow... Yeah, I'm lazy.

[Tokelil]

That is exactly what I was going to suggest. Just add a note to the skins section about development skins only being available from the internal browser... :)Personnaly Id prefer a section dedicated to skins developed for betas under the skins section. A link or something taking you to another page showing you the beta skins with a disclaimer that those wont work with officiel releases.

(All spelling mistakes I blame my half drunk mind!)

[Young Twig]

Personnaly Id prefer a section dedicated to skins developed for betas under the skins section. A link or something taking you to another page showing you the beta skins with a disclaimer that those wont work with officiel releases.

(All spelling mistakes I blame my half drunk mind!)
What I was thinking was maybe an option like so:
o - view skins compatible with current release
o - view skins compatible with lastest dev. build

(you like those radio buttons, huh?)

[Paul]

Heh... Yeah. Paul would you be planning on coming out with a release between now and the 23rd? Because I'd like to have the smaller, better GVB up there and I don't want to have to make a not resizable version of Snow... Yeah, I'm lazy.
There wont be a release until at least Jan 10. I'm far away from my QCD machine so I don't have any code to work on, and I won't get back to it until after Jan.