Plugins
SeedCodeHierarchy.Plugins History
Hide minor edits - Show changes to output
Changed lines 5-9 from:
However, we do include a couple of instance of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.html | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter"of tab out of the field. This is done with an auto-enter calc on the field Hierarchy::FilterGlob
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "GoCorrect Tab" as soon as a the example three layout is drawn. This isn't really necessary since most times you'll be using the "Example Three" button at the top of the screen to arrive here, but using the plugin is nice when you may be arriving at the layout some other, non-scripted way. In this case the plugin is called through conditionally formatted orange text at the bottom of the example tab.
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter"
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "Go
to:
However, we do include a couple of instances of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.html | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter" or tab out of the field. This is done with an auto-enter calc on the field Hierarchy::FilterGlob and again, is not required.
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "Go to Correct Tab" as soon as a the example three layout is drawn. This isn't really necessary since most times you'll be using the "Example Three" button at the top of the screen to arrive here, but using the plugin is nice in case you may be arriving at the layout some other, non-scripted way. In this case the plugin is called through conditionally formatted orange text at the bottom of the example tab.
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter" or tab out of the field. This is done with an auto-enter calc on the field Hierarchy::FilterGlob and again, is not required.
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "Go to Correct Tab" as soon as a the example three layout is drawn. This isn't really necessary since most times you'll be using the "Example Three" button at the top of the screen to arrive here, but using the plugin is nice in case you may be arriving at the layout some other, non-scripted way. In this case the plugin is called through conditionally formatted orange text at the bottom of the example tab.
Changed lines 3-4 from:
to:
The hierarchy does not require any plugins and is drawn using all native FileMaker techniques.
Changed lines 5-6 from:
However, we do include a couple of instance of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.htm | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
to:
However, we do include a couple of instance of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.html | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
Added lines 1-9:
!! Does SeedCode Hierarchy Require any Plugins?
No. The hierarchy is drawn using all native FileMaker techniques.
However, we do include a couple of instance of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.htm | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter" of tab out of the field. This is done with an auto-enter calc on the field Hierarchy::FilterGlob
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "Go to Correct Tab" as soon as a the example three layout is drawn. This isn't really necessary since most times you'll be using the "Example Three" button at the top of the screen to arrive here, but using the plugin is nice when you may be arriving at the layout some other, non-scripted way. In this case the plugin is called through conditionally formatted orange text at the bottom of the example tab.
No. The hierarchy is drawn using all native FileMaker techniques.
However, we do include a couple of instance of [[http://homepage.mac.com/jkornhaus/filemaker/plugins.htm | zippScript]] code for people who have this free plugin. This plugin isn't required but it makes a couple of areas of the hierarchy a little more smooth...
1. When you type some contents into the filter field on [[UsingExampleTwo | Example Two]], the zippScript plugin will run the "Filter Hierarchy" script automatically when you press "enter" of tab out of the field. This is done with an auto-enter calc on the field Hierarchy::FilterGlob
2. The tabs in [[UsingExampleThree | Example Three]] use zippScript to automatically call the script "Go to Correct Tab" as soon as a the example three layout is drawn. This isn't really necessary since most times you'll be using the "Example Three" button at the top of the screen to arrive here, but using the plugin is nice when you may be arriving at the layout some other, non-scripted way. In this case the plugin is called through conditionally formatted orange text at the bottom of the example tab.
