🚀 go-pugleaf

      so I'm not exactly sure what the translate object is. Can you elaborate?




Look at page 162 of the SDK Programmer's Guide. I think that it what you would want to use when editing a repeating table. It is a placeholder that GoLive can manipulate in Layout. So, it would translate all of the underlying code into a table that GoLive could manipulate, all the while, what is actually being written is the code for the repeating table. When I tried to do it, I could never get my head around it, so when I tried to make a Dynamic Content extension, I had to resort to doing tags, which could then be inspected. The source translation would allow for inspector AND layout editing offering a simulation of what the dynamic content would look like.

      Our thought is that most people are developing locally, so it shouldn't
      be a problem.




Whereas I've never developed locally. Too much hassle to install and configue Apache/PHP/MySQL on a Windows box if what you will be deploying on is a LAMP box. Of course, I might be an unusual case: I'm also a system administrator, so I could easily set up the required aliases and databases and permissions to create testing servers then simply publish to the production server, if needed for making changes on a site that was in production.

If you are assuming they develop locally, then you are gonna have to provide very specific instructions on how to download, insatall and get Apache/PHP and MySQL running. If people cannot get that, they won't even try, and many will simply go 'un-uh' -- it is that geekish, coding stuff and I'm sure it will trash my machine, my site, my server, etc, etc.

If you have a site from an ISP, you have the MySQL database, the web server and PHP. Connect and start working.

If you assume people develop locally, then:

Install Apache
Install PHP
Install MySQL

...then after development, upload to a server and replicate what you did locally in MySQL on the server.

The develop locally assumption requires quite a bit of installation and configuration...while the remote should start working immediately.

As I learned, you gotta watch out for assumptions. I got NAILED on them.

 <http://users.camalott.com/~jtpolk/extensions/>

FYI: there was a giant rant on that page until recently (grimace).

The other assumption(s) you are going to have to overcome is what people think that DreamWeaver does that GoLive does not, and that is pretty large. I use GoLive CS AND DreamWeaver MX 2004 to develop new sites, and much of what I heard about dW's amazing abilities, well, was a tad off the mark. For instance, GoLive (6.0 with DC and CS for HTML) offer a tab that when you click on it Previews in the browser.

dW does not have that. I was amazed. And the rendering of the dW Dyanmic Content in Layout mode is somewhat cruder than what I was used to in GoLive 6.0.

And for forms, if you use dW, forget trying to do them in anything but tables: it cannot render fieldsets and legends in it's layout mode worth a dang...actually, not at ALL.

Good luck, and if you need a beta tester, drop me a line. I do have a local development environment (grin) of FabDesigner4, MySQL, Apache, PHP and Zend Studio.