On 13-May-07, at 8:52 PM, Tim Jones wrote: > On May 13, 2007, at 12:48 PM, Norman Palardy wrote: > >> On 13-May-07, at 1:21 PM, Tim Jones wrote: >> >>> Does that make it more clear? Is anyone else not getting my >>> point in >>> this or am I simply not typing clearly? >> >> And you run the same risks with Apple or even MS tools >> What do you do if you were a successful VB 6 developer ? Or FoxPro ? >> Or a Mac developer that relied on CodeWarrior ? > > Apple (best) and MS both will always provide developers with the > tools they need ahead of public release. We've been building and > testing for Leopard for 8 months now. And we had our Vista tools 13 > months before the public got access. To do otherwise would not only > kill the ISV marketspace, but also the OSes as the apps would dry up.
Both have killed tools and screwed developers that used them Hypercard, opendoc, foxpro, vb6 >> There are risks with every choice and how you mitigate and deal with >> those risks is what's important. > > That's an answer from someone who's not weighed all of the issues - > your broken leg doesn't hurt me, so it can't really be hurting you. > And, you keep coming up with these answers, so I'll just step away > from this now. However, that - getting back to Karen's original post > - is why many of us avoid 3rd party plugins. Granted, I've found MBS > to be a very risk-free add-in. It's not a risk some of us are > willing to take. I've been down this road successfully and been part of teams that have successfully released products with third party code in them It's possible if you really want to make your product happen >> Third party items in RB are no different and arrangements can be made >> to deal with the perceived risks > > How do you make arrangements with the author that no longer maintains > their code nor has any interest in doing so - aka, the Doggie Spa > owners n Sedona? They dropped it, they're done, your screwed. > Again, getting back to Karen's original post - this is why many of us > either write our own features or don't use RB for more than simple > solutions - in a previous post you compared the work by XSliva and > then admitted that the bulk of the UI is custom work. So, without > the custom work, were do that leave RB developers? You do that BEFORE hand, not after. Negotiate an escrow license where you get source if they don't meet some criteria. But you have to do it before hand. Their custom work uses plugins, declares, some very talented artists and programmers > Ah well, I know my reasons and you know yours. Let's just agree that > we disagree and stop trying to sell each other. Fair enough I really was interested in what it WOULD take to get people who prefer not to use plugins to use them. That is really where the talk at the conference was headed anyways. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
