Re: 2.5 Release Candidate 1
On 28/8/04 2:28 am, Alex Tweedly [EMAIL PROTECTED] wrote: No, in fact that's outright common sense. Introducing changes to software carries a risk of unintended consequences - even with the best automated testing methods around, you can't afford to risk making unnecessary changes at the last minute. Right. One example might be making a last minute minor fix to the player that has the result that it no longer loads on startup. This is exactly *why* we won't be making minor fixes to the release candidate. We will be fixing the player issue however :) Kevin Kevin Miller ~ [EMAIL PROTECTED] ~ http://www.runrev.com/ Runtime Revolution - User-Centric Development Tools ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1
The way 2.5 beta was taking forever to access a mysql database when using the linked controls is now fixed. I didn't even have a chance to make a bug report. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
Before I log this to Bugzilla, I just want to check and see if anyone else sees this with the RC1 build - double-click on the Revolution Player and it will get to a point where it says Preparing... and then it freezes (I'm on OS X 10.3.4). If I force quit, there's a file left behind called Revolution Launcher. Anyone else see this? Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
Heck, I didn't even get a Revolution Player in my OS X download. :-( Dan On Aug 27, 2004, at 4:00 PM, Ken Ray wrote: Before I log this to Bugzilla, I just want to check and see if anyone else sees this with the RC1 build - double-click on the Revolution Player and it will get to a point where it says Preparing... and then it freezes (I'm on OS X 10.3.4). If I force quit, there's a file left behind called Revolution Launcher. Anyone else see this? Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
It almost seems like we got different downloads, Dan. There IS a player in my download but the docs definitely still don't work. Dox work for you but there is no player. What gives? And, yes Ken the player hangs for me, too. Just out of curiosity, am I the only person who still gets xmlerr as a response when selecting an item in the dox? M On Aug 27, 2004, at 7:30 PM, Dan Shafer wrote: Heck, I didn't even get a Revolution Player in my OS X download. :-( Dan On Aug 27, 2004, at 4:00 PM, Ken Ray wrote: Before I log this to Bugzilla, I just want to check and see if anyone else sees this with the RC1 build - double-click on the Revolution Player and it will get to a point where it says Preparing... and then it freezes (I'm on OS X 10.3.4). If I force quit, there's a file left behind called Revolution Launcher. Anyone else see this? Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
Re: 2.5 Release Candidate 1 - Player Freeze? From: Ken Ray Subject: Re: 2.5 Release Candidate 1 - Player Freeze? Date: Fri, 27 Aug 2004 17:39:33 -0700 On 8/27/04 7:26 PM, Wouter [EMAIL PROTECTED] wrote: True the player hangs when inside the Rev folder. If one drags a stack on the app icon after the clock cursor has changed to pointer it will open in the player though the home stack won't hide. But the player works like a charm when outside the rev folder and started with a stack. This just shouldn't be... how many people are going to see another app in the Rev folder and 2x-click it to see what it does? Answer: Lots. And they shouldn't be greeted with a hanging application. It should at least say something like Move this out of the Rev folder before launching, although for the life of me I can't understand why it doesn't work in the Rev folder but does outside of it. Correct. But Rev is not really *hanging*. You still can drag stacks on the player icon and they will be loaded. Only minor change in script will resolve this in the final candidate I am sure. That's why they should still accept bugzilla reports or read the list thoroughly. Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] WA ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
This version of Rev seems to be quite sensitive to placement inside folders. See the solution I just posted to why the dox were not displaying for me. I had moved Rev app folder into a folder named Rev 2.5 RC1 and Rev apparently didn't like the fact that it was nested inside a folder with special characters in the name (opt-f, opt-;) M On Aug 27, 2004, at 8:38 PM, Ken Ray wrote: It should at least say something like Move this out of the Rev folder before launching, although for the life of me I can't understand why it doesn't work in the Rev folder but does outside of it. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1
At 20:16 27/08/2004 -0400, yoy wrote: - Original Message - From: Kevin Miller [EMAIL PROTECTED] Subject: 2.5 Release Candidate 1 At this time we are no longer able to respond to minor glitches or annoyances reported. This is because we must change as little as possible in any rebuild to ensure we don't introduce any new issues. C'mon! That's an outright POS comment. Establish a known bugged FC??? No, in fact that's outright common sense. Introducing changes to software carries a risk of unintended consequences - even with the best automated testing methods around, you can't afford to risk making unnecessary changes at the last minute. If you find a major problem, you must fix it; if you find a serious or moderate problem, you have to make judgement - that's why software development managers gets paid big bucks; but if you find a minor annoyance you must not fix it. As the release date gets closer, you have to throttle down on introducing changes to minor bugs and annoyances. I don't know a software company that doesn't use some form of this throttling technique as it gets to final release of large products. You can do it differently for smaller products, where the predictability of unintended consequences is orders of magnitude smaller - but not for medium or large products, and I think Rev must be big enough to qualify for that category. -- Alex. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1
Alex is right. What's more Kevin didn't say RunRev was going to disregard minor glitches, just that fixes may have to wait until a later release. Frankly, I'd rather deal with the devil I know (minor glitches) than with one I don't (unrecognized bugs introduced in the process of last minute tweaks to fix minor annoyances). On Aug 27, 2004, at 9:28 PM, Alex Tweedly wrote: At 20:16 27/08/2004 -0400, yoy wrote: - Original Message - From: Kevin Miller [EMAIL PROTECTED] Subject: 2.5 Release Candidate 1 At this time we are no longer able to respond to minor glitches or annoyances reported. This is because we must change as little as possible in any rebuild to ensure we don't introduce any new issues. C'mon! That's an outright POS comment. Establish a known bugged FC??? No, in fact that's outright common sense. Introducing changes to software carries a risk of unintended consequences - even with the best automated testing methods around, you can't afford to risk making unnecessary changes at the last minute. If you find a major problem, you must fix it; if you find a serious or moderate problem, you have to make judgement - that's why software development managers gets paid big bucks; but if you find a minor annoyance you must not fix it. As the release date gets closer, you have to throttle down on introducing changes to minor bugs and annoyances. I don't know a software company that doesn't use some form of this throttling technique as it gets to final release of large products. You can do it differently for smaller products, where the predictability of unintended consequences is orders of magnitude smaller - but not for medium or large products, and I think Rev must be big enough to qualify for that category. -- Alex. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 [bug# 1962 still broken]
This was bugzilla'd as RunRev instructed me to enter it there. The Bug number was 1962 I have downloaded and installed 2.5 Release Candidate 1. My Rev preferences has the correct http proxy info, yet Rev Online still fails from behind our corporate firewall. Why doesn't it prompt for firewall authentication like all other internet applications? I hope the final release won't be like this. http://www.runrev.com/revolution/developers/bugdatabase/show_bug.cgi?id=1962 Summary: Can not access Rev-Online from behind firewall Product: Revolution Version: 2.5 B1 Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: Revolution Online AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Roger Eller [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
On Aug 27, 2004, at 5:26 PM, Wouter wrote: The player object is produced once Rev is started up once. True. Odd but true. The launcher object is produced once the player is launched. True the player hangs when inside the Rev folder. If one drags a stack on the app icon after the clock cursor has changed to pointer it will open in the player though the home stack won't hide. But the player works like a charm when outside the rev folder and started with a stack. Greetings, WA ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: 2.5 Release Candidate 1 - Player Freeze?
On 8/27/04 6:00 PM, Ken Ray wrote: Before I log this to Bugzilla, I just want to check and see if anyone else sees this with the RC1 build - double-click on the Revolution Player and it will get to a point where it says Preparing... and then it freezes (I'm on OS X 10.3.4). If I force quit, there's a file left behind called Revolution Launcher. Anyone else see this? I've just entered bug #2086. I think removing the word Preparing won't cause too many glitches this late in the game, and would be enough to prevent users from thinking the app has hung. My other suggestion -- to ask for a stack to open -- could be postponed till a later version. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
