GhostMVC - Revision history

Adamcolton at 12:27, 30 May 2013

2013-05-30T12:27:20Z

← Older revision		Revision as of 12:27, 30 May 2013
Line 2:		Line 2:

	==Core==		==Core==
			Should be able to call functions like Post or PostArgs more than once (though args should only be called once).

	Use a profiler on some basic pages to see what takes the most time. Any improvements to the core could be substantial.		Use a profiler on some basic pages to see what takes the most time. Any improvements to the core could be substantial.

Adamcolton: /* Utilities */

2013-05-14T19:55:17Z

Utilities

← Older revision		Revision as of 19:55, 14 May 2013
Line 58:		Line 58:

	==Utilities==		==Utilities==
			I need to think about how these should be installed. I can do a web installer from the admin panel easily - and that's what most people will probably use, but there needs to be a more fundamental way. Where do the files go, how does that work?

	===Edit===		===Edit===

Adamcolton: /* V 2.0 */

2013-05-09T13:28:26Z

V 2.0

← Older revision		Revision as of 13:28, 9 May 2013
Line 22:		Line 22:

	=== V 2.0 ===		=== V 2.0 ===
	Move hooks and config into directories. Anything in the root will be included. Functions in the "before" and "after" sub-directories. This makes it easier for people to write plug-ins as opposed to libraries because you don't have to modify the hooks or config file, you just drop a new file in the folders.		Move hooks and config into directories. Anything in the root will be included. Functions in the "before" and "after" sub-directories. This makes it easier for people to write plug-ins as opposed to libraries because you don't have to modify the hooks or config file, you just drop a new file in the folders. I would like to take Ghost in a bit of a Wordpress direction - couple the framework with some default application (basic site operations) so that users can manage a site. The core framework will remain simple and very pure (separate from the default application). This creates a continuum for users from basic experience to highly advanced.

	I would like to find a way to change the conditional routing so that it doesn't build up a massive array but does a lazy process. To accomplish this, I need someway to exit the sequence when I've found a match.		I would like to find a way to change the conditional routing so that it doesn't build up a massive array but does a lazy process. To accomplish this, I need someway to exit the sequence when I've found a match.

Adamcolton: /* = V 2.0 */

2013-05-09T13:18:20Z

= V 2.0

← Older revision		Revision as of 13:18, 9 May 2013
Line 21:		Line 21:
	Create a redirect at the same level as view		Create a redirect at the same level as view

	=== V 2.0 ==		=== V 2.0 ===
	Move hooks and config into directories. Anything in the root will be included. Functions in the "before" and "after" sub-directories. This makes it easier for people to write plug-ins as opposed to libraries because you don't have to modify the hooks or config file, you just drop a new file in the folders.		Move hooks and config into directories. Anything in the root will be included. Functions in the "before" and "after" sub-directories. This makes it easier for people to write plug-ins as opposed to libraries because you don't have to modify the hooks or config file, you just drop a new file in the folders.

Adamcolton at 13:14, 9 May 2013

2013-05-09T13:14:27Z

← Older revision		Revision as of 13:14, 9 May 2013
Line 20:		Line 20:

	Create a redirect at the same level as view		Create a redirect at the same level as view

			=== V 2.0 ==
			Move hooks and config into directories. Anything in the root will be included. Functions in the "before" and "after" sub-directories. This makes it easier for people to write plug-ins as opposed to libraries because you don't have to modify the hooks or config file, you just drop a new file in the folders.

			I would like to find a way to change the conditional routing so that it doesn't build up a massive array but does a lazy process. To accomplish this, I need someway to exit the sequence when I've found a match.

	==Libraries==		==Libraries==
	Look into memcache, output buffering		Look into memcache, output buffering

	===Database===		===Database===
	*Finish 'having' functions in database library		*Finish 'having' functions in database library

Adamcolton: /* User Model */

2013-04-29T17:52:46Z

User Model

← Older revision		Revision as of 17:52, 29 April 2013
Line 85:		Line 85:

	Properties		Properties
	*email		* email
	*name		* name
	*passhash		* passhash
	*salt		* salt
	*hash algorithm		* hash algorithm
	*id		* id

	Methods		Methods
Line 102:		Line 102:
	*errorArr sendResetPassword(email)		*errorArr sendResetPassword(email)
	*errorArr User::ConfirmResetPassword(hash)		*errorArr User::ConfirmResetPassword(hash)

			There will also be tbl_permission and link_user_permission. This allows extensible, atomic permissions.

	==Module Names==		==Module Names==

Adamcolton at 15:24, 2 October 2012

2012-10-02T15:24:36Z

← Older revision		Revision as of 15:24, 2 October 2012
Line 79:		Line 79:

	==Installer==		==Installer==
	~~This needs~~ to ~~be updated~~ and I ~~really need to give some more thought to~~ the ~~user module~~. ~~Also~~, ~~might be nice to include some other modules (though~~ I ~~don~~'~~t know what)~~.		I seem to have lost this project. I should rebuild it and get it out and GitHub. Have that serve as the base template for GhostMVC. I saw a framework a while ago that set up all the base files you want - robots.txt, favicon, css and so forth. I'd really like to get that setup.

	===User Model===		===User Model===

Adamcolton: /* Installer */

2012-07-27T12:52:00Z

Installer

@@ Line 80: / Line 80: @@
 ==Installer==
 This needs to be updated and I really need to give some more thought to the user module. Also, might be nice to include some other modules (though I don't know what).
 ==Module Names==

Adamcolton: /* Layout */

2012-07-27T12:37:52Z

Layout

← Older revision		Revision as of 12:37, 27 July 2012
Line 46:		Line 46:
	Need to finish (and touch up) the html class.		Need to finish (and touch up) the html class.

	~~Resolve in views how~~ to display many one-to-many relationships (or deeper). Some sort of nest array thing might work; instead of passing in a view, pass in an array of view, but then I need some way to package the data so that it's still usable. It should also map easily to the database utility.		Allow user to set headers and return codes.

	===Validation===		===Validation===

Adamcolton at 12:36, 27 July 2012

2012-07-27T12:36:46Z

← Older revision		Revision as of 12:36, 27 July 2012
Line 1:		Line 1:
	[[GhostMVC IDE]]		[[GhostMVC IDE]]

	=Core=		==Core==
	Use a profiler on some basic pages to see what takes the most time. Any improvements to the core could be substantial.		Use a profiler on some basic pages to see what takes the most time. Any improvements to the core could be substantial.

Line 21:		Line 21:
	Create a redirect at the same level as view		Create a redirect at the same level as view

	=Libraries=		==Libraries==
	Look into memcache, output buffering		Look into memcache, output buffering
	==Database==		===Database===
	*Finish 'having' functions in database library		*Finish 'having' functions in database library
	*Update database library to throw useful errors		*Update database library to throw useful errors
Line 37:		Line 37:
	(this requires the the library hook in core) Have the constants defined with tails so that MYSQL_HOST becomes MYSQL_HOST_DEFAULT allow a range such as MYSQL_HOST_QUIZ, MYSQL_HOST_JOURNAL (using Moon-Jumper as an example). User the constant function (http://dk.php.net/manual/en/function.constant.php) to dynamically access them. Store each connection persistently in an array indexed by host and user, then close all the connections when the request finishes (or allow the user to manually close the connections early).		(this requires the the library hook in core) Have the constants defined with tails so that MYSQL_HOST becomes MYSQL_HOST_DEFAULT allow a range such as MYSQL_HOST_QUIZ, MYSQL_HOST_JOURNAL (using Moon-Jumper as an example). User the constant function (http://dk.php.net/manual/en/function.constant.php) to dynamically access them. Store each connection persistently in an array indexed by host and user, then close all the connections when the request finishes (or allow the user to manually close the connections early).

	===Parameterized SQL===		====Parameterized SQL====
	Use PDO. Seems simple enough, put ? where user data goes then bind data to position. The important (and tricky) part is keeping the data in order so that it will line up with the correct position.		Use PDO. Seems simple enough, put ? where user data goes then bind data to position. The important (and tricky) part is keeping the data in order so that it will line up with the correct position.
	http://net.tutsplus.com/tutorials/php/why-you-should-be-using-phps-pdo-for-database-access/		http://net.tutsplus.com/tutorials/php/why-you-should-be-using-phps-pdo-for-database-access/
Line 43:		Line 43:
	http://projects.adamcolton.net/pdo/		http://projects.adamcolton.net/pdo/

	==Layout==		===Layout===
	Need to finish (and touch up) the html class.		Need to finish (and touch up) the html class.

	Resolve in views how to display many one-to-many relationships (or deeper). Some sort of nest array thing might work; instead of passing in a view, pass in an array of view, but then I need some way to package the data so that it's still usable. It should also map easily to the database utility.		Resolve in views how to display many one-to-many relationships (or deeper). Some sort of nest array thing might work; instead of passing in a view, pass in an array of view, but then I need some way to package the data so that it's still usable. It should also map easily to the database utility.

	==Validation==		===Validation===
	Add phone numbers, sql-scrubbing... Look up common regex patterns and add those in. Some sort of a mass form validator would be nice, with the ability to pass back an array of errors.		Add phone numbers, sql-scrubbing... Look up common regex patterns and add those in. Some sort of a mass form validator would be nice, with the ability to pass back an array of errors.

	=Utilities=		==Utilities==

	==Edit==		===Edit===
	Add 'New' buttons to model, view, controller and resources in Edit utility.		Add 'New' buttons to model, view, controller and resources in Edit utility.

	Move this into a more IDE like environment with the files in an UL on the left and the editor being tabbed (possibly split-able).		Move this into a more IDE like environment with the files in an UL on the left and the editor being tabbed (possibly split-able).

	==Test Framework==		===Test Framework===
	Good base class, need to rename a lot of the methods to follow the camel casing that I choose. I also want to finish turning this into a real test interface where I can run a subset of tests.		Good base class, need to rename a lot of the methods to follow the camel casing that I choose. I also want to finish turning this into a real test interface where I can run a subset of tests.

	For a first step, I would like to detect anytime a model or test is updated (by last modified date) and automatically re-run the tests when it changes. This way, every time I upload code, the unit tests will be run automatically. This could be very cool because I could set up the page on another computer or a tablet and it will provide feedback while I work.		For a first step, I would like to detect anytime a model or test is updated (by last modified date) and automatically re-run the tests when it changes. This way, every time I upload code, the unit tests will be run automatically. This could be very cool because I could set up the page on another computer or a tablet and it will provide feedback while I work.

	==Form Utility==		===Form Utility===
	Form builder utility. Select the controller, name the form (used as function name, view name and form id), add inputs and select their type. The utility automatically stubs out the view, both controller methods (name and _name) and the submit hook so that the post variables are passed as arguments.		Form builder utility. Select the controller, name the form (used as function name, view name and form id), add inputs and select their type. The utility automatically stubs out the view, both controller methods (name and _name) and the submit hook so that the post variables are passed as arguments.

	==Publish Utility==		===Publish Utility===
	Use FTP to publish to another destination. Needs a process for 'popping' configs off a stack. Allow user to show all files, different by date, different by size and both. Use this (http://scrivna.com/blog/php-file-diff) to show the file differences.		Use FTP to publish to another destination. Needs a process for 'popping' configs off a stack. Allow user to show all files, different by date, different by size and both. Use this (http://scrivna.com/blog/php-file-diff) to show the file differences.

	==Database==		===Database===
	Add modify table to database utility		Add modify table to database utility

Line 78:		Line 78:
	For debugging, create a logging option that will store all queries in a log.		For debugging, create a logging option that will store all queries in a log.

	=Installer=		==Installer==
	This needs to be updated and I really need to give some more thought to the user module. Also, might be nice to include some other modules (though I don't know what).		This needs to be updated and I really need to give some more thought to the user module. Also, might be nice to include some other modules (though I don't know what).

	=Module Names=		==Module Names==
	One principle I like is to give things gibberish or unrelated names rather than meaningful but generic names (think about Access, it makes searching and naming difficult). For that reason I want to pull in names of ghosts and ghost-like things to name them.		One principle I like is to give things gibberish or unrelated names rather than meaningful but generic names (think about Access, it makes searching and naming difficult). For that reason I want to pull in names of ghosts and ghost-like things to name them.
	*Test Framework - Osiris (Egyptian god that tests spirits for the afterlife)		*Test Framework - Osiris (Egyptian god that tests spirits for the afterlife)