by tperry2x » Sat Aug 31, 2024 10:50 am
mwieder wrote: ↑Fri Aug 30, 2024 10:43 pm
Not to distract you from benchmarks, Tom, but here's an easy one for you.
Don't worry, I think I'm almost done with that. (edit: I am done with it now)
mwieder wrote: ↑Fri Aug 30, 2024 10:43 pm
This fixes linux printing (bugzilla #21131).
LC is trying to shell out to lp to do the printing, and that requires elevated privileges.
This patch uses the cups library instead.
Thanks Mark. This is very very much appreciated. Great work, and I hope it can be rolled into the source for the engine.
Actually, that's a good point. This isn't meant as a 'snarky' remark (or anything like that), it's a genuine question:
Is the engine of LCC the one we are using from
here,
here, or
here currently? - is it possible to pull all these together (for want of a better phrase?)
Either way, I've also added it to my
list of possible C++ engine fixes, just in case anyone asks me ever.
I don't think it's going to be easy for me to implement any C++ changes to the engine any time soon, and I think I'd rather wait to see a
release of the engine from a github repo - that way I know I'm getting any cumulative fixes.
But once again, genuinely, a massive thank you for working on this. All updates to the engine are very welcome, and are very much needed. (don't solely take my word on that, but the voting poll at the top of this topic would suggest people feel the same).
I'm probably going to take a back seat from OXT Lite development for a while, due to other circumstances, so someone else can pick up the lead from here.
[quote=mwieder post_id=10734 time=1725057808 user_id=1734]
Not to distract you from benchmarks, Tom, but here's an easy one for you.
[/quote]
Don't worry, I think I'm almost done with that. (edit: I am done with it now)
[quote=mwieder post_id=10734 time=1725057808 user_id=1734]
This fixes linux printing (bugzilla #21131).
LC is trying to shell out to lp to do the printing, and that requires elevated privileges.
This patch uses the cups library instead.
[/quote]
Thanks Mark. This is very very much appreciated. Great work, and I hope it can be rolled into the source for the engine.
Actually, that's a good point. This isn't meant as a 'snarky' remark (or anything like that), it's a genuine question:
Is the engine of LCC the one we are using from [url="https://github.com/OpenXTalk-org/OpenXTalk-Community-DPE"]here[/url], [url="https://github.com/mwieder/OpenXTalkEngine"]here[/url], or [url="https://github.com/openxtalk/openxtalk"]here[/url] currently? - is it possible to pull all these together (for want of a better phrase?)
Either way, I've also added it to my [url="https://mega.nz/folder/kK0D1Y6I#yEMBwjxzvg_23zGybbUZyA"]list of possible C++ engine fixes[/url], just in case anyone asks me ever.
I don't think it's going to be easy for me to implement any C++ changes to the engine any time soon, and I think I'd rather wait to see a [url="https://github.com/mwieder/OpenXTalkEngine/releases"]release of the engine[/url] from a github repo - that way I know I'm getting any cumulative fixes.
But once again, genuinely, a massive thank you for working on this. All updates to the engine are very welcome, and are very much needed. (don't solely take my word on that, but the voting poll at the top of this topic would suggest people feel the same).
I'm probably going to take a back seat from OXT Lite development for a while, due to other circumstances, so someone else can pick up the lead from here.