GhostMVC IDE - Revision history

Adamcolton: /* Version Control */

2013-05-09T13:33:08Z

Version Control

← Older revision		Revision as of 13:33, 9 May 2013
Line 26:		Line 26:

	== Version Control ==		== Version Control ==
	I should look into tying into git.		I should look into tying into git. I do like the idea of being able to branch the whole site - some structure that allows multiple developers to work on the site without stepping on each others toes.

	== Publish ==		== Publish ==
	Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.		Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.

Adamcolton at 13:17, 9 May 2013

2013-05-09T13:17:17Z

← Older revision		Revision as of 13:17, 9 May 2013
Line 3:		Line 3:
	The IDE will be called MarleyIDE (after Jacob Marley).		The IDE will be called MarleyIDE (after Jacob Marley).

	=Editor=		== Editor ==
	This is the big question. The base editor needs to cover all default text behavior (select, cut, copy, move, type, display cursor) but have hooks so I can do syntax highlighting and text manipulation. It also needs to be mono-spaced and show spaces and tabs accurately.		This is the big question. The base editor needs to cover all default text behavior (select, cut, copy, move, type, display cursor) but have hooks so I can do syntax highlighting and text manipulation. It also needs to be mono-spaced and show spaces and tabs accurately.

Line 15:		Line 15:
	Or this: http://codemirror.net/		Or this: http://codemirror.net/

	==Features==		=== Features ===
	#Line Numbers		#Line Numbers
	#Indenting		#Indenting
Line 22:		Line 22:
	#Code folding		#Code folding

	=Database=		== Database ==
	The database tool will allow all the database manipulation one would expect. Any command that alters the schema is saved to version control and can be added to a publish (or discarded).		The database tool will allow all the database manipulation one would expect. Any command that alters the schema is saved to version control and can be added to a publish (or discarded).

	= Version Control =		== Version Control ==
	I should look into tying into git.		I should look into tying into git.

	=Publish=		== Publish ==
	Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.		Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.

Adamcolton: /* Version Control */

2013-05-09T13:16:31Z

Version Control

← Older revision		Revision as of 13:16, 9 May 2013
Line 25:		Line 25:
	The database tool will allow all the database manipulation one would expect. Any command that alters the schema is saved to version control and can be added to a publish (or discarded).		The database tool will allow all the database manipulation one would expect. Any command that alters the schema is saved to version control and can be added to a publish (or discarded).

	=Version Control=		= Version Control =
	Not quite the typically check-in check out model, a site is a branch so everything is checked out all the time. But you can 'mark' a change set so that you can roll-back to that point or view it in history.		I should look into tying into git.

	~~To achieve this,~~ I'm going to go with a really simple system. One folder contains everything. Any time a file is saved to version control it's given a unique name. A single log holds all the information and maps that unique name to what file it really is as well as change set and version.

	=Publish=		=Publish=
	Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.		Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.

Adamcolton: /* Editor */

2013-05-09T13:15:04Z

Editor

← Older revision		Revision as of 13:15, 9 May 2013
Line 12:		Line 12:

	USE THIS: http://ace.ajax.org/		USE THIS: http://ace.ajax.org/

			Or this: http://codemirror.net/

	==Features==		==Features==

Adamcolton at 19:13, 20 April 2012

2012-04-20T19:13:48Z

← Older revision		Revision as of 19:13, 20 April 2012
Line 10:		Line 10:

	Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.		Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.

			USE THIS: http://ace.ajax.org/

	==Features==		==Features==

Adamcolton at 14:27, 6 January 2012

2012-01-06T14:27:08Z

← Older revision		Revision as of 14:27, 6 January 2012
Line 12:		Line 12:

	==Features==		==Features==
	*Code highlighting (using GeSHI)		#Line Numbers
	*Code folding		#Indenting
	*Indenting		#Code highlighting (using GeSHI)
	*Basic code completion (dictionary look-up)		#Basic code completion (dictionary look-up)
			#Code folding

	=Database=		=Database=

Adamcolton at 14:25, 6 January 2012

2012-01-06T14:25:38Z

← Older revision		Revision as of 14:25, 6 January 2012
Line 10:		Line 10:

	Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.		Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.

			==Features==
			*Code highlighting (using GeSHI)
			*Code folding
			*Indenting
			*Basic code completion (dictionary look-up)

	=Database=		=Database=

Adamcolton at 17:25, 5 January 2012

2012-01-05T17:25:57Z

← Older revision		Revision as of 17:25, 5 January 2012
Line 1:		Line 1:
	The IDE has a few components designed to build a site through a web browser and maintain it.		The IDE has a few components designed to build a site through a web browser and maintain it.

			The IDE will be called MarleyIDE (after Jacob Marley).

	=Editor=		=Editor=
	This is the big question. The base editor needs to cover all default text behavior (select, cut, copy, move, type, display cursor) but have hooks so I can do syntax highlighting and text manipulation. It also needs to be mono-spaced and show spaces and tabs ~~accuratly~~.		This is the big question. The base editor needs to cover all default text behavior (select, cut, copy, move, type, display cursor) but have hooks so I can do syntax highlighting and text manipulation. It also needs to be mono-spaced and show spaces and tabs accurately.

			It seems the best way to do this is through an iframe in designMode:
			document.getElementById("marleyEditor").contentDocument.designMode = "On";

	Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.		Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.

Adamcolton: Created page with "The IDE has a few components designed to build a site through a web browser and maintain it. =Editor= This is the big question. The base editor needs to cover all default text b..."

2011-12-13T16:44:04Z

Created page with "The IDE has a few components designed to build a site through a web browser and maintain it. =Editor= This is the big question. The base editor needs to cover all default text b..."

New page

The IDE has a few components designed to build a site through a web browser and maintain it.

=Editor=
This is the big question. The base editor needs to cover all default text behavior (select, cut, copy, move, type, display cursor) but have hooks so I can do syntax highlighting and text manipulation. It also needs to be mono-spaced and show spaces and tabs accuratly.

Once I have that, I want to follow a sort of unixy model of having a number of small utilities that can be chained together.

=Database=
The database tool will allow all the database manipulation one would expect. Any command that alters the schema is saved to version control and can be added to a publish (or discarded).

=Version Control=
Not quite the typically check-in check out model, a site is a branch so everything is checked out all the time. But you can 'mark' a change set so that you can roll-back to that point or view it in history.

To achieve this, I'm going to go with a really simple system. One folder contains everything. Any time a file is saved to version control it's given a unique name. A single log holds all the information and maps that unique name to what file it really is as well as change set and version.

=Publish=
Allows you to push change sets over FTP to a site. It would be nice if that site could automatically check-in the change set. Configs will exist on a stack so that the bottom most layer can edit configs for each site.