Hi Jon, Im the first one to jump on the detonate button when it comes to idiosyncratic software i can't control. And rev really hit me where it hurts the most last time with teh GM. I bought Rev so i could have their GM and it became my biggest nightmare...
6 months later, i wrote my own and im 4X better off... And unless Rev comes out with the significant bug fixes i've been waiting for, im not upgrading... at work (enterprise), or at home (studio). Now, that's the casual bug i run into. I got a few 100's bugzillas and i keep creating them. And i think that when these will be fixed, like many others, i'll have to shell a license upgrade. Uh, that a big rant. Dont hate, me, im just a factoid... The point is that i learned something from that limitation, created a much more flexible and run-steady GM for rev and MC, and now, scripting is just faster every day... But note we dont all work at the same scale of things... For some a small stack can be daunting, while for others an algoritm in a framework is much harder than the framework itself! Thing is that most people think this is confusing while they dont compare it to another programming environment (most of which are 10X more confusing and tedious) but which many new comers here dont put into the equation. Tried learning C lately? Ever seen a single IDE language "how to get started" in those IDE boxes? Did you have to buy an OS reference on top? Spend a week in a technit website to find one stupid problem? All these are not considered. Many of us started programming in C and didn't ask the Symantec ThinkC or the Metrowerks team how to write C. And this is a major problem when it's compounded with an interface - script api that is just so oblivious to complex myobject = &(new*) thisarray.object++; kinds of constructs. I see a nice boat below, know a sailing boat that comes with sailing instructions? Know a car manufacturer that delivers the rules of the road book along with the insurance tips and all the shortcuts to go to work? You got my point... Second point... (you didn't think it was that easy did you?) practice, practice, practice, practice, practice, practice, practice, practice, compile, compile, compile, compile, compile, compile, compile, compile, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, test, fix a few things and hop, deliver... correct the announcement mail 3 times, fix the url 1 or 2 times, etc... other than that, it's marketing, and that's another manual that wasn't furnished in the damn ide either! One trick: if you build solid software from the start, you wont have to rewrite it again and write bugzillas for the rest... that's the sorcery of software - nobody is perfect in the chain of software - luck for those who practice a lot, there's more than one way to do everything. That's where the skill of programming kicks in... Rev is just a pneumatic-nailer compared to a hammer and box of nails... Whatever you build still needs to be based on solid computing design principles in both the GUI, the program code, the external IO, and the best practical economic benefit for the user. How to use this great-maillist: Did i mention testing? Never deliver a half-made stack for testing! People here hate that. I got one praise for my last winNO2 plugin, only one testing request, and nothing else... Lots of jealous people out there it seems who dont encourage that people test their apps, but if you just ask if they can solve a problem then you'll get a miriad solutions, bug rants, etc... cheers Xavier http://monsieurx.com Keep out - Taoist empty object shooting zone > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jon > Sent: Tuesday, July 26, 2005 16:32 > To: How to use Revolution > Subject: Re: Another Doc Thought > > "But how would you fix this?" > > By making the IDE UI less confusing?!? This is a good > example of why RR is so difficult for the uninitiated, and > still somewhat confusing to the moderately experienced. You > can't be productive when you're not confident that the IDE's > UI is under YOUR control. > > :) > > Jon > > > Bill wrote: > > >That happens to me all the time. I just change the name of > the main stack > >back. I think it happens when you think a particular object > is selected and > >it is actually the main stack that is selected. > > > >But how would you fix this? > > > > > >On 7/26/05 9:12 AM, "Charles Hartman" > <[EMAIL PROTECTED]> wrote: > > > > > > > >>some point (??) I discover that in the locked Inspector the name of > >>my main stack has been changed. (The title of the Inspector window > >> > >> > > > > | | | > > )_) )_) )_) > > )___))___))___)\ > > )____)____)_____)\\ > > _____|____|____|____\\\__ > >-------\ /--------- > http://www.bluewatermaritime.com > > ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ > > ^^^^ ^^^^ ^^^ ^^ > > ^^^^ ^^^ > > > >24 hour cell: (787) 378-6190 > >fax: (787) 809-8426 > > > >Blue Water Maritime > >P.O. Box 91 > >Puerto Real, PR 00740 > > > > > > > >_______________________________________________ > >use-revolution mailing list > >[email protected] > >Please visit this url to subscribe, unsubscribe and manage > your subscription preferences: > >http://lists.runrev.com/mailman/listinfo/use-revolution > > > > > > > > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage > your subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
