core.git: sw/source
sw/source/core/inc/UndoTable.hxx|5 + sw/source/core/inc/unoevent.hxx |6 ++ sw/source/core/inc/unofield.hxx |5 + sw/source/core/inc/unoflatpara.hxx |5 + sw/source/core/inc/unofldmid.h |6 ++ sw/source/core/inc/unofootnote.hxx |5 + sw/source/core/inc/unoidx.hxx |6 ++ sw/source/core/inc/unolinebreak.hxx |5 + sw/source/core/inc/unometa.hxx |5 + sw/source/core/inc/unoparaframeenum.hxx |5 + sw/source/core/inc/unoport.hxx |6 ++ sw/source/core/inc/unorefmark.hxx |5 + sw/source/core/inc/unosection.hxx |5 + sw/source/core/inc/unotextmarkup.hxx|5 + sw/source/core/inc/viewimp.hxx |5 ++--- sw/source/core/inc/visiturl.hxx |5 + sw/source/core/inc/wrong.hxx|5 + 17 files changed, 22 insertions(+), 67 deletions(-) New commits: commit b117f7d42c7c8bce12d61c01b92b8af4e9aa70b1 Author: Jonah Janzen AuthorDate: Wed Mar 6 19:40:14 2024 -0700 Commit: Ilmari Lauhakangas CommitDate: Thu Mar 7 19:13:48 2024 +0100 tdf#143148 Use #pragma once instead of include guards Uses #pragma once in several files under sw/source/core/inc. Change-Id: I3052462232665a4efa301afd51e9f64fa3567c44 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/164517 Tested-by: Jenkins Tested-by: Ilmari Lauhakangas Reviewed-by: Ilmari Lauhakangas diff --git a/sw/source/core/inc/UndoTable.hxx b/sw/source/core/inc/UndoTable.hxx index 29850d2f07e2..40d4d0547b6a 100644 --- a/sw/source/core/inc/UndoTable.hxx +++ b/sw/source/core/inc/UndoTable.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNDOTABLE_HXX -#define INCLUDED_SW_SOURCE_CORE_INC_UNDOTABLE_HXX +#pragma once #include #include @@ -424,6 +423,4 @@ public: virtual SwRewriter GetRewriter() const override; }; -#endif // INCLUDED_SW_SOURCE_CORE_INC_UNDOTABLE_HXX - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sw/source/core/inc/unoevent.hxx b/sw/source/core/inc/unoevent.hxx index 4906f447f685..ddf7b0713770 100644 --- a/sw/source/core/inc/unoevent.hxx +++ b/sw/source/core/inc/unoevent.hxx @@ -16,8 +16,8 @@ * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNOEVENT_HXX -#define INCLUDED_SW_SOURCE_CORE_INC_UNOEVENT_HXX + +#pragma once #include @@ -90,6 +90,4 @@ private: virtual sal_uInt16 getMacroItemWhich() const override; }; -#endif - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sw/source/core/inc/unofield.hxx b/sw/source/core/inc/unofield.hxx index 313185a0001b..3224db126fca 100644 --- a/sw/source/core/inc/unofield.hxx +++ b/sw/source/core/inc/unofield.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNOFIELD_HXX -#define INCLUDED_SW_SOURCE_CORE_INC_UNOFIELD_HXX +#pragma once #include #include @@ -224,6 +223,4 @@ public: }; -#endif - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sw/source/core/inc/unoflatpara.hxx b/sw/source/core/inc/unoflatpara.hxx index 9fd768d277a9..30631fabae6a 100644 --- a/sw/source/core/inc/unoflatpara.hxx +++ b/sw/source/core/inc/unoflatpara.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNOFLATPARA_HXX -#define INCLUDED_SW_SOURCE_CORE_INC_UNOFLATPARA_HXX +#pragma once #include @@ -133,6 +132,4 @@ private: SwNodeOffset mnEndNode;// used for non-automatic mode }; -#endif - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sw/source/core/inc/unofldmid.h b/sw/source/core/inc/unofldmid.h index 8c1838f45636..b0ae0cea1644 100644 --- a/sw/source/core/inc/unofldmid.h +++ b/sw/source/core/inc/unofldmid.h @@ -16,8 +16,8 @@ * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNOFLDMID_H -#define INCLUDED_SW_SOURCE_CORE_INC_UNOFLDMID_H + +#pragma once // mapping of the properties on the descriptor #define FIELD_PROP_PAR1 10 @@ -53,6 +53,4 @@ #define FIELD_PROP_USHORT3 38 -#endif - /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/sw/source/core/inc/unofootnote.hxx b/sw/source/core/inc/unofootnote.hxx index 23f22bee2cd3..a7498a730749 100644 --- a/sw/source/core/inc/unofootnote.hxx +++ b/sw/source/core/inc/unofootnote.hxx @@ -17,8 +17,7 @@ * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ -#ifndef INCLUDED_SW_SOURCE_CORE_INC_UNOFOOTNOTE_HXX -#define
Jonah Janzen License Statement
All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license.
Hoping to be part of GSoC 2024
Hi there! My name is Jonah, and I'm a Canadian engineering student. I recently found out about Google Summer of Code, and after doing some more reading about it, it seems like a wonderful opportunity that I would love to be a part of. As a longtime user of LibreOffice, it's high on my list of organizations I want to give back to, and hence I'm reaching out to you today to start a conversation about doing so. I've been programming since I was 8 doing everything from amateur gamedev to competitive programming. This past year, I worked as a web developer building a full-stack application with C#/Blazor, and I've also made occasional contributions to FOSS like Godot and LMMS. There are a couple of ideas that I would be most interested in working on, which I'll list below: *UNO Rust Bindings* I have vague familiarity with the Rust language and the ideas behind it, but I have little hands-on experience with it. My initial thoughts about this idea are that it would almost certainly involve the use of the CXX.RS utility, and that I would hope to be able to auto-generate as much of the code as possible, by using the public API specification. I have a strong desire to get more familiar with Rust, and I love working on low-level backend stuff so this would probably be my top choice. *Forgejo Migration (my own idea)* >From the perspective of a newcomer to the project, between Gitiles, Gerrit, Bugzilla, Jenkins, etc., the different parts of LibreOffice development feel disjointed and initially challenging to grasp. I sincerely don't mean to cause offense, and I don't come across as abrasive rather than reflective. What I would propose is to move the LibreOffice repository, issue tracker, code review process, and CI all onto the Forgejo platform. This would offer a more centralized experience for all aspects of project management that I think would make core developers' lives much easier, and provide another, more superficial benefit: young (and occasionally foolish) individuals like myself are used to the GitHub style of Git server, and things like Gitiles tend to feel outdated and unapproachable. Forgejo would provide a more familiar UX that would ease the process of onboarding new contributors. Gitea is another possibility, because it seems to be more active and it's used by high-profile projects like Blender, although it's owned by a for-profit now. I've also heard about OneDev, but don't know as much about it. Since this is my own idea, there are a couple potential challenges I'm not sure about that I'd appreciate input on: - This would require transferring account data, and I understand that you might not be willing to entrust me with the power to access that. - I would like for my GSoC project to be 350 hours, and I don't have an estimate for how long this would take. I guess we could tack on other stuff under the migration umbrella as well, like a shift from IRC to Matrix, for example. *LibreOffice Theme* Although I'm personally not as interested in this idea, it seems like it would offer a significant leap forward in LibreOffice's UI capabilities, and might make the software more appealing to a lot of people. If you think this would do the most good for the project overall, then I'd be glad to take it on for that reason. I would want to consider what the best way to store custom styles is (CSS? XML? and so on), and how this can be integrated as tightly as possible with the way Mozilla themes are used, so that the new setup can do all the same things. - I would really appreciate feedback on what you think the best of those ideas (or any others) might be for me to work on. I would also be curious to know how much interest from other GSoC applicants you have had thus far, and whether I would have a significant chance of being accepted if I actually were to work on a proposal. If the answer to that is yes, then I will start working on an easy hack as soon as possible, and collaborating with potential mentors to shape my proposal. Thank you so much, and I hope to work with you soon! Jonah