<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: 5 Ways to Automate Development in FoxPro</title>
	<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/</link>
	<description>Business Intelligence, Data Warehousing, SQL, Visual FoxPro.</description>
	<pubDate>Fri, 21 Nov 2008 00:35:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Frank Dietrich</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-1215</link>
		<author>Frank Dietrich</author>
		<pubDate>Sun, 16 Mar 2008 14:38:14 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-1215</guid>
		<description>Tod, 

if You remember CEE from the old old Fox2.6 days, have a look at my CEEClone for VFP7+, available at the UniversalThread. It is integrated into intellisense and gives You all the editor enhancements we had in earlier times and much more. Did it ages ago by now and could not live without it anymore. 
Every time I do some .NET development, I go knuts and think I *must* do this for .NET as well</description>
		<content:encoded><![CDATA[<p>Tod, </p>
<p>if You remember CEE from the old old Fox2.6 days, have a look at my CEEClone for VFP7+, available at the UniversalThread. It is integrated into intellisense and gives You all the editor enhancements we had in earlier times and much more. Did it ages ago by now and could not live without it anymore.<br />
Every time I do some .NET development, I go knuts and think I *must* do this for .NET as well</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tod McKenna</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-83</link>
		<author>Tod McKenna</author>
		<pubDate>Fri, 07 Sep 2007 00:35:31 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-83</guid>
		<description>That sounds pretty interesting. I can't wait to see Brian's presentation at Fox Forward. I'm in Atlanta now and gearing up!</description>
		<content:encoded><![CDATA[<p>That sounds pretty interesting. I can&#8217;t wait to see Brian&#8217;s presentation at Fox Forward. I&#8217;m in Atlanta now and gearing up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Marquis</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-81</link>
		<author>Brian Marquis</author>
		<pubDate>Thu, 06 Sep 2007 14:57:49 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-81</guid>
		<description>I've gotten some feedback about a member of the Chicago Foxpro User Group, Tom Corrigan, who is using Fox Trails as a code generator, instead of generating html. As I recall, he was using it to create C# classes.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve gotten some feedback about a member of the Chicago Foxpro User Group, Tom Corrigan, who is using Fox Trails as a code generator, instead of generating html. As I recall, he was using it to create C# classes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tod McKenna</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-77</link>
		<author>Tod McKenna</author>
		<pubDate>Fri, 17 Aug 2007 03:04:50 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-77</guid>
		<description>What a great tip!</description>
		<content:encoded><![CDATA[<p>What a great tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wOOdy</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-76</link>
		<author>wOOdy</author>
		<pubDate>Thu, 16 Aug 2007 18:56:09 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-76</guid>
		<description>Hi Tod,

another speed-up for using macros:  Put in your config.fpw:
MACKEY = Ctrl+F12

From now on, you just press Ctrl+F12 to directly launch the Macro-recorder. In earlier Foxpro-versions, that hotkey was Shift+F10, but then MS Windows assigned that one as the keyboardway for the Shortcut-Menues.  That's why we got SET MACKEY to assign our own hotkey.

Greetings from good ol' Germany!</description>
		<content:encoded><![CDATA[<p>Hi Tod,</p>
<p>another speed-up for using macros:  Put in your config.fpw:<br />
MACKEY = Ctrl+F12</p>
<p>From now on, you just press Ctrl+F12 to directly launch the Macro-recorder. In earlier Foxpro-versions, that hotkey was Shift+F10, but then MS Windows assigned that one as the keyboardway for the Shortcut-Menues.  That&#8217;s why we got SET MACKEY to assign our own hotkey.</p>
<p>Greetings from good ol&#8217; Germany!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhonda Tipton&#8217;s WebLog Links - 08.05.07 &#171;</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-58</link>
		<author>Rhonda Tipton&#8217;s WebLog Links - 08.05.07 &#171;</author>
		<pubDate>Sun, 05 Aug 2007 21:01:52 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-58</guid>
		<description>[...] DevelopmentURL Validator - RegExLibEmail Validator - RegExLib5 Ways to Automate Development in FoxPro - Tod McKennaArrays vs. Linked Lists - Adam [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] DevelopmentURL Validator - RegExLibEmail Validator - RegExLib5 Ways to Automate Development in FoxPro - Tod McKennaArrays vs. Linked Lists - Adam [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tod McKenna</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-53</link>
		<author>Tod McKenna</author>
		<pubDate>Tue, 31 Jul 2007 13:28:07 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-53</guid>
		<description>Wow Mike! Great tip. Somehow I missed that in VFP8. Most of my projects went from VFP7 to VFP9 -- so I admit to being a little fuzzy on the some of the cool things introduced in version 8. Some other cool little tidbits include (from VFP8's new feature listing):

# Typing WS in a program (.prg) file opens the Select dialog box for choosing a registered XML Web service. XML Web services are no longer added in code using a type, for example, LOCAL oWS AS myWebService.

# Typing ZLOC in a .prg file displays a list of available local memory variables and parameters.

The complete lists IntelliSense scripts is located in FoxCode.dbf.</description>
		<content:encoded><![CDATA[<p>Wow Mike! Great tip. Somehow I missed that in VFP8. Most of my projects went from VFP7 to VFP9 &#8212; so I admit to being a little fuzzy on the some of the cool things introduced in version 8. Some other cool little tidbits include (from VFP8&#8217;s new feature listing):</p>
<p># Typing WS in a program (.prg) file opens the Select dialog box for choosing a registered XML Web service. XML Web services are no longer added in code using a type, for example, LOCAL oWS AS myWebService.</p>
<p># Typing ZLOC in a .prg file displays a list of available local memory variables and parameters.</p>
<p>The complete lists IntelliSense scripts is located in FoxCode.dbf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Potjer</title>
		<link>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-52</link>
		<author>Mike Potjer</author>
		<pubDate>Mon, 30 Jul 2007 18:26:38 +0000</pubDate>
		<guid>http://blog.todmeansfox.com/2007/07/30/5-ways-to-automate-development-in-foxpro/#comment-52</guid>
		<description>Hi Tod,

Under IntelliSense, you mention adding custom IntelliSense records for common DEFINEs.  Are you aware of the "zdef" IntelliSense script which ships with VFP?  First, you have to make sure that you have the lAllowCustomDefScripts custom property set to .T. in the IntelliSense Manager.  Then type "zdef" (without the quotes) followed by a space, and the script presents a list of all the DEFINEs for the current program or method, including those contained in INCLUDE files.  The tooltip for each item displays the value of the constant.  Very handy!</description>
		<content:encoded><![CDATA[<p>Hi Tod,</p>
<p>Under IntelliSense, you mention adding custom IntelliSense records for common DEFINEs.  Are you aware of the &#8220;zdef&#8221; IntelliSense script which ships with VFP?  First, you have to make sure that you have the lAllowCustomDefScripts custom property set to .T. in the IntelliSense Manager.  Then type &#8220;zdef&#8221; (without the quotes) followed by a space, and the script presents a list of all the DEFINEs for the current program or method, including those contained in INCLUDE files.  The tooltip for each item displays the value of the constant.  Very handy!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
