console (not only)

[chdelfosse]

congratulations and thank you for this project

I wondered if an access to the user console would be possible,
as the only debug tool I see at present is to fire an alert()

also : disable-element() blocks silently when [erroneously] called on a div, could possibly be a no-op or yield a warning

[epeios-q37]

Thanks! Glad you enjoy my toolkit.

I wondered if an access to the user console would be possible

I suppose you would be interested by the equivalent of the console.log(…) of JavaScript. Wouldn't it be better to use Python to write debugging messages in the console from which the application is launched?

disable-element() blocks silently when [erroneously] called on a div

I was not able to reproduce this issue. Here is the code used for testing: https://replit.com/@AtlasTK/DIVDisablingBlocks. Can you please provide an example, possibly by forking and modifying this Replit-hosted code accordingly?

[chdelfosse]

I tried "print ()" AFTER the problem arose, and it did not work, hence my request In a clean state, "print()" works and is certainly the better solution As to "disable-element()", I did not check-point the wrong version, but I will restore it from memory (for the sake of the project) and send it to you thanks again, regards ch

…

On Sun, 17 Oct 2021 at 11:04, Claude SIMON ***@***.***> wrote: Thanks! Glad you enjoy my toolkit. I wondered if an access to the user console would be possible I suppose you would be interested by the equivalent of the console.log(…) of *JavaScript*. Wouldn't it be better to use *Python* to write debugging messages in the console from which the application is launched? disable-element() blocks silently when [erroneously] called on a div I was not able to reproduce this issue. Here is the code used for testing: ***@***.***/DIVDisablingBlocks. Can you please provide an example, possibly by forking and modifying this *Replit*-hosted code accordingly? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ2KAUOJE6UQT3DASLFH23UHKGS3ANCNFSM5F7YN3FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[chdelfosse]

wrong clue, I confirm that disabling a div is not blocking the process, but that means that I must have corrected two mistakes at the same time, and I can't remember the other one, sorry about that regards ch

…

On Sun, 17 Oct 2021 at 11:04, Claude SIMON ***@***.***> wrote: Thanks! Glad you enjoy my toolkit. I wondered if an access to the user console would be possible I suppose you would be interested by the equivalent of the console.log(…) of *JavaScript*. Wouldn't it be better to use *Python* to write debugging messages in the console from which the application is launched? disable-element() blocks silently when [erroneously] called on a div I was not able to reproduce this issue. Here is the code used for testing: ***@***.***/DIVDisablingBlocks. Can you please provide an example, possibly by forking and modifying this *Replit*-hosted code accordingly? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ2KAUOJE6UQT3DASLFH23UHKGS3ANCNFSM5F7YN3FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[epeios-q37]

Glad to see that everything is working properly.

Concerning the printing on the JS console, it's not a big deal, so I will implement a dom.log() function in the next version of the Atlas toolkit.

Regards,

Claude.

[chdelfosse]

this will make using Google's [for example] Inspector easier when handling more complex html structures by having a single debug tool (because your toolkit already makes extensive use of that very console) thanks again ch

…

On Tue, 19 Oct 2021 at 17:34, Claude SIMON ***@***.***> wrote: Glad to see that everything is working properly. Concerning the printing on the JS console, it's not a big deal, so I will implement a dom.log() function in the next version of the *Atlas* toolkit. Regards, Claude. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ2KATALJB3Q6MWM6YDRS3UHWFZLANCNFSM5F7YN3FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[epeios-q37]

A new version of the Atlas toolkit is available, which provides a log function. Simply call dom.log("message") from a callback, and message will be displayed in the web console.

Regards.

Claude.

[chdelfosse]

splendid, thank you, I will get it when my main occupation gives me some time to spare thanks again ch

…

On Tue, 9 Nov 2021 at 16:54, Claude SIMON ***@***.***> wrote: A new version of the *Atlas* toolkit is available, which provides a log function <https://atlastk.org/api/en#log>. Simply call dom.log("message") from a callback, and message will be displayed in the web console. Regards. Claude. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ2KAU7UEKJ2SV3PC7TPYDULE72HANCNFSM5F7YN3FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[chdelfosse]

thank you again, most helpul when you use Google's inspector console ch

…

On Tue, 9 Nov 2021 at 16:54, Claude SIMON ***@***.***> wrote: A new version of the *Atlas* toolkit is available, which provides a log function <https://atlastk.org/api/en#log>. Simply call dom.log("message") from a callback, and message will be displayed in the web console. Regards. Claude. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ2KAU7UEKJ2SV3PC7TPYDULE72HANCNFSM5F7YN3FA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[epeios-q37]

Pleased that it meets your expectations.
To make these messages easier to spot, the debugging messages from the toolkit itself have also been removed. So now only the messages from the browser itself remain.