Uniface User Forum

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff
------------------------------

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Yep Daniel... it was an assumption on my part. 

I am assuming the work area support uses something outside of uniface to do the deleting?

------------------------------
Osman Shariff
------------------------------

Original Message:
Sent: 01-26-2023 07:54
From: Daniel Iseli
Subject: $ude clean

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Okay, thanks for clarifying.

And the work area support uses normal Uniface functionality to delete the (main development) objects. Not really different from what the IDE is doing when you are deleting something in an Editor.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------

Original Message:
Sent: 01-26-2023 07:59
From: Osman Shariff
Subject: $ude clean

Yep Daniel... it was an assumption on my part. 

I am assuming the work area support uses something outside of uniface to do the deleting?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 07:54
From: Daniel Iseli
Subject: $ude clean

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Is that functionality available for us to use... what is the command?

------------------------------
Osman Shariff
------------------------------

Original Message:
Sent: 01-26-2023 08:02
From: Daniel Iseli
Subject: $ude clean

Okay, thanks for clarifying.

And the work area support uses normal Uniface functionality to delete the (main development) objects. Not really different from what the IDE is doing when you are deleting something in an Editor.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:59
From: Osman Shariff
Subject: $ude clean

Yep Daniel... it was an assumption on my part. 

I am assuming the work area support uses something outside of uniface to do the deleting?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 07:54
From: Daniel Iseli
Subject: $ude clean

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Sure. At its core the IDE is just a "normal" Uniface application that uses ProcScript statements such as (e.g.) remocc.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------

Original Message:
Sent: 01-26-2023 08:19
From: Osman Shariff
Subject: $ude clean

Is that functionality available for us to use... what is the command?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 08:02
From: Daniel Iseli
Subject: $ude clean

Okay, thanks for clarifying.

And the work area support uses normal Uniface functionality to delete the (main development) objects. Not really different from what the IDE is doing when you are deleting something in an Editor.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:59
From: Osman Shariff
Subject: $ude clean

Yep Daniel... it was an assumption on my part. 

I am assuming the work area support uses something outside of uniface to do the deleting?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 07:54
From: Daniel Iseli
Subject: $ude clean

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------

Thanks... Got it, Cheers

------------------------------
Osman Shariff
------------------------------

Original Message:
Sent: 01-26-2023 08:49
From: Daniel Iseli
Subject: $ude clean

Sure. At its core the IDE is just a "normal" Uniface application that uses ProcScript statements such as (e.g.) remocc.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 08:19
From: Osman Shariff
Subject: $ude clean

Is that functionality available for us to use... what is the command?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 08:02
From: Daniel Iseli
Subject: $ude clean

Okay, thanks for clarifying.

And the work area support uses normal Uniface functionality to delete the (main development) objects. Not really different from what the IDE is doing when you are deleting something in an Editor.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:59
From: Osman Shariff
Subject: $ude clean

Yep Daniel... it was an assumption on my part. 

I am assuming the work area support uses something outside of uniface to do the deleting?

------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 07:54
From: Daniel Iseli
Subject: $ude clean

Thanks Osman. And you are welcome.

The documentation of $ude ("delete") is quit clear, I think. It says: "Delete a symbol table or script listing, or a resource (compiled runtime object) on the $RSO path." There is nothing mentioned about source code.

I hope this clarifies this matter.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 07:36
From: Osman Shariff
Subject: $ude clean

Thanks Daniel

That saved a lot of messy code, especially as ude-delete does not as I expected delete the source code.


------------------------------
Osman Shariff

Original Message:
Sent: 01-26-2023 06:46
From: Daniel Iseli
Subject: $ude clean

Hello Osman,

There is a cleanup operation for $ude, but it is not documented (yet). At this moment I do not know the exact reason for this, but this will work:

vResult = $ude("cleanup", "component", "mycomponent")

This is the same as executing the ide command line: /cln mycomponent

In case you would use the Work Area Support Utility (or something similar) then objects are deleted automatically before new sources are imported.

I hope this helps.

------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland

Original Message:
Sent: 01-26-2023 06:37
From: Osman Shariff
Subject: $ude clean

Hello All

Is there an option to have an $ude clean or a $ude import component with a clean option.  
If not, could it be something to add for the future?

The problem is, if you import a component, you will always need to clean it for ghost fields.

The workaround is a 'delete' and then an 'import'; assuming the imported is already correct.

Thanks

------------------------------
Osman Shariff
------------------------------