Long name of this stack

2003-07-23 Thread Ray Horsley


I'm just starting to use OSX on the Mac, and I've noticed the long name of
this stack doesn't start with the name of the volume.  I've always used
this to determine the name of the volume the stack is on.  Does anybody have
any ideas as to how I can get this information on OSX?  The only work around
I can think of is to get all of the drives and then start guessing, but
that's not really bullet proof if there's another stack of the same name on
another volume.

Thanks,


Ray Horsley
Developer, LinkIt! Software

___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: Long name of this stack

2003-07-23 Thread Jeanne A. E. DeVoto
At 8:04 AM -0700 7/23/03, Ray Horsley wrote:
I'm just starting to use OSX on the Mac, and I've noticed the long name of
this stack doesn't start with the name of the volume.  I've always used
this to determine the name of the volume the stack is on.


Paths on the boot volume don't include the name of the volume. (The boot
volume - instead of the desktop - is the filesystem root in OS X, so
there's actually a reason for this.) If the file is on the boot volume, the
path will look something like:

  /Applications/Test Apps/mystack.mc

but if it's on a non-boot volume named, say, Backup Disk, the path will
look like:

  /Volumes/Backup Disk/Applications/Test Apps/mystack.mc

So the path is unique even though it doesn't include the boot volume. If
you need the boot volume's name, it's the first one in the drives.

--
Jeanne A. E. DeVoto ~ [EMAIL PROTECTED]
Runtime Revolution Limited - Software at the Speed of Thought
http://www.runrev.com/


___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: Standalone Builder question

2003-07-23 Thread Klaus Major
Hi JB,

Hi list,

I'm about to do something I haven't done
before : build a MC standalone for Windows
on a Mac (OS 9).
So I guess I simply need to select the MC Win
engine, and that's all, right ?
This has been described before on this list so
I guess it shouldn't be a problem...
Yes, that's the way it works :-)

You may have to type the path to the win-engine manually,
since the choose button will not show the mc.exe, but then it works...
Beware to doubleclick that EXE file, because the some resource is added
which says I am an apple app :-) and so that would not be a good idea 
;-)

But that resource will be lost anyway once that file arrives on some 
win-hd :-)

Be sure to test it carefully before shipping :-)

You'll never know...

And there may be some font issues, too...
Hey, its windoze ;-)
So doublecheck, please :-)

However I have a question regarding the
resource mover : can I move resources like
ask  answer dialogs to my stack on Mac
(before building the standalone of course)
so that they'll be recognized on Win ?
Yes.

Thanks,
You're welcome :-)

Hope that helps.

Regards

Klaus Major
[EMAIL PROTECTED]
www.major-k.de
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: Standalone Builder question

2003-07-23 Thread Alain Farmer
Hello jbv,

 I'm about to do something I haven't done
 before : build a MC standalone for Windows
 on a Mac (OS 9). So I guess I simply need to
 select the MC Win engine and that's all, right ?

Affirmative.

 can I move resources like ask  answer
 dialogs to my stack on Mac
 (before building the standalone of course)
 so that they'll be recognized on Win ?

Yes.

Go forth and be happy!  ;-)

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: Standalone Builder question

2003-07-23 Thread Alain Farmer
 You may have to type the path to the win-engine
 manually, since the choose button will not
 show the mc.exe, but then it works...

Very good point, Klaus.

My *easy* workaround is to put both engines in the
same folder. In the build standalone dialog, you
select the Mac engine, and thereby get the full path
to the folder that contains both engines. All you have
to do is change the last item of the path, e.g. the
filename, so that it builds with mc.exe instead.

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: Standalone Builder question

2003-07-23 Thread Shari
And there may be some font issues, too...
Hey, its windoze ;-)
I encountered font issues.  Even with the most generic font I could 
choose, it doesn't always look the same on Windows.  Ditto for some 
colored graphic objects I was using.  Ditto for some color blends, 
that were supposed to be cross platform, but looked different on each 
platform.  I ended up writing a startup handler to get the OS, and 
make certain changes to the objects/fonts of the affected areas. 
That worked like a charm.

As a Mac person who just released my first two Windows programs, I 
HIGHLY recommend that you test it on a Windows machine thoroughly 
before releasing it.  Not all things work the same, I discovered. 
The convert command, for example, gave a different result on Windows, 
because it was a negative number being converted.

Shari C
Gypsy King Software
--
--Shareware Games for the Mac--
http://www.gypsyware.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: MC IDE discussion list

2003-07-23 Thread Richard Gaskin
 Quote Actually, I would not mind continuing such a
 general list for metacard as we have now. The Rev list
 has more noise and significantly more traffic. People
 who would likely remain on the MC list will be the
 hardcore MC users and thus likely interested in at
 least theoretical participation in changes to GUI. A
 separate list for GUI developers can be always spun
 off if the situation warrants it./quote

I like it because it takes a step out of the process. ;)

To some degree this has been happening naturally already:  most of us on
this list also subscribe to the larger Rev list, so if this list has a
little more IDE-specific traffic and maybe a less language discussion than
some would prefer, then there's already a great community for that.

But moreover, I don't think there are likely to be very many IDE-specific
posts, since it seems what most MC users want is to maintain iits
simplicity.

I guess all we need now is for someone from the mother ship to lay down some
ground rules on the mechanics of this process.  Dr. Raney, what's the word?

-- 
 Richard Gaskin 
 Fourth World Media Corporation
 Developer of WebMerge 2.2: Publish any database on any site
 ___
 [EMAIL PROTECTED]   http://www.FourthWorld.com
 Tel: 323-225-3717   AIM: FourthWorldInc

___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Buggy post url cmd - socket stays open

2003-07-23 Thread Alain Farmer
Hello Scott and y'all,

I have a persistant problem with the post url syntax
of MetaCard 2.5, as I did with 2.4 as well. The client
is a MetaCard 2.5 stack with the following handler in
a button :

on mouseUp
  put http://www.giguere.uqam.ca/; into myHost
  put myHost  XA/MenusXApost.cgi into myURL
  if the openSockets is empty then
post field 1 to url myURL
if the result is not empty
then answer the result
else answer it
  else
beep
  end if
end mouseUp

The CGI program on the server-side is a
HyperCard-based CGI which performs marvelously. It
returns the minimum set of HTTP headers required by
MetaCard. The proof of this is that the first click on
the above button indeed returns what it is supposed
to. Btw, I am using Webstar 2.1 on MacOS 8.6 on the
server-side.

The problem arises after the first click of this
button. On the second and subsequent clicks of this
button, the handler beeps, e.g. the openSockets is not
empty which, IOW, means that the socket remains open
after the first click. In fact, it (the socket)
*never* closes, and this inhibits it from doing its
thing more than once.

My diagnostic, therefore, is that there is a bug in
MC's post command whereby the socket that is opened is
never closed. Please fix this *bug* by making the
socket close automatically ASAP after the reply is
received by the MC client. Or give us the new syntax
we need to *close* the open sockets ourselves.

If you disbelieve my account, then feel free to
download a copy of my client stack which exhibits this
problem :

  http://ufp.uqam.ca/MC/test_url_stuff.mc.zip

Thank you for your time and earnest work,  :)

Alain Farmer

NB: This is relatively URGENT for me. Please respond
as soon as you can [Scott]. It has nothing to do with
the interface; this is clearly an engine issue.

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard