Very slick code by the way. I don't like how the code is being used within Disco (as you might have been able to tell from the tone of my post ;-) But I love the effect itself. Very cool. Very interesting looking at the cikernel code too. Very slick indeed.
Justin Williams
· 3 years ago
For some reason I sense hostility towards smoking windows in this post. :-P
Kevin Hoctor
· 3 years ago
"Bad developer. No cookie."
Wow, that just hit me as so funny. Thanks for the laugh!
Brian Ball
· 3 years ago
Wow! Whoever coded that smoking framework must be a genius.
Also, it's great that you made this post public so their lawyers can contact you easily.
Keep up the good work!
dave
· 3 years ago
wow, this is cool. I was too late to get Disco with the intact headers, but yours worked just fine, as did changing the settings in disco. Smart thinking, thanks for sharing this!
Indigo
· 3 years ago
hay, i am on an intel mac and i can't get it to work. it just won't start. as soon as it starts to start, i quits. any help?
schwa
· 3 years ago
Brian: I've chatted with one of the developers of Disco, and the developer of the smoke effect actually commented on this post earlier. I'm not really worried about being contacted by anyone's laywers.
Brian Ball strikes me as an odd duck. First he grabs people's names and email addresses from the macsb mailing list (and then spams them) to promote MacZot. Then he comments here about lawyers.
That's just silly.
David Young
· 3 years ago
I dunno man, while it's true that anyone with class-dump could've reverse-engineered Smoke.framework on their own, it certainly looks like a lot of effort went into engineering it. Ripping it off (especially if one were to link to the framework and redistribute it) seems pretty uncool. If I were the developer, and the smoke effect turned up in a bunch of applications, I probably wouln't waste money on a lawyer, but I wouldn't be happy either.
But, if you've chatted with one of the developers and he/she says it's okay, no harm done. Have the developers really confirmed that they meant for other developers to use Smoke.framework? (Having removed the headers from the shipping product indicates to me that the answer is probably no...)
schwa
· 3 years ago
David Young: Yes ripping it off and redistributing it, especially if I had tried to pass it off as my own work would have been uncool. But I didn't do that.
The DiscoApp developer I smoke (Austin) even mentioned sponsoring a contest for the best smoke related hacks with free copies of Disco to the winners. Basically I think that they look at this as extra free publicity.
Libb
· 3 years ago
Forget NNW, I want NewsFire to burn baby burn :)
Awesome hack, wish I knew Objective-C so I could actually make use of it, but still cool.
Peter
· 2 years ago
"...that Disc burning program that does a fraction of what Disk Utility does"
There's really only one feature of Disco that interests me, and that's "Spandex". Given the above statement, can Disk Utility do what Spandex does, and if so how? It's something I've been trying to figure out for some time.
Matt
· 2 years ago
"There’s really only one feature of Disco that interests me, and that’s “Spandexâ€"
Spandex is nothing special, it actually doesnt seperate large files, it just splits up the directories amoungst multiple discs... wupdidoo. So if you have one huge video file, it won't even be able to span.
Brad Choate
· 2 years ago
So can the amount and density of the plume be derived on a combination of memory and CPU usage? So once you have a couple of dozen tabs open in Safari, it should look like Rome burning?
Kelvin
· 2 years ago
"Spandex is nothing special, it actually doesnt seperate large files, it just splits up the directories amoungst multiple discs… wupdidoo..."
That's quite true but there's a certain derision in the post about how Disco is charging for features that are available free in Disk Utility. I think there's some value in the streamlined interface that does automatic spanning and indexing and automatically chooses the type of disc to be burned based on the context of the files being thrown at it.
While most expert users would have no use for this I could see a lot of novice users finding a use for a utility like that (I don't know how many times I've had to explain that you can't just burn MP3s or VIDEO_TS folders as normal data CDs and expect them to work in the normal media players...)
I think the main problem though is that demographic is one of the least likely type of users to look on the internet for a third-party shareware solution.
David
· 2 years ago
Never mind "novice users". Real world users, ie people who use computers to do useful things, rather than people who use computers to use computers, I think would find this pretty good. Maybe it would be fairer - and considerably less disingenuous - to compare with Toast. I don't Toast has got anything like "Discography".
Ankur
· 2 years ago
Thanks for making this known. I've had a lot of fun with the smoke.
However, it doesn't work when using the framework from Disco 1.0. I've taken another class-dump, but I can't beat the errors. Maybe I should've kept a copy of the beta version... Anyone got any ideas?
All Comments
Very slick code by the way. I don't like how the code is being used within Disco (as you might have been able to tell from the tone of my post ;-) But I love the effect itself. Very cool. Very interesting looking at the cikernel code too. Very slick indeed.
Wow, that just hit me as so funny. Thanks for the laugh!
Also, it's great that you made this post public so their lawyers can contact you easily.
Keep up the good work!
Dave: glad you enjoyed it.
Indigo: You're on your own :-)
class-dump Disco.app/Contents/Frameworks/Smoke.framework/Versions/A/Smoke
I don't know why they bothered to take them out.
(class-dump is available from http://www.codethecode.com/Projects/class-dump/ )
That's just silly.
But, if you've chatted with one of the developers and he/she says it's okay, no harm done. Have the developers really confirmed that they meant for other developers to use Smoke.framework? (Having removed the headers from the shipping product indicates to me that the answer is probably no...)
The DiscoApp developer I smoke (Austin) even mentioned sponsoring a contest for the best smoke related hacks with free copies of Disco to the winners. Basically I think that they look at this as extra free publicity.
Awesome hack, wish I knew Objective-C so I could actually make use of it, but still cool.
There's really only one feature of Disco that interests me, and that's "Spandex". Given the above statement, can Disk Utility do what Spandex does, and if so how? It's something I've been trying to figure out for some time.
Spandex is nothing special, it actually doesnt seperate large files, it just splits up the directories amoungst multiple discs... wupdidoo. So if you have one huge video file, it won't even be able to span.
That's quite true but there's a certain derision in the post about how Disco is charging for features that are available free in Disk Utility. I think there's some value in the streamlined interface that does automatic spanning and indexing and automatically chooses the type of disc to be burned based on the context of the files being thrown at it.
While most expert users would have no use for this I could see a lot of novice users finding a use for a utility like that (I don't know how many times I've had to explain that you can't just burn MP3s or VIDEO_TS folders as normal data CDs and expect them to work in the normal media players...)
I think the main problem though is that demographic is one of the least likely type of users to look on the internet for a third-party shareware solution.
However, it doesn't work when using the framework from Disco 1.0. I've taken another class-dump, but I can't beat the errors. Maybe I should've kept a copy of the beta version... Anyone got any ideas?