Activity

From 10/23/2023 to 11/21/2023

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

11/08/2023

08:05 AM Bug #7946: Default selection and current browse row color differs for different customers applica...: Hynek: Please review. Greg Shah
12:56 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Greg Shah wrote:
> The device id needs to be persistent across browser restarts and past the point where all FWD s... Galya B
12:39 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Greg Shah wrote:
> There should be no association (at the FWD level) between accounts and devices. I don't want to ... Galya B

11/07/2023

05:08 PM Bug #7946 (Review): Default selection and current browse row color differs for different customer...: The fix is in 7946a rev 14826. Please review. Stanislav Lomany
12:30 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: Rebased task branch 7946a from FWD trunk revision 14824. Stanislav Lomany
10:20 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: There should be no association (at the FWD level) between accounts and devices. I don't want to mix the two concepts... Greg Shah
09:36 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: A few aspects to be taken into consideration are: simultaneous logins; the fact that sessions in the same browser can... Galya B
09:22 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: The browser id will be changed the moment all sessions are closed. We can have server-side initiated checks for who l... Galya B
09:18 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Greg Shah wrote:
> > It's doable to create a mechanism confirming which web sessions are in the same browser with Br... Galya B
09:01 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: > It's doable to create a mechanism confirming which web sessions are in the same browser with Broadcast Channel comm... Greg Shah
08:19 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Also obviously it doesn't depend on id that can be altered, but real time communication between the live sessions. Galya B
08:11 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Galya B wrote:
> I have one blurred idea without clear form yet. It's doable to create a mechanism confirming which ... Galya B
08:09 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: I have one blurred idea without clear form yet. It's doable to create a mechanism confirming which web sessions are i... Galya B
08:03 AM Feature #4853: implement support for reporting a device-id which is meant to identify a unique cl...: Since there is no good solution for fingerprinting or even for detecting the network configuration, I think we just i... Greg Shah
08:05 AM Bug #8012 (WIP): Fix combo-box corner cases: There are quite a lot of corner cases regarding combo-boxes. While working on another task, I managed to identify a f... Radu Apetrii
06:49 AM Bug #8012 (Test): Fix combo-box corner cases: Radu Apetrii
06:57 AM Feature #3931: single sign-on for virtual desktop mode: Galya B wrote:
> Guido Brandsen wrote:
> > Galya, today we saw a minor problem with client spawning.
> > The error... Galya B
06:55 AM Feature #4517 (Test): optionally back the 4GL features for Registry access with the user-specific...: 4854a was merged to trunk as rev. 14823 and archived.
It's important customers to get familiar with the table in #... Galya B
06:51 AM Feature #4854 (Test): origin affinity: 4854a was merged to trunk as rev. 14823 and archived. Galya B
06:31 AM Feature #4854: origin affinity: Galya, you can merge to trunk now. Greg Shah
06:27 AM Feature #4854: origin affinity: Greg Shah wrote:
> Galya: If Sergey is OK with the code, then we will queue this for merge.
The changes are OK for ... Sergey Ivanovskiy
01:58 AM Feature #4854: origin affinity: Sergey Ivanovskiy wrote:
> Found minor issue related to
> [...]
Fixed in r14836.
Galya B

11/06/2023

03:25 PM Feature #4854: origin affinity: Found minor issue related to... Sergey Ivanovskiy
12:58 PM Feature #4854: origin affinity: Galya: If Sergey is OK with the code, then we will queue this for merge. Greg Shah
12:56 PM Feature #4854: origin affinity: Galya B wrote:
> Sergey,
>
> I've changed @UserPreferences.MAXIMAL_STRING_LENGTH@ to @6@ and saved the browse con... Sergey Ivanovskiy
12:43 PM Feature #4854: origin affinity: Code review 4854a. The changes look good. Hynek Cihlar
12:05 PM Feature #4854: origin affinity: Just a note: If @webClient/useLocalStorage@ is @TRUE@ in Windows it applies only for enhanced browse configs, but not... Galya B
12:01 PM Feature #4854: origin affinity: I couldn't start web in Windows VM, there is a new issue with networking/ports I don't want to know about, but web cl... Galya B
12:00 PM Feature #4854: origin affinity: Stanislav Lomany wrote:
> The code looks good. I did some testing and it works fine. One minor thing: javadoc for @U... Galya B
11:56 AM Feature #4854: origin affinity: Registry in Windows is working as before:
!windows-registry.png!
But doesn't look good in that place. Galya B
11:50 AM Feature #4854: origin affinity: The code looks good. I did some testing and it works fine. One minor thing: javadoc for @UserPreferences()@ is missing. Stanislav Lomany
10:33 AM Feature #4854: origin affinity: Sergey/Hynek/Stanislav: Please review. Greg Shah
10:10 AM Feature #4854: origin affinity: r14834:
* Applies the change to @UserPreferences.delete@ as described in #4854-147;
* @com/goldencode@ as root node... Galya B
09:24 AM Feature #4854: origin affinity: Sergey,
I've changed @UserPreferences.MAXIMAL_STRING_LENGTH@ to @6@ and saved the browse configs.
KEY @enhanced... Galya B
09:02 AM Feature #4854: origin affinity: I still haven't tested registry in Windows. Galya B
09:02 AM Feature #4854: origin affinity: Is the only remaining known issue the "delete chunks" problem?
Is there any remaining testing to do? Greg Shah
08:27 AM Feature #4854: origin affinity: r14833:
* fixes for @LOAD INI@. Tested with:... Galya B
08:18 AM Feature #4854: origin affinity: I guess we'll need another stopper instead of root preferences. Maybe "chunks" node. I'll have to test chunks first t... Galya B
08:16 AM Feature #4854: origin affinity: Galya B wrote:
> I'm not sure how to test the chunks. Can you give me an example how it should be stored in the path... Sergey Ivanovskiy
08:04 AM Feature #4854: origin affinity: Galya, I don't know how chunks work in details, I dealt only with higher level of abstraction which is @TC.setObject(... Stanislav Lomany
07:52 AM Feature #4854: origin affinity: I'm not sure how to test the chunks. Can you give me an example how it should be stored in the path? This @enhancedBr... Galya B
07:48 AM Feature #4854: origin affinity: The idea was to remove all chain of chunks because one chain stores key and value. I do not check if this logic is pr... Sergey Ivanovskiy
07:18 AM Feature #4854: origin affinity: Stanislav, I've encountered a behavior in enhanced browse:
1. Save @This Browse, Current User@;
2. Save @All Brow... Galya B
04:51 AM Feature #4854: origin affinity: 4854a re-based on latest trunk r14819. Galya B

11/03/2023

10:25 AM Feature #4854: origin affinity: . Galya B
09:52 AM Feature #4854: origin affinity: . Galya B
08:32 AM Feature #4854: origin affinity: > From SVL:
>
> Assuming that it's OK that we've moved from the in-browser storage to the file system (java prefs),... Greg Shah
04:43 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> Found #4854-103, I got now what you and Greg meant. The change in #4854-135 is OK.
Than... Galya B
04:41 AM Feature #4854: origin affinity: Galya B wrote:
> Constantin Asofiei wrote:
> > Thanks for bearing with me. Please add back the @catch (Exception@ t... Constantin Asofiei
04:31 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> Thanks for bearing with me. Please add back the @catch (Exception@ to get any unexpected... Galya B
04:28 AM Feature #4854: origin affinity: Thanks for bearing with me. Please add back the @catch (Exception@ to get any unexpected abends, and for these:
* th... Constantin Asofiei
04:23 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> Galya, one more question, please: can you point where the ErrorConditionException is rai... Galya B
04:17 AM Feature #4854: origin affinity: Galya, one more question, please: can you point where the ErrorConditionException is raised in 4854a, and caught by @... Constantin Asofiei
04:08 AM Feature #4854: origin affinity: The error is non-OE one, but had to be treated like OE errors, so I used @ErrorConditionException@ like similar expor... Galya B
03:54 AM Feature #4854: origin affinity: Galya B wrote:
> Constantin Asofiei wrote:
> > * we need to add a specific @catch (ErrorConditionException@ for the... Constantin Asofiei
03:53 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> * we need to add a specific @catch (ErrorConditionException@ for these kind of errors. T... Galya B
03:51 AM Feature #4854: origin affinity: The confusing part is the usage of @catch (Exception@. So, as the FWD client can throw @ErrorConditionException@, pl... Constantin Asofiei
03:45 AM Feature #4854: origin affinity: Constantin Asofiei wrote:
> Galya, @catch Exception@ will show a Java-style error message for things like abends and... Galya B
03:38 AM Feature #4854: origin affinity: Galya, @catch (Exception@ will show a Java-style error message for things like abends and others. What kind of excep... Constantin Asofiei
03:35 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> Hynek Cihlar wrote:
> > Galya B wrote:
> > > Hynek Cihlar wrote:
> > > > No, it's not. You ... Galya B
03:18 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> Galya B wrote:
> > Hynek Cihlar wrote:
> > > No, it's not. You only log the error message, b... Hynek Cihlar
03:14 AM Feature #4854: origin affinity: Galya B wrote:
> Hynek Cihlar wrote:
> > No, it's not. You only log the error message, but not the call stack. We n... Hynek Cihlar
02:58 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> Galya B wrote:
> > Hynek Cihlar wrote:
> > > The exception caught in @EnvironmentOps.setKeyV... Galya B
02:55 AM Feature #4854: origin affinity: Galya B wrote:
> Hynek Cihlar wrote:
> > The exception caught in @EnvironmentOps.setKeyValue@ should be logged. Whi... Hynek Cihlar
02:36 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> The exception caught in @EnvironmentOps.setKeyValue@ should be logged. While the message is sh... Galya B

11/02/2023

12:17 PM Feature #4854: origin affinity: Code review 4854a revision 14804.
The exception caught in @EnvironmentOps.setKeyValue@ should be logged. While th... Hynek Cihlar
10:10 AM Feature #4854: origin affinity: Hmm. The encryption point is a good one. We don't know how this will be used. Even for configuration data, this is... Greg Shah
09:28 AM Feature #4854: origin affinity: If they use the storage / registry for configurations, it won't matter much, otherwise the customers need to use thei... Galya B
09:26 AM Feature #4854: origin affinity: Hynek Cihlar wrote:
> * In @ClientStorageImpl.java@ the copyright message is broken, the line with GNU location is r... Galya B
08:14 AM Feature #4854: origin affinity: Code review 4854a 14792..14803.
The changes look good. Just a couple of points below.
* In @ClientStorageImpl.j... Hynek Cihlar
06:13 AM Feature #4854: origin affinity: Fix in r14803.
Testing methods:
Prerequisite for @localStorage@ as client storage is adding:... Galya B
04:23 AM Feature #4854: origin affinity: I'll go over the major changes in the order they appear with diff:
* With 3931a the login page @web_landing.html@ ha... Galya B
11:32 AM Feature #7997: Encryption for client storage data / registry: Yes, and we need to decide if we would use a server-wide key or if we would implement per-account level keys. Greg Shah
10:27 AM Feature #7997: Encryption for client storage data / registry: What encryption? It should be reversible. Galya B
10:26 AM Feature #7997: Encryption for client storage data / registry: Registry is accessed in 4GL via @GET-KEY-VALUE@ and @PUT-KEY-VALUE@ methods. In FWD registry is backed up by differen... Galya B
10:18 AM Feature #7997 (New): Encryption for client storage data / registry: Galya B

11/01/2023

04:48 PM Feature #4854: origin affinity: Greg Shah wrote:
> Eugenie/Hynek/Sergey: Please review 4854a.
I have no objections in general(just because it is ... Eugenie Lyzenko
02:48 PM Feature #4854: origin affinity: Eugenie/Hynek/Sergey: Please review 4854a. Greg Shah
11:28 AM Feature #4854 (Review): origin affinity: 4854a r14802 ready for review. Based on trunk r14792. Changes solve #4854, #4517 and a few unrelated small issues, in... Galya B
08:26 AM Feature #4854: origin affinity: I'm fine with that so long as it all matches the 4GL behavior. Greg Shah
08:05 AM Feature #4854: origin affinity: Greg Shah wrote:
> Does @GET-KEY-VALUE@ support @NO-ERROR@ in the 4GL?
No, it seems. I don't know what kind of er... Galya B
07:55 AM Feature #4854: origin affinity: Does @GET-KEY-VALUE@ support @NO-ERROR@ in the 4GL? Greg Shah
04:59 AM Feature #4854: origin affinity: How to suppress error from @GET-KEY-VALUE@? The following line produces @expecting DOT, found 'NO-ERROR'@:... Galya B
11:27 AM Feature #4517 (Review): optionally back the 4GL features for Registry access with the user-specif...: 4854a r14802 ready for review. Based on trunk r14792. Changes solve #4854, #4517 and a few unrelated small issues, in... Galya B
07:46 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: It is for consistency of the protocol and for performance. Greg Shah
03:21 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Why is WebSocket messaging using only byte arrays and no text messages? Is there a reason behind that decision or it ... Galya B

10/31/2023

04:35 AM Feature #3931: single sign-on for virtual desktop mode: Guido Brandsen wrote:
> Galya, today we saw a minor problem with client spawning.
> The error shown in OS login was... Galya B
04:30 AM Feature #3931: single sign-on for virtual desktop mode: Galya, today we saw a minor problem with client spawning.
The error shown in OS login was:... Guido Brandsen

10/30/2023

03:34 PM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: I'd prefer if both act the same way (default to preferences). Greg Shah
11:28 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: @Browse@ configs will continue to be saved only in @localStorage@, while registry will fallback to @Preferences@ by d... Galya B

10/27/2023

03:31 PM Feature #4854: origin affinity: Hynek Cihlar wrote:
> With @waitForResult@ you will make @MSG_SET_KEY_VALUE@ effectively synchronous. So I suppose t... Hynek Cihlar
03:28 PM Feature #4854: origin affinity: AFAIK every message deals with errors on its own, we don't have a common error handling mechanism. Look at @GuiWebSoc... Hynek Cihlar
03:24 PM Feature #4854: origin affinity: Galya B wrote:
> Is there any practice already in place for sending back errors from the front-end for WebSocket mes... Sergey Ivanovskiy
03:12 PM Feature #4854: origin affinity: Galya B wrote:
> 5 mil chars is quite a lot for config storage. This @localStorage@ will be available to customers t... Sergey Ivanovskiy
10:23 AM Feature #4854: origin affinity: Is there any practice already in place for sending back errors from the front-end for WebSocket messages? ... if some... Galya B
10:10 AM Feature #4854: origin affinity: > Currently @localStorage@ is used only for the enhanced @browse@ configs. There is no error handling in place. This ... Greg Shah
10:06 AM Feature #4854: origin affinity: Greg Shah wrote:
> I'm OK with storage limitations, so long as we have a consistent behavior that is exposed to the ... Galya B
08:15 AM Feature #4854: origin affinity: I'm OK with storage limitations, so long as we have a consistent behavior that is exposed to the 4GL code as a legacy... Greg Shah
01:48 AM Feature #4854: origin affinity: 5 mil chars is quite a lot for config storage. This @localStorage@ will be available to customers through the registr... Galya B
10:27 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: > It's doable, but then can we make localStorage the non-default, because it's more different?
Yes, that makes sense. Greg Shah
10:15 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Greg Shah wrote:
> Review of #4517-13:
> > Do we want the web under linux to also store in @Preferences.userRoot@? ... Galya B
10:08 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Review of #4517-13:
* Shouldn't the "Shared between" column for the @Win/other@ scenarios that use @LOAD BASE-KEY ... Greg Shah
09:54 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: I'm almost ready with the implementation. Can I have a review of the table? Galya B
09:17 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Greg Shah wrote:
> The table in #4517-13 is about FWD behavior (I think). Is this meant to document the current beh... Galya B
09:16 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Do we want the web under linux to also store in @Preferences.userRoot@? It will be more consistent to everything else... Galya B
09:16 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The table in #4517-13 is about FWD behavior (I think). Is this meant to document the current behavior before any cha... Greg Shah
09:13 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: > Do we want all web clients always to store registry in the browser for consistency?
No, some customers will want... Greg Shah
09:11 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The client process for web is on the server if no brokers are configured. And brokers are reused by multiple clients. Galya B
09:11 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Do we want all web clients always to store registry in the browser for consistency? Galya B

10/26/2023

12:05 PM Feature #4854: origin affinity: I guess that solution can be using a local storage for a different origin that extends the common origin. Sergey Ivanovskiy
11:04 AM Feature #4854: origin affinity: It seems that there is an open question how to extent a storage for a user as there is the web storage limit for the ... Sergey Ivanovskiy
10:06 AM Feature #4854: origin affinity: OK. I checked this test for the Firefox, so it follows that the @locationStorage@ storage is used per origin but not ... Sergey Ivanovskiy
09:54 AM Feature #4854: origin affinity: Unfortunately Redmine struggles with the 5MB texts for each value, so if you're not able to copy it from here, copy i... Galya B
09:44 AM Feature #4854: origin affinity: OK, here is the test (inspired by https://arty.name/localstorage.html):
Key 'test' is successfully saved, 'test2' ... Galya B
09:33 AM Feature #4854: origin affinity: I need to prove the Mozilla documentation? It's written in the link you shared https://developer.mozilla.org/en-US/do... Galya B
09:29 AM Feature #4854: origin affinity: I would agree if you proved it by the similar test that the storage is used per origin but not per a key. This test i... Sergey Ivanovskiy
09:11 AM Feature #4854: origin affinity: So do we agree on the change? Galya B
09:03 AM Feature #4854: origin affinity: Nice, I was about to write something. 5200000 chars max in my case. According to https://developer.mozilla.org/en-US/... Galya B
09:00 AM Feature #4854: origin affinity: You can use this test program https://arty.name/localstorage.html that checks... Sergey Ivanovskiy
08:21 AM Feature #4854: origin affinity: Galya B wrote:
> Sergey Ivanovskiy wrote:
> > Why @UserKeyValueStorage@ was removed? What is its substitution? @Use... Sergey Ivanovskiy
04:24 AM Feature #4854: origin affinity: Sergey Ivanovskiy wrote:
> Why @UserKeyValueStorage@ was removed? What is its substitution? @UserKeyValueStorage@ wa... Galya B
03:42 AM Feature #4854: origin affinity: Why @UserKeyValueStorage@ was removed? What is its substitution? @UserKeyValueStorage@ was needed to store large data... Sergey Ivanovskiy
04:43 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: The most obvious problem I see right away is with web users on Windows. All of them would share this "device id" the ... Galya B
03:19 AM Feature #4517: optionally back the 4GL features for Registry access with the user-specific offlin...: Storage for @GET-KEY-VALUE@ and @PUT-KEY-VALUE@:
|OS|@LOAD BASE-KEY "INI"@|Client Type|Storage|Storage lifespan|Sh... Galya B

10/25/2023

08:13 AM Feature #4854: origin affinity: Stanislav is the expert in enhanced browse. Greg Shah
08:13 AM Feature #4854: origin affinity: Hotel GUI embedded mode has the enhanced browse activated, but virtual desktop mode doesn't (if I recall correctly). Greg Shah
08:06 AM Feature #4854: origin affinity: For the old @testcases@ project I have these settings ... Sergey Ivanovskiy
07:54 AM Feature #4854: origin affinity: Galya, see this wiki: [[p2j:Browse_Widget_Enhancements]]. Hotel GUI has the enhanced browse (if it doesn't, then thi... Constantin Asofiei
07:51 AM Feature #4854: origin affinity: Sergey, can you help me with an example in 4GL for enhanced @browse@. I don't seem to understand how to enable the ge... Galya B
07:50 AM Feature #4854 (WIP): origin affinity: Although 4854 is done, 4854a will also have the changes for #4517, because both tasks are related in the code. Movin... Galya B

10/24/2023

12:33 AM Feature #3931: single sign-on for virtual desktop mode: Eugenie Lyzenko wrote:
> Galya,
>
> Should the following entries also be removed from @directory.xml@?
>
> [..... Galya B

10/23/2023

03:36 PM Feature #3931: single sign-on for virtual desktop mode: Galya,
Should the following entries also be removed from @directory.xml@?... Eugenie Lyzenko
11:56 AM Feature #3931: single sign-on for virtual desktop mode: 3931a was merged to trunk as rev. 14783 and archived. Galya B
11:34 AM Feature #3931 (Test): single sign-on for virtual desktop mode: Galya B
01:10 PM Bug #7946 (WIP): Default selection and current browse row color differs for different customers a...: Created task branch 7946a from FWD trunk revision 14786. Stanislav Lomany
12:38 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: Very nice work in figuring this out! Greg Shah
12:38 PM Bug #7946: Default selection and current browse row color differs for different customers applica...: Stanislav Lomany wrote:
> Should we add @oldBrowseSelectionBar@ parameter to the directory? E.g. in @server/default/... Greg Shah
11:57 AM Feature #4129: map web client users to OS accounts: 3931a was merged to trunk as rev. 14783 and archived. Galya B
11:34 AM Feature #4129 (Test): map web client users to OS accounts: Galya B

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » User Interface

Activity

Activity

11/21/2023

11/18/2023

11/17/2023

11/15/2023

11/14/2023

11/09/2023

11/08/2023

11/07/2023

11/06/2023

11/03/2023

11/02/2023

11/01/2023

10/31/2023

10/30/2023

10/27/2023

10/26/2023

10/25/2023

10/24/2023

10/23/2023