Skip to main content

[archive] How do you work?

  • April 7, 2007
  • 3 replies
  • 0 views

[Migrated content. Thread originally posted on 03 April 2007]

Hi,

Recently, our company had a meet to talk about how things are doing and we reach the conclusion that we aren't doing well with acubench.

I start this thread to see how all of you (or who wants to answer :p ) works with the acubench to see if we are doing wel or at least known of other ways to workl, because in some cases we are getting a too low development speed.

Where we are a bit slow is in screen design. Normally, to create a new program, we copy paste the .psf and .wrk and start modifying the screen and i have some questions:

- We loose a lot of time deleting the events asigned to a control in the screen and in the .evt, acubench is a bit slow in that aspect or at least the way we use it, selecting the control, going to event tab, entering in the "..." button (it takes a bit to open the .evt for each control and event) and deleting the code we not going to use in that control. And all of this using the mouse; we dont see any other way to access with keyboard.
* Is there some way to create a new base form to select when pushing the "new" button in the acubench?
* You manually control the events of your screen?
* Is there a way to create a model of a control with default properties or events assigned on it and drag and drop it to your screen?
* And a more wide question, Is there a faster way to design a screen? :confused:

- The other big question is, How you generate your programs? I mean, when we generate our .psf file (we do not generate .wrk, we change it manually because in version 6.x the working manager doesn't work correctly and with the time we see that changing it manually is better because we can put coments in the variables and things get more clear) acubench generate lots of archives .lst, .evt, .lnk, .cbl, and so on. I know this can be changed in the project settings to only generate one file or the files you want. What i want is to know if there is some type of benefit using a one source file (.psf) or multiple files.
* The acubench opens faster the programs to edit them if they are splitted in vaious copy files, or not?
* Maybe you work with another editor of cobol?

I'll update this post with new doubts about how we are doing but basically what i want is to share our experience to know if another way to work better and faster is posible.

Thanks for reading and if want post some tip

3 replies

[Migrated content. Thread originally posted on 03 April 2007]

Hi,

Recently, our company had a meet to talk about how things are doing and we reach the conclusion that we aren't doing well with acubench.

I start this thread to see how all of you (or who wants to answer :p ) works with the acubench to see if we are doing wel or at least known of other ways to workl, because in some cases we are getting a too low development speed.

Where we are a bit slow is in screen design. Normally, to create a new program, we copy paste the .psf and .wrk and start modifying the screen and i have some questions:

- We loose a lot of time deleting the events asigned to a control in the screen and in the .evt, acubench is a bit slow in that aspect or at least the way we use it, selecting the control, going to event tab, entering in the "..." button (it takes a bit to open the .evt for each control and event) and deleting the code we not going to use in that control. And all of this using the mouse; we dont see any other way to access with keyboard.
* Is there some way to create a new base form to select when pushing the "new" button in the acubench?
* You manually control the events of your screen?
* Is there a way to create a model of a control with default properties or events assigned on it and drag and drop it to your screen?
* And a more wide question, Is there a faster way to design a screen? :confused:

- The other big question is, How you generate your programs? I mean, when we generate our .psf file (we do not generate .wrk, we change it manually because in version 6.x the working manager doesn't work correctly and with the time we see that changing it manually is better because we can put coments in the variables and things get more clear) acubench generate lots of archives .lst, .evt, .lnk, .cbl, and so on. I know this can be changed in the project settings to only generate one file or the files you want. What i want is to know if there is some type of benefit using a one source file (.psf) or multiple files.
* The acubench opens faster the programs to edit them if they are splitted in vaious copy files, or not?
* Maybe you work with another editor of cobol?

I'll update this post with new doubts about how we are doing but basically what i want is to share our experience to know if another way to work better and faster is posible.

Thanks for reading and if want post some tip
It sounds like you aren't use the stf function of AcuBench. You can create a base screen, then right click on it and choose "Generate stf", which creates a screen template file. Then when you need a new screen, you use that template. You can add this template to your "new" options through Tools/Options/Environment/Template

Also, all of the events are in the Event Paragraph. You can open this up and go through all of the code, instead of having to click on each control and access the code that way.

There isn't a performance benefit to generating to one file. You can use separate files if you prefer, usually if you are using version control software and don't want to save the generated code. Or you can compile to one file so that it looks more like what a lot of programmers are used to.

If you are having small problems like this, Acucorp's technical support should be very helpful. AcuBench's 7.2.0 manual has been completely rewritten and might be more helpful to you than previous manuals. We also have a lot of specialized AcuBench training available.

I'll keep my eye on this posting to see if you have any other problems that you want to share.

Marilyn Prince
AcuBench Project Manager

[Migrated content. Thread originally posted on 03 April 2007]

Hi,

Recently, our company had a meet to talk about how things are doing and we reach the conclusion that we aren't doing well with acubench.

I start this thread to see how all of you (or who wants to answer :p ) works with the acubench to see if we are doing wel or at least known of other ways to workl, because in some cases we are getting a too low development speed.

Where we are a bit slow is in screen design. Normally, to create a new program, we copy paste the .psf and .wrk and start modifying the screen and i have some questions:

- We loose a lot of time deleting the events asigned to a control in the screen and in the .evt, acubench is a bit slow in that aspect or at least the way we use it, selecting the control, going to event tab, entering in the "..." button (it takes a bit to open the .evt for each control and event) and deleting the code we not going to use in that control. And all of this using the mouse; we dont see any other way to access with keyboard.
* Is there some way to create a new base form to select when pushing the "new" button in the acubench?
* You manually control the events of your screen?
* Is there a way to create a model of a control with default properties or events assigned on it and drag and drop it to your screen?
* And a more wide question, Is there a faster way to design a screen? :confused:

- The other big question is, How you generate your programs? I mean, when we generate our .psf file (we do not generate .wrk, we change it manually because in version 6.x the working manager doesn't work correctly and with the time we see that changing it manually is better because we can put coments in the variables and things get more clear) acubench generate lots of archives .lst, .evt, .lnk, .cbl, and so on. I know this can be changed in the project settings to only generate one file or the files you want. What i want is to know if there is some type of benefit using a one source file (.psf) or multiple files.
* The acubench opens faster the programs to edit them if they are splitted in vaious copy files, or not?
* Maybe you work with another editor of cobol?

I'll update this post with new doubts about how we are doing but basically what i want is to share our experience to know if another way to work better and faster is posible.

Thanks for reading and if want post some tip
Several things you might want to think about are:
1. I think Marilyn's suggestion about versioning is right on the mark. Do you plan to keep some record of changes made to any part of the program i.e. using PVCS or something like that for version control? If so, you might want to think about at least generating a separate evt as Marilyn suggests if you have decided not to. I think generating the STF would help here as well plus you have a copy of your screen if something gets corrupted some how, some way.
2. Although you can change the events in the event editor, you st ill need to go back to the screen editor and change/modify any names or delete out any items you eliminated so this helps somewhat for what you are doing but not entirely.
3. On your version, I would not use drag and drop, or at least rely on it. I had used drag and drop of buttons from one part of my screen to another to create a new icon and success was somewhat inconsistant.
4. If you are doing a lot of screen changes you probably want to generate more often because of memory constraints.
5. We generate a PSF and it helps when moving a program into another project - i.e. for merging projects, etc. For source control, it is not effective.

[Migrated content. Thread originally posted on 03 April 2007]

Hi,

Recently, our company had a meet to talk about how things are doing and we reach the conclusion that we aren't doing well with acubench.

I start this thread to see how all of you (or who wants to answer :p ) works with the acubench to see if we are doing wel or at least known of other ways to workl, because in some cases we are getting a too low development speed.

Where we are a bit slow is in screen design. Normally, to create a new program, we copy paste the .psf and .wrk and start modifying the screen and i have some questions:

- We loose a lot of time deleting the events asigned to a control in the screen and in the .evt, acubench is a bit slow in that aspect or at least the way we use it, selecting the control, going to event tab, entering in the "..." button (it takes a bit to open the .evt for each control and event) and deleting the code we not going to use in that control. And all of this using the mouse; we dont see any other way to access with keyboard.
* Is there some way to create a new base form to select when pushing the "new" button in the acubench?
* You manually control the events of your screen?
* Is there a way to create a model of a control with default properties or events assigned on it and drag and drop it to your screen?
* And a more wide question, Is there a faster way to design a screen? :confused:

- The other big question is, How you generate your programs? I mean, when we generate our .psf file (we do not generate .wrk, we change it manually because in version 6.x the working manager doesn't work correctly and with the time we see that changing it manually is better because we can put coments in the variables and things get more clear) acubench generate lots of archives .lst, .evt, .lnk, .cbl, and so on. I know this can be changed in the project settings to only generate one file or the files you want. What i want is to know if there is some type of benefit using a one source file (.psf) or multiple files.
* The acubench opens faster the programs to edit them if they are splitted in vaious copy files, or not?
* Maybe you work with another editor of cobol?

I'll update this post with new doubts about how we are doing but basically what i want is to share our experience to know if another way to work better and faster is posible.

Thanks for reading and if want post some tip
Thanks for reply :D, we'll study the fact of work with psf, because we dont care much about if a part of the program is modified.

Still open the thread for more suggestions if wanted