1. Desarollo 07
  2. PowerBuilder
  3. Thursday, 2 May 2024 21:01 PM UTC

Hi, any example to work a window with header datawindow and detail datawindow in STD Framerowk?

Accepted Answer
Desarollo 07 Accepted Answer Pending Moderation
  1. Thursday, 23 May 2024 19:35 PM UTC
  2. PowerBuilder
  3. # Permalink

Should I create the oe_std_fc user event in all my classes of my framework so that I can work with the STD classes?

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 May 2024 20:29 PM UTC
That is totally up to you. The minimum would be the objects that you want to have "coexist". ;-)
  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Friday, 24 May 2024 15:21 PM UTC
  2. PowerBuilder
  3. # 1

Chris thanks for the time to answer my questions.

It is very clear to me and the best thing is to implement the STD Framework in new developments, which is what I will do.

Greetings

Comment
  1. Chris Pollach @Appeon
  2. Friday, 24 May 2024 16:40 PM UTC
You are most welcome! Yes with any "working" PB App, the changeover to any framework requires refactoring. So you need to be prepared for the extended time to make the code changes. A new App of course, would be the ideal time to introduce a framework.
  1. Helpful 1
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Friday, 24 May 2024 13:41 PM UTC
  2. PowerBuilder
  3. # 2

I could use my following objects:

- my logon window
- my mdi window (w_app)
- my menu object

Replacing the ones used by STD so I can continue using my objects that are already in production?

Comment
  1. Chris Pollach @Appeon
  2. Friday, 24 May 2024 15:10 PM UTC
Without knowing your current PB Apps architecture - it's hard to answer that question.

Like the PFC framework, the STD framework is best ALL used for maximum functionality, performance and stability.

That would be up to you to access in your Unit Testing.
  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Thursday, 23 May 2024 21:10 PM UTC
  2. PowerBuilder
  3. # 3

Okay, is the nc_app_controller_master control the one that activates the services of all the STD controls? If I don't use it, is there a way to use the controls?

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 May 2024 21:45 PM UTC
The "Controller" is required as it's the brains (central nervous system) of the framework.
  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Thursday, 23 May 2024 18:46 PM UTC
  2. PowerBuilder
  3. # 4

Chris, Is it possible to add the STD libraries to my application and have a hybrid with what is already working in production and with what is new under STD?

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 May 2024 19:03 PM UTC
Yes you can! The framework will still flag any non-framework compliant objects. So what you need to do is add a user event called "oe_std_fc" . As long as the framework sees that UE in your non-framework object class (it's like a "Trust Me") it will not complain. HTH

  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Wednesday, 22 May 2024 21:20 PM UTC
  2. PowerBuilder
  3. # 5

Hi Chris

I have imported some Example App objects from PowerBuilder 12.6 to STD_FC_OrderEntry_v2017R1_PB12.6.0_Classic_B4108_2017-05-17.

It shows me the following message, what should I do?

This works in Example App and I wish it worked in STD

 

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 May 2024 17:52 PM UTC
Hi Desarollo;

It looks like you are trying to use object classes from the PB IDE's System Class repository vs equivalent Object Classes from the STD Framework. The framework checks this at runtime and if the object is not from the framework (visual or non-visual), then it lets you know.

HTH

Regards... Chris
  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Monday, 6 May 2024 14:44 PM UTC
  2. PowerBuilder
  3. # 6

Hi Chris
I have this window and I want to double click on a record and show me the information from the detail tab using STD.

 

Comment
  1. Chris Pollach @Appeon
  2. Monday, 6 May 2024 18:06 PM UTC
Hi Desarollo;

To do that operation, you would just use the standard PB events & methods. The Double clicked event to get the Row #, then the GetItemXxxxx() method to get the DB key. From there if the Detail Window was not open, then use an Open(Sheet)withParm() to display the detail. If then detail DWO is in a separate tab, then you just need a SetFocus() to have it displayed. I would them use the TriggerEvent () command to send that DW control the DB key in order to retrieve.

HTH

Regards... Chris
  1. Helpful
There are no comments made yet.
Desarollo 07 Accepted Answer Pending Moderation
  1. Friday, 3 May 2024 16:05 PM UTC
  2. PowerBuilder
  3. # 7

Hi Chris, thanks

I'm doing some tests with : STD_FC_OrderEntry_v2017R1_PB12.6.0_Classic_B4108_2017-05-17

And checking I found the window wn_extension which is ancestor of wn_controller_master wn_extension is not found in the latest version of STD Foundation Classes.

The company where I work for now does not plan to migrate to the latest version of PowerBuilder.

My question is when to inherit from wn_extension and when to inherit from wn_controller_master?

Comment
  1. Chris Pollach @Appeon
  2. Friday, 3 May 2024 17:03 PM UTC
Hi Desarollo;

Wow, that is a very old framework version & *not* compatible (or even migrate capable ) for use with PB 2022 R3!!!!

You should be using "STD_FC_Integrated_Framework_v2024.1.0.374_PB2022R3_B3289_2024-02-12.zip" or higher. release

=> https://sourceforge.net/projects/stdfndclass/files/FrameWork/Integrated

The "wn_extension" class and in fact all "extension" objects were *removed* in newer framework releases. The rational for that was: They took up PBL space, Slowed down the compiles; and added slower runtime performance (like the PFC does - way too much overhead). The idea here would be to allow the PB Developer to create the "extension" classes "only when need". So if you have code in that extension object class, please create your own "extension" PBL(s) in your App WorkSpace's Target as needed and then copy them to the newer PBL. If you do not have code in that extension class, then just ignore it an inherit your working Concrete classes from the Base level window ancestor (as appropriate) in the ".STD_FC_PB_Base.pbl;" library. HTH

Regards .. Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 May 2024 21:19 PM UTC
  2. PowerBuilder
  3. # 8

Hi Desarollo;

    The framework does not care too much about this as it would be handled internally by the Parent & Child DWO's and their relationship to each other. Once that is defined in the DW Painter, the DWO runtime engine is responsible for handling that symbiotic relationship. The only choice from a PB developers POV would be the DW Control ancestor to use, There are a few DC ancestor's that might be the best for the way that your App wants the DWO's to be processed, as follows:

  • vs_dc_report_master - if the DWO's will be used for viewing, printing, PDF generation (non-update mode only).
  • vs_dc_detail_master - if the DWO's will be used in an update mode.
  • vs_dc_master - can be used for any read only or update mode combination - but may require some more coding on your part.

HTH

Regards .. Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.