System Window

Discussion in 'Pro/Engineer & Creo Elements/Pro' started by Gra-gra, Jan 15, 2004.

  1. Gra-gra

    Gra-gra Guest

    Happy New Year to all.

    Just wondering, does anyone have any useful ProE related commands that
    they use at the system window? I get the feeling it's a hangover from
    the good old days when people occasionally used a command prompt. The
    only time I use it is to purge the current folder, which I find
    useful, but are there any other commands in ProE?
     
    Gra-gra, Jan 15, 2004
    #1
    1. Advertising

  2. Gra-gra

    David Janes Guest

    "Gra-gra" <> wrote in message
    news:...
    : Happy New Year to all.
    :
    : Just wondering, does anyone have any useful ProE related commands that
    : they use at the system window? I get the feeling it's a hangover from
    : the good old days when people occasionally used a command prompt. The
    : only time I use it is to purge the current folder, which I find
    : useful, but are there any other commands in ProE?

    Whatever you can do with the system window, it is still a holdover from the 'good
    ole daze'. If it's worth doing, it ought to be integrated into the main program.
    Purge: aside from the fact that the whole file menu needs reworking and the file
    stucture simplifying, this function, basic to good file management, ought to long
    ago, have been made a file menu function, not a stinky batch file. Another one
    which missed the gui boat over the last 10 years is Pro/BATCH, also in the /bin
    directory (which points to the executable in my i486/obj directory called
    pro_batch.exe). Even if one wished to run this as a standalone tsr, it should
    start from the File menu and use a common gui interface with the main program. It
    reminds one that Pro/e has been around for the last 20 years, but seems to have
    entirely missed the GUI revolution of the last ten. Another one that you can run
    standalone from the command prompt is Pro/TABLE. Yet this program component, which
    was an insult to amateur, much less professional, programmers in the 80s and
    should have been dumped or fixed long ago, is somehow a mainstay of Pro/e. What
    you find through the system window is a trailer park garage sale, running under
    the banner of 'Estate Sale: Antiques'.

    David Janes
     
    David Janes, Jan 19, 2004
    #2
    1. Advertising

  3. Gra-gra

    Gra-gra Guest

    "David Janes" <.2emove> wrote in message news:<ZSWOb.21290$zP6.7123@okepread02>...
    > "Gra-gra" <> wrote in message
    > news:...
    > : Happy New Year to all.
    > :
    > : Just wondering, does anyone have any useful ProE related commands that
    > : they use at the system window? I get the feeling it's a hangover from
    > : the good old days when people occasionally used a command prompt. The
    > : only time I use it is to purge the current folder, which I find
    > : useful, but are there any other commands in ProE?
    >
    > Whatever you can do with the system window, it is still a holdover from the 'good
    > ole daze'. If it's worth doing, it ought to be integrated into the main program.
    > Purge: aside from the fact that the whole file menu needs reworking and the file
    > stucture simplifying, this function, basic to good file management, ought to long
    > ago, have been made a file menu function, not a stinky batch file. Another one
    > which missed the gui boat over the last 10 years is Pro/BATCH, also in the /bin
    > directory (which points to the executable in my i486/obj directory called
    > pro_batch.exe). Even if one wished to run this as a standalone tsr, it should
    > start from the File menu and use a common gui interface with the main program. It
    > reminds one that Pro/e has been around for the last 20 years, but seems to have
    > entirely missed the GUI revolution of the last ten. Another one that you can run
    > standalone from the command prompt is Pro/TABLE. Yet this program component, which
    > was an insult to amateur, much less professional, programmers in the 80s and
    > should have been dumped or fixed long ago, is somehow a mainstay of Pro/e. What
    > you find through the system window is a trailer park garage sale, running under
    > the banner of 'Estate Sale: Antiques'.
    >
    > David Janes


    Yep, that Pro/TABLE was a pain in the butt back when I started on ProE
    8 years ago. What does Pro/BATCH do though? Something to do with
    plotting, isn't it?
     
    Gra-gra, Jan 20, 2004
    #3
  4. Gra-gra

    David Janes Guest

    "Gra-gra" <> wrote in message
    news:...
    : "David Janes" <.2emove> wrote in message
    news:<ZSWOb.21290$zP6.7123@okepread02>...
    : > "Gra-gra" <> wrote in message
    : > news:...
    : > : Happy New Year to all.
    : > :
    : > : Just wondering, does anyone have any useful ProE related commands that
    : > : they use at the system window? I get the feeling it's a hangover from
    : > : the good old days when people occasionally used a command prompt. The
    : > : only time I use it is to purge the current folder, which I find
    : > : useful, but are there any other commands in ProE?
    : >
    : > Whatever you can do with the system window, it is still a holdover from the
    'good
    : > ole daze'. If it's worth doing, it ought to be integrated into the main
    program.
    : > Purge: aside from the fact that the whole file menu needs reworking and the
    file
    : > stucture simplifying, this function, basic to good file management, ought to
    long
    : > ago, have been made a file menu function, not a stinky batch file. Another one
    : > which missed the gui boat over the last 10 years is Pro/BATCH, also in the
    /bin
    : > directory (which points to the executable in my i486/obj directory called
    : > pro_batch.exe). Even if one wished to run this as a standalone tsr, it should
    : > start from the File menu and use a common gui interface with the main program.
    It
    : > reminds one that Pro/e has been around for the last 20 years, but seems to
    have
    : > entirely missed the GUI revolution of the last ten. Another one that you can
    run
    : > standalone from the command prompt is Pro/TABLE. Yet this program component,
    which
    : > was an insult to amateur, much less professional, programmers in the 80s and
    : > should have been dumped or fixed long ago, is somehow a mainstay of Pro/e.
    What
    : > you find through the system window is a trailer park garage sale, running
    under
    : > the banner of 'Estate Sale: Antiques'.
    : >
    : > David Janes
    :
    : Yep, that Pro/TABLE was a pain in the butt back when I started on ProE
    : 8 years ago. What does Pro/BATCH do though? Something to do with
    : plotting, isn't it?

    Yeah, you know how, with Windows, you can tag a bunch of files, do Ctrl P and get
    them all to print. That's what Pro/BATCH does, with some added goodies, like
    scheduling. I think it's even gotten a gui interface in the last couple revs.
    Before, it was a pain just to create the list. Or you had to set up special
    directories, yada yada. I'm not sure if it was ever any use on Unix systems since
    they have their own way of queing plot jobs. The batch plot utility just made it
    possible to plot without the program loaded, supposing you could be confident
    enough of the system to have a reasonable hope of coming back in the morning and
    finding everything printed.

    David Janes
     
    David Janes, Jan 21, 2004
    #4
  5. Gra-gra

    Gra-gra Guest

    "David Janes" <.2emove> wrote in message news:<ZxkPb.25674$zP6.3246@okepread02>...
    > "Gra-gra" <> wrote in message
    > news:...
    > : "David Janes" <.2emove> wrote in message
    > news:<ZSWOb.21290$zP6.7123@okepread02>...
    > : > "Gra-gra" <> wrote in message
    > : > news:...
    > : > : Happy New Year to all.
    > : > :
    > : > : Just wondering, does anyone have any useful ProE related commands that
    > : > : they use at the system window? I get the feeling it's a hangover from
    > : > : the good old days when people occasionally used a command prompt. The
    > : > : only time I use it is to purge the current folder, which I find
    > : > : useful, but are there any other commands in ProE?
    > : >
    > : > Whatever you can do with the system window, it is still a holdover from the
    > 'good
    > : > ole daze'. If it's worth doing, it ought to be integrated into the main
    > program.
    > : > Purge: aside from the fact that the whole file menu needs reworking and the
    > file
    > : > stucture simplifying, this function, basic to good file management, ought to
    > long
    > : > ago, have been made a file menu function, not a stinky batch file. Another one
    > : > which missed the gui boat over the last 10 years is Pro/BATCH, also in the
    > /bin
    > : > directory (which points to the executable in my i486/obj directory called
    > : > pro_batch.exe). Even if one wished to run this as a standalone tsr, it should
    > : > start from the File menu and use a common gui interface with the main program.
    > It
    > : > reminds one that Pro/e has been around for the last 20 years, but seems to
    > have
    > : > entirely missed the GUI revolution of the last ten. Another one that you can
    > run
    > : > standalone from the command prompt is Pro/TABLE. Yet this program component,
    > which
    > : > was an insult to amateur, much less professional, programmers in the 80s and
    > : > should have been dumped or fixed long ago, is somehow a mainstay of Pro/e.
    > What
    > : > you find through the system window is a trailer park garage sale, running
    > under
    > : > the banner of 'Estate Sale: Antiques'.
    > : >
    > : > David Janes
    > :
    > : Yep, that Pro/TABLE was a pain in the butt back when I started on ProE
    > : 8 years ago. What does Pro/BATCH do though? Something to do with
    > : plotting, isn't it?
    >
    > Yeah, you know how, with Windows, you can tag a bunch of files, do Ctrl P and get
    > them all to print. That's what Pro/BATCH does, with some added goodies, like
    > scheduling. I think it's even gotten a gui interface in the last couple revs.
    > Before, it was a pain just to create the list. Or you had to set up special
    > directories, yada yada. I'm not sure if it was ever any use on Unix systems since
    > they have their own way of queing plot jobs. The batch plot utility just made it
    > possible to plot without the program loaded, supposing you could be confident
    > enough of the system to have a reasonable hope of coming back in the morning and
    > finding everything printed.
    >
    > David Janes


    That sounds very optimistic to me!
     
    Gra-gra, Jan 21, 2004
    #5
  6. The only usefull thing with the system window, i think, is programming.
    Since the standard versions of pro and wildfire have no programming
    utilities at all (unlike Solid Works for instance...), the only way of
    programming in pro is calling batch or some other script files that creates
    trail files, in the system window, which you call with mapkeys.

    Grts, Gerard

    "Gra-gra" <> schreef in bericht
    news:...
    > "David Janes" <.2emove> wrote in message

    news:<ZxkPb.25674$zP6.3246@okepread02>...
    > > "Gra-gra" <> wrote in message
    > > news:...
    > > : "David Janes" <.2emove> wrote in message
    > > news:<ZSWOb.21290$zP6.7123@okepread02>...
    > > : > "Gra-gra" <> wrote in message
    > > : > news:...
    > > : > : Happy New Year to all.
    > > : > :
    > > : > : Just wondering, does anyone have any useful ProE related commands

    that
    > > : > : they use at the system window? I get the feeling it's a hangover

    from
    > > : > : the good old days when people occasionally used a command prompt.

    The
    > > : > : only time I use it is to purge the current folder, which I find
    > > : > : useful, but are there any other commands in ProE?
    > > : >
    > > : > Whatever you can do with the system window, it is still a holdover

    from the
    > > 'good
    > > : > ole daze'. If it's worth doing, it ought to be integrated into the

    main
    > > program.
    > > : > Purge: aside from the fact that the whole file menu needs reworking

    and the
    > > file
    > > : > stucture simplifying, this function, basic to good file management,

    ought to
    > > long
    > > : > ago, have been made a file menu function, not a stinky batch file.

    Another one
    > > : > which missed the gui boat over the last 10 years is Pro/BATCH, also

    in the
    > > /bin
    > > : > directory (which points to the executable in my i486/obj directory

    called
    > > : > pro_batch.exe). Even if one wished to run this as a standalone tsr,

    it should
    > > : > start from the File menu and use a common gui interface with the

    main program.
    > > It
    > > : > reminds one that Pro/e has been around for the last 20 years, but

    seems to
    > > have
    > > : > entirely missed the GUI revolution of the last ten. Another one that

    you can
    > > run
    > > : > standalone from the command prompt is Pro/TABLE. Yet this program

    component,
    > > which
    > > : > was an insult to amateur, much less professional, programmers in the

    80s and
    > > : > should have been dumped or fixed long ago, is somehow a mainstay of

    Pro/e.
    > > What
    > > : > you find through the system window is a trailer park garage sale,

    running
    > > under
    > > : > the banner of 'Estate Sale: Antiques'.
    > > : >
    > > : > David Janes
    > > :
    > > : Yep, that Pro/TABLE was a pain in the butt back when I started on ProE
    > > : 8 years ago. What does Pro/BATCH do though? Something to do with
    > > : plotting, isn't it?
    > >
    > > Yeah, you know how, with Windows, you can tag a bunch of files, do Ctrl

    P and get
    > > them all to print. That's what Pro/BATCH does, with some added goodies,

    like
    > > scheduling. I think it's even gotten a gui interface in the last couple

    revs.
    > > Before, it was a pain just to create the list. Or you had to set up

    special
    > > directories, yada yada. I'm not sure if it was ever any use on Unix

    systems since
    > > they have their own way of queing plot jobs. The batch plot utility just

    made it
    > > possible to plot without the program loaded, supposing you could be

    confident
    > > enough of the system to have a reasonable hope of coming back in the

    morning and
    > > finding everything printed.
    > >
    > > David Janes

    >
    > That sounds very optimistic to me!
     
    Gerard van de Schoot, Jan 22, 2004
    #6
  7. Gra-gra

    Alex Sh. Guest

    "Gerard van de Schoot" <> wrote in message
    news:400f8cf1$0$41756$...
    > The only usefull thing with the system window, i think, is programming.
    > Since the standard versions of pro and wildfire have no programming
    > utilities at all (unlike Solid Works for instance...), the only way of
    > programming in pro is calling batch or some other script files that

    creates
    > trail files, in the system window, which you call with mapkeys.
    >
    > Grts, Gerard


    Gerard,

    1. Basic Pro/E (2000i2, 2001, Wildfire) has built-in free Java API (JLINK).
    So it does have a programming utility, arguably a better one than VB bundled
    into SolidWorks.
    2. Yes, the batch or other script file is about the only excuse left for the
    system window. Not that you need such workarounds anymore, but maybe as
    legacy code support...

    Alex
     
    Alex Sh., Jan 22, 2004
    #7
  8. Tnkx Alex, but programming in java isn't quite as easy, adjustable, and it's
    more time consuming compared with a script
    file. That's what i mean with it. (I haven't figured it out also...)

    Gerard

    "Alex Sh." <> schreef in bericht
    news:tWSPb.3103$...
    >
    > "Gerard van de Schoot" <> wrote in message
    > news:400f8cf1$0$41756$...
    > > The only usefull thing with the system window, i think, is programming.
    > > Since the standard versions of pro and wildfire have no programming
    > > utilities at all (unlike Solid Works for instance...), the only way of
    > > programming in pro is calling batch or some other script files that

    > creates
    > > trail files, in the system window, which you call with mapkeys.
    > >
    > > Grts, Gerard

    >
    > Gerard,
    >
    > 1. Basic Pro/E (2000i2, 2001, Wildfire) has built-in free Java API

    (JLINK).
    > So it does have a programming utility, arguably a better one than VB

    bundled
    > into SolidWorks.
    > 2. Yes, the batch or other script file is about the only excuse left for

    the
    > system window. Not that you need such workarounds anymore, but maybe as
    > legacy code support...
    >
    > Alex
    >
    >
     
    Gerard van de Schoot, Jan 23, 2004
    #8
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. vincent
    Replies:
    0
    Views:
    101
    vincent
    Dec 8, 2003
  2. Frank Nitsche
    Replies:
    2
    Views:
    229
    Frank Nitsche
    Sep 13, 2004
  3. Suresh Jeevanandam
    Replies:
    4
    Views:
    274
    John Gianni
    Jun 2, 2005
  4. P?l
    Replies:
    1
    Views:
    219
    Corey Scheich
    Aug 23, 2004
  5. Captain Chaos
    Replies:
    1
    Views:
    250
    Captain Chaos
    Dec 23, 2003
Loading...

Share This Page