Thanks everyone for the very useful insight. I think my original
question was answered -- or at least I have a different way to look at
things now! I'm sure I'll be back for more questions soon.
On 3/29/07, Chuck Hill <email@hidden> wrote:
> I think the problem is how to detach the programmer from the web
> designer. So if the web designer adds a new page that utilitizes
> existing WO components, that a new WO component to represent the new
> page itself doesn't have to be created by a programmer. But I guess
> that's where the SSI (or similar) solution might work.
I think the problem might be your perception of WO. WO is meant to
build web _applications_ not web _sites_. Generally, the web
designer does not just decide to add a page. A page gets added, and
linked to other pages, because there is a business need. Often that
requires code changes, yes. If you are just building a site, then
what you want is to use WO to build a CMS application like Guido
described. See http://www.gvcsitemaker.com for another example).
The designer is then just a user of the WO application.
On 3/29/07, David Avendasora <email@hidden> wrote:
This is one of the key distinctions between WO and a lot of other
frameworks or web-technologies out there. A WO application can have
any kind of a front-end. A website is just one of them (certainly the
most common). You can have a Swing front end, or something along the
lines of iTunes.
You should approach the creation of a WO application from the C++/
Java/C#/etc. application-development perspective, not the web-
development perspective. How do you think developers of Photoshop or
Excel handle UI design? How is THAT design integrated in the
development process?
