| T O P I C R E V I E W |
| K. Miller |
Posted - 26 Dec 2003 : 00:10:56
As great as the Dynamic HTML Editor interface is, its proprietary file storage system means only a limited number of people can consider using it.
It's not an ideal program for beginners, because it requires a fair knowledge of web page structure to understand and use it well. As the documentation improves, this door should open wider.
Unfortunately it's not an ideal program for experienced users either, because it's a "closed" system. It won't open their existing web pages so they can't convert existing sites, and they won't want to rebuild them from scratch. They won't use it for new sites either, because the Dynamic HTML Editor features aren't complete enough (yet) for most. Dynamic HTML Editor's current ability to import HTML segments is very useful, but as they're not truly integrated, it doesn't really solve the problem.
So the best use for Dynamic HTML Editor is either for creating and maintaining relatively simple sites; or used only for developing original site designs, and then use other editors to do all future maintenance. But I'm sure you'd like to see it used as a one-stop web solution; and it would be a shame if it couldn't.
To correct this, ideally Dynamic HTML Editor would store its work files as generic HTML files. I can see many reasons you wouldn't want to do this, such as losing the multiple output file-types and the ability to switch objects between text and graphics states. Generic HTML storage would also force you to imbed much of the code you now allow export of, such as CSS and Javascript, with export a much better practice. Possibly a combination of .htm and .dhe files could constitute a "normal" save with all necessary information, but I can see this approach could become very complex and unreliable.
As a second choice then, Dynamic HTML Editor should at least gain a true HTML import feature. It could then open an existing HTML file and convert it to the Dynamic HTML Editor WYSIWYG display, and allow save-as into a .dhe file. This would be a huge advantage, opening the use of Dynamic HTML Editor to many more users, and making it a much more valuable and even primary tool.
I do hope you give this file storage matter serious consideration. Programs built around proprietary standards almost always fail. Dynamic HTML Editor has some wonderful aspects, and it would be satisfying to see it realize its potentials, but it needs to become an "open" web-builder to achieve this. Good luck.
Karl |
| 1 L A T E S T R E P L I E S (Newest First) |
| s.dav |
Posted - 26 Dec 2003 : 10:38:38
As you've said the only choice for me is to implement a true HTML import feature but this is a very very hard work; Dynamic HTML Editor cannot manage a lot of HTML elements such tables, relative positioning (present in 90% of sites), all CSS styles, etc...
Maybe I'll try to import elements and limit the resulting page. |
|
|
