On 7 Jan 2012, at 22:04, smajor <[email protected]> wrote:
> On Saturday, January 7, 2012 2:27:26 PM UTC-5, phat bob wrote: > > Please define "tons". 1.3.2 added two new displays which broke Growl when > run on case-sensitive filesystems. > > Read the changelog to start: > http://growl.info/documentation/version_history.php A little bit more than > two broken styles, although maybe "pounds" instead of "tons." > > Visit the googlecode site and check out the "Issues" area for another. You > can see if your issue might be addressed in an upcoming update. Shouldn't be > too much trouble for a dev to find their way around. > > Its admirable that you want to support the devs but I spent a number of > unpaid weekends trying to get 1.3.1 working before eventually rolling it off > 50 machines and putting 1.2.2 back - during which time putting up with the > abuse and heckling from my users. > > I guess that'll teach me to use "free" software then? Oh, hang on, 1.3.x is > the paid for version isn't it? :) > > As someone who is co-support for 1,400+ computers at a University, your long > weekends are, respectfully, your own fault. We'd NEVER roll out software to > 50, 100 or 500 machines without testing! I should have pointed out that the 50 users were the PoC team - we have 500 users running Growl. They still moan and grumble like real users though. My main frustration is that Growl simply broke comparability with almost all applications and the view from the developers is "meh, fix it yourself". We have a bunch of in-house applications, all of which would have required updating simply to support 1.3.x - something we don't have a business case for. We're now back on 1.2.2 and actively looking for an alternative to Growl. This isn't a threat or flame, by the way; just the way it is... > Be it Adobe CS, Office, or something comparatively trivial as an FTP client > or, yes, even Growl. Even though it's been out a little while now, and it's > been rolled into my 10.7 master image, it's STILL in limited deployment > undergoing some testing. I'm comfortable enough with what I've seen that it > will make it into my summer faculty replacement cycle which will encompass > many more computers. We're private sector so have to justify any expenditure and upgrading 12 apps simply because some middleware has broken things doesn't stack up. > > As an aside, you might want to look at Remote Desktop and the task server > feature. While you might have lost a weekend; maybe only 1/2 of one, you > could have automated the shuffling around of Growl. Task it to run the switch > as each user's computer becomes visible, assuming you're not in a position to > have them all running and on the net at the same time. > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/growldiscuss/-/0YH7iXOB8rgJ. > 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.
