A week has passed and it is time for me to look back.
This week was kind of a rabbit hole.
I am still trying to get trunk windows to compiling. And i started of
last week with a full update process, before realizing that this was
pulling in one change after another. I paused that effort for now, and
going to split it in smaller chunks.
I am not sure how to chunk down the DPI topic so thats deferred for now.
Basically what it seems like is that if we activate dpi aware handling
in the code, the old code starts to break through and we get a lot of
unharmonized objects.
Not to speak of that bitmaps are not scaled and then suddenly looking
off and deranged.
And if you look deeper, you start thinking in themeing fixing and
meshing up things substanitally.
The ui looks very bad if we just do chunks of the work. so I need to
think how we get this in a flow.
Long story short, this rabbit hole was not a good approach. so i decided
to do a minimal bumb. just get the sdk building the code. Worry about
all the other issues later.
That approach was narrower worked a bit better, except the 2019 SDK i
have installed, and i was to lazy to pick another one was only
supporting C++14 and up.
Thats not really a problem, but it got us into this discussion with the
declaration on exceptions. I have now removed all issues from what has
been discussed.
So the next thing did something break?
I tested my build (only X64 and x86), win10 i think does not yet
completly build. I picked for nice cross boundary uno checks, base as my
test object.
And i run into a crash. Which has been primarily caused by my incomplete
migration. But that again surfaced the issue we have as report bz-80429.
After some back and forth, and it took a while until i understood what
is going on, i produced a PR, which will help developers at debugging,
since AOO will popup an error message now instead of ignoring the issue.
Afterwards i migrated the wizards to bazel. I have cleaned up my local
repository too.
Now i will not have any conflicts once i rebase my work on
bazel-migration when i proceed to. The agent documents became more
structured by that and are now independant from claude, so i can try
other AI.
so next week i will continue with the win10 part, and i hope we can
build windows soon again on trunk (with anything up to sdk 2019)
We have a new PR by Jean-Michael coste. who picked up a patch from
bugzilla and pushed it to the PR. There are a lot more patches and we
should review them, over time if they are still valid and close what
they adress. I will look into this one after win10 and the review
Matthias has asked me to do for the calc Zoom slider. I would be
gratefull if someone else could take a look. But its okay if not. :)
On this weekend we had a presence at FOSDEM. Mechtilde and Michael were
nice to set this up. I visited only on Saturday, and the travel return
was horrible. But that is another story.
What I can say for my part it was nice visiting the community.I can look
back of interesting talks with various Volunteers from the open source
scene. My highlight was the discussion with Thorsten Behrens, from
Collabora. Providing some interesting views and Ideas. I am not agreeing
on all. But i enjoyed the exchange and i am very thankfull for that.
So thats all for this week. I hope you enjoyed this write up, and if you
have any comments you are welcome to drop them.
Next weeks target is to continue on win10 for trunk. Lets cross fingers,
i can finish on that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
