EasyCoding - Revision history

Bssarkar: /* Debug mode */ issue fixed on PR 8767

2024-04-29T17:23:58Z

Debug mode: issue fixed on PR 8767

← Older revision		Revision as of 17:23, 29 April 2024
Line 126:		Line 126:

	* New debug command functionality (setting additional status.variables, possibly terrain)		* New debug command functionality (setting additional status.variables, possibly terrain)
	* Allowing teleportation via debug mode contextual menu: https://github.com/wesnoth/wesnoth/issues/5649

	=== woptipng / wesnoth-optipng ===		=== woptipng / wesnoth-optipng ===

Egallager: /* WML-related features */ "Good first issue" tag was removed from the [query_location] one, so I'm moving it to NotSoEasyCoding

2022-12-23T08:52:28Z

WML-related features: "Good first issue" tag was removed from the [query_location] one, so I'm moving it to NotSoEasyCoding

← Older revision		Revision as of 08:52, 23 December 2022
Line 91:		Line 91:

	https://github.com/wesnoth/wesnoth/issues/2326		https://github.com/wesnoth/wesnoth/issues/2326

	~~=== Game Information ===~~

	* [query_location] - queries a location from the user
	** variable
	** [filter_location]
	''Regarding [query_location]: probably a better name would be choose_location. This is used when a wml event is running and needs to get a target location hex from the user. For example, you right click on a catapult unit and choose the menu item "fire Catapult." Now a [message] says to click on any target within 5 hexes. Now [choose_location] is encountered and the mouse cursor changes to a target sign (possibly customizable). If the user's mouse drifts outside of the allowed locations it changes to a cancel icon. If the operation is cancelled then the variable is cleared and no location stored. --Sapient''

	~~''This can be implemented in lua by using wesnoth.game_events.on_mouse_action and wesnoth.syncronize_choice''~~

	~~https://github.com/wesnoth/wesnoth/issues/2325~~

	== Improvements to AI ==		== Improvements to AI ==

Egallager: /* Debug mode */

2022-12-23T08:45:08Z

Debug mode

← Older revision		Revision as of 08:45, 23 December 2022
Line 137:		Line 137:

	* New debug command functionality (setting additional status.variables, possibly terrain)		* New debug command functionality (setting additional status.variables, possibly terrain)
			* Allowing teleportation via debug mode contextual menu: https://github.com/wesnoth/wesnoth/issues/5649

	=== woptipng / wesnoth-optipng ===		=== woptipng / wesnoth-optipng ===

Egallager: /* woptipng / wesnoth-optipng */

2022-12-23T08:43:43Z

woptipng / wesnoth-optipng

← Older revision		Revision as of 08:43, 23 December 2022
Line 143:		Line 143:
	* a quick profiling of compression ratio and decompression speed for all relevant tools		* a quick profiling of compression ratio and decompression speed for all relevant tools
	* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut or oxipng (whichever makes more sense)		* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut or oxipng (whichever makes more sense)
	* note that there is a separate repository for woptipng: [https://github.com/matthiaskrgr/woptipng https://github.com/matthiaskrgr/woptipng]		* note that there is a separate repository for woptipng: [https://github.com/matthiaskrgr/woptipng https://github.com/matthiaskrgr/woptipng] (with its own issue tracker, etc.)

	== Bugs ==		== Bugs ==

Egallager: /* Make a "map diff" tool to visualizes changes between two version of a map */ Update about status

2022-12-23T08:42:22Z

Make a "map diff" tool to visualizes changes between two version of a map: Update about status

← Older revision		Revision as of 08:42, 23 December 2022
Line 24:		Line 24:

	https://github.com/wesnoth/wesnoth/issues/2323		https://github.com/wesnoth/wesnoth/issues/2323

			Note that the current status here is that a "map diff" tool now actually exists as a GitHub action that runs on pull requests with changed maps, although there are some bugs with it that could be fixed, and having a native "map diff" tool that runs as part of Wesnoth itself would fit the original request better.

	=== Add an option to not store replays ===		=== Add an option to not store replays ===

Egallager: /* WML-related features */ 1477 has been closed

2022-06-25T11:30:32Z

WML-related features: 1477 has been closed

← Older revision		Revision as of 11:30, 25 June 2022
Line 75:		Line 75:

	== WML-related features ==		== WML-related features ==

	~~=== Side filter support in [item] ===~~

	~~Currently [items] allows a team_name= attribute to specify for which side the item is displayed; it would be better if [item] allowed a side filter to specify for which side the item is displayed.~~

	~~See the bug report https://github.com/wesnoth/wesnoth/issues/1477~~

	=== Support variable poison properties ===		=== Support variable poison properties ===

Egallager: /* woptipng / wesnoth-optipng */ note separate repository for woptipng

2022-06-25T11:29:03Z

woptipng / wesnoth-optipng: note separate repository for woptipng

← Older revision		Revision as of 11:29, 25 June 2022
Line 144:		Line 144:
	=== woptipng / wesnoth-optipng ===		=== woptipng / wesnoth-optipng ===

	For lossless png compression we use woptipng, a script using an external toolchain (ImageMagick, OptiPNG, Advdef). Perhaps the performance could be improved by using PNGOut instead of advdef. This task includes:		For lossless png compression we use woptipng, a script using an external toolchain (ImageMagick, OptiPNG, Advdef, oxipng). Perhaps the performance could be improved by using oxipng or PNGOut instead of advdef. This task includes:
	* a quick profiling of compression ratio and decompression speed for ~~both~~ tools		* a quick profiling of compression ratio and decompression speed for all relevant tools
	* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut		* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut or oxipng (whichever makes more sense)
			* note that there is a separate repository for woptipng: [https://github.com/matthiaskrgr/woptipng https://github.com/matthiaskrgr/woptipng]

	== Bugs ==		== Bugs ==

Pentarctagon at 18:13, 24 June 2022

2022-06-24T18:13:03Z

← Older revision		Revision as of 18:13, 24 June 2022
Line 1:		Line 1:
	'''~~We are permanently updating this~~ page. ~~Parts marked by <s>strikeout<~~/~~s> will likely be deleted shortly~~.		'''This page is outdated. For an up to date list of good starting issues, see [https://github.com/wesnoth/wesnoth/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%22 here].

	This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.		This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

Egallager: misc. copyediting

2021-09-15T09:17:15Z

misc. copyediting

Wedge009: /* GUI2 features */

2021-09-15T03:32:47Z

GUI2 features

← Older revision		Revision as of 03:32, 15 September 2021
Line 134:		Line 134:
	* Make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)		* Make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
	* The biggest feature yet to be converted to GUI2 is the in-game Help documentation (first available from the main screen).		* The biggest feature yet to be converted to GUI2 is the in-game Help documentation (first available from the main screen).
			** There was an [https://github.com/wesnoth/wesnoth/pull/3653 initial effort to convert Help to GUI2], but appears to be pending on the implementation of a [https://github.com/wesnoth/wesnoth/issues/2687 rich-text label widget].

	== Miscellaneous ==		== Miscellaneous ==

← Older revision		Revision as of 09:17, 15 September 2021
Line 5:		Line 5:
	If you are such a person, you should feel free to edit this page.		If you are such a person, you should feel free to edit this page.

	If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.		If you're not, you should post a feature request and discuss your idea on the forum or IRC or Discord. A coder with better knowledge of the code might give you the green light to add your feature here.

	Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.		Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.
Line 27:		Line 27:
	=== Add an option to not store replays ===		=== Add an option to not store replays ===

	As noted in https://wiki.wesnoth.org/SavefileWML all normal savefiles usually contain [replay] and [replay_start] tags that usually take over 50% of the total savefile size and are only used for providing the ~~possibilty~~ to replay scenarios. It's be nice to have an option to skip these information to reduce the savefile size. ~~Alternativeley~~ one could create a tool ~~inrtegated~~ in a load/savegame dialog to remove the replay information from a given savegame file.		As noted in https://wiki.wesnoth.org/SavefileWML all normal savefiles usually contain [replay] and [replay_start] tags that usually take over 50% of the total savefile size and are only used for providing the possibility to replay scenarios. It's be nice to have an option to skip these information to reduce the savefile size. Alternatively one could create a tool integrated in a load/savegame dialog to remove the replay information from a given savegame file.

	See the feature request https://github.com/wesnoth/wesnoth/issues/1457		See the feature request https://github.com/wesnoth/wesnoth/issues/1457
Line 64:		Line 64:
	Often times in mp, players concede the game before their leader is actually killed. When the game ends 'officially' the map is revealed, which can sometimes be instructive for the losing player. Additionally, it makes it easier to analyze the results of many games, for purposes of balancing, or for maintaining a ladder. So while it may seem small, this would actually be a pretty useful feature.		Often times in mp, players concede the game before their leader is actually killed. When the game ends 'officially' the map is revealed, which can sometimes be instructive for the losing player. Additionally, it makes it easier to analyze the results of many games, for purposes of balancing, or for maintaining a ladder. So while it may seem small, this would actually be a pretty useful feature.

	~~FIXME~~: ~~figure out gh issue id~~		There was a PR to fix this, but it never got merged due to being broken: https://github.com/wesnoth/wesnoth/pull/535

	This could be implemented in lua.		This could be implemented in lua.
Line 70:		Line 70:
	=== Show [options] values in the mp lobby gameslist ===		=== Show [options] values in the mp lobby gameslist ===

	It' be useful for newly joining ~~payer~~ to see the chosen [options] of a mp game, since most ~~likeley~~ there isn't enough space we could for example wigher show the options via an extra dropdown button in ~~th elobby~~ or show them in the mp waiting dialog instead.		It'd be useful for a newly-joining player to see the chosen [options] of a mp game, since most likely there isn't enough space we could for example wigher show the options via an extra dropdown button in the lobby or show them in the mp waiting dialog instead.

	See the featurerequest https://github.com/wesnoth/wesnoth/issues/1514		See the featurerequest https://github.com/wesnoth/wesnoth/issues/1514
Line 78:		Line 78:
	=== Side filter support in [item] ===		=== Side filter support in [item] ===

	~~currently~~ [items] allows a team_name= attribute to specify for which side the item is displayed, it would be better if [item] allowed a side filter to specify for which side the item is displayed.		Currently [items] allows a team_name= attribute to specify for which side the item is displayed; it would be better if [item] allowed a side filter to specify for which side the item is displayed.

	See the bug report https://github.com/wesnoth/wesnoth/issues/1477		See the bug report https://github.com/wesnoth/wesnoth/issues/1477
Line 144:		Line 144:
	=== woptipng / wesnoth-optipng ===		=== woptipng / wesnoth-optipng ===

	For lossless png compression we use woptipng, a script using an external toolchain (ImageMagick, OptiPNG, Advdef). Perhaps the performance could be improved by using PNGOut instead of advdef. This task includes		For lossless png compression we use woptipng, a script using an external toolchain (ImageMagick, OptiPNG, Advdef). Perhaps the performance could be improved by using PNGOut instead of advdef. This task includes:
	* a quick profiling of compression ratio and decompression speed for both tools		* a quick profiling of compression ratio and decompression speed for both tools
	* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut		* if it provides a higher compression while not significantly slowing down decompression, adapt woptipng to use PNGOut