Hi all,
New weekend, new summary of my progress.
1) Bazel experiment.
Well it is hard work to figure out what goes wrong. And it is really
annoying work. I would like to show off what we can do with Bazel, but i
am stuck with debugging and i find a lot of side issues, catching my focus.
so I am slower. Because i analyses these issues to a point where i think
i can pick it up later and fix them. I fear i will do more annoying not
plan able stuff. 🙈 i will however go by the roadmap i have described
earlier this year.
currently i still look for a modern way to get translation into a build.
The Bazel experiment should have cleanup and enabled me, but instead i
have more topics. lets see.
Building AOO with Bazel in a normal setup takes currently 2h on my
machine. If i try to build debug build with more checks, and stricter
error search, i end up that i have to build with only one job. That
delays the build into really long, wait times if you rebuild from
scratch. A day or so. I need to look at that and fix it. But have no
idea how at the moment. (it is not a pressing matter so i push this to
the back)
Bazel builds every module on its own and ensures repeatability. (At
least as long as we do not tell a different build tool what to do) This
means once we build the source code we need to package the result.
Currently i dont package to get a installer file but stage the result in
a staging folder. that means i have a staging directory in my build area
that contains the result. However we seem to define things during
install. Like build Version and Product name. So i have these small
fragment that window names are not correct.
During install in the wizard some labels are missing, which means a
resource file is missing.
The last issue i am currently aware of, and it drives me crazy, is the
free after use error i run into.
So what the issue is, that during the load / initialization of a new
document, the process is unexpectedly done and closes AOO again. Now
this cascades into that the main window is killed, but all the child
objects of the window are nod deleted. Which results in the wired
situation that AOO closes partially and other parts stay undead. I have
to hard kill them. Now i am still looking for the missing part. It is
nothing like an obvious missing dll or resource file. That looks great
compared to my installed instance.
So some detail is probably missing. so i continue with my debug work. I
could use help for ideas how to get this. If someone wants to help
please reach out.
how ever this issue showed me that the way AOOs GUI works is incredible
fragile. The Gui works in a pretty anarchic way. Each Gui Object seems
to be hierarchic independent, the hierarchy is then build by a "pointer
reference house". We introduced an point counter (called weak reference)
already, but that is not introduced everywhere. This weak pointer
mitigate the issue. LO seems to went down the same route, and completely
fixed it. However i don't like it.
2 VCL
I started with low time invest to create concepts how a solution can
look like. I wrote a mail to start a discussion, but that seemed to
failed to connect. I am working on a plan how to build a clear ownership
model and use more reference architecture to obtain a modern safe to use
UI framework, even if we then link old GUIs into them. In my mail i
looked into other frameworks that sounded awesome to me. (enlightenment
or inclusion of rust, or AOO as a tomcat servlet.) I will continue the
architecture and design work in the background and write from time to
time about it. i hope i don't bore anyone with that.
3) Extension website
no progress sorry.
4) pootle -> weblate
i have installed weblate locally and wow was that easy.
I could even integrate our translation git repository quiet well. It
seemed off at some points, i have to take another look, but it seems i
can very easily produce a test environment. I have passed the
requirements to infra. Now it is my turn to deploy a first test version.
In my opinion this looks really great to get this maybe up quickly. What
i did not manage was to manipulate the appearance.
so next step is. i need to figure out how to limit registration. Then i
would deploy this to the server.
Next step would be to integrate translation, but i think i branch off a
weblate-test branch in order to check if a folder rearrangement would
help fixing missing languages.
i will ask for support soon.
5) FroSCon
I have applied for a talk on FroSCon, to talk about the Bazel migration.
However it got rejected. So no AOO talk on FroSCon sadly.
Maybe on a later stage i could have a talk on our own YouTube channel.
The charm would be that i could do it to my own speed. Or i try to do a
talk on a different Open Source Event.
I thought about Europe Apache event, but i will not manage it there
(time and Money), but in future i would like to try to bring my talks
more into public rooms.
All the best
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
