Future

Future

Back to Snip <-- Previous Change | Next Change -->

	2008-04-19 23:44:59 by Herbert Poul			2008-04-19 23:45:26 by Herbert Poul
	6			6
	7			7
	8			8
	9	# Framework		9	# Framework
	10			10
t	11	I have always tried to keep things as generic as p	t	11	I have always tried to keep things as generic as p
	>	ossible - this made the [Community] application (i		>	ossible - this made the [Community] application (i
	>	n my opinion) to a good toolbox for developing dja		>	n my opinion) a good toolbox for developing django
	>	ngo applications.		>	applications.
	12			12
	13	## Block framework		13	## Block framework
	14			14
	15	The "Block framework" (i am really bad at naming t		15	The "Block framework" (i am really bad at naming t
	>	hings) could be described as very, very light weig		>	hings) could be described as very, very light weig
	>	ht version of "portlets" - basically they are pyth		>	ht version of "portlets" - basically they are pyth
	>	on classes which can be dynamically added to a sit		>	on classes which can be dynamically added to a sit
	>	e and will be called to render their content whene		>	e and will be called to render their content whene
	>	ver necessary. They are meant to replace things li		>	ver necessary. They are meant to replace things li
	>	ke navigation, user box, ads, etc. which are curre		>	ke navigation, user box, ads, etc. which are curre
	>	ntly in a sites base template. - This would make s		>	ntly in a sites base template. - This would make s
	>	ite templates much more generic.		>	ite templates much more generic.
	16			16

Sphene Community Tools