> I've seen pictures of the display you can generate with 3D data.
> I've looked at the options screen. It seems you (Sunsoft compiler
> folks) invested some effort in the tool.
> I know there are times when people want to see graphical
> representations of data arrays. But I've never needed it. I often
> find that nobody sees the world like I do. Do most developers place
> a higher value on contour maps of 2D arrays than a graphical
> representation of their data structures?
You're right; I suspect most developers prefer data structure graphs
over array visualization. But the visualization tool was done by the
performance computing group, so the exact components that go into the
release is also a resource issue.
Quote:> I understand the next version of the workshop is out for Sparc,
> and will be out soon for my system, Intel. Will this version have
> a Data Inspector that can plot the data structures like the previous
> offering did?
WorkShop 5.0 is not out yet, but it will be soon. It will be released
for sparc and intel at the same time. It does not have a Data
Inspector; as I said it is still at the prototype stage.
> While I have your attention:
> Is there a way to import all of the environmental variables
> into the build code? I can't use the build command, for reasons
> I describe below, but when I did, specifying all of the variables
> I needed was tedious and error prone.
I don't quite understand what you're asking. Do you mean the
environment variable editor in the Build Tool? Then the answer is no
(but in WorkShop 5.0 the answer is yes).
> The vi editor in the workshop moves the, uh, "active insertion
> point", to where the mouse points when I click on the vi window to
> bring it to focus. The vi default directory changes when I edit a
> file in a different directory. I understand these are probably
> nice, but I would rather have vi behave like I'm used to having it
> work. Can these features be turned off?
No. Of course, the mark is only moved if you single click on a window,
so double click instead to bring it into focus. I use the Front key,
and F2 when I'm on a PC keyboard. The vi directory scheme was based on
usability studies and you cannot change the current behavior. I'll
file a request to make this configurable in the future.
> What seems like a bug is that the vi window starts up about two
> chars less than it needs to be in order to display the standard 80
> char line. It sometimes looses it's place, like a vi session with
> the wrong termcap, unless I manually pull the window wider myself.
> The window would be large enough, but it looks like nobody took into
> account the two or three extra chars that are used to draw the
> symbols for brake points and to show the next statement to be
You are correct. The terminal emulator code has been cleaned up
substantially for WorkShop 5.0.
> I've stopped using the build option in the workshop. The build
> operation would crash the workshop with core dump, not always, but
> with a monotonous regularity that made build unusable. Now I compile
> from the command line, no big deal, and witness the source browser
> database build crash about a quarter of the compiles. This happens
> outside the Workshop, and after the executable is generated, so it's
> a minor annoyance. But it means I can't use the feature of, when
> compile errors are found, having the offending lines displayed, and
> having the vi screen to to them with a mouse click. I had a
> frustrating experience trying to have this problem resolved with what
> passes for sunsoft support. Has anybody else reported this problem?
> Are any of these issues being addressed in the next Workshop?
Yes, a large number of bugs have been fixed in WorkShop 5.0.
Also, it sounds like you have not installed the patches for
WorkShop 4.0. These should fix some of your problems.
Get the jumbo patches for WorkShop IPE, dbx and source browser
and other components you have here:
> Despite this long list of problems, I actually like the Workshop
> de*. It's just that it could be so much more.
> Thanks for responding to my original question. And I mean this,
> thanks for a very nice tool in the workshop.
Hope that helps,
| Developer Environment & Tools Sun Microsystems, Inc. |
| Speaking for myself, not for Sun Microsystems. |