the change wiki:Calculator/Feature requests - Revision history

Elie: /* See also */

2023-10-17T18:59:33Z

Elie: /* Tables */

2023-10-17T18:51:21Z

Tables

← Older revision		Revision as of 14:51, 17 October 2023
Line 25:		Line 25:
	===Tables===		===Tables===
	* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.
	** Implementation idea subpage: [[/~~spreadsheets~~]]		** Implementation idea subpage: [[/Spreadsheets]]

	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==

Elie: Elie moved page Wiki for a better world:Calculator/feature requests to Wiki for a better world:Calculator/Feature requests without leaving a redirect: we capitalizing subpages now

2023-10-17T18:47:23Z

Elie moved page Wiki for a better world:Calculator/feature requests to Wiki for a better world:Calculator/Feature requests without leaving a redirect: we capitalizing subpages now

← Older revision	Revision as of 14:47, 17 October 2023
(No difference)

Elie: /* Calculations embedded on wikipages */

2023-05-17T21:59:41Z

Calculations embedded on wikipages

← Older revision		Revision as of 17:59, 17 May 2023
Line 23:		Line 23:
	** Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).		** Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).

			===Tables===
	* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.
	** Implementation idea subpage: [[/~~spreadsheet~~]]		** Implementation idea subpage: [[/spreadsheets]]

	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==

Elie: /* Calculations embedded on wikipages */

2023-05-17T20:33:33Z

Calculations embedded on wikipages

← Older revision		Revision as of 16:33, 17 May 2023
Line 25:		Line 25:

	* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.
			** Implementation idea subpage: [[/spreadsheet]]

	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==

Elie: /* Inline calculations (embedding on wikipages) */

2023-04-04T06:07:58Z

Inline calculations (embedding on wikipages)

← Older revision		Revision as of 02:07, 4 April 2023
Line 8:		Line 8:


	==~~Inline calculations (embedding~~ on wikipages)==		==Calculations embedded on wikipages==


Line 25:		Line 25:

	* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.



	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==

Elie at 06:05, 4 April 2023

2023-04-04T06:05:08Z

← Older revision		Revision as of 02:05, 4 April 2023
Line 1:		Line 1:
	Non-logged-in users can also make feature requests in ~~[[Talk:Calculator]]~~.		Non-logged-in users can also make feature requests in the {{talk}} page.

	==General==		==General==
Line 11:		Line 11:


	* ~~Green sections on pages need some kinda notice like "click a part of the equation~~ for ~~more details" (whenever there are 1 or more datapoints in the equation). Wiki writers shouldn't have to manually say it every time~~.		* Ability to split calculations onto multiple lines, for better readability.


	* ~~The 'from previous calculation' box could really~~ benefit from having the ~~numerical value in it~~ (~~preferrably~~ in the '~~units wanted' of the previous calculation~~. ~~Is this easy to implement?~~		* Green sections on pages would benefit from having some kinda notice like "click a part of the equation for more details" (whenever there are 1 or more datapoints in the equation). Wiki writers shouldn't have to manually say it every time.


	* ~~Better graceful failure when javascript isn~~'~~t available. The green section should say something about needing a browser that has javascript. Instead,~~ it ~~currently just shows a half-baked~~ calculation~~, in a way that would confuse most readers~~.		* The 'from previous calculation' box could really benefit from having the numerical value in it (preferrably in the 'units wanted' of the previous calculation. Is this easy to implement?


	* Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).		* Better error handling: Currently, syntax errors will bleed into the next calculations and produce messages that don't even make sense.
			** Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).

Elie: Elie moved page Calculator/feature requests to Wiki for a better world:Calculator/feature requests

2023-04-03T00:13:50Z

Elie moved page Calculator/feature requests to Wiki for a better world:Calculator/feature requests

← Older revision	Revision as of 20:13, 2 April 2023
(No difference)

Elie at 06:02, 22 February 2023

2023-02-22T06:02:05Z

← Older revision		Revision as of 02:02, 22 February 2023
Line 1:		Line 1:
	Non-logged-in users can also make feature requests in [[Talk:Calculator]].		Non-logged-in users can also make feature requests in [[Talk:Calculator]].

			==General==

			* Have a margin of error for each datapoint, so you can combine all your high and low estimates into one calculation.
			** Maybe it could even generate a popup with a distribution curve (idk maybe that's too complicated to implement).
			** Ranges are supported by [http://frinklang.org Frink], but not GNU Units. The calculator is currently powered by GNU Units. Switching to Frink might come with a lot of complications {{x\|For one, Java Runtime Environment would need to be installed on the web server. If the Frink program has to load every time a user makes a calculation, it could be very slow. Maybe there's a way to keep one instance of Frink running and feed calculations through it. This could take a lot of work to implement with threading etc. Or maybe running one instance of Frink per ''user session'' would be a good idea. Or maybe we could make a program in Java that uses the Frink Java Library. Lots of design decisions would need to be made. Also, some current datapoints would need to be updated (both in the database ''and'' inline on wikipages), because in Frink, the operator-precedence of ''implied multiplication'' is lower than division; in GNU Units, it is higher.}}


Line 5:		Line 11:


	Green sections on pages need some kinda notice like "click a part of the equation for more details" (whenever there are 1 or more datapoints in the equation). Wiki writers shouldn't have to manually say it every time.		* Green sections on pages need some kinda notice like "click a part of the equation for more details" (whenever there are 1 or more datapoints in the equation). Wiki writers shouldn't have to manually say it every time.


	The 'from previous calculation' box could really benefit from having the numerical value in it (preferrably in the 'units wanted' of the previous calculation. Is this easy to implement?		* The 'from previous calculation' box could really benefit from having the numerical value in it (preferrably in the 'units wanted' of the previous calculation. Is this easy to implement?


	Better graceful failure when javascript isn't available. The green section should say something about needing a browser that has javascript. Instead, it currently just shows a half-baked calculation, in a way that would confuse most readers.		* Better graceful failure when javascript isn't available. The green section should say something about needing a browser that has javascript. Instead, it currently just shows a half-baked calculation, in a way that would confuse most readers.


	Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).		* Better graceful failure when datapoints aren't available. Just give some notice - maybe keep the equation the way it is, but put the result as 'unknown - missing data points' and put the missing datapoints as red links which show a box "data unavailable - research is unfinished" (or if that takes to long, then at least just have the datapoints as red text).


	Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		* Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.


	Implement ''ranges'' of data, so you can combine all your high and low estimates into one calculation which can expand to give u a popup with the distribution curve idk maybe that's too complicated to implement.

	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==


	Need a "copy wikitext" button beside each datapoint		* Need a "copy wikitext" button beside each datapoint


			* Maybe the user interface should have a right arrow (forward) instead of "Link", and a left arrow (back) instead of "Do another calculation".


	Maybe ~~the user interface should~~ have a ~~right arrow (forward) instead~~ of ~~"Link", and a left arrow (back)~~ instead ~~of "Do another calculation".~~		* Maybe have some easy way to pull datapoints from wiki pages
			** box to paste wikitext into?
			** or some automatic thing when you publish a page? in which case, how would it handle multiple datapoints of the same name? too complicated; do the first option instead


	~~Maybe have some easy way to pull datapoints from wiki pages~~		==See also==
	* ~~box to paste wikitext into?~~		* [[Calculator/known bugs]]
	* ~~or some automatic thing when you publish a page? in which case, how would it handle multiple datapoints of the same name? too complicated; do the first option instead~~		* [[Expandables/feature requests]]

Elie: /* Inline calculations (embedding on wikipages) */

2022-11-04T07:07:52Z

Inline calculations (embedding on wikipages)

← Older revision		Revision as of 03:07, 4 November 2022
Line 18:		Line 18:

	Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.		Alternative 'span'-type calculations that can fit inside tables. Should show just the result, but as a link that shows a popup with the equation {{x\|should act basically the same as the popups of you currently get when clicking on datapoints - because the subpopup problem is already solved there}}. Ideally, this should load last, so you can have your summary table at the top of the page, one that depends on calculations below it.


			Implement ''ranges'' of data, so you can combine all your high and low estimates into one calculation which can expand to give u a popup with the distribution curve idk maybe that's too complicated to implement.

	==[https://olam.wiki/calc Common calculator]==		==[https://olam.wiki/calc Common calculator]==

← Older revision		Revision as of 14:59, 17 October 2023
Line 42:		Line 42:

	==See also==		==See also==
	* [[Calculator/~~known~~ bugs]]		* [[{{NAMESPACE}}:Calculator/Known bugs]]
	* [[Expandables/~~feature~~ requests]]		* [[{{NAMESPACE}}:Expandables/Feature requests]]