You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we don't rely on any file to configure the behavior of EWF classes.
But in practice, the code may have hard-coded port number when connector is Nino, or verbose status settings.
And for nino, we can imagine many more settings in the future.
Thanks to WSF_SERVICE_LAUNCHER_OPTIONS_FROM_INI , we have a simple way to use an ini file for those settings.
But what about having a default configuration location and format.
And by default, the EWF code would load in order
if environment variable EWF_INI is set to an existing file
if there is a ewf.ini in the current path
if there is a ewf.ini in /etc/ewf/conf/ewf.ini , or on Windows %APP_DATA%/... (to be defined)
An alternative would be to have a ewf folder instead of a file, this way we can reuse it for other purpose.
For instance, we could have various tool in it that could be reused, even resources such as icons, and so on.
And we could have EWF module that could reuse this folder, such as CMS, or gewf tool, ...
So we could just use
environment variable EWF_DIR
or ".ewf" in current folder
or "/etc/ewf" on linux, ...
About Nino and port number, probably, this should not be set from EWF code, but we could have an alternative with a "nino" specific configuration file.
All this are for now just idea, but with "gewf", and also "cms" component, sometime I would love to have such common place.
Maybe this is not that easy for now to have a system wide folder, since this would be a trouble with application compiled with various EWF framework, but soon or later we should start thinking about it.
The text was updated successfully, but these errors were encountered:
Currently we don't rely on any file to configure the behavior of EWF classes.
But in practice, the code may have hard-coded port number when connector is Nino, or verbose status settings.
And for nino, we can imagine many more settings in the future.
Thanks to WSF_SERVICE_LAUNCHER_OPTIONS_FROM_INI , we have a simple way to use an ini file for those settings.
But what about having a default configuration location and format.
And by default, the EWF code would load in order
An alternative would be to have a ewf folder instead of a file, this way we can reuse it for other purpose.
For instance, we could have various tool in it that could be reused, even resources such as icons, and so on.
And we could have EWF module that could reuse this folder, such as CMS, or gewf tool, ...
So we could just use
About Nino and port number, probably, this should not be set from EWF code, but we could have an alternative with a "nino" specific configuration file.
All this are for now just idea, but with "gewf", and also "cms" component, sometime I would love to have such common place.
Maybe this is not that easy for now to have a system wide folder, since this would be a trouble with application compiled with various EWF framework, but soon or later we should start thinking about it.
The text was updated successfully, but these errors were encountered: