Windows/Foundation - Revision history

Dave at 07:40, 5 April 2012

2012-04-05T07:40:08Z

← Older revision		Revision as of 07:40, 5 April 2012
Line 1:		Line 1:
	Durations: The FIRST number represent my original guesstimate of how many 5 hour days it would take to implement the feature. The second represents how long it actually took. a ? means i never estimated it		Durations: The FIRST number represent my original guesstimate of how many 5 hour days it would take to implement the feature. The second represents how long it actually took. a ? means i never estimated it

	* September 2008		==September 2008==
	* ?-22 CoreFoundation: Hired this one out. This became the OpenCFLite project. the mac version heavily relied on CF for everything, so re-writing that was more expensive than porting CoreFoundation (CFLite)		* ?-22 CoreFoundation: Hired this one out. This became the OpenCFLite project. the mac version heavily relied on CF for everything, so re-writing that was more expensive than porting CoreFoundation (CFLite)
	* ?-10 DataBrowser: test code project: reverse-engineered the mac API, wrote a compatible system for windows. Now i can plug in my existing mac data browser code and it will call native windows GUI controls, with drag and drop, editing etc, tree view & table view.		* ?-10 DataBrowser: test code project: reverse-engineered the mac API, wrote a compatible system for windows. Now i can plug in my existing mac data browser code and it will call native windows GUI controls, with drag and drop, editing etc, tree view & table view.
	* January 2009		==January 2009==
	* 5-4 My CoreFoundation: Take the CF project and shoehorn it into my app code.		* 5-4 My CoreFoundation: Take the CF project and shoehorn it into my app code.
	* ?-3 SuperString: my string package, capable of translating TO any language, and encoding TO and FROM any encoding (7-bit, multibyte, MacRoman, WindowsLatin1 etc)		* ?-3 SuperString: my string package, capable of translating TO any language, and encoding TO and FROM any encoding (7-bit, multibyte, MacRoman, WindowsLatin1 etc)
Line 23:		Line 23:
	* 2-10 Dialogs: lots of plat code		* 2-10 Dialogs: lots of plat code
	* 2-3 Rez: whatever resources are left		* 2-3 Rez: whatever resources are left
	* Jan 2010		==Jan 2010==
			* first announcement

Dave at 07:39, 5 April 2012

2012-04-05T07:39:35Z

← Older revision		Revision as of 07:39, 5 April 2012
Line 1:		Line 1:
	~~asdf~~		Durations: The FIRST number represent my original guesstimate of how many 5 hour days it would take to implement the feature. The second represents how long it actually took. a ? means i never estimated it

			* September 2008
			* ?-22 CoreFoundation: Hired this one out. This became the OpenCFLite project. the mac version heavily relied on CF for everything, so re-writing that was more expensive than porting CoreFoundation (CFLite)
			* ?-10 DataBrowser: test code project: reverse-engineered the mac API, wrote a compatible system for windows. Now i can plug in my existing mac data browser code and it will call native windows GUI controls, with drag and drop, editing etc, tree view & table view.
			* January 2009
			* 5-4 My CoreFoundation: Take the CF project and shoehorn it into my app code.
			* ?-3 SuperString: my string package, capable of translating TO any language, and encoding TO and FROM any encoding (7-bit, multibyte, MacRoman, WindowsLatin1 etc)
			* 1-5 DataBrowser: Shoehorn test code into my app code
			* 1-1 Exceptions: cross platform throw/catch for error handling
			* 2-6 Menus: cross platform method of menu handling
			* 3-5 Controls: for dialogs
			* 5-10 Languages: get ready for any language
			* 5-7 Bundle: make sure CF properly locates / recognizes Bundle structure even on windows
			* 3-1 Resources: did bundle first, got most of this for free.
			* 6-4 CoreGraphics: haven't really done a unified approach, this is the least cross-platform code in the app
			* 1-5 CFileRef: managing files/aliases/paths/folders
			* 6-20 CNetworkHTTP: could not use x-plat code cuz CFNetwork is not part of CFLite (yet: see 2011)
			* 4-1 CMeta: my meta data system, was easy to integrate, no plat dependent code
			* 7-10 Disc ripping: OMG i did not expect it would be so difficult, but i figured it out
			* 7-60 Disc Burning: yes this took 4 months, not 1 week
			* 4-1 CSongDatabase: no plat code, easy
			* 2-10 Dialogs: lots of plat code
			* 2-3 Rez: whatever resources are left
			* Jan 2010

Dave: Created page with "asdf"

2012-04-05T07:07:11Z

Created page with "asdf"

New page

asdf