More efficient CSS
An area I hope will be improved in forthcoming products is better CSS implementation; currently the way styles are applied is extremely clumsy - in DataAssist for example. If CSS Form Builder is to be integrated witih DataAssist, things could get a lot worse. I tried Form Builder when it was released; when a two field login form created 1000 lines of CSS code, I knew this would not be a useful product as far as I was concerned. However DataAssist is useful, and hopefully will be better in the next release, particularly if it gets closer to ADDT.
Looking at the HTML taken from a dynamically-generated results page (created initially using DataAssist), there are 332 occurences of:
Obviously the number will vary according to the number of columns and rows, but the point is there no need for a single occurence. The same goes for class="WADAResultsTableHeader" etc..
Adding ".WADAResultsTable td" in the style sheet and removing the redundant class="WADAResultsTableHeader" would of course solve the problem.
Is there any reason for this approach (which is used throughout your CSS generation as far as I know)? Tidying up the CSS for this single page shaved 10k of the filesize. If many users page through many pages this becomes significant as far as loading times/bandiwidth is concerned, and it seems to be totally unnecessary. It also makes the pages very cluttered and difficult to work with.
I hope this can be considered in future updates. Perhaps there is some benefit to this approach (perhaps Netscape browsers work better with this type of CSS) but I find it frustrating and amateurish, and time-consuming to fix.
I understand that requests have been made for options to exclude CSS from code generation. This is a good idea but it would better if choosing styled HTML was a usable option (particularly if the styles can be defined).