Contribute - Revision history

Aoineko: /* Assembly code */

2025-02-05T08:17:05Z

‎Assembly code

Aoineko: /* Knowledge base */

2025-02-05T08:15:37Z

‎Knowledge base

Aoineko: /* SDCC */

2025-02-05T08:12:41Z

‎SDCC

Aoineko: /* Knowledge base */

2025-02-05T08:09:32Z

‎Knowledge base

Aoineko: /* SDCC */

2025-02-05T08:06:05Z

‎SDCC

Aoineko: /* Assembly code */

2025-02-03T18:52:47Z

‎Assembly code

Aoineko: /* SDCC */

2025-02-03T18:50:04Z

‎SDCC

Aoineko at 18:44, 3 February 2025

2025-02-03T18:44:06Z

Aoineko at 18:43, 3 February 2025

2025-02-03T18:43:29Z

Aoineko at 18:30, 3 February 2025

2025-02-03T18:30:44Z

@@ Line 22: / Line 22: @@
 === Assembly code ===
-All assembly codes must be created by people who are familiar with the Z80 assembler and who are able to create code optimized for both speed and size.
+⚠️ All assembly codes must be created by people who are familiar with the Z80 assembler and who are able to create code optimized for both speed and size.
 Even providing only minimalist assembly code and a usage example is sufficient. The MSXgl creator can easily take care of the C wrapping and integration into the library.

@@ Line 15: / Line 15: @@
 ** The [https://aoineko.org/msxgl-doc source code documentation].
-* Improve the modules documentation by giving more code snapshot and give deeper explanation (for example about the library options).
+* '''Improve the modules documentation''' by adding more code example and giving deeper explanation (for example about the library options).
 * '''Improve sample programs documentation''', in particular through source code comments. To do this, you can use Push requests (PR) via the [https://github.com/aoineko-fr/MSXgl project's GitHub].

@@ Line 49: / Line 49: @@
 *: An alternative would be to add to the Build tool a script to parse all the assembly files generated, to go down the function hierarchy from main() and thus establish a list of used functions and variables. In a second step, further parsing could be used to remove what is not being used. The problem with this method is that functions are not well delimited in the assembler code. In any case, we'd need to find a way of forcing functions not to be eliminated in order to deal with very specific cases.
-* '''Report any SDCC bugs or non-optimal code generation''' (in terms of speed or size) to the [https://sourceforge.net/projects/sdcc SDCC support site].
+* '''Report any SDCC bugs or non-optimal code generation''' (in terms of speed or size) to the [https://sourceforge.net/projects/sdcc SDCC support site]. This is the best way to help SDCC to become better and improve not only MSXgl projects, but also all other libraries based on SDCC.
 === Tool ===
 * '''Create an MSXgl project creation wizard''' which allows the user to choose all the options he wants for his new project (MSX generation, target media, modules, ...) and which will generate the directory containing all the files needed to get started (library and project configuration, and source code template). The tool should not require the installation of any additional tools. It is therefore preferable that the tool be written either in Node.js (already supplied with the MSXgl package), or in C.

@@ Line 9: / Line 9: @@
 * '''Create MSXgl based programs''' and share the source code. If you can film the creation and share the video, that's even better. 😎
 ** This is useful for game creators, as they can see how others solve challenges they may also face, and it can serve as a tutorial for people discovering the MSXgl library and tools chain.
-** It's also very helpful for MSXgl creator, as it provides programs that can serve as test cases when there are impactful changes to the library or build tool.
+** It's also very helpful for MSXgl creator, as it provides programs that can serve as actual test cases when there are impactful changes to the library or build tool.
 * '''Review the documentation''' and report errors, omissions, or unclear parts. If you can provide improved version, it's even better. 🖤
 ** The articles on [https://aoineko.org/msxgl this wiki].
 ** The [https://aoineko.org/msxgl-doc source code documentation].
 * '''Improve sample programs documentation''', in particular through source code comments. To do this, you can use Push requests (PR) via the [https://github.com/aoineko-fr/MSXgl project's GitHub].

@@ Line 47: / Line 47: @@
 *: An alternative would be to add to the Build tool a script to parse all the assembly files generated, to go down the function hierarchy from main() and thus establish a list of used functions and variables. In a second step, further parsing could be used to remove what is not being used. The problem with this method is that functions are not well delimited in the assembler code. In any case, we'd need to find a way of forcing functions not to be eliminated in order to deal with very specific cases.
-* '''Report any SDCC bugs or non-optimal code generation''' (in terms of speed or size) to their [https://sourceforge.net/projects/sdcc support site].
+* '''Report any SDCC bugs or non-optimal code generation''' (in terms of speed or size) to the [https://sourceforge.net/projects/sdcc SDCC support site].
 === Tool ===
 * '''Create an MSXgl project creation wizard''' which allows the user to choose all the options he wants for his new project (MSX generation, target media, modules, ...) and which will generate the directory containing all the files needed to get started (library and project configuration, and source code template). The tool should not require the installation of any additional tools. It is therefore preferable that the tool be written either in Node.js (already supplied with the MSXgl package), or in C.

@@ Line 39: / Line 39: @@
 ** KSS replayer.
 ** MGSP2 replayer.
 === SDCC ===

@@ Line 42: / Line 42: @@
 === SDCC ===
-* '''Create a tool for deleting unused codes and variables'''. Currently, a large number of functions and variables can end up in the final binary file, potentially causing a big waste in terms of size. The SDCC team seems open to creating this feature directly in SDCC, but without some effort on our part, it could be several years before we can actually use it.
+* '''Create a tool to remove unused codes and variables'''. Currently, a large number of functions and variables can end up in the final binary file, potentially causing a big waste in terms of size. The SDCC team seems open to creating this feature directly in SDCC, but without some effort on our part, it could be several years before we can actually use it.
 * '''Report any SDCC bugs or non-optimal code generation''' (in terms of speed or size) to their [https://sourceforge.net/projects/sdcc support site].

← Older revision		Revision as of 18:43, 3 February 2025
Line 48:		Line 48:
	=== Tool ===		=== Tool ===

−	* '''Create an MSXgl project creation wizard''' which allows the user to choose all the options he wants for his new project (MSX generation, target media, modules, ...) and which will generate the directory containing all the files needed to get started (library and project configuration, and source code template).	+	* '''Create an MSXgl project creation wizard''' which allows the user to choose all the options he wants for his new project (MSX generation, target media, modules, ...) and which will generate the directory containing all the files needed to get started (library and project configuration, and source code template). The tool should not require the installation of any additional tools. It is therefore preferable that the tool be written either in Node.js (already supplied with the MSXgl package), or in C.

← Older revision		Revision as of 18:30, 3 February 2025
Line 45:		Line 45:

	* '''Report any bugs or non-optimal code generation''' (in terms of speed or size) to the [https://sourceforge.net/projects/sdcc SDCC support site].		* '''Report any bugs or non-optimal code generation''' (in terms of speed or size) to the [https://sourceforge.net/projects/sdcc SDCC support site].
		+
		+	=== Tool ===
		+
		+	* '''Create an MSXgl project creation wizard''' which allows the user to choose all the options he wants for his new project (MSX generation, target media, modules, ...) and which will generate the directory containing all the files needed to get started (library and project configuration, and source code template).