Hi Freaks
(Test)Migration from UnifAce 9 to UnifAce 10 almost done.
Now I want't to set up a deployment setting where I use UAR instead of output to directories.
But not all "things" should go into one UAR.
e.g.
1. APS and global objects into another UAR
2. Specific components should in another UAR (like debug-tools)
In good old time, it was possible to use [files] like this:
DBG*.frm .\\compiled\\debug\\frm\\DBG*.frm
*.frm .\\compiled\\frm\\*.frm
Is there any way to tell UnifAce to do so with UF 10 ?
$RESOURCES_OUTPUT ??? = .\\compiled\\DBG_Components.uar
$RESOURCES_OUTPUT ??? = .\\compiled\\Components.uar
This redirection should happen at compile time and not later when it goes to develop!
Ingo
Hello Ingo
The same Uniface object can be in multiple resources.
Make sure the version you want to use comes first in the [RESOURCES] section.
$resources_output is a development setting to create resources.
When testing , deploying the [RESOURCES] section specifies which resources to use and in which order to read them.
One can not redirect Uniface objects in [FILES] section when using standardized deployment.
So you would need
[RESOURCES]
.\\DBG_Components.uar
.\\compiled\\Components.uar
Regards
Peter
Hi Freaks
(Test)Migration from UnifAce 9 to UnifAce 10 almost done.
Now I want't to set up a deployment setting where I use UAR instead of output to directories.
But not all "things" should go into one UAR.
e.g.
1. APS and global objects into another UAR
2. Specific components should in another UAR (like debug-tools)
In good old time, it was possible to use [files] like this:
DBG*.frm .\\compiled\\debug\\frm\\DBG*.frm
*.frm .\\compiled\\frm\\*.frm
Is there any way to tell UnifAce to do so with UF 10 ?
$RESOURCES_OUTPUT ??? = .\\compiled\\DBG_Components.uar
$RESOURCES_OUTPUT ??? = .\\compiled\\Components.uar
This redirection should happen at compile time and not later when it goes to develop!
Ingo
Hi Peter
Yes, I know I can have multiple inputs for resources 🙂
BUT...
But I want to separate the files already at compile time in different UAR and/or directories
Due to our name schema, we do this in UF9 by [files]
So there was no need to take care, if a debug component find its way to customers
I heard, that UF10 is so much better then UF9, so ... 🙂
Ingo
Hi Peter
Yes, I know I can have multiple inputs for resources 🙂
BUT...
But I want to separate the files already at compile time in different UAR and/or directories
Due to our name schema, we do this in UF9 by [files]
So there was no need to take care, if a debug component find its way to customers
I heard, that UF10 is so much better then UF9, so ... 🙂
Ingo
Hi Ingo
Uniface 10 has many new ways to do things.
$resources_output is a static setting.
One can have multiple asn with different values for $resources_output
so start IDE , compile using an asn to create the DBG archive when this is needed
or use in script
$ude("archive", "list", ListOfResources, ArchiveFile{, OptionList})
to create an uar
A form using all options from $ude or a batch that can handle all $ude options on the command line is also handy.
Another tool to manipulate archives is the urm (Uniface resource manager).
You can for example compile to a folder and use urm in a script to create,modify archives.
To create multiple uar from within one IDE session a component using $ude("archive",...) seems a good option:
$resources_output to a folder and use a component using $ude("archive",...) to create archives
Peter
Hi Freaks
(Test)Migration from UnifAce 9 to UnifAce 10 almost done.
Now I want't to set up a deployment setting where I use UAR instead of output to directories.
But not all "things" should go into one UAR.
e.g.
1. APS and global objects into another UAR
2. Specific components should in another UAR (like debug-tools)
In good old time, it was possible to use [files] like this:
DBG*.frm .\\compiled\\debug\\frm\\DBG*.frm
*.frm .\\compiled\\frm\\*.frm
Is there any way to tell UnifAce to do so with UF 10 ?
$RESOURCES_OUTPUT ??? = .\\compiled\\DBG_Components.uar
$RESOURCES_OUTPUT ??? = .\\compiled\\Components.uar
This redirection should happen at compile time and not later when it goes to develop!
Ingo
Hi Peter
I know all this possibilities, but none of them are doing the same then the good old UF9
So we have to do an extra task (time and cost) to separat components&co
Why do you break so much good things working perfect in UF9?
grumbel
BTW: we will do it like many other: developing in UF9 and then migrate - just for deployment - to UF10 until the editor and functionality is like UF9
Hi Peter
Yes, I know I can have multiple inputs for resources 🙂
BUT...
But I want to separate the files already at compile time in different UAR and/or directories
Due to our name schema, we do this in UF9 by [files]
So there was no need to take care, if a debug component find its way to customers
I heard, that UF10 is so much better then UF9, so ... 🙂
Ingo
I heard, that UF10 is so much better then UF9, so ... 🙂
Was it Donald Trump who told you that?
Then it's fake news 😉
Norbert
Hi Peter
Yes, I know I can have multiple inputs for resources 🙂
BUT...
But I want to separate the files already at compile time in different UAR and/or directories
Due to our name schema, we do this in UF9 by [files]
So there was no need to take care, if a debug component find its way to customers
I heard, that UF10 is so much better then UF9, so ... 🙂
Ingo
lol
Hi Freaks
(Test)Migration from UnifAce 9 to UnifAce 10 almost done.
Now I want't to set up a deployment setting where I use UAR instead of output to directories.
But not all "things" should go into one UAR.
e.g.
1. APS and global objects into another UAR
2. Specific components should in another UAR (like debug-tools)
In good old time, it was possible to use [files] like this:
DBG*.frm .\\compiled\\debug\\frm\\DBG*.frm
*.frm .\\compiled\\frm\\*.frm
Is there any way to tell UnifAce to do so with UF 10 ?
$RESOURCES_OUTPUT ??? = .\\compiled\\DBG_Components.uar
$RESOURCES_OUTPUT ??? = .\\compiled\\Components.uar
This redirection should happen at compile time and not later when it goes to develop!
Ingo
What we do is to set the resources_output to one place, and then use the command line "urm.exe" move which takes wildcards to split the output into different chunks (We split forms into on UAR, services into another and leave the rest in a general one.) as a batch file. (We compile the whole system every night, so it goes on the end of the batch file. )
I do have a wishlist entry for switches similar to those you've requested, Feel free to vote for it, you never know, the Labs may actually develop one of the wishes 🙂
We split ours, because we are using web-services to distribute new versions to our customers, and the files were getting a little big, but other than that, and aesthetic reasons, I'm not sure why you would want them split?
Iain
Hi Peter
I know all this possibilities, but none of them are doing the same then the good old UF9
So we have to do an extra task (time and cost) to separat components&co
Why do you break so much good things working perfect in UF9?
grumbel
BTW: we will do it like many other: developing in UF9 and then migrate - just for deployment - to UF10 until the editor and functionality is like UF9
Hello Ingo
Uniface 10 is about a new Uniface development environment:
The IDE is not and never will be a copy of Uniface 9 IDF.
If you like pressing buttons all the time to see for example simple field properties then Uniface 9 is your thing.
The IDE needs to be a modern tool so newer generations will keep on using Uniface.
Improving Uniface 10 , adding functionality is an ongoing process.
Every 2 weeks there is a patch with added features , currency and fixes.
The editor is one off the things we are currently looking at.
User-Defined Options for IDE menus and User-Defined Worksheets for IDE editors also make it also possible to add your set off tools in the IDE.
Migration from Uniface 9 to Uniface 10 is intended and designed as a one time action.
When migrating multiple times best is each time to start with empty Uniface 10 repository.
Peter
