Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Resave Sourceobjects / Upgrade DW-Syntax

  1. Misc
0
Votes
Undo
  1. Tobias Roth
    Tobias Roth
  2. PowerBuilder
  3. Tuesday, 22 December 2020 06:48 AM UTC

Hi,

does anyone know a tool or some "IDE-tricks" to convert the sourceobjects of a pbl to a newer pbversion (for example DWs) or just "resave" the objects of a pbl?

Background:

We want to track the changes a developer make exactly as possible. 

So it would be great to do a convert/resave of every object for example after a successful migration. The datawindow would be converted to the newer pb-version and newer column-properties are getting added. 
We know that otherwise there is no real benefit in converting a DW to the new version. Its just for a clean changlog in the git historie.

Another usecase:

Resaving sourceobjects for hierarchical class changes, so the changes will be applied to the descendent objects.

Background: The hierarchical changes in every descendent should be committed by the developer that caused the change.

Thanks

Regards Tobi

Advice on switching from WinHttp.WinHttpRequest to...
How to connect Powerbuilder source code to GIT
Responses (2)
Tobias Roth
Tobias Roth Accepted Answer Pending Moderation
  1. Monday, 28 December 2020 06:30 AM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,

Thanks for the tip, but we would need a bit more that LibraryExport and LibrayImport.
We think the upgrading of a object is a internal process inside the IDE.

Example changes:

  • new DW Properties are added
  • inherited changes getting applied to the child object (when you change a property inside a parent object the changes are automatically appied by opening and saving the object.)

Regards,

Tobi

Comment
Load more comments
Andreas Mykonios
  1. Andreas Mykonios
  2. Wednesday, 31 May 2023 05:59 AM UTC
Hi Miguel.

That's can be done using automation tools. I personally used AutoIt with powerbuilder lot of times.

Andreas.
  1. Helpful 1
Tobias Roth
  1. Tobias Roth
  2. Wednesday, 31 May 2023 06:52 AM UTC
Hi Miguel and Andreas,

Thanks for the suggestions. I think this is a good workaround, I will test AutoIt.

The changes we would like to do specifically during migration so that in the review process we are only reviewing the actual changes made by the programmer and not automatic changes.

Regards Tobi
  1. Helpful
Simon Jutzi
  1. Simon Jutzi
  2. Thursday, 8 June 2023 08:51 AM UTC
Hi all

I'm glad it works, but would it be so difficult for Appeon to provide us with a "MigrateDwSyntax" feature (e.g. via ORCA)?

AutoIt/AHK and CI/CD piplines are an evil combination from my point of view.

Regards Simon
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 22 December 2020 14:47 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tobias;

  The LibraryExport and LibrayImport commands could be your friend here. With these two commands you can write a simple PB App to ...

  • Export the DWO source
  • Replace the 1st line in the source "release nn;" with "release 19;" (for example)
  • Import the DWO source back into the original PBL.

Food for thought

Regards ... Chris

 

Comment
Roland Smith
  1. Roland Smith
  2. Thursday, 8 June 2023 15:22 PM UTC
I don't think that won't add the new properties. I'm pretty sure it is the DW Painter that does that.
  1. Helpful 1
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 8 June 2023 18:28 PM UTC
Hi Roland;

Yes, during the Import, it will force new PB release DWO syntax to be added. ;-)

Regards ... Chris
  1. Helpful
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.