#Running 2 TPMs
10 messages in this thread
Kevin,
Sometimes it's convenient to look at two projects side by side. Previously, you
could just duplicate Think C and run them both.
In 6.0, launching a second copy from the same folder gives the message "file
'Symantec C++' (or Think C) is already open."
Fine, but is it really necessary to disable the entire Search menu, and
disallow opening all project files with a double-click? How about dimming just
the menu items that depend on the already-opened translator.
For that matter, why can't more than one TPM read from the translators? Surely
they're not being written to?
A lot of use were hoping 6.0 would allow having several project windows open at
once. I'm not real concerned the feature didn't make it (though it "seems"
simple to add). But I'm kinda bugged that the side-by-side workaround we did
have is gone for no good reason (that I see…).
Other workarounds…I can also duplicate a translator and put the duplicated
files in a new folder. That'll work, except on my PB 140. It has 450K free, but
not 750K. Wah.
There's the Switch to Project menu. A useful thing, but not helpful for
side-by-side stuff.
So, I'd like to see this marked as a buglet, and fixed to allow opening and
seaching even if the translators are already open. (I'd really prefer to see
multiple project windows instead, but I'm not asking for that right now.)
Thanks,
Bill
Give BBEdit 2.5 a try – a demo version is in Library 7 of MACSYS (I think…).
One of the things you can do is open as many THINK C 5.0 or 6.0 projects as you
wish, and if you're running TPM, you can open a specified one in the TPM with a
single mouse click.
(BTW, you don't need to be running either THINK C 5.0 or the TPM in order to
open projects. It helps to have it somewhere on a mounted volume in order to
locate files in the <…> tree, but it's not essential, and it doesn't have to
be running.)
R.
I see I didn't explore the demo thoroughly enough…that's nice. Even though
I've promised "no more buying stuff for awhile", the 2.5 demo hsa me teetering
on the edge.
Now if you could have CMaster in BBEdit text windows there would be nothing
else to ask for, ever again. Well….for a while anyway.
>>>
Now if you could have CMaster in BBEdit text windows there would be nothing
else to ask for, ever again. Well….for a while anyway.
<<<
You should take that up with Jersey Scientific. In the past, I've approached
them about supporting BBEdit from within CMaster, and they've seemed reticent
to do it. Something about how CMaster is so reliant on the reverse-engineering
they did on the THINK C editor, or something…
PopUpFuncs offers some useful functionality; if there are specific CMaster
capabilities that you'd like to see in BBEdit, drop a note and tell me what
they are. It's possible that someone could write an extension for some of
them…
R.
Will do…
I think the three things I use most in CMaster are comment/uncomment selection,
prototype building, and multiple clipboards.
The first two no doubt no doubt could be done with BBEdit extensions if they
havn't already. (Prefix Lines works for commenting, but takes a few more steps
than I'd like. Also, in the demo, the prefix character(s) aren't remembered
between invocations).
Thanks,
Bill
>>>>
I think the three things I use most in CMaster are comment/uncomment selection,
prototype building, and multiple clipboards.
The first two no doubt no doubt could be done with BBEdit extensions if they
havn't already. (Prefix Lines works for commenting, but takes a few more steps
than I'd like. Also, in the demo, the prefix character(s) aren't remembered
between invocations).
<<<<
It should be trivial to write an extension for comment/uncomment. (Actually,
PopupFuncs comes with an xPOP extension to do this.) It should be only slightly
less trivial to write an extension to generate a prototype.
Prefix Lines was actually originally intended for preparing Usenet posting
quotes. It doesn't remember the prefix string simply for historical reasons; by
adding a GetPreference() and SetPreference() call in the right place, you can
make it remember the prefix string. [You're welcome to try this.]
R.
>> if there are specific CMaster capabilities that you'd like to see in BBEdit,
drop a note and tell me
How about bulk comment/uncomment function?
– Burt
"why can't more than one TPM read from the translators?"
The Symantec C++ and THINK C translators are both marked as "memory resident".
This makes compiles faster, since they don't need to be read from disk every
time you compile a file. However, due to the way that the TPM works, this also
means that they have resource forks that must stay open. At this point, the
open resource forks can't be shared.
"is it really necessary to disable the entire Search menu, and disallow opening
all project files with a double-click? How about dimming just the menu items
that depend on the already-opened translator."
All file operations (including Search) depend on the translator for the
project's files being loaded. The TPM can't tell that a given file is a text
file unless it's sucessfully mapped to a translator that it can find when it
loads up. If it can't find the translator, it can't tell the difference between
a text and binary file in the project.
"I can also duplicate a translator and put the duplicated files in a new
folder. That'll work, except on my PB 140. It has 450K free, but not 750K."
Try making a copy of the TPM and the "none" translator. Rename none to be
"THINK C" or "Symantec C++". This should let you browse the source files in the
project, and won't take up that much disk space.
You can also try turning off the memory resident switch for the translators.
Open them up with ResEdit and modify the INFO resource using the template. This
will let you put your two TPMs in one folder, but it will slow down compiles.
We are looking into supporting multiple open projects in a future release. It
is not a simple modification, however.
-phil
Phil,
Thanks for the info and tips. I'll try the "none" translator approach, that
should be fine.
Bill
PS> Didn't mean to grouse, that one just caught me by surprise…
Phil,
Speaking about future releases, I'd like to see an "enhancement" to TPM. How
about adding better window management under the "Windows" menu? Like tiling
side-by-side, top-and-bottom, etc. Multiple files are almost always open, and
it's a pain to rearrange them by hand all the time.
Also, any progress in getting the whole environment more stable when running on
a 68000? Although I have an LC3, I do the bulk of my work on my PowerBook 100.
It works for the most part, but there are certain things I know to avoid unless
I want Think to go down in flames.
-mike