Well, the answer to that is going to be "it depends" :).
Spinning up the HTMLRenderer probably costs about 10,000 times more than producing a chart in JavaScript, so I wouldn't spin a new one up each time, if performance was critical.
Search found 460 matches
- Sat Oct 05, 2024 5:29 pm
- Forum: Language
- Topic: HTMLRenderer on the Server
- Replies: 3
- Views: 3534
- Sat Oct 05, 2024 7:17 am
- Forum: Language
- Topic: HTMLRenderer on the Server
- Replies: 3
- Views: 3534
Re: HTMLRenderer on the Server
Hi Paul! I can't think of a reason why it would be a quote bad idea unquote to create an HTMLRenderer with ('Visible' 0) to run JavaScript. In fact, I have been experimenting with doing exactly this in our experimental "EWC" tool ( http://github.com/dyalog/ewc ), to have the ApexCharts library ...
- Sun May 05, 2024 2:26 pm
- Forum: Language
- Topic: Bug? Timers fire even after being erased
- Replies: 5
- Views: 18064
Re: Bug? Timers fire even after being erased
Thanks! As far as I can see, the system is behaving "as designed".
- Sun May 05, 2024 11:44 am
- Forum: Language
- Topic: Bug? Timers fire even after being erased
- Replies: 5
- Views: 18064
Re: Bug? Timers fire even after being erased
Hi Rav, sorry about my fading eyesight :) I'm afraid I must disagree with you when you say it acts as if it has been erased. On the contrary, the timer is very much acting as if it exists, by continuing to fire events. Note that any namespace can have multiple references to it. For example, you ...
- Sun May 05, 2024 7:31 am
- Forum: Language
- Topic: Bug? Timers fire even after being erased
- Replies: 5
- Views: 18064
Re: Bug? Timers fire even after being erased
Hi Ray! I think the problem may be caused by changing space into the timer namespace. As long as you have code which is running "in" that namespace, the expunge will only remove the reference from to the space from the global name #.timer, but it cannot actually erase the timer namespace. If I ...
- Sat Apr 27, 2024 7:07 am
- Forum: Language
- Topic: Thoughts on Threads
- Replies: 2
- Views: 12336
Re: Thoughts on Threads
Hi Paul, thanks for the question, as they say. I'm surprised, do you have some benchmark code that you could share with us?
P.S. Could you run the code that listens on the websocket in a thread other than 0? That's what I'm doing in my latest project.
P.S. Could you run the code that listens on the websocket in a thread other than 0? That's what I'm doing in my latest project.
- Tue Apr 23, 2024 7:29 am
- Forum: Object Oriented Programming
- Topic: Modified assignment with objects: should it work?
- Replies: 5
- Views: 18972
Re: Modified assignment with objects: should it work?
Hi Peter! Yes, it should work, with caveats like there being no guarantees on how many times the get and set functions will be called. However, I see that it does NOT work properly, in the simple example that I constructed, only the first index was updated. I will log an issue and we'll get back to ...
- Thu Apr 04, 2024 4:08 pm
- Forum: APL Chat
- Topic: Wish List: Support for Double Quotes
- Replies: 6
- Views: 39163
Re: Wish List: Support for Double Quotes
Do you know of APLs beside Dyalog that do not support them? IBM/LOGON APL2 does not, and although GNU APL and a couple of experimental APLs support double quotes, they do not define them the same way as APL+Win: A double-quoted string is aways a vector, and can contain "escaped" characters. If we ...
- Thu Apr 04, 2024 3:49 pm
- Forum: APL Chat
- Topic: Wish List: Support for Double Quotes
- Replies: 6
- Views: 39163
Re: Wish List: Support for Double Quotes
I'm not sure the "most other APL's" statement is entirely accurate. APL+Win supports this but the implementors did not (as far as I know) consult other vendors when doing it. APLX, which was very much a clone of APL+Win at the language level, followed suit, but I am not aware of other APL systems ...
- Sun Mar 03, 2024 3:33 pm
- Forum: APL Chat
- Topic: Optional output for debugging
- Replies: 6
- Views: 22138
Re: Optional output for debugging
The branch to zero is an old habit, an :If statement would be nicer...