Thanks, those are all good points, but my simple answer would be then why use a technology "ajax" that doesn't meet 99% of web app/sites needs - being indexed by google is considered mandatary. I understand tersus is mostly apps but what if I were to use it for a blog, content management, a web site dare I say. Would GM allow all their web pages to not be indexed by Google ? Who do you think would be fired first? Now I understand this ajax might be the underlying way so it is hard to remove how tersus does things but ajax is simply a call to the server so that the client doesnt have to reload, to theoretically save time by the user. That is okay and having web services on the server called by the client is okay, but every 'page' which may or may not be considered a 'view' by tersus I beleive ought to have it wons unique URL (unique resource locator) that initially loads the page actions within that page can use ajax. But the inital load should not. I think sometimes the option to make a view have URL would be nice versus a client calling the server to load the html.
So basically every app's top level element should have a URL and sub elements the option to such as forums entries and blog entries should they be on the same page or have a permalink the spiders can index or both?
Also I can't get over the fact that it is so unintuitive to modify the html design of a default tersus page, modify its data source, deploy it to a tomcat server and create a simple table insert and display. I know the tutorials do it all for you, But I would like to do it myself being an SSE at a fortune 100 in the USA I think it should be intuitive to do so. At this point it seems quicker to code by hand or else spend a lot of time really understanding how to do the most basic things in tersus.
Regards and thanks for the reply.
For best results, use the Firefox browser..