Le 01/08/2003 07:22, [EMAIL PROTECTED] a �crit :Just my comments from using Composer since Netscape Gold...
Just wondering what the actual goal is of composer? I mean, in terms of composer being a good dev-environment, it's horrible. TopStyle is currently my favored dev tool- the way they deal with css and properties is just amazing.
Anyway....i guess what im really wondering is whether or not composer will begin to resemble TopStyle, or if it's gonna stay a relatively weak tool meant for creating simnple pages really easily. im not bashing it or anything. im just trying to understand what it's trying to be.
best, -john
Daniel is busy improving the program, he also has an extension to composer called CaScadeS which is a CSS editor and is going to turn the product into a standalone software. In the last months he added absolute positionning support, table and image resizing and fixed many bugs. You should check his weblog, it is currently the best source of information on the evolution of Composer :
http://daniel.glazman.free.fr/weblog/
Pascal
PS : I totally agree with you about topstyle, it is a great tool
Most Web Servers no longer support HTTP PUT/GET which forces the user to use FTP (passive) to transfer files to/from the server. The FTP interface is horrible at best... Composer developers should look at Dreamweaver's FTP interface and use something very close to it. Better yet, Convince the major Unix/Liunix Web Server vendors to go back to supporting HTTP PUT/GET which allows one to simply go to the page, edit page, make changes, etc. publish page not have to set up relative path info for each page.. Composer know where the page came from and knows where to put it back..
Just my comments..
