User:Kim/Prototyping 2nd year/GitPub - Revision history

Kim: /* changes made: */

2026-05-09T07:56:15Z

changes made:

2026-05-09T07:55:43Z

changes made:

@@ Line 246: / Line 246: @@
 # toc is rendered in python (beatifulsoup), currently has 1 level (thesis version has 2)
 # cleaned up file structure:
 === pending / further: ===

2026-05-09T07:53:27Z

v 0.6

← Older revision		Revision as of 09:53, 9 May 2026
Line 245:		Line 245:
	## citation has validation for .bib file		## citation has validation for .bib file
	# toc is rendered in python (beatifulsoup), currently has 1 level (thesis version has 2)		# toc is rendered in python (beatifulsoup), currently has 1 level (thesis version has 2)
			# cleaned up file structure:

	=== pending / further: ===		=== pending / further: ===

2026-05-09T07:47:23Z

v 0.5 iso

← Older revision		Revision as of 09:47, 9 May 2026
Line 232:		Line 232:

	the script repository does not have to be a git, but can be any directory containing the specified files and installations.		the script repository does not have to be a git, but can be any directory containing the specified files and installations.

			== v 0.6 ==

			=== changes made: ===

			# added paged js (for browser preview and pdf conversion)
			## added parallel flow plugin to paged js to format metadata output
			# using python yaml to ensure correctly formatted commit messages
			# final html document uses jinja template
			## allowed to restructure html for parallel-flow plugin to work
			# adjusted user input options: (file types, cover, css and citation)
			## citation has validation for .bib file
			# toc is rendered in python (beatifulsoup), currently has 1 level (thesis version has 2)

			=== pending / further: ===

			# make different templates for jinja html output (currently, its optimized for paged js output but could also be web...)
			# remaining: file sorting

	== outlook ==		== outlook ==

2026-03-03T11:57:41Z

repository connection

← Older revision		Revision as of 13:57, 3 March 2026
Line 259:		Line 259:

	see: [[User:Kim/Prototyping 2nd year/GitPub#v 0.5 iso\|Gitpub]]		see: [[User:Kim/Prototyping 2nd year/GitPub#v 0.5 iso\|Gitpub]]

			=== git blame ===
			use git blame instead of git log to let the text unfold through its metadata (commits)

2026-03-03T11:55:16Z

repository connection

← Older revision		Revision as of 13:55, 3 March 2026
Line 258:		Line 258:
	keep the scripts in a separate (from your project) repository that you also dump the metadata output files in. This way the working repository stays 'clean' and you can apply gitpub to diverse projects.		keep the scripts in a separate (from your project) repository that you also dump the metadata output files in. This way the working repository stays 'clean' and you can apply gitpub to diverse projects.

	* which repository do i execute the script from? (script repository)		see: [[User:Kim/Prototyping 2nd year/GitPub#v 0.5 iso\|Gitpub]]

2026-02-12T09:29:55Z

v 0.5 iso

← Older revision		Revision as of 11:29, 12 February 2026
Line 222:		Line 222:

	== v 0.5 iso ==		== v 0.5 iso ==
	''separating the script (and rendering files) from the repository it is applied to. (Although not the main goal) this step makes it easier for the gitpub to be applied to and tested on existing repositories.''		''separating the script (and rendering files) from the repository it is applied to. (Although not the main goal) this step makes it easier for the gitpub to be applied to and tested on existing repositories.''<gallery>
			File:Gitpub-iso.pdf
			</gallery>
	# the gitpub-iso script can be run from an external git repository (''script repo'').		# the gitpub-iso script can be run from an external git repository (''script repo'').
	# the script asks for a local, absolute file path to the repository it should applied to (''project repo'').		# the script asks for a local, absolute file path to the repository it should applied to (''project repo'').

2026-02-12T07:17:25Z

← Older revision		Revision as of 09:17, 12 February 2026
Line 3:		Line 3:
	\|+log		\|+log
	\|prototype status		\|prototype status
	\|~~v2 basic~~ .~~py script running~~		\|v 0.5 (iso)
	\|-		\|-
	\|~~next steps~~		\|remote
	\|~~sort files + add print output to~~ .~~py script~~		\|https://gitlab.com/km_kt/gitpub-scripts
	\|-		\|-
	\|pmomm		\|initial pmomm
	\|[[User:Kim/Projects That May or May Not Be Made/2nd year pmomms#1._gitpub \| #1. gitpub]]		\|[[User:Kim/Projects That May or May Not Be Made/2nd year pmomms#1._gitpub \| #1. gitpub]]
	\|}		\|}

2026-02-12T07:15:28Z

v 0.5

@@ Line 220: / Line 220: @@
 ## reference file always rendered / appended last
 ## currently all sources from .bib are rendered (possible to only include those in use?) otherwise rm manually
 == outlook ==

2026-02-06T14:59:09Z

outlook

← Older revision		Revision as of 16:59, 6 February 2026
Line 242:		Line 242:
	* flask to render to html (or pdf) more continuously		* flask to render to html (or pdf) more continuously
	* share html on localhost (enter same localhost with same ip address, bc we dont have a server) (maybe needs (web) [https://hybridpc.co.uk/how-to-access-localhost-from-another-computer-on-the-same-network/ server configuration], apache / nginx)		* share html on localhost (enter same localhost with same ip address, bc we dont have a server) (maybe needs (web) [https://hybridpc.co.uk/how-to-access-localhost-from-another-computer-on-the-same-network/ server configuration], apache / nginx)

			=== repository connection ===
			keep the scripts in a separate (from your project) repository that you also dump the metadata output files in. This way the working repository stays 'clean' and you can apply gitpub to diverse projects.

			* which repository do i execute the script from? (script repository)