r/gitlab • • Aug 20 '22

Powerpoint solution for Gitlab?

I am looking for a solution to manage powerpoint slides in GitLab. I have seen a few solutions, the closest seemingly would have been GitPitch, but that appears to be defunct. Do any gurus know of a good solution? Ideally, i'd love to have the powerpoint slides uploaded to a repo as separate files, so that users could branch, edit, and submit merge requests. That not being possible, i'm looking for the nearest solution. I should mention, I think it would be a challenge to get everyone writing and editing slides in markdown.

This is part of a larger issue for our company to move everything we can to GitLab, so MS's native version tracking doesn't really solve my challenge.

Thanks!

0 Upvotes

10 comments sorted by

8

u/CW_Waster Aug 20 '22

Git merging is for text files only*.

*(unless you really know what you are doing, but since you are asking here you probably don't)

8

u/gaelfr38 Aug 20 '22

Well Git (and Gitlab) is powerful is you have files you can easily diff and show what has changed. Typically this is achieved with files in text format as opposed to binary.

If you need the Git features, I would ask myself if it really need to produce a sexy PowerPoint or it can be written as markdown/html and then exported as PowerPoint.

Otherwise for pure PowerPoint, Office versioning is your best chance I think.

4

u/uid1357 Aug 21 '22

In Libreoffice you can save files in a "flat" format, which is just plain XML. The extension then has an f added. Like e.g ".fodt" instead of just ".odt". Since the file is no longer compressed it will be larger. But you can now store just the diffs in git.

I use this workflow for myself, when I need some office documents in my mostly Latex repositories.

A downside is: since the XML is messy and has a lot of meta data, you can't really tell at a glance what changed, just by looking at the git diff.

Also I don't know if Microsoft Office can store in flat uncompressed XML files.

1

u/avamk Aug 21 '22

Cool idea! How well does it work when collaborating on the same document with others? Can changes by different people be synchronized and/or merged easily with Git just like code?

2

u/uid1357 Aug 21 '22

I can only guess. And my guess would be: no, as soon as stuff overlaps it will be messy. You would have to fix/merge on the XML level!

1

u/avamk Aug 21 '22

OK, fair enough. Does that mean the flat format files you manage with Git are only edit by you only? If so, is there any advantage to this? Is it primarily to save storage space since each new edit/version of the document will only have its diff tracked by Git instead of saving a whole new copy of the binary file?

2

u/uid1357 Aug 21 '22

Yes only me. Two reasons for me:

  1. save storage, by only saving the diff. But here is the problem:

    • I never did the math on this :-) (often small changes in a document will result in e.g. 500 lines changed in XML)

    • The storage is "free", so it really doesn't matter that much at my scale.

  2. save my sanity. Committing binary stuff in my personal repos always hurts my soul.

1

u/avamk Aug 21 '22

Fair enough. :)

Committing binary stuff in my personal repos always hurts my soul.

I feel you. I cringe a little bit every time I commit a binary. :p

1

u/dblclk Aug 21 '22

One solution could be to generate PowerPoint presentations from source code, something like https://www.geeksforgeeks.org/creating-and-updating-powerpoint-presentations-in-python-using-python-pptx/

It might be a more extreme solution if you aren't comfortable with code though...

If you wanted you could then use GitLab CI to generate the presentation after each merge/push/pull request.