--
You received this message because you are subscribed to the Google Groups "Cache Server Page" group.
To view this discussion on the web visit https://groups.google.com/d/msg/cache-server-page/-/0aJgE6OlFPYJ.
To post to this group, send email to cache-se...@googlegroups.com.
To unsubscribe from this group, send email to cache-server-p...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cache-server-page?hl=en.
I can eat, sleep, and breathe CSP on a modern version of Cache', no
problem. The thing I'm not used to (and having a bit of trouble with)
is configuring CSP properly on Release 4. The tools like Object
Architect and the configuration are foreign to me. Not bad, just really
different. I'm used to going into the Studio and just banging out a
class.
You can't do that on Release 4. The cube and Studio are vastly
different to what we're used to. That's all.
I'm getting the rhythm of it. I was able to translate a good bit of my
content management system from Cache MVBasic into COS (even COS is a bit
lobotomized in Release 4; again just not what we're used to in modern
Cache').
Rather than make tagged CSP pages, I wrote a content manager that
operates as classes. That lets me leverage existing routines in the
system with little to no change. In my last position, it was MVBasic
routines. In this new job, most of the back-end code is straight MUMPS,
not even COS.
One of the goals of my new job is to convert a lot of the straight MUMPS
routines into real COS classes with methods and properties. I'm one of
two people in my department who's had that kind of experience with
Cache'. So, my supervisor, the DBA, and I are trying to map out a
course with the least pain on the programmers' part. There are many
other factors in the mix, but that's the short version.
Our first goal is to get to Release 5 and begin converting straight
routines into more object-oriented programming. Once that project is on
its way, we hope I can start writing more web-based offerings to provide
up-to-the minute information on the company intranet. It's extremely
doubtful that any of those web-based processes will be served on the
company public web pages.
From what I understand, it's much easier for us and for InterSystems if
we follow an upgrade path to get to at least, say, 2007.x or 2008.x.
From there it's a lot less internal agony to get to 2012 (where I'd love
to see us).
So, insofar as CSP goes, I did find Release 5 docs on the InterSystems
site. The architecture described in the Release 5 docs more closely
resemble what I'm used to with, say, 2008 to 2012. Not exactly, but the
design methods are similar. Release 4 is a whole-nother animal; CSP is
a bit primitive and the design tools are clumsy as compared.
I'm in a place where I have to "run what they brung" and make the best
of it until we can figure the best way upward. Before I started this
new job I got in contact with Stephan Angevine at InterSystems on
another issue (starting up my own project to develop an eco-farm
management package) and he forwarded my name to the engineer who's in
contact with the company I'm working for now. I haven't heard from or
met him yet, but I'm sure we'll soon be in touch. No panic; the
projects I'm working on for this company are going to take some time and
planning.
Again, thanks for your post.
Bill