Also, to answer your point on why we tell you to contact them. We already have, or will. I find it's more important to respond here to you guys, and to the people emailing support@ than to email every single developer, or contact them in some other way at the moment. I'm working to get back to the point where I can start contacting them again.
Anyhow, on to the point. If I file a single ticket, great, it's a single ticket. However, if the application developer gets a ticket from say, 10 or 20 people, then it becomes more important to them. This is typically how most ticket systems work. So in order for say Skype to make this a priority, then they'd need to see how it's affecting their userbase as a whole. Also, it's good to know when something is fixed, as I'm sure you are aware. So if Skype (in this example) were to close their tickets with a status email saying it's fixed in xyz version, then it'd be good for you to know right? That's my thought at least. Chris On Thu, Oct 13, 2011 at 10:02 PM, Christopher Forsythe <[email protected]>wrote: > So let me be clear here. I replied in the way that I did since most people > don't seem to want the very technical explanation. However, just to make > sure you understand why I said to go to Skype support, I'm going to be as > verbose as I can be without providing what my wife calls a "level 11 on the > geek scale". If this needs to be simpler or more complex, let me know and > I'll try to accommodate. > > Alright, so in Growl.framework 1.2.1, the framework stopped assuming that > Growl was a system preference pane, or prefpane. This was actually a fix > performed by accident, but luck would have it that is what happened. The > framework is what cocoa applications use to talk to Growl typically. So any > application which uses the 1.2.0, 1.1.x, or 0.x line of frameworks are not > going to work with Growl 1.3. This is something that the end user can > address with a workaround, but we're also working on a tool to make this > easier for users, enabling you folks to make things just work while waiting > on application developers to fix things. > > Also, if a developer decided to use the isInstalled method, then no amount > of workarounds will work. They will need to update their Growl support. This > was not something in our documentation, and was intended for Growl.framework > to use the method, but it is what it is and we can't go back now. We must > move forward. > > The problem is that we didn't expect that this would be a very large issue > at all really. One or two applications wouldn't work. But instead it's > happening with more applications than we thought. If we had thought for even > a moment that this would be the amount of feedback we would be getting, the > updated Growl Version Detective to update application bundles with a newer > framework would have been done before we even submitted Growl to the app > store. More or less when the 1.3 sdk is completed, people will be able to > hand replace the Growl.framework inside of applications and they will start > to work again, like magic (yay, magic!). Except for a few apps, like > Spotify, Firefox and Thunderbird for example, since they implemented things > in a different way. > > That said, I'm not a fan of instructing anyone to go into an application > bundle of any other developers apps. It's the workaround we have now, but > the ideal solution would be to have something where you can pick an > application, tell something to update it, and then when it's working contact > the developer to let them know that there's a problem, and that you're using > this modified solution for now. > > So, if and when an application decides to update, if they fix their Growl > support you wouldn't need to reapply the workaround. But if they did, then > you would. > > We're looking at about another week to two weeks on the whole solution for > folks. We also have a crasher in 1.3 that we're working on updating, so we > haven't turned on the update checker for Growl to inform 1.2.2 users on 10.7 > that 1.3 is available. Obviously a lot of people learned from other sources, > but as of yet we haven't sent any announcements out yet. > > I've typed a small novel here, hopefully it all makes sense. If it doesn't > I'm happy to explain any portion a bit further. > > Chris > > > > On Thu, Oct 13, 2011 at 7:14 PM, Chris Georgiev > <[email protected]>wrote: > >> AH, what a answer, isn't Growl your product that I paid for, why the >> hell I need to contact Skype, it's your product that used to be free >> and perfectly working with Skype, now I have to take care of your >> issues, guess what review I will be posting for the app... Guys, >> seriously, have to push and fix that problems.. >> >> best, >> >> Chris >> >> On Oct 13, 1:18 am, Christopher Forsythe <[email protected]> wrote: >> > On the style configuration issue, you'll need to restart Growl for that >> to >> > reflect the changes. We have this fixed in 1.3.1. >> > >> > Regarding Skype, you will need to contact their support, they need to >> update >> > Skype to work with Growl. >> > >> > Chris >> > >> > On Wed, Oct 12, 2011 at 6:28 AM, Chris Georgiev < >> [email protected]>wrote: >> > >> > >> > >> > >> > >> > >> > >> > > Just installed Growl 1.3 on OS X Lion 10.7.1 and can't control the >> > > style and position of notifications at all. I use Skype 5.03 and can't >> > > make him work with Growl - the growl option for the notifications is >> > > inactive so can't be selected. Can you pls advice what have caused the >> > > problem? >> > >> > > -- >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Growl Discuss" group. >> > > To post to this group, send email to [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected]. >> > > For more options, visit this group at >> > >http://groups.google.com/group/growldiscuss?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Growl Discuss" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/growldiscuss?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
