Yuck. OPC Projects

I have a lot of OPC projects.  I tend to avoid them when I can but sometimes it’s unavoidable.

Whenever I deal with an OPC project I’m screaming ‘encapsulation!’ half the time and the other half the time I’m screaming ‘container controls’!  Yeesh.  Seems like people are making their lives harder than it needs to be.

The answer, of course, is that programming is not easy and they wouldn’t be paying me to work for them if they could do it themselves.  It’s pays the bills so I guess I shouldn’t complain.

How do we teach RB newbies some of skills that will make their lives easier?

4 thoughts on “Yuck. OPC Projects

  1. One thing that would be nice is a book where a simple project is outlined, step by step, then subsequent chapters go back and rewrite the code to incorporate new techniques and then explain after making the changes why it is a “Good Thing” until at the end of the book you can compare what you began with and what you end up with. Maybe show benchmarks or detail anecdotes to illustrate maintainability or whatever the goal for the chapter would be. That’s one idea.

    Problem with RB is that the audience is too small for the author to make a profit unless either RS sponsors the project or someone decided to do it as a labor of love.

    It would also be difficult to find someone willing to do this that would focus on technique only slightly more than code, as for beginners both would be necessary but a niche product like RB often deprecates or alters functionality (as their own language reference often has code that won’t work in newer versions now…).

    That’s just my suggestion as an outsider who tried dabbling in RB. Take it for what it’s worth.

  2. I have to chime in again because Ive been chasing a big issue with opc in that hellacious financial app that pays my bills……urghhh!!!!!!!

    But…..nothing that a few glasses of wine won’t dissolve:)

  3. In my opinion, one of the issues with training people how to use REALbasic is that the examples RS gives in document and example projects don’t use ‘best practices’ and encourages sloppy coding. RB is easy to use but that doesn’t mean you don’t need to know a few things to help code scale well, make it more efficient, or make complex applications.

    To be fair, the examples and documentation are meant to be easy to understand. So making them more ‘real world’ would do nothing to make the concepts easier to understand for beginners.

    I’m not sure what the proper approach is. If I figure it out I’ll be sure to let people know. 😉

Comments are closed.