Documentation:Rules and recommendations - Revision history

Karen at 08:27, 8 March 2022

2022-03-08T08:27:19Z

← Older revision		Revision as of 08:27, 8 March 2022
Line 1:		Line 1:
	Please, read this article before you contribute to the [https://~~historytimeline~~.~~app~~ Timeline].		Please, read this article before you contribute to the [https://timeline.oldera.org/timeline Timeline].

	==Notability==		==Notability==

Karen: 9 revisions imported

2022-03-08T08:25:46Z

9 revisions imported

← Older revision	Revision as of 08:25, 8 March 2022
(No difference)

Karen: /* How data is organised in the Library (categorisation) */

2021-07-02T13:20:54Z

How data is organised in the Library (categorisation)

← Older revision		Revision as of 13:20, 2 July 2021
Line 8:		Line 8:

	==How data is organised in the Library (categorisation)==		==How data is organised in the Library (categorisation)==
	Regular users can’t place layers anywhere other than the special folder already mentioned above. If you have a suggestion on where to put your layer, or maybe you have some general thoughts on how to organise data in the Library you can message me on [~~https~~:~~//twitter.com/HTimelineApp Twitter~~] ~~or [https://www.reddit.com/user/kgcoder Reddit~~]~~. Also, we will probably have a community on Reddit and/or there will be discussion pages on the this website~~.		Regular users can’t place layers anywhere other than the special folder already mentioned above. If you have a suggestion on where to put your layer, or maybe you have some general thoughts on how to organise data in the Library you can message me on my [[User_talk:Karen\|talk page]].

	Basically, how to organise data in the Library is an open question. I’m not a historian, and even if I was, I wouldn’t want to impose my views on everybody. So there must be a way for everybody to have a say in this matter.		Basically, how to organise data in the Library is an open question. I’m not a historian, and even if I was, I wouldn’t want to impose my views on everybody. So there must be a way for everybody to have a say in this matter.

Karen: Protected "Documentation:Rules and recommendations" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2021-06-18T13:47:40Z

Protected "Documentation:Rules and recommendations" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 13:47, 18 June 2021
(No difference)

Karen: /* Conflicting sources */

2021-06-17T14:14:49Z

Conflicting sources

← Older revision		Revision as of 14:14, 17 June 2021
Line 82:		Line 82:
	[[File:QuintillusConflict.png]]		[[File:QuintillusConflict.png]]

	One layer says that Quintillus began his reign in April 270, while ~~the other~~ layer says he died in April 270. If one of the sources has an error in it, then such error should be fixed. You can always fix errors on Wikipedia. However, if we genuinely don’t know when Quintillus died and the sources simply cite two different versions which come from two different books, and one version is not better then the other, then it’s OK to just show the conflicting versions of history on the Timeline.		One layer says that Quintillus began his reign in April 270, while another layer says he died in April 270. If one of the sources has an error in it, then such error should be fixed. You can always fix errors on Wikipedia. However, if we genuinely don’t know when Quintillus died and the sources simply cite two different versions which come from two different books, and one version is not better then the other, then it’s OK to just show the conflicting versions of history on the Timeline.

	The fact that we can visualise the conflict of versions of history on the Timeline is actually a good thing.		The fact that we can visualise the conflict of versions of history on the Timeline is actually a good thing.

Karen: /* How data is organised in the Library (categorisation) */

2021-06-17T14:12:39Z

How data is organised in the Library (categorisation)

← Older revision		Revision as of 14:12, 17 June 2021
Line 8:		Line 8:

	==How data is organised in the Library (categorisation)==		==How data is organised in the Library (categorisation)==
	Regular users can’t place layers anywhere other than the special folder already mentioned above. If you have a suggestion on where to put your layer, or maybe you have some general thoughts on how to organise data in the Library you can message me on Twitter or Reddit. Also, we will probably have a community on Reddit and/or there will be discussion pages on the ~~Timeline~~ website.		Regular users can’t place layers anywhere other than the special folder already mentioned above. If you have a suggestion on where to put your layer, or maybe you have some general thoughts on how to organise data in the Library you can message me on [https://twitter.com/HTimelineApp Twitter] or [https://www.reddit.com/user/kgcoder Reddit]. Also, we will probably have a community on Reddit and/or there will be discussion pages on the this website.

	Basically, how to organise data in the Library is an open question. I’m not a historian, and even if I was, I wouldn’t want to impose my views on everybody. So there must be a way for everybody to have a say in this matter.		Basically, how to organise data in the Library is an open question. I’m not a historian, and even if I was, I wouldn’t want to impose my views on everybody. So there must be a way for everybody to have a say in this matter.

Karen: /* Time intervals */

2021-06-17T14:07:15Z

Time intervals

← Older revision		Revision as of 14:07, 17 June 2021
Line 45:		Line 45:
	When the program reads the instructions, it places time intervals on the Timeline one by one, in order of their appearance in the list of instructions. It happens very quickly so it seems as though all the time intervals appear on the Timeline at the same moment. But in reality there is a process that looks like upside down Tetris, where each time interval tries to end up as high as possible.		When the program reads the instructions, it places time intervals on the Timeline one by one, in order of their appearance in the list of instructions. It happens very quickly so it seems as though all the time intervals appear on the Timeline at the same moment. But in reality there is a process that looks like upside down Tetris, where each time interval tries to end up as high as possible.

	So what happened in our example, is that ''Time interval 1'' was placed first as high as possible. Then ''Time interval 2'' was placed as high as possible. Then when it was time to place ''Time interval 3'' on the timeline, the ~~place~~ in the highest level was occupied by ''Time interval 2'', so the third interval had to go lower.		So what happened in our example, is that ''Time interval 1'' was placed first as high as possible. Then ''Time interval 2'' was placed as high as possible. Then when it was time to place ''Time interval 3'' on the timeline, the space in the highest level was already occupied by ''Time interval 2'', so the third interval had to go lower.

	To fix it, you simply change the order of time intervals in the instructions, placing ''Time interval 3'' before ''Time interval 2''.		To fix it, you simply change the order of time intervals in the instructions, placing ''Time interval 3'' before ''Time interval 2''.

Karen: /* Time intervals */

2021-06-17T14:05:46Z

Time intervals

← Older revision		Revision as of 14:05, 17 June 2021
Line 45:		Line 45:
	When the program reads the instructions, it places time intervals on the Timeline one by one, in order of their appearance in the list of instructions. It happens very quickly so it seems as though all the time intervals appear on the Timeline at the same moment. But in reality there is a process that looks like upside down Tetris, where each time interval tries to end up as high as possible.		When the program reads the instructions, it places time intervals on the Timeline one by one, in order of their appearance in the list of instructions. It happens very quickly so it seems as though all the time intervals appear on the Timeline at the same moment. But in reality there is a process that looks like upside down Tetris, where each time interval tries to end up as high as possible.

	So what happened in our example, is that Time interval 1 was placed first as high as possible. Then Time interval 2 was placed as high as possible. Then when it was time to place Time interval 3 on the timeline, the place in the highest level was occupied by ~~time~~ interval 2, so the third interval had to go lower.		So what happened in our example, is that ''Time interval 1'' was placed first as high as possible. Then ''Time interval 2'' was placed as high as possible. Then when it was time to place ''Time interval 3'' on the timeline, the place in the highest level was occupied by ''Time interval 2'', so the third interval had to go lower.

	To fix it, you simply change the order of time intervals in the instructions, placing Time interval 3 before Time interval 2.		To fix it, you simply change the order of time intervals in the instructions, placing ''Time interval 3'' before ''Time interval 2''.

	<blockquote><poem>		<blockquote><poem>
Line 61:		Line 61:

	Looks much better.		Looks much better.


	==Sources==		==Sources==

Karen: /* Where to save your layers in the Library */

2021-06-17T14:04:50Z

Where to save your layers in the Library

← Older revision		Revision as of 14:04, 17 June 2021
Line 5:		Line 5:

	==Where to save your layers in the Library==		==Where to save your layers in the Library==
	Use the folder ''Sandbox/Add'' your layers here		Use the folder ''Sandbox/Add your layers here''. The rest of the folders in the Library are protected from editing. The reason is that if someone messes up the Library structure, be it accidentally or on purpose, this will make entire app unusable for everybody until the problem is fixed. That’s why only admins are allowed to place layers in folders other than the one specified above. If everything is OK with your layer, some admin will eventually move it from the Sandbox to a more appropriate location.
	The rest of the folders in the Library are protected from editing. The reason is that if someone messes up the Library structure, be it accidentally or on purpose, this will make entire app unusable for everybody until the problem is fixed. That’s why only admins are allowed to place layers in folders other than the one specified above. If everything is OK with your layer, some admin will eventually move it from the Sandbox to a more appropriate location.

	==How data is organised in the Library (categorisation)==		==How data is organised in the Library (categorisation)==

Karen: /* Where to save your layers in the Library */

2021-06-17T14:04:24Z

Where to save your layers in the Library

← Older revision		Revision as of 14:04, 17 June 2021
Line 5:		Line 5:

	==Where to save your layers in the Library==		==Where to save your layers in the Library==
	Use the folder Sandbox/Add your layers here		Use the folder ''Sandbox/Add'' your layers here
	The rest of the folders in the Library are protected from editing. The reason is that if someone messes up the Library structure, be it accidentally or on purpose, this will make entire app unusable for everybody until the problem is fixed. That’s why only admins are allowed to place layers in folders other than the one specified above. If everything is OK with your layer, some admin will eventually move it from the Sandbox to a more appropriate location.		The rest of the folders in the Library are protected from editing. The reason is that if someone messes up the Library structure, be it accidentally or on purpose, this will make entire app unusable for everybody until the problem is fixed. That’s why only admins are allowed to place layers in folders other than the one specified above. If everything is OK with your layer, some admin will eventually move it from the Sandbox to a more appropriate location.

	==How data is organised in the Library (categorisation)==		==How data is organised in the Library (categorisation)==