Ugly Client
- Thread starter Hackuou
- Start date
Ram: yes (well it's electron which will may never change)I like teaclient, but my friend do not like it at all...
They say Tea*Speak client use less ram / cpu, so it is more gamer friendly..
Lets wait and see if it will be better
CPU: No, since the last version the server connection is native and don't affect the cpu at all. Ofc on servers with a lot of clients channels and specially activity the cpu usage might increase due to the UI updates
Well I may should consider to paint the channel tree as well the permission editor via WebGL.
This would be the much better, but it will reduce the possibilities to style that thing :/
This would be the much better, but it will reduce the possibilities to style that thing :/
Vafin
TeaFanatic
I think it's enough to revise CSS. WebGL is likely to consume more system resources.
Hmm? Well not that sure. Generally this improves a lot, depends on the implementation ofc.
I'll may give it a try
I'll may give it a try
Vafin
TeaFanatic
Okay, but first please fix the problem with SRV records, this is an important issue.Hmm? Well not that sure. Generally this improves a lot, depends on the implementation ofc.
I'll may give it a try
Locally fixed :/
Vafin
TeaFanatic
Have you tried developing a client on Qt Creator?
https://blog.qt.io/blog/2019/04/15/qt-creator-4-9-0-released/
Last edited:
Yes, but a native implementation needs a lot of maintenance as well it would be another new UI which differs from the already known web client once.
The goal in general is to sync the WebUI and the native client UI to improve the user experience
The goal in general is to sync the WebUI and the native client UI to improve the user experience
Vafin
TeaFanatic
In the latest client updates I noticed that you have started to apply Canvas technology. I was disappointed because it didn't work well enough, the small performance and the blurry font didn't give the desired result. In my opinion it is better to leave pure CSS.
Hey,
it gave exactly the effect which was wanted.
I know it might looks a bit odd, but it improved the performance a lot.
Because images: If I would not render the permission via a canvas each permission would have at least 4 DOM elements (It were about 6 in total due to design needs). We're having about 300 up to 350 permissions which mean 350 * 6 = 2100 DOM elements, which have to be updated each time you scroll, or click anywhere. This is an incredible performance bottleneck.
Vafin
TeaFanatic
Yes its because I forgot to add a resize listener, so I don't repaint it
Will be fixed soonly
Will be fixed soonly
Vafin
TeaFanatic
Okay, thanks. Please also make a horizontal scroll for the resolution editor or reduce the font size as everything does not fit into the width of the modal window.Yes its because I forgot to add a resize listener, so I don't repaint it
Will be fixed soonly
Take the example of YaTQa. It uses a smaller font and everything fits in a small window.
Last edited:
Yes I'll do that. Actually that the font is such bis is because the rows are so high (the font depends on the row hight).
And the "bit to big" size is because I'm using a 4k screen xD So sometimes I design stuff too large
And the "bit to big" size is because I'm using a 4k screen xD So sometimes I design stuff too large
Still would on 4K not fitYes I'll do that. Actually that the font is such bis is because the rows are so high (the font depends on the row hight).
And the "bit to big" size is because I'm using a 4k screen xD So sometimes I design stuff too large
It does believe in me xD