cocoaforge

What (need specifics) needs to be changed on the server side for this to work? Just change urls to adiumxtras://?

Besides the handler change IIRC the compression is the major hang-up (.sit [not supported in the xtra handler but is on site] vs tar.gz [in handler not site])

If we can add support for zip too I think that would cover the majority of compressions that users would upload.

Yay for catch-alls *listens for Catfish_Man's groan *

I could enforce archives to be zip files - would a dev be willing to keep me posted on what the outcome of this is, and what is required of me and the xtras site?

I'm supportive assuming it's possible.
Benjamin

I added support for .zip archives (and .tgz, a synonym for .tar.gz) last night

Not sure what info you need, Benjamin; just let me know.

After a year on the forums I finaly get to ask a dumb question. What's quicksilver?

wunderwood wrote:After a year on the forums I finaly get to ask a dumb question. What's quicksilver?

http://blacktree.com/

evands wrote:I added support for .zip archives (and .tgz, a synonym for .tar.gz) last night

Not sure what info you need, Benjamin; just let me know.

Danke sehr

/me goes off to work on something else

Let me know if it needs any more tweaking.

I guess I'm hoping someone can tell me what needs to happen on the server side. This protocol business is new to me.

Let me know - hopefully.
Benjamin

PS - I put up a new mini-feature on the site, which allows me to show a collection of xtras. I gathered all the holiday stuff together for festive customizers :-P

Benjamin wrote:I guess I'm hoping someone can tell me what needs to happen on the server side. This protocol business is new to me.

Nothing exciting at all. Just replace the http:// in the Download link with adiumxtra:// and you get an Install link.

I put up a new mini-feature on the site, which allows me to show a collection of xtras.

Neat

What are the implications -- does it involve an update to the Adium application to recognize it? Do I need to make changes to the httpd config to understand it?

What happens to people with an older version of adium. Do I need to make it a user-cookie based pref whether they are http or the other?

What about people that package with readmes and other extra files - what about the folders with more than one version?

Let me know. Thanks.
Benjamin

Benjamin wrote:What are the implications -- does it involve an update to the Adium application to recognize it? Do I need to make changes to the httpd config to understand it?

What happens to people with an older version of adium. Do I need to make it a user-cookie based pref whether they are http or the other?

What about people that package with readmes and other extra files - what about the folders with more than one version?

Let me know. Thanks.
Benjamin

The current svn versions register themselves as the system handler for adiumxtra://; as far as I know no server side changes are needed beyond that (I tested on my comcast account, which I don't really have the ability to mess with much). I suggest looking at QuickSilver's download page. IIRC they have an install link (qsinstall:// or something like that) and a download link (http://). The installation code (rather than the downloading code) is unchanged from 0.7, so if you want to test how it works, just double click on xtras and see if they're installed. If they aren't, then they won't be by the downloader.

<edit> Note that the code has a check in it to see if the xtra is from adiumxtras.com, so if you want to use another domain for testing that'll have to be turned off. </edit>

Benjamin wrote:What are the implications

Good questions, sorry I didn't answer more fully before.

Does it involve an update to the Adium application to recognize it?

Yes. Currently .8 (development source) supports it; we could easily port this to the .7x tree. In any case, it will need an update.. in fact, it would make sense to have it included in builds before we start using it to minimize problems with people not having the right version. I'll move the code into .73 before we release... it clearly won't do anything yet, but it'll be there waiting.

Do I need to make changes to the httpd config to understand it?

I don't think so. I'm not an httpd person though...

What happens to people with an older version of adium. Do I need to make it a user-cookie based pref whether they are http or the other? What about people that package with readmes and other extra files - what about the folders with more than one version?

As Catfish_Man said, it would make sense to have a Download link and an Install link side-by-side. This is because 1) Old versions will not support Install and 2) Packages with readmes and other extra files aren't going to install properly. It might be necessary, then, for 'enable automatic installation' to be an option when submitting xtras, with an explanation of the criteria for automatic installation (packaged as a .zip or .tar.gz file, which contains only the xtra itself and no other files).

Thanks evands - it's getting clearer to me now. So, we can plan to institute the changes with a release of .8 -- can you let me know publically or otherwise about what kind of timeframe we're talking about?

Thanks!
Benjamin

Benjamin wrote:Thanks evands - it's getting clearer to me now. So, we can plan to institute the changes with a release of .8 -- can you let me know publically or otherwise about what kind of timeframe we're talking about?

Thanks!
Benjamin

I can send a build to you for testing if you like (with or without the domain check), although from asking on #adium it should be in 0.73b2.

If we had a get info button for xtras so that a readme could be displayed, that'd kill the need for an extra one to be built into the same zip, it could be built into the xtra and probably be more intuitive.

The_Tick wrote:If we had a get info button for xtras so that a readme could be displayed, that'd kill the need for an extra one to be built into the same zip, it could be built into the xtra and probably be more intuitive.

I like the idea of including it in the xtra itself.

although from asking on #adium it should be in 0.73b2.

Confusion on this point is 100% my fault. Initially, I thought (as I posted above) that we should just include the functionality in 0.73. However, after a bit more consideration, I realized that we may want to implement installation a bit differently -- say, allowing for multiple xtras to be installed by a single download in some way, or handling non-xtra files within the package in some way, or something -- and having versions "in the wild" which respond to adiumxtra:// but don't do it the way we really want would be a giant mess. I therefore pulled registering for the handler from 0.73.... it'll be less confusing to just say "Automatic installation requires 0.80 or better" or whatever.

Benjamin, I'd give you a time frame on 0.80 if I could... best I can do is that it should be at least a month, possibly more. Lots of big stuff coming, much of which is partially complete, and the .7x series is stable enough that we're not feeling incredibly pressured to push it out the door before it is ready. So, um, next year sometime, and not a huge rush. :-)

Bad Evan, no ETA! ETAs are :twisted: