Hi Kirk,
You really have 4 modes you can always work with. 1. You can process data in 4D code and call a method from process tag code. 2. You can process data using embedded process tag code itself 3. You can inject the data as json into the page using tags, and process it using javascript client side 4. You can request the data from the server separately using an ajax call, and process it using javascript client side You appear to be investigating how to work best with scheme #2, but that is by far the least appealing of the 4 choices. While we now have ways to work with objects in 4D, I would argue that it is always far easier to use object data with javascript, as long as you are comfortable enough working with it. When you are building a page, you have the initial load, and then you have any interactivity you may need afterward, which requires ajax. Tags only apply to the initial load of the page, so any work done that way can’t be reused for anything. That’s why tags are most useful for quick and dirty static pages. If you have a choice and you might have interactive pages, it’s always best to stick with scheme #4, because the initial load and the subsequent actions all can be done in one consistent way Tom D ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
