Activity

From 11/09/2023 to 12/08/2023

12/08/2023

09:49 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Sergey Ivanovskiy wrote:
> We can change the code of @WebClientsManager@ for the case when agent range is not config... Hynek Cihlar
09:47 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Sergey Ivanovskiy wrote:
> At this moment the debug mode is not enabled if the agent range is not configured. For th... Hynek Cihlar
08:43 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Sergey Ivanovskiy wrote:
> These web client settings (under @webClient@ node)
> [...]
> are set automatically for... Greg Shah
07:22 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: We can change the code of @WebClientsManager@ for the case when agent range is not configured but the @jvmArgs@ is gi... Sergey Ivanovskiy
07:10 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: The agent range is common for the debugger and jmx agents so jvmArgs just describes jmx and/or debug agents should be... Sergey Ivanovskiy
07:06 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: At this moment the debug mode is not enabled if the agent range is not configured. For the known application there ar... Sergey Ivanovskiy
06:48 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Sergey Ivanovskiy wrote:
> The agent port is assigned by @WebClientManager@ that reads @jvmArgs@ option in the direc... Hynek Cihlar
06:31 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Hynek Cihlar wrote:
> Code review 7824a revisions 14862..14867.
>
> I may be misinterpreting the changes, but I d... Sergey Ivanovskiy
05:05 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Hynek Cihlar wrote:
> Code review 7824a revisions 14862..14867.
>
> I may be misinterpreting the changes, but I d... Hynek Cihlar
05:04 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Code review 7824a revisions 14862..14867.
I may be misinterpreting the changes, but I don't see how the debug mode... Hynek Cihlar
02:46 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: These web client settings (under @webClient@ node) ... Sergey Ivanovskiy
02:16 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: This is what was changed in this task in one patch. Sergey Ivanovskiy
02:13 AM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Hynek, please review rev 14867 (7824a) that removed @MAX_HTTP_IDLE_TIMEOUT@ and added @CONNECTION_TIMEOUT@ and @INFIN... Sergey Ivanovskiy

12/07/2023

03:01 PM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Is there any documentation about the connection settings (the full set, not just the ones changed here)?
Hynek: Pl... Greg Shah
12:25 PM Bug #7824: Simplify idle connection settings and apply the default configuration for the web clie...: Could this task be reviewed? I rebased 7824a. Sergey Ivanovskiy
10:42 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> Eric: Is @org.apache.commons.lang3.tuple.*@ a supported/approved library for use in persistence? ... Eric Faulhaber
10:06 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > I've been obedient adding the overloaded method with the logical name, but where is the java @SsoAuthenticator@ get... Greg Shah
09:55 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: I've been obedient adding the overloaded method with the logical name, but where is the java @SsoAuthenticator@ getti... Galya B
09:51 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: We're doing a default authentication for SSO login, where the customer should not know anything about the details, bu... Galya B
09:50 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> Supplement to the code review: the @ldbname@ parameter must be processed case insensitively (e.g.... Galya B
09:45 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Supplement to the code review: the @ldbname@ parameter must be processed case insensitively (e.g. storing/retrieving ... Greg Shah
09:20 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: >
> > Anyway, the directory database cfgs are there for runtime usage. Any usage from import is a side usage.
> >... Greg Shah
09:17 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> > > I thought I had answered this in #7884-25. We are reworking the code DB logic into sessionle... Galya B
09:15 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > Such reader will need to learn to read the names of the classes and the javadoc, where it says:
My comment stand... Greg Shah
09:10 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> > > 2. The logic in @connectToDb()@ which reads configuration from the directory is also somethin... Galya B
09:01 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> Galya B wrote:
> > Greg Shah wrote:
> > > > 4. There is nothing hidden. The connection is clean... Galya B
09:00 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya B wrote:
> Greg Shah wrote:
> > > 4. There is nothing hidden. The connection is cleaned up on JVM shutdown.
... Greg Shah
08:58 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > > I thought I had answered this in #7884-25. We are reworking the code DB logic into sessionless code that is in F... Greg Shah
08:55 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > 2. Is it better to create a DB connection on each login attempt in a live system?
This was a retorical question. Galya B
08:54 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> > 4. There is nothing hidden. The connection is cleaned up on JVM shutdown.
>
> I mean it is a... Galya B
08:52 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > 1. It's expected to be only one connection.
Per database instance. This may be many connections to a given clus... Greg Shah
08:50 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> I thought I had answered this in #7884-25. We are reworking the code DB logic into sessionless c... Galya B
08:49 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > > 2. The logic in @connectToDb()@ which reads configuration from the directory is also something that should not be... Greg Shah
08:40 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya B wrote:
> Greg Shah wrote:
> > Code Review Task Branch 7884a Revision 14843
> >
> > 1. I think the logic ... Greg Shah
08:24 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> 3. I don't think it is a good idea to implement long lived connections to the database here, nor ... Galya B
08:18 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> 2. The logic in @connectToDb()@ which reads configuration from the directory is also something th... Galya B
08:15 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> Code Review Task Branch 7884a Revision 14843
>
> 1. I think the logic for obtaining the defaul... Galya B
07:27 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Code Review Task Branch 7884a Revision 14843
1. I think the logic for obtaining the default database name (@Databa... Greg Shah
07:21 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Eric: Is @org.apache.commons.lang3.tuple.*@ a supported/approved library for use in persistence? I see it used there... Greg Shah
07:06 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: r14843: @setuserid(userid, password, ldbname)@. Galya B
06:45 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: It will optionally be present in the original 4GL code. There are 2 forms:
* @setuserid(userid, password)@
* @se... Greg Shah
02:26 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> My primary concern is that we don't support the @ldbname@ parameter variant of @setuserid()@. I ... Galya B
02:22 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Ovidiu Maxiniuc wrote:
> For the second part. Provided the @ldbname@, the database configuration from registry can b... Galya B
09:23 PM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: I reviewed the changes in 7884a.
I am OK with the changes. My concerns were for:
* duplicate code;
* hardcoded t... Ovidiu Maxiniuc
02:19 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Eugenie Lyzenko wrote:
> In general I have no objections.
>
> But I have the question and the clear answer is ver... Galya B

12/06/2023

04:20 PM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Code Review Task Branch 7884a Revisions 14840 through 14842
The overall approach is reasonable. Ovidiu and Eric w... Greg Shah
07:31 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: 7884a r14842 ready for review. The dialect and conversion specifics now shared between @MetadataSecurityOps.NoSession... Galya B
05:23 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya, yes, @SQL_MODE_DEFAULT@ is the default if otherwise not specified in p2j.cfg.xml, as a @conversion="minimal"@ ... Constantin Asofiei
03:40 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya B wrote:
> Is the "conversion" always @SQL_MODE_DEFAULT@. I don't see a case where @NsConfig.setConversion@ is... Galya B
03:33 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: In general I have no objections.
But I have the question and the clear answer is very important. How the custom th... Eugenie Lyzenko
12:56 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Eugenie/Hynek: Please review. Greg Shah

12/05/2023

11:58 AM Bug #8098: The task bar without tasks is not displayed or drawn if ui program displays a lonely d...: The task bar is not displayed for this program... Sergey Ivanovskiy
09:29 AM Bug #8098 (New): The task bar without tasks is not displayed or drawn if ui program displays a lo...: Sergey Ivanovskiy
07:37 AM Bug #8074 (Review): Preferred UI Theme not selected in web with auto-login and forked sessions: 8074a based on trunk r14859 ready for review. Includes (in order of appearance):
* Theme options include an empty op... Galya B
04:38 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: A note: The path in @FallbackEnvironmentReader@ when using @Preferences@ is composed from root user node @~/.java/.us... Galya B
02:17 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> > But java @Preferences@ is case-sensitive, so we can either keep the original names (envs / keys... Galya B

12/04/2023

01:38 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > But java @Preferences@ is case-sensitive, so we can either keep the original names (envs / keys / sections), or mak... Greg Shah
12:01 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: @EnvironmentDaemon@ is almost case-insensitive (check occurrences of @.toLowerCase()@). I guess it started with the r... Galya B
08:54 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Eugenie Lyzenko wrote:
> Greg Shah wrote:
> > > Also there is a problem in registry where the @base_name@ is actual... Galya B
08:43 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> > Also there is a problem in registry where the @base_name@ is actually not used in the native co... Eugenie Lyzenko
08:26 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> Galya B wrote:
> > Actually there is another conversion issue with the example.
> >
> > It ha... Galya B
08:20 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > Also there is a problem in registry where the @base_name@ is actually not used in the native code. The char is load... Greg Shah
08:18 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Galya B wrote:
> Actually there is another conversion issue with the example.
>
> It has @PUT-KEY-VALUE SECTION "... Greg Shah
07:45 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Also there is a problem in registry where the @base_name@ is actually not used in the native code. The char is loaded... Galya B
07:30 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Actually there is another conversion issue with the example.
It has @PUT-KEY-VALUE SECTION "PSC\Clue\TEMP-PRGM" KE... Galya B
06:27 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: I'm trying to convert an example procedure from "here":https://community.progress.com/s/article/21529.
Edited: Co... Galya B
02:52 AM Feature #4203 (Test): expose some web-client details as 4GL global variables: 4203a was merged to trunk as rev. 14856 and archived. Galya B

12/03/2023

09:39 AM Bug #8095: LEAVE trigger fires in no focus change situation: In the following code, a @FILL-IN@ is created in its own frame, and three @ON LEAVE@ triggers are attached to the @FI... Vladimir Tsichevski
08:07 AM Bug #8095 (New): LEAVE trigger fires in no focus change situation: Vladimir Tsichevski

12/01/2023

10:08 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > > > Indeed, the use of @setuserid@ is very common.
> > As far as I understand @setuserid@ is a common DB authent... Greg Shah
04:07 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Is the "conversion" always @SQL_MODE_DEFAULT@. I don't see a case where @NsConfig.setConversion@ is used. Galya B
10:00 AM Feature #4203 (Merge Pending): expose some web-client details as 4GL global variables: Greg Shah
02:08 AM Feature #4203: expose some web-client details as 4GL global variables: I've tested with testcases all types of drivers. The procedure I used is a simple @message FWD-CLIENT-DRIVER@. I also... Galya B
09:13 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: My bad. The enhanced configs for all users are stored in directory, so this is not in conflict with isolating the use... Galya B

11/30/2023

12:56 PM Feature #4203 (Internal Test): expose some web-client details as 4GL global variables: Code Review Task Branch 4203a Revision 14851
The changes are good. Greg Shah
09:09 AM Feature #4203 (Review): expose some web-client details as 4GL global variables: 4203a r14851 based on trunk r14850 ready for review. Implements @FWD-CLIENT-DRIVER@, adds short readable names to dri... Galya B
08:28 AM Feature #4203: expose some web-client details as 4GL global variables: Greg Shah wrote:
> The value should be added to @ClientParameters@ at startup so that it is always available at the ... Galya B
08:23 AM Feature #4203 (WIP): expose some web-client details as 4GL global variables: Galya B
08:18 AM Feature #4203: expose some web-client details as 4GL global variables: The value should be added to @ClientParameters@ at startup so that it is always available at the server (without the ... Greg Shah
08:32 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> > There are only two solutions: either we "degrade" the functionality by removing both options, o... Galya B
08:18 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > > Anything that targets more than the current user must (by definition) be stored in the directory, not in user-spe... Greg Shah
01:40 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> What changes are needed in @SsoAuthenticator@ to provide the @storageId@?
It is present in the i... Galya B

11/29/2023

03:32 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: The value should be added to @ClientParameters@ at startup so that it is always available at the server (without the ... Greg Shah
03:05 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > I'm working on isolating the users in the client storage, but I forgot that the enhanced browse configs can be appl... Greg Shah
03:04 PM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > Since we probably don't have enough control over the customer behavior, then the solution I propose is to always in... Greg Shah
03:12 PM Feature #4203: expose some web-client details as 4GL global variables: > May I ask if the IPs will be used for licensing in 4GL? Because I would hope, since the IPs (the external one and t... Greg Shah
02:02 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Ovidiu Maxiniuc wrote:
> Just a small observation: at line 406 in @MetadataSecurityOps@, @SecurityOps._encode(String... Galya B

11/28/2023

03:03 PM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Review of 7884a, r14840.
The new code in @MetadataSecurityOps.java@ is well written. Just a small observation: at ... Ovidiu Maxiniuc
08:09 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: I'm working on isolating the users in the client storage, but I forgot that the enhanced browse configs can be applie... Galya B

11/27/2023

08:24 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Ovidiu: Please review. Consider if there is any common code that can be shared with the existing session-based @setu... Greg Shah
04:59 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: If we want to support multiple users in one browser, then the theme drop-down on the login page should never have a p... Galya B

11/24/2023

05:57 AM Bug #8074 (WIP): Preferred UI Theme not selected in web with auto-login and forked sessions: Since we probably don't have enough control over the customer behavior, then the solution I propose is to always inco... Galya B
05:49 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Basically the authentication code presented in #3931-435 is moved from @HotelGuiSsoAuthenticator@ to @MetadataSecurit... Galya B
05:37 AM Feature #7884 (Review): Standard 4GL methods used for login screen authentication to be exposed i...: Galya B
05:37 AM Feature #7884 (WIP): Standard 4GL methods used for login screen authentication to be exposed in s...: 7884a r14840: MetadataSecurityOps.NoSessionHelper class added to support sso login screen authentication. Galya B

11/23/2023

10:55 AM Feature #4203: expose some web-client details as 4GL global variables: May I ask if the IPs will be used for licensing in 4GL? Because I would hope, since the IPs (the external one and the... Galya B
10:35 AM Feature #4856 (Test): web client session forking: 7813a was merged to trunk as rev. 14839 and archived. Galya B
10:19 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: So I'm seeing the options as:
1. All users happily share the same configs and override each other;
2. The customer ... Galya B
09:59 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: The core issue is that in the original OE 'end user' == 'OS user' and client storage (registry, ini) rarely clashes b... Galya B
09:47 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: This @storageId@ should ensure the same client process reused by many users can store end user specific info in indep... Galya B
09:38 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: The solution should not be specific to SSO. Why not just use the FWD account name or some UUID associated with the F... Greg Shah
09:36 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> Where is the @storageId@ coming from?
Hopefully from well written @SsoAuthenticator@ implementat... Galya B
09:32 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: I agree that we don't have to worry about the existing production cfg values. Right now is the best time to make any ... Greg Shah
09:27 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Maybe now it's the right time to do it, since we've just launched the methods accessing client storage, up till now t... Galya B
09:22 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: I ponder on more trivial matters like: Should I break all current prod client storage configs and add the @storageId@... Galya B
09:17 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Some customer applications do use their own subclasses of our themes. When doing so, these themes are registered in ... Greg Shah
09:09 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: Greg Shah wrote:
> > you were mentioning before there are supposed to be changes related to themes.
>
> Can you ... Galya B
09:06 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: > you were mentioning before there are supposed to be changes related to themes.
Can you remind me of where/when ... Greg Shah
06:50 AM Bug #8074: Preferred UI Theme not selected in web with auto-login and forked sessions: The flows of auto-login and forking a new session in web bypass the login screen, thus a preferred UI theme can't be ... Galya B
06:48 AM Bug #8074 (Closed): Preferred UI Theme not selected in web with auto-login and forked sessions: Galya B
09:11 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: It is a good point. I think what we are looking for here is to expose the authentication check itself, without the p... Greg Shah
08:38 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: There is something tricky with exposing @setuserid@ before the session has started. It can be used to validate the lo... Galya B

11/22/2023

01:59 PM Feature #4856 (Internal Test): web client session forking: Greg Shah
08:10 AM Feature #4856 (Review): web client session forking: In 7813a r14861 virtual desktop taskbar menu item 'New Session' is wired up to @SessionUtils.forkNewSesion@. Galya B
09:42 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Greg Shah wrote:
> I'm not opposed to exposing some useful state out to the 4GL code (like the web client IP address... Galya B
09:39 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Don't work on this right now. I am discussing the requirement with the customer and they may be dropping it on their... Greg Shah
09:32 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Also I'm always thinking of a flow where the IP and fingerprint don't matter, but it works only when 'one browser' po... Galya B
09:27 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Can I implement a simple fingerprint myself? It will take a while to figure out how to test the canvas and the audio,... Galya B
05:54 AM Feature #3931: single sign-on for virtual desktop mode: I think we should reference the feature as simple sign-on (SSO). This way we'll be keeping all the SSO references, bu... Galya B
05:25 AM Bug #8012: Fix combo-box corner cases: After putting some thought into this, I came up with a format that, IMO, would make the changes relatively easy to re... Radu Apetrii

11/21/2023

04:26 PM Bug #7515: FILL-IN: editing dates issues: Vladimir Tsichevski wrote:
> # The @gso_171@ test: the @Dist date@ is @01/01/-099@ instead of expected @01/01/-999... Vladimir Tsichevski
12:31 PM Feature #4856: web client session forking: > Can I directly execute 4GL method from the front-end
Not from the virtual desktop. Embedded mode does have tool... Greg Shah
09:07 AM Feature #4856: web client session forking: Can I directly execute 4GL method from the front-end or I need to create a new WebSocket msg and handle it all the wa... Galya B
06:19 AM Bug #8012: Fix combo-box corner cases: I added to @testcases/uast/combo_box/screen_value@ some more tests regarding @ADD-LAST@, @ADD-FIRST@, @LIST-ITEM-PAIR... Radu Apetrii

11/18/2023

02:23 PM Bug #7515: FILL-IN: editing dates issues: Running MAJIC tests revealed at teast two regressions in ChUI in @7019a@:
# incorrect behavior of date @FILL-IN@ f... Vladimir Tsichevski

11/17/2023

07:18 AM Bug #7946 (Test): Default selection and current browse row color differs for different customers ...: Greg Shah

11/15/2023

08:01 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > It will hide the implementation details, which can be considered an improvement,
This isn't just an improvement... Greg Shah
07:43 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> No, I don't think that is a likely approach. Those classes are tightly coupled to context, to th... Galya B
07:41 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: No, I don't think that is a likely approach. Those classes are tightly coupled to context, to the legacy transaction... Greg Shah
07:36 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: OK, so then we agree to proceed with reworking the core FWD DB classes to work without context, so that the DB check ... Galya B
07:28 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > > Indeed, the use of @setuserid@ is very common.
> As far as I understand @setuserid@ is a common DB authenticat... Greg Shah
07:25 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya B wrote:
> Greg Shah wrote:
> > Indeed, the use of @setuserid@ is very common.
> As far as I understand @s... Galya B
07:23 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Greg Shah wrote:
> Indeed, the use of @setuserid@ is very common.
As far as I understand @setuserid@ is a common ... Galya B
07:23 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: > I need a definition of 'properly'.
Directly showing the replacement of the original 4GL authentication method, e... Greg Shah
07:21 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: Galya wrote:
> Actually hotel gui works properly and exemplary now (tested with h2). The raised concern was that i... Greg Shah
07:21 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: I need a definition of 'properly'. Galya B
07:19 AM Feature #7884: Standard 4GL methods used for login screen authentication to be exposed in session...: We may want to work part of this task so that the Hotel GUI SSO is properly implemented as an example. Greg Shah
07:03 AM Feature #4856: web client session forking: > > Is 7813a involved in future headway on this task?
> Yes. It will use the same mechanism, started in a different ... Greg Shah
01:49 AM Feature #4856: web client session forking: Greg Shah wrote:
> Is 7813a involved in future headway on this task?
Yes. It will use the same mechanism, started i... Galya B

11/14/2023

02:13 PM Feature #4856: web client session forking: Is 7813a involved in future headway on this task? Greg Shah

11/09/2023

03:39 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: 7946a has been merged into the trunk as bzr revision 14825.
app_C changes to the @directory.xml@ template have been ... Stanislav Lomany
01:33 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: @app_A@ actually uses Material theme and therefore it hasn't been regressed by the Windows 10 theme changes as I assu... Stanislav Lomany
11:38 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: > should I commit?
Yes, you can merge to trunk now.
>I think that for @app_A@ we should set the new Windows 2... Greg Shah
11:07 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: Greg, I think that for @app_A@ we should set the new Windows 2012 theme, and for @app_C@ - enable the new @oldBrowseS... Stanislav Lomany
11:04 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: > The assignment of @oldBrowseSelectionBar@ in @EBCM.isOldBrowseSelectionBar@ should be double-locked
Fixed in 794... Stanislav Lomany
03:05 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: Code review 7946a.
The assignment of @oldBrowseSelectionBar@ in @EBCM.isOldBrowseSelectionBar@ should be double-lo... Hynek Cihlar

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » User Interface

Activity

Activity

12/08/2023

12/07/2023

12/06/2023

12/05/2023

12/04/2023

12/03/2023

12/01/2023

11/30/2023

11/29/2023

11/28/2023

11/27/2023

11/24/2023

11/23/2023

11/22/2023

11/21/2023

11/18/2023

11/17/2023

11/15/2023

11/14/2023

11/09/2023