Wxfred2Contributions - Revision history

TopAce: -

2022-10-18T07:09:51Z

← Older revision		Revision as of 07:09, 18 October 2022
Line 18:		Line 18:
	* Issue a Pull Request, and a badged SCP member (probably z64555) will review & commit your changes		* Issue a Pull Request, and a badged SCP member (probably z64555) will review & commit your changes

	=Mission statement of the wxFRED2 project=		==Mission statement of the wxFRED2 project==
	Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the existing code as possible (while not screwing over future development)		Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the existing code as possible (while not screwing over future development)

TopAce: formatting

2022-10-18T07:02:54Z

formatting

← Older revision		Revision as of 07:02, 18 October 2022
Line 3:		Line 3:
	First off, thanks for stopping by!		First off, thanks for stopping by!

	If you've found this page, it probably means that you or someone you know is interested in the development of the upcoming wxFRED2, a port of the ~~Freespace~~ 2 Editor to use the wxWidgets GUI library. Here we'll post some useful links as well as a guideline or two.		If you've found this page, it probably means that you or someone you know is interested in the development of the upcoming wxFRED2, a port of the FreeSpace 2 Editor to use the wxWidgets GUI library. Here we'll post some useful links as well as a guideline or two.

	If you have not done so already, please skim over this forum topic: [http://www.hard-light.net/forums/index.php?topic=82688.0 The "Read Me First" Posts]		If you have not done so already, please skim over this forum topic: [http://www.hard-light.net/forums/index.php?topic=82688.0 The "Read Me First" Posts]

	=Getting the source code=		==Getting the source code==
	We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow.		We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow.

Line 21:		Line 21:
	Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the existing code as possible (while not screwing over future development)		Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the existing code as possible (while not screwing over future development)

	=Coding Gudelines=		==Coding Gudelines==
	"The Golden Rule"		"The Golden Rule"
	* No business logic be located in the UI elements		* No business logic be located in the UI elements
Line 27:		Line 27:
	* Any operations in the UI that do actual work must go through an API provided by wxfred2.h and wxfred2.cpp		* Any operations in the UI that do actual work must go through an API provided by wxfred2.h and wxfred2.cpp

	=Coding Style=		==Coding Style==
	* Any coding style is permitted, just be sure to follow the existing style if you are editing a file		* Any coding style is permitted, just be sure to follow the existing style if you are editing a file
	* "Allman" is the most prevalent brace and spacing style		* "Allman" is the most prevalent brace and spacing style
Line 35:		Line 35:
	** All other methods/functions may have their own style, but please be sure to follow existing style if present		** All other methods/functions may have their own style, but please be sure to follow existing style if present

	=Features and Bugs=		==Features and Bugs==
	<nowiki>Maintainers: Please be sure to mark the date this was last edited by using --~~~~----</nowiki>		<nowiki>Maintainers: Please be sure to mark the date this was last edited by using --~~~~----</nowiki>

Z64555 at 11:05, 1 May 2022

2022-05-01T11:05:03Z

← Older revision		Revision as of 11:05, 1 May 2022
Line 1:		Line 1:
			{{Note \| wxFRED has been abandoned in favor of qtFRED. This page has been left as a testament to efforts put into wxFRED as it laid the foundation for qtFRED.}}

	First off, thanks for stopping by!		First off, thanks for stopping by!

Echelon9: Reflect source code hosting via Git

2015-05-03T04:38:00Z

Reflect source code hosting via Git

← Older revision		Revision as of 04:38, 3 May 2015
Line 6:		Line 6:

	=Getting the source code=		=Getting the source code=
	We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow~~. Should the need arise, we can switch back to the main SVN repository~~.		We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow.

	* Download and install the [http://git-scm.com/downloads latest version of git]		* Download and install the [http://git-scm.com/downloads latest version of git]

Z64555 at 11:13, 23 October 2013

2013-10-23T11:13:20Z

← Older revision		Revision as of 11:13, 23 October 2013
Line 36:		Line 36:
	<nowiki>Maintainers: Please be sure to mark the date this was last edited by using --~~~~----</nowiki>		<nowiki>Maintainers: Please be sure to mark the date this was last edited by using --~~~~----</nowiki>

	Updated by: --[[User:Z64555\|Z64555]] 00:02, 22 October 2013 (UTC)----		Updated by: --[[User:Z64555\|Z64555]] 11:13, 23 October 2013 (UTC)----

	{\| class="wikitable" style="color:red"		{\| class="wikitable" style="color:red"
Line 49:		Line 49:
	\|-		\|-
	\| glViewport		\| glViewport
			\| z64555
			\| no
			\|-
			\| docFRED
	\| z64555		\| z64555
	\| no		\| no

Niffiwan at 00:35, 22 October 2013

2013-10-22T00:35:11Z

← Older revision		Revision as of 00:35, 22 October 2013
Line 3:		Line 3:
	If you've found this page, it probably means that you or someone you know is interested in the development of the upcoming wxFRED2, a port of the Freespace 2 Editor to use the wxWidgets GUI library. Here we'll post some useful links as well as a guideline or two.		If you've found this page, it probably means that you or someone you know is interested in the development of the upcoming wxFRED2, a port of the Freespace 2 Editor to use the wxWidgets GUI library. Here we'll post some useful links as well as a guideline or two.

	If you have not done so already, please skim over this forum topic: [http://www.hard-light.net/forums/index.php?topic=82688.0\| The "Read Me First" Posts]		If you have not done so already, please skim over this forum topic: [http://www.hard-light.net/forums/index.php?topic=82688.0 The "Read Me First" Posts]

	=Getting the source code=		=Getting the source code=
	We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow. Should the need arise, we can switch back to the main SVN repository.		We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow. Should the need arise, we can switch back to the main SVN repository.

	* Download and install the [http://git-scm.com/downloads\| latest version of git]		* Download and install the [http://git-scm.com/downloads latest version of git]
	* Sign Up on or Log Into [http://github.com\| GitHub]		* Sign Up on or Log Into [http://github.com GitHub]
	* Fork the [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2\| wxFRED2 branch] from the GitHub repository		* Fork the [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2 wxFRED2 branch] from the GitHub repository
	* Make changes to the wxfred2 branch		* Make changes to the wxfred2 branch
	** Verify the changes are compilable and buildable		** Verify the changes are compilable and buildable
Line 68:		Line 68:
	* http://pastebin.com/z8nADzxt mission frame (context) source		* http://pastebin.com/z8nADzxt mission frame (context) source

	Please use [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2\| Mantis] for bug tracking.		Please use [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2 Mantis] for bug tracking.

Z64555: /* Features and Bugs */

2013-10-22T00:13:08Z

Features and Bugs

← Older revision		Revision as of 00:13, 22 October 2013
Line 33:		Line 33:
	** All other methods/functions may have their own style, but please be sure to follow existing style if present		** All other methods/functions may have their own style, but please be sure to follow existing style if present

	=Features to Bugs=		=Features and Bugs=
	<nowiki>Please be sure to mark the date this was last edited by using --~~~~----</nowiki>		<nowiki>Maintainers: Please be sure to mark the date this was last edited by using --~~~~----</nowiki>

	Updated by: --[[User:Z64555\|Z64555]] 00:02, 22 October 2013 (UTC)----		Updated by: --[[User:Z64555\|Z64555]] 00:02, 22 October 2013 (UTC)----

Z64555 at 00:02, 22 October 2013

2013-10-22T00:02:43Z

← Older revision		Revision as of 00:02, 22 October 2013
Line 1:		Line 1:
	~~=Get the source code=~~		First off, thanks for stopping by!

	* Fork ~~this~~ [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2 ~~git~~ repository]		If you've found this page, it probably means that you or someone you know is interested in the development of the upcoming wxFRED2, a port of the Freespace 2 Editor to use the wxWidgets GUI library. Here we'll post some useful links as well as a guideline or two.

			If you have not done so already, please skim over this forum topic: [http://www.hard-light.net/forums/index.php?topic=82688.0\| The "Read Me First" Posts]

			=Getting the source code=
			We'll be starting off by using the GitHub repository for the wxFRED2, so as to achieve familiarity with the GitHub workflow. Should the need arise, we can switch back to the main SVN repository.

			* Download and install the [http://git-scm.com/downloads\| latest version of git]
			* Sign Up on or Log Into [http://github.com\| GitHub]
			* Fork the [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2\| wxFRED2 branch] from the GitHub repository
	* Make changes to the wxfred2 branch		* Make changes to the wxfred2 branch
	* Issue a ~~pull request for someone~~ (z64555?) to review & commit your changes		** Verify the changes are compilable and buildable
			* Commit your changes to your local repo, then push your local repo onto your forked repo on GitHub
			* Issue a Pull Request, and a badged SCP member (probably z64555) will review & commit your changes

			=Mission statement of the wxFRED2 project=
			Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the existing code as possible (while not screwing over future development)

	=Coding Gudelines=		=Coding Gudelines=
			"The Golden Rule"
			* No business logic be located in the UI elements
			* UI stuff is strictly UI
			* Any operations in the UI that do actual work must go through an API provided by wxfred2.h and wxfred2.cpp

	(~~taken from z64555 on IRC~~)		=Coding Style=
			* Any coding style is permitted, just be sure to follow the existing style if you are editing a file
			* "Allman" is the most prevalent brace and spacing style
			* wxWidgets class names are camel case, and have a lowercase prefix of 2 to 4 letters. ex: "frmFRED" for frame, "glcVieport" for a glCanvas, etc.
			** All other class names are camel case and have no prefix, and first letter is capitalized. ex: ViewSettings
			* wxWidgets Handler methods/functions are camel case, and have the first letter capitalized ex: OnPaint()
			** All other methods/functions may have their own style, but please be sure to follow existing style if present

	* "Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the backend code as possible" (while not screwing over future development)		=Features to Bugs=
	* "the golden rule for wxFred is that no business logic be ~~located in~~ the ~~UI elements"~~		<nowiki>Please be sure to mark the date this was last edited by using --~~~~----</nowiki>
	* "UI stuff is strictly UI, any op's that do actual things must go through an API provided by ~~wxfred2.h and .cpp"~~
	* Coding style - ~~I think we should enforce one for new wxfred2 code, I don't which one, just any one~~

	~~=Features to work on=~~		Updated by: --[[User:Z64555\|Z64555]] 00:02, 22 October 2013 (UTC)----

	{\| class="wikitable" style="color:red"		{\| class="wikitable" style="color:red"
	\|- style="color:black"		\|- style="color:black"
	! Feature ~~name~~		! Component or Feature
	! ~~Who is working on it?~~		! Active Developer(s)
	! ~~Is it done?~~		! Completed
	\|- style="color:green"		\|- style="color:green"
	\| create all windows		\| create all windows
Line 26:		Line 48:
	\| yes		\| yes
	\|-		\|-
	\| ~~glViewpoint~~		\| glViewport
	\| z64555		\| z64555
	\| no		\| no
	\|-		\|-
	\| New Mission		\| File-New Mission
	\| ?		\| ?
	\| no		\| no
	\|-		\|-
	\| Save ~~mission file~~		\| File-Save Mission
	\| niffiwan?		\| niffiwan?
	\| no		\| no
	\|}		\|}

	Some ~~pastebins:~~		Some Pastebins for reference/discussion
	* http://pastebin.com/qBSATeP2 ~~(object management?)~~		* http://pastebin.com/qBSATeP2 Early API for UI/backend
	* http://pastebin.com/BWXamnrf (viewport)		* http://pastebin.com/BWXamnrf viewport header
	* http://pastebin.com/uu87vurg (viewport)?		* http://pastebin.com/uu87vurg viewport source
	* http://pastebin.com/v9Sh58v9 (mission frame (context))		* http://pastebin.com/v9Sh58v9 mission frame (context) header
	* http://pastebin.com/z8nADzxt (mission frame (context))?		* http://pastebin.com/z8nADzxt mission frame (context) source

	~~Or - just link to~~ [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2 ~~mantis~~]?		Please use [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2\| Mantis] for bug tracking.

Niffiwan at 22:59, 21 October 2013

2013-10-21T22:59:02Z

← Older revision		Revision as of 22:59, 21 October 2013
Line 1:		Line 1:
	=Get the source code=		=Get the source code=

	* Fork this [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2\| git repository]		* Fork this [https://github.com/scp-fs2open/fs2open.github.com/tree/wxfred2 git repository]
	* Make changes to the wxfred2 branch		* Make changes to the wxfred2 branch
	* Issue a pull request for someone (z64555?) to review & commit your changes		* Issue a pull request for someone (z64555?) to review & commit your changes
Line 46:		Line 46:
	* http://pastebin.com/z8nADzxt (mission frame (context))?		* http://pastebin.com/z8nADzxt (mission frame (context))?

	Or - just link to [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2\| mantis]?		Or - just link to [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2 mantis]?

Niffiwan at 03:44, 21 October 2013

2013-10-21T03:44:23Z

← Older revision		Revision as of 03:44, 21 October 2013
Line 4:		Line 4:
	* Make changes to the wxfred2 branch		* Make changes to the wxfred2 branch
	* Issue a pull request for someone (z64555?) to review & commit your changes		* Issue a pull request for someone (z64555?) to review & commit your changes

			=Coding Gudelines=

			(taken from z64555 on IRC)

			* "Trash the MFC UI elements, Use wxWidgets UI elements, use as much of the backend code as possible" (while not screwing over future development)
			* "the golden rule for wxFred is that no business logic be located in the UI elements"
			* "UI stuff is strictly UI, any op's that do actual things must go through an API provided by wxfred2.h and .cpp"
			* Coding style - I think we should enforce one for new wxfred2 code, I don't which one, just any one

	=Features to work on=		=Features to work on=


	{\| class="wikitable" style="color:red"		{\| class="wikitable" style="color:red"
Line 17:		Line 25:
	\| z64555		\| z64555
	\| yes		\| yes
			\|-
			\| glViewpoint
			\| z64555
			\| no
	\|-		\|-
	\| New Mission		\| New Mission
Line 26:		Line 38:
	\| no		\| no
	\|}		\|}

			Some pastebins:
			* http://pastebin.com/qBSATeP2 (object management?)
			* http://pastebin.com/BWXamnrf (viewport)
			* http://pastebin.com/uu87vurg (viewport)?
			* http://pastebin.com/v9Sh58v9 (mission frame (context))
			* http://pastebin.com/z8nADzxt (mission frame (context))?

	Or - just link to [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2\| mantis]?		Or - just link to [http://scp.indiegames.us/mantis/set_project.php?project_id=1;2\| mantis]?