So far I have been really impressed with XWD.
The biggest drawback for me is the publish all pages issue.
I am delighted to hear this is on the wish list.
The program I started my web experience with was Trellix. Like XWD, the WYSIWYG program used a compressed file format and would convert the HTML during the publishing process, then connect to the FTP destination assigned. Then the program produced a simple txt file at the end of publishing process. Generally speaking, a txt file was simply a list of all page/file names within that design file along with a date/time change coding for each. At the beginning of the next publish procedure, the content of that file was compared to the content of the edited file and since only one or two pages changed, only those pages were uploaded and the txt file was overwritten with the latest information. Simple and added only a couple seconds to the process. Could something like that be used by XWD?
This is a sample of what our old txt would looked like for reference.
"index.htm",35283,-1628222506
"id3.htm",9499,626357139
"HTMLobj-1567/reps1107-600x234.jpg",36574,518489714
"id7.htm",42762,-1366632116
"thanks.htm",4823,-2094612716
"kkorder.php",84858,-1460477786
"thanksorder.htm",5238,-227848959
"4e50a0b0.gif",861,409007795
"7fc090a0.png",1170,934130568
"7e1090a0.gif",854,-1481313950
Bookmarks