tcl-mac — Q&A for Tcl on the Macintosh platform

Re: [MACTCL] exec on mac

[Jon G. <jg...@hi...>]

At 3:59 PM +0100 3/12/02, Jack Jansen wrote:
>For Python there's an extension module that uses AppleEvents to talk
>to the MPW tool server and thereby provide functionality to
>exec()/system(), through the 'misc'/'dosc' event. You could do
>something similar for Tcl, I guess.

Sure. Either TclAppleScript 
<http://tcl.activestate.com/software/mac/AppleScript.html> or TclAE 
<http://www.his.com/jguyer/Alpha/TclAE%20Help/> can call MPW's 
misc/dosc event.

>This only gives you access to stuff compiled as an MPW tool, not to
>general applications, but for general applications it would be
>unclear anyway what "output" would mean.

Yep, this is the rub. AppleEvents are extraordinarily powerful... 
between agreeable apps...
-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

Re: [MACTCL] exec on mac

[Jack J. <Jac...@or...>]

For Python there's an extension module that uses AppleEvents to talk to 
the MPW tool server and thereby provide functionality to 
exec()/system(), through the 'misc'/'dosc' event. You could do something 
similar for Tcl, I guess.

And MPW understands < and > I/O redirection, so you could redirect 
output to a file that you would then open from your Tcl code.

This only gives you access to stuff compiled as an MPW tool, not to 
general applications, but for general applications it would be unclear 
anyway what "output" would mean.
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -

[MACTCL] BUILD: tcl8.3.4, WodeWarrior 4.1, TclShells.<PI>, sh*SimpleTcl

[<AO...@t-...>]

Hi,

 in the file "tclMacAppInit.c" 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
#elif defined(__MWERKS__)
#   include <SIOUX.h>
EXTERN short InstallConsole _ANSI_ARGS_((short fd));
#endif
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

  the extern procedure "InstallConsole" was *not* defined in <SIOUX.h> 
  and the compilation failed


  what I have to do ??


mfg

  aotto :)

Re: [MACTCL] How-to Changing Type/Creator?

[<AO...@t-...>]

Hi,

>
> find /Volumes/StartPoint -name \*.gif | xargs /Developer/Tools/SetFile -t
> 'xxxx' -c 'xxxx'
>
> SetFile comes on the DeveloperTool CD.
>

  how I get the DeveloperTool CD



mfg

  aotto

Re: [MACTCL] BUG: file join ?

[<AO...@t-...>]

Am Dienstag 12 März 2002 09:49 schrieb Daniel A. Steffen:
> At 9:01 +0100 on 12/3/02, AO...@t-... wrote:
> >this is an absolut path name not relative
>
> no relative
>
> c.f. man n filename
>
> you should use [file join {} a b] to get consistent results, if a
> user has a volume named 'a', [file join a b] will give a:b and not

> file volume
> tcl: tk: ...

> file join tcl b
> :tcl:b

> file join tcl: b
> tcl:b


mfg

 aotto :)

Re: [MACTCL] BUG: file join ?

[Daniel A. S. <st...@ic...>]

At 9:01 +0100 on 12/3/02, AO...@t-... wrote:

>this is an absolut path name not relative

no relative

c.f. man n filename

you should use [file join {} a b] to get consistent results, if a 
user has a volume named 'a', [file join a b] will give a:b and not 
:a:b like you might expect. (the behaviour [file join a b] => :a:b is 
a unix compatibility hack since so many scripts use it, but it's not 
guaranteed...)

the correct crossplatform way to construct a relative path to 
directory/file 'a' is [file join {} a] (or using [pwd])

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>

[MACTCL] BUG: file join ?

[<AO...@t-...>]

Hi,

 > file join a b
 > :a:b

this is an absolut path name not relative

I'm right ?

mfg

  aotto

[MACTCL] BUG: file copy

[<AO...@t-...>]

Hi,

 desktop freeze ...

 If you do a "file copy .." with a large directory on the same volume
 the MacOS 9.1 desktop freeze ( no background copy )

 not only the Tcl application freeze it's the whole desktop 


mfg

  aotto :)

Re: [MACTCL] exec on mac

[Jean-Claude W. <jc...@eq...>]

Andreas Otto <AO...@t-...> wrote:

> I found MPW on "http://developer.apple.com/tools/mpw-tools/" is this right ?
>
> the problem is that are a lot of single files and not one bing download
> is such a one big download is available ?

<ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./
%21ReadMe.txt>

<ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-
GM_Images/MPW-GM.img.bin>

-jcw

Re: [MACTCL] exec on mac

[<AO...@t-...>]

Hi,

 I found MPW on "http://developer.apple.com/tools/mpw-tools/" is this right ?

 the problem is that are a lot of single files and not one bing download

 is such a one big download is available ?


mfg

  aotto :)

Re: [MACTCL] exec on mac

[<AO...@t-...>]

Am Montag 11 März 2002 17:23 schrieben Sie:
> At 3:16 PM +0100 3/11/02, Andreas Otto wrote:
> >  there have to be a way to call additional executables from
> >  a Tcl script
>
> and there is... just not the Tcl norm.

Hi,

 are examples available ...

from main
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
void
main(
    int argc,                           /* Number of arguments. */
    char **argv)                        /* Array of argument strings. */
{
    char *newArgv[2];
        
    if (MacintoshInit()  != TCL_OK) {
        Tcl_Exit(1);
    }
 
    argc = 1;
    newArgv[0] = "tclsh";
    newArgv[1] = NULL;
    Tcl_Main(argc, newArgv, Tcl_AppInit);
}   
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

why does tcl blow away the argv array ?



>
> >  I need the channel output back into a string
> >
> >  I have an additional API for calling external SW ->
> >  does Applescript helps ?
>
> Sure AppleScript/Tclapplescript is one option. My TclAE

Is a download path available ?


 is another.
> In either case, you can get a reply, assuming the external app sends
> one, but it's really not the same as the channel output you are
> probably expecting.
>
> >  does "open |..." works ?
>
> Mac OS 9? No. No pipes.
>
> >  1) is a commandline interface available
> >
> >   cammandline + some kind of exec would be perfect
>
> Neither of these things really exist on Classic Mac. CodeWarrior
> provides for a limited command-line interface in your apps (look for
> docs on SIOUX and ccommand()). If you want your app to execute other
> apps, you'll need to do it with AppleEvents. Tell us more about
> exactly what you'd like to do and we can tell you more about how to
> accomplish it.

Hi,

  the current strategic decision would be using the xml interface of
 code-warrior. Yo can create a Code warrior project as xml file and
 import it into the gui.

 One help would be not only to cretae the xml files, it should be possible
 to call code-warrior to do the compiling and linking themself without
 using the user-interface. If this is possible it would be a big step in the 
 right direction.


>
> >  2) is a cross compiler linux -> macOs9.1 ppc available
> >    gcc does not support MacOs9.1 (this speak for them-
> >    self) perhaps CodeWarrior ???
>
> CodeWarrior has a linux variant. I've never used it and don't know
> what it's cross-compilation options are.

Re: [MACTCL] exec on mac

[<AO...@t-...>]

> If you just want a more command-line oriented development environment you
> might try MPW, there is a version of the CW compiler for this, and MrC is
> also a pretty good compiler.  The MW libc support is better than the
> built-in MPW library, so you might want to use that.


How I can find this software ?

>
> If you want gcc extensions, you are pretty much out of luck...
>
> Jim

Re: [MACTCL] exec on mac

[<AO...@t-...>]

Am Montag 11 März 2002 19:45 schrieben Sie:
> Hi.
>
> I am interested in a command line mode.  I hope that by this
> weekend, I can explore this option.


Hi,

 please keep me up to date, there is a strong need for such kind
 ot tool

[MACTCL] Missing MPW instructions

[macnerd <ma...@re...>]

The link describing how to compile stuff from MPW is missing. :-(
  =20
        http://www.teamwave.com/mactcl/

This was mentioned in=20
 =20
       =
http://tcl.activestate.com:8002/resource/software/extensions/macintosh/

Anyone knows what happened to that information?

[MACTCL] What is required to compile MacTcl/TK

[macnerd <ma...@re...>]

I was looking at the website, and noticed it mentioned that Code Warrior =
Pro 1 or 2 is=20
needed.  Is this true? I find this shocking as the current version is 7 =
now.

          http://tcl.activestate.com/doc/howto/compile.html

Re: [MACTCL] exec on mac

[Franc B. <br...@cb...>]

thanks, Jim ... very perceptive observations ...

I would just like to add that our goal is not only to invoke tcl 
scripts but also any remotely accessible legacy programs or 
web-services "encapsulated" within the tcl script. The "hypothenuse" 
example below could well represent a wrapper for an old fortran/cobol 
executable or a soap-based tcl client such as described under 
http://tclsoap.sourceforge.net/, or whatever. If on mac, tcl may 
invoke applescript, but not otherwise.

A cross-plaform solution that would really make my day (in the 
context of ezample below) would be the one that would allow me so 
"store" intermmediate variables between the exec calls so that there 
would longer be the need to save "output" variable value in a file 
such a 'cValue' used in this example.

Thanks -- franc



>On 3/11/02 3:02 PM, "Franc Brglez" <br...@cb...> wrote:
>
>>  Here is our take on the exec -- if you are interested to repeat our
>>  cross-platform experiment, cut the text below and place it under a
>>  mac, a unix, a linux. a ... directory as the following three files:
>>
>>  @hypothenuse -- to be invoked as 'exec tclsh @hypothenuse' from a 
>>tclsh under
>>                 any platform ( it also uses 'exec' to invoke 
>>hypothenuse below)
>>
>>  hypothenuse -- a simple proc and its main (to be invoked by @hypothenuse)
>>
>>  exec4mac.tcl -- Hemang Lavana's  adaptation for Franc Brglez from
>>                 http://mini.net/tcl/894.html
>
>This isn't a real exec, since it can ONLY run tcl scripts.  But it is useful
>if that is all you need to do.
>
>>
>>  Our requirement is to write tcltk once and run everywhere, including
>>  code that contains exec command. In this context, we would also be
>>  interested to hear from Jim about any follow-up his earlier work under
>> 
>>http://www.usenix.org/publications/library/proceedings/tcl97/full_papers/ingha
>>  m/ingham_html/ingham.html
>
>Well, the part of this paper that is really useful is available on Classic
>MacOS as the tclAppleScript extension.  The other parts described in the
>paper are (a) connecting to arbitrary OSA extensions, and (b) using Tcl as
>an OSA language. 
>
>There is code around from the original version - TcOSAScript, but the only
>other OSA language of any consequence was Frontier, and I didn't get any
>requests to support it, so I took out the complexity of supporting other
>languages in the version shipped with Tcl.  The code would be easy enough to
>revive, if you had a reason.  Using Tcl as an OSA language was never
>terribly interesting, and generally very unstable.  OSA languages run in the
>system heap, and that environment doesn't fit with Tcl's "all malloc's
>succeed" practices...  Vince did more work on this than I did, but I don't
>think it (or the Perl version) ever got very far.
>
>For your purposes, you could also do exec by using TclAppleScript.  The
>problem is that mapping from real exec to AppleScript is not
>straightforward, and the fact that the Mac only spawns off 1 copy of each
>executable, and feeds all requests to it can cause unexpected behavior if
>you are thinking of Unix exec.  Most of the tools you use when you do exec
>are also not present on the Mac.  So I am not sure the attempt to make a
>"cross-platform exec" really gains you that much.
>
>Jim
>--
>++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
>Jim Ingham                              ji...@ap...
>Developer Tools - gdb

Re: [MACTCL] exec on mac

[Jim I. <ji...@ap...>]

On 3/11/02 3:02 PM, "Franc Brglez" <br...@cb...> wrote:

> Here is our take on the exec -- if you are interested to repeat our
> cross-platform experiment, cut the text below and place it under a
> mac, a unix, a linux. a ... directory as the following three files:
> 
> @hypothenuse -- to be invoked as 'exec tclsh @hypothenuse' from a tclsh under
>                any platform ( it also uses 'exec' to invoke hypothenuse below)
> 
> hypothenuse -- a simple proc and its main (to be invoked by @hypothenuse)
> 
> exec4mac.tcl -- Hemang Lavana's  adaptation for Franc Brglez from
>                http://mini.net/tcl/894.html

This isn't a real exec, since it can ONLY run tcl scripts.  But it is useful
if that is all you need to do.

> 
> Our requirement is to write tcltk once and run everywhere, including
> code that contains exec command. In this context, we would also be
> interested to hear from Jim about any follow-up his earlier work under
> http://www.usenix.org/publications/library/proceedings/tcl97/full_papers/ingha
> m/ingham_html/ingham.html

Well, the part of this paper that is really useful is available on Classic
MacOS as the tclAppleScript extension.  The other parts described in the
paper are (a) connecting to arbitrary OSA extensions, and (b) using Tcl as
an OSA language.  

There is code around from the original version - TcOSAScript, but the only
other OSA language of any consequence was Frontier, and I didn't get any
requests to support it, so I took out the complexity of supporting other
languages in the version shipped with Tcl.  The code would be easy enough to
revive, if you had a reason.  Using Tcl as an OSA language was never
terribly interesting, and generally very unstable.  OSA languages run in the
system heap, and that environment doesn't fit with Tcl's "all malloc's
succeed" practices...  Vince did more work on this than I did, but I don't
think it (or the Perl version) ever got very far.

For your purposes, you could also do exec by using TclAppleScript.  The
problem is that mapping from real exec to AppleScript is not
straightforward, and the fact that the Mac only spawns off 1 copy of each
executable, and feeds all requests to it can cause unexpected behavior if
you are thinking of Unix exec.  Most of the tools you use when you do exec
are also not present on the Mac.  So I am not sure the attempt to make a
"cross-platform exec" really gains you that much.

Jim
-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

Re: [MACTCL] exec on mac

[Franc B. <br...@cb...>]

Here is our take on the exec -- if you are interested to repeat our 
cross-platform experiment, cut the text below and place it under a 
mac, a unix, a linux. a ... directory as the following three files:

@hypothenuse -- to be invoked as 'exec tclsh @hypothenuse' from a tclsh under
                 any platform ( it also uses 'exec' to invoke hypothenuse below)

hypothenuse -- a simple proc and its main (to be invoked by @hypothenuse)

exec4mac.tcl -- Hemang Lavana's  adaptation for Franc Brglez from
                 http://mini.net/tcl/894.html

Our requirement is to write tcltk once and run everywhere, including 
code that contains exec command. In this context, we would also be 
interested to hear from Jim about any follow-up his earlier work under
http://www.usenix.org/publications/library/proceedings/tcl97/full_papers/ingham/ingham_html/ingham.html

Thanks -- franc brglez --

>>>>>>>>>  save as file '@hypothenuse' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
puts "\n... executing [file tail [info script]] under 
'$tcl_platform(platform)'\
   \n... on [clock format [clock seconds]]"

source exec4mac.tcl

set aList {1 1 2 2 3 3 4}
set bList {1 2 2 3 3 4 4}
set cFile cValue

foreach a $aList b $bList {

     exec tclsh hypothenuse $a $b $cFile

     source $cFile ;# the file $cFile contains the value of c
     puts "a=$a b=$b c=$c"
}
# % pwd
# franc-OS9:CVSArchives:cbl:tcltkSW:ticklish:examples:exec4macTestDir:
# % ls
# @hypothenuse
# exec4mac.tcl
# hypothenuse
# % source exec4mac.tcl
# %
# % exec tclsh @hypothenuse
#
# ... executing @hypothenuse under 'macintosh'
# ... on Mon Mar 11 16:26:18 EST 2002
# a=1 b=1 c=1.41421356237
# a=1 b=2 c=2.2360679775
# a=2 b=2 c=2.82842712475
# a=2 b=3 c=3.60555127546
# a=3 b=3 c=4.24264068712
# a=3 b=4 c=5.0
# a=4 b=4 c=5.65685424949
# %

# @vela: [132] cd exec4macTestDir
# @vela: [133] tclsh
# % ls
# @hypothenuse exec4mac.tcl  hypothenuse
# %
# % exec tclsh @hypothenuse
#
# ... executing @hypothenuse under 'unix'
# ... on Mon Mar 11 16:24:08 EST 2002
# a=1 b=1 c=1.41421356237
# a=1 b=2 c=2.2360679775
# a=2 b=2 c=2.82842712475
# a=2 b=3 c=3.60555127546
# a=3 b=3 c=4.24264068712
# a=3 b=4 c=5.0
# a=4 b=4 c=5.65685424949
# %
>>>>>>>>>  end as file '@hypothenuse' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


>>>>>>>>>  save as file 'hypothenuse' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
proc hypothenuse {a b cFile} {

     set c [expr {sqrt( $a*$a + $b*$b )}]
    
     set fileId [open $cFile w]
     puts -nonewline $fileId "set c \"$c\""
     close $fileId

}
eval hypothenuse $argv
>>>>>>>>>  end as file 'hypothenuse' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


>>>>>>>>>  save as file 'exec4mac.tcl' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
# exec4mac script, created from a mini.net posting by Hemang Lavana
# for Franc Brglez, (October 2001).
#
# So far, this script works just fine under MacOS9.2 and Tcl/Tk 8.3.4
# (see the test example exec4macTest.tcl in this directory)
#
# FROM: http://mini.net/tcl/894.html
# FILE: clone.tcl (original name)

global tcl_platform
if {$tcl_platform(platform) != "macintosh"} {return}

global alreadySourced
if {[info exists alreadySourced([info script])]} {return}
set alreadySourced([info script]) 1

namespace eval ::exec4mac {
     variable vars
     namespace export exec
}

  package require Tcl 8          ;# We use [namespace] now.
#  package require Tk
  proc ::exec4mac::slaveExit {slave {code 0}} {
      interp delete $slave
      #if {[llength [interp slaves]] == 0} {exit $code}
  }

  # Return list of commands in $slave in namespace $ns
  proc ::exec4mac::commandsIn {slave {ns {}}} {
      set cmds [$slave eval [list info commands ${ns}::*]]
      foreach child [$slave eval [list namespace children $ns]] {
         set cmds [concat $cmds [commandsIn $slave $child]]
      }
      return $cmds
  }

  proc ::exec4mac::slaveDisable {slave {code 0}} {
      # Prevent re-entrancy problems.  Don't want deletion callbacks of
      # commands we redefine below (notably [.]) to recursively call us.
      $slave eval {proc exit args {}}
      # Convert all commands in $slave to no-ops.
      foreach cmd [commandsIn $slave] {
          if {[string match ::proc $cmd]} {continue}
          $slave eval [list proc $cmd args [list]]
      }
      $slave eval [list proc ::proc args [list]]
      # Delete $slave later.  Make sure $slave is not deleted
      # within the current [update], if any.
      after idle [list after 1 [namespace code [list slaveExit $slave $code]]]
      return -code $code
  }
  proc ::exec4mac::exec {progName scriptName args} {
      global errorCode errorInfo
      # progName can only be 'tclsh' or 'wish'
      set pwd [pwd]
      #cd [file dirname $scriptName]
      set slave [interp create]
      $slave eval [list set argv0 $scriptName]
      $slave eval [list set argv $args]
      $slave eval {set argc [llength $argv]}
      #load {} Tk $slave
      #$slave alias exec ::exec4mac::exec
      $slave alias exit ::exec4mac::slaveDisable $slave
#      $slave eval {
#          bindtags . [linsert [bindtags .] end cloneMainWindow]
#          bind cloneMainWindow <Destroy> [list exit 0]
#          frame .clone
#          pack [button .clone.btn -text clone -command clone] -in .clone
#          pack .clone -side top
#      }
      set code [catch {$slave eval [list source $scriptName]} result]
      catch {$slave eval exit}
      cd $pwd
      return -code $code -errorcode $errorCode -errorinfo $errorInfo $result
  }
#  if {!$argc} {
#      return -code error "\nusage: exec appScript ?arg ...?"
#  }
#  wm withdraw .
#  clone [lindex $argv 0] [lrange $argv 1 end]

namespace import ::exec4mac::exec
>>>>>>>>>  end as file 'exec4mac.tcl' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



At 3:16 PM +0100 3/11/02, Andreas Otto wrote:
>Hi,
>
>  there have to be a way to call additional executables from
>  a Tcl script
>
>  I need the channel output back into a string
>
>  I have an additional API for calling external SW ->
>  does Applescript helps ?
>
>  does "open |..." works ?
>
>
>well
>
>   like you mention I'm working on a Mac port of "Compiler"
>   MacOS 9.1 well no 10
>
>
>  I use Code Warrior (well the name fits exactly)
>
>  1) is a commandline interface available
>
>   cammandline + some kind of exec would be perfect
>
>  2) is a cross compiler linux -> macOs9.1 ppc available
>    gcc does not support MacOs9.1 (this speak for them-
>    self) perhaps CodeWarrior ???
>
>
>mfg
>
>   aotto
>
>
>_______________________________________________
>Tcl-mac mailing list
>Tc...@li...
>https://lists.sourceforge.net/lists/listinfo/tcl-mac

RE: [MACTCL] How-to Changing Type/Creator?

[macnerd <ma...@re...>]

Thanks.

I am forced to be in the Classic world because sometimes I need to test
scripts under Windows.  VPC is too sloooow under Mac OS X, and a tad bit
more smooth under Classic. :-\

 - Joaquin

PS - Another annoying thing I found is that you cannot take screen shots
of DVD movies under Mac OS X, but you can under Classic.  Hmm...

-----Original Message-----
From: tcl...@li...
[mailto:tcl...@li...]On Behalf Of Jim Ingham
Sent: Monday, March 11, 2002 10:53 AM
To: ma...@do...; tc...@li...
Subject: Re: [MACTCL] How-to Changing Type/Creator?


Note that type & creator bits are metadata stored with the file, so you
won't be able to do this on a read-only CD...

There are commands to modify creator & filetype in Classic MacTk, but I
haven't ported them over to Aqua yet.  Probably not too hard, but I haven't
needed it yet, so I haven't ported it.  But in general, the non-GUI parts of
MacTcl is just straightforward Unix.

For this sort of simple thing, find is easy enough...  For example, one easy
way to do this is:

find /Volumes/StartPoint -name \*.gif | xargs /Developer/Tools/SetFile -t
'xxxx' -c 'xxxx'

SetFile comes on the DeveloperTool CD.

Jim

>
> Hello.
>
> I have a major annoyance in that I have a CD of HTMLs and GIFs, which have
> generic TYPE/CREATORS.
> I would like to change this to TYPE/CREATOR of my choosing, so I want to
> create a tool that will walk
> through all of the directories.
>
> I'm so new to the Mac scripting, so I was wondering if someone could tell
me
> how can I change the
> type/creator and walk through the folders.  Do the folders look like UNIX
> directories in MacTCL?
> Are there symbolic . and ..?
>
> thanx,
> Joaquin
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>

--
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb


_______________________________________________
Tcl-mac mailing list
Tc...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

Re: [MACTCL] How-to Changing Type/Creator?

[Jim I. <ji...@ap...>]

Note that type & creator bits are metadata stored with the file, so you
won't be able to do this on a read-only CD...

There are commands to modify creator & filetype in Classic MacTk, but I
haven't ported them over to Aqua yet.  Probably not too hard, but I haven't
needed it yet, so I haven't ported it.  But in general, the non-GUI parts of
MacTcl is just straightforward Unix.

For this sort of simple thing, find is easy enough...  For example, one easy
way to do this is:

find /Volumes/StartPoint -name \*.gif | xargs /Developer/Tools/SetFile -t
'xxxx' -c 'xxxx'

SetFile comes on the DeveloperTool CD.

Jim

> 
> Hello.
> 
> I have a major annoyance in that I have a CD of HTMLs and GIFs, which have
> generic TYPE/CREATORS.
> I would like to change this to TYPE/CREATOR of my choosing, so I want to
> create a tool that will walk
> through all of the directories.
> 
> I'm so new to the Mac scripting, so I was wondering if someone could tell me
> how can I change the
> type/creator and walk through the folders.  Do the folders look like UNIX
> directories in MacTCL?
> Are there symbolic . and ..?
> 
> thanx,
> Joaquin
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
> 

-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

RE: [MACTCL] exec on mac

[macnerd <ma...@re...>]

Hi.

I am interested in a command line mode.  I hope that by this
weekend, I can explore this option.  

I would like to at least compile tcl/tk using MPW-CodeWarrior,
i.e. MPW build environment, which then uses MPW Metrowerks
compilers to achieve the same result.

I get annoyed with the current setup because the project files
NEVER work.  It is always two versions or so behind the times,
and since the project file is a proprietary binary, there's not
much one can do about it.

Though with MPW, the build can be stored in a make file for use
with the MPW environment.  The make file will always work.  Also,
for the really bold, someone at Apple a long long time ago, 
actually ported GCC to MPW.  Though I think it only builds 68K
binaries.

Another thing I wanted to do, is take any resource files and 
store them as .r text files.  These would be compiled into the
appropriate form.  The reason being is that resource files are
not cross platform, as other platforms do not have resource 
forks.  It'd be easy to archive, email, check-in, etc. .r 
files.

  - Joaquin



-----Original Message-----
From: tcl...@li...
[mailto:tcl...@li...]On Behalf Of Andreas Otto
Sent: Monday, March 11, 2002 6:16 AM
To: tc...@li...
Subject: [MACTCL] exec on mac



Hi,

 there have to be a way to call additional executables from
 a Tcl script

 I need the channel output back into a string

 I have an additional API for calling external SW -> 
 does Applescript helps ?

 does "open |..." works ?


well 

  like you mention I'm working on a Mac port of "Compiler"
  MacOS 9.1 well no 10


 I use Code Warrior (well the name fits exactly)

 1) is a commandline interface available

  cammandline + some kind of exec would be perfect

 2) is a cross compiler linux -> macOs9.1 ppc available
   gcc does not support MacOs9.1 (this speak for them-
   self) perhaps CodeWarrior ???


mfg

  aotto


_______________________________________________
Tcl-mac mailing list
Tc...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

RE: [MACTCL] TkDiff on AquaTK

[macnerd <ma...@re...>]

Awesome.  Really.  Awesome!!!!

-----Original Message-----
From: tcl...@li...
[mailto:tcl...@li...]On Behalf Of Dorothy
Robinson
Sent: Sunday, March 10, 2002 5:58 PM
To: Tc...@li...
Subject: [MACTCL] TkDiff on AquaTK


I've been playing with AquaTK some more, and I ported TkDiff.  (Silly me,
it's
not even my program.)  It's old, with a patched-up UI, and it had some
challenges.  Here are some notes I made about problems I ran into, in case
anyone's interested. I would like to know about the button padx issue in the
first note, before I finish it. What's remarkable maybe is how good it
turned
out, once I got the UI problems straightened out.  I put my version of
TkDiff up
on http://www.twobarleycorns.net/vat.html.  I'm not quite ready to submit it
to
Accurev, where it lives.

The notes:

With padx any less than the default, the text of buttons is obscured by
the ends of the lozenges.  I'd think that padx 0 should be such that all
the text shows, and if that makes the buttons longer than on other
platforms, so be it.

There's no way to move transients.  Isn't there an Aqua window type
with only the red glassie, that has a border so you can move it?

It would be nice if tcl_platform(platform) were "aqua" or something.
AquaTK is - well - different from X11, and it would be good to be able
to distinguish it in order to make adjustments.

If you query a widget for its font, the size comes back without a minus
sign, so if you use it like that it's in pixels instead of points and it's
too
big. This is unlike the other platforms and I had to insert a kludge for it.

tkTabToWindow and its ilk are not recognized.  That's probably OK but
at least one call was causing an endless loop of errors, and the app
had to be killed.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Dorothy Robinson
http://www.twobarleycorns.net


_______________________________________________
Tcl-mac mailing list
Tc...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

[MACTCL] How-to Changing Type/Creator?

[macnerd <ma...@re...>]

Hello.

I have a major annoyance in that I have a CD of HTMLs and GIFs, which =
have generic TYPE/CREATORS.
I would like to change this to TYPE/CREATOR of my choosing, so I want to =
create a tool that will walk
through all of the directories.

I'm so new to the Mac scripting, so I was wondering if someone could =
tell me how can I change the=20
type/creator and walk through the folders.  Do the folders look like =
UNIX directories in MacTCL?
Are there symbolic . and ..?

thanx,
 Joaquin

Re: [MACTCL] exec on mac

[Jim I. <ji...@ap...>]

On 3/11/02 8:23 AM, "Jon Guyer" <jg...@hi...> wrote:

>>  2) is a cross compiler linux -> macOs9.1 ppc available
>>    gcc does not support MacOs9.1 (this speak for them-
>>    self) perhaps CodeWarrior ???
> 
> CodeWarrior has a linux variant. I've never used it and don't know
> what it's cross-compilation options are.
> 

The Linux CW just used gcc as its compiler - so far as I know they never
ported their own compiler/debugger to Linux.

There is target support in gcc & gdb for the classic Mac platform (done by
Cygnus to support General Magic development 5 or 6 years ago).  But this
hasn't been touched in about that many years, so it would be a real struggle
to revive it, almost certainly not worth the effort.

If you just want a more command-line oriented development environment you
might try MPW, there is a version of the CW compiler for this, and MrC is
also a pretty good compiler.  The MW libc support is better than the
built-in MPW library, so you might want to use that.

If you want gcc extensions, you are pretty much out of luck...

Jim
-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

Re: [MACTCL] exec on mac

[Jon G. <jg...@hi...>]

At 3:16 PM +0100 3/11/02, Andreas Otto wrote:

>  there have to be a way to call additional executables from
>  a Tcl script

and there is... just not the Tcl norm.

>  I need the channel output back into a string
>
>  I have an additional API for calling external SW ->
>  does Applescript helps ?

Sure AppleScript/Tclapplescript is one option. My TclAE is another. 
In either case, you can get a reply, assuming the external app sends 
one, but it's really not the same as the channel output you are 
probably expecting.

>  does "open |..." works ?

Mac OS 9? No. No pipes.

>  1) is a commandline interface available
>
>   cammandline + some kind of exec would be perfect

Neither of these things really exist on Classic Mac. CodeWarrior 
provides for a limited command-line interface in your apps (look for 
docs on SIOUX and ccommand()). If you want your app to execute other 
apps, you'll need to do it with AppleEvents. Tell us more about 
exactly what you'd like to do and we can tell you more about how to 
accomplish it.

>  2) is a cross compiler linux -> macOs9.1 ppc available
>    gcc does not support MacOs9.1 (this speak for them-
>    self) perhaps CodeWarrior ???

CodeWarrior has a linux variant. I've never used it and don't know 
what it's cross-compilation options are.

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>