| T O P I C R E V I E W |
| herodes |
Posted - 29 Jul 2004 : 14:14:55
Would it be possible to create cleaner code with Dynamic HTML Editor ?
I found out that it needs tons of work to make a exported file "validated" by the w3c validator ...
I wish this really useful app was able to do that...
--- I just read another post on that issue .. I got the responses from there too... ty
1 more think ... I tried to do a translation in Greek but it wont do it ... the menus, palletes and all is going character crazy. Can u Make the code accept other encoding as well apart from the latin characters ? |
| 6 L A T E S T R E P L I E S (Newest First) |
| herodes |
Posted - 11 Aug 2004 : 20:54:47
quote:
Originally posted by s.dav
For the fisrt question:
quote:
<font class='verdana80FFFFFFt'><br><br>- </font><font class='verdana80FFFFFFt'><a href="#introduzione" class='verdana80FFFFFFt'>Introduction</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#strumenti" class='verdana80FFFFFFt'>The Toolbar</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#barraalto" class='verdana80FFFFFFt'>Upper Bar<br></a></font>
I can say you that Dynamic HTML Editor v.2.0 already creates a clean code like yours but it uses the tag FONT instead of tag SPAN for retro compatibily with Netscape 4.x.
Maybe we would be able to choose what of the two ( span/font) tags we want DHEditor to generate ?
quote:
quote:
Also one more thing is the special characters. Where the text contains characters that
are used in HTML syntax, such as <, >, &, or " it is prefered to use the proper HTML notation
for special characters, such as "<", ">", "&", """ ...
I think that a label is a label so all you write in a label tool have to be viewed in the page so some special characters are translated.
You can use the HTML tool instead if you want to write HTML tag.
Maybe I can think a method to permit a user to insert HTML tag into a label tool so you can create a label with dome pictures into.
I actually was taklking about " = &.q.u.o.t.; and,& = &.a.m.p.;(I put in the .'s because they would display as characters and not code) Html characters ... that are universally available and not depended on the fontface one uses .. :)
quote:
quote:
Also it would be nice to have a choice on how the css styles are named so that it would be possible
for someone to have instead of 'verdana80FFFFFFt' something like 'normaltext'
Why? It's automatic and the classes are uniques!
In the next version you can create custom classes and assign them to input controls or label text (for label, only for the a:hover property), but the classes are always generated.
Ok no more arguing about that it is quite clear :)quote:
quote:
Furthermore, I noticed that the editor generates different css styles for underlined text, bold text, and italic text.
There are tags that can be used for this. <b></b> for bold; <i></i> for italics; <u></u> for underline;
I suppose that could be fixed too. I am talking on text not the links.
I already know these tags but with tags I can'y says "don't underline a link" for example.
My choice is to use always class styles.
Maybe in future I can create an option "generate tags instead style class".
but I was talking about the text not the links ... they should be having a style class of their own :) Although the text could benefit from having those tags because it wouldnt need the continuous <font class='verdana80FFFFFFt'>blah blah blah blah </font><font class='verdana80FFFFFFtu'>blahblahbalh</font><font class='verdana80FFFFFFt'> blah blah blah</font>
Thank You  |
| s.dav |
Posted - 08 Aug 2004 : 11:25:12
For the fisrt question:
quote:
<font class='verdana80FFFFFFt'><br><br>- </font><font class='verdana80FFFFFFt'><a href="#introduzione" class='verdana80FFFFFFt'>Introduction</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#strumenti" class='verdana80FFFFFFt'>The Toolbar</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#barraalto" class='verdana80FFFFFFt'>Upper Bar<br></a></font>
I can say you that Dynamic HTML Editor v.2.0 already creates a clean code like yours but it uses the tag FONT instead of tag SPAN for retro compatibily with Netscape 4.x.
quote:
Also one more thing is the special characters. Where the text contains characters that
are used in HTML syntax, such as <, >, &, or " it is prefered to use the proper HTML notation
for special characters, such as "<", ">", "&", """ ...
I think that a label is a label so all you write in a label tool have to be viewed in the page so some special characters are translated.
You can use the HTML tool instead if you want to write HTML tag.
Maybe I can think a method to permit a user to insert HTML tag into a label tool so you can create a label with dome pictures into.
quote:
Also it would be nice to have a choice on how the css styles are named so that it would be possible
for someone to have instead of 'verdana80FFFFFFt' something like 'normaltext'
Why? It's automatic and the classes are uniques!
In the next version you can create custom classes and assign them to input controls or label text (for label, only for the a:hover property), but the classes are always generated.
quote:
Furthermore, I noticed that the editor generates different css styles for underlined text, bold text, and italic text.
There are tags that can be used for this. <b></b> for bold; <i></i> for italics; <u></u> for underline;
I suppose that could be fixed too. I am talking on text not the links.
I already know these tags but with tags I can'y says "don't underline a link" for example.
My choice is to use always class styles.
Maybe in future I can create an option "generate tags instead style class".
quote:
One more last thing is the name of the 'Text Tool' it should really be something
like 'Input Field Tool' and the Label Tool should be the real 'Text Tool' as it describes what it does better.
Probably yes  |
| herodes |
Posted - 04 Aug 2004 : 17:59:19
Below you will see what I mean by "dirty code" ...
This code was taken from the English Help File found in the Dynamic HTML Editor instalation folder:
<font class='verdana80FFFFFFt'><br><br>- </font><font class='verdana80FFFFFFt'><a href="#introduzione" class='verdana80FFFFFFt'>Introduction</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#strumenti" class='verdana80FFFFFFt'>The Toolbar</a></font>
<font class='verdana80FFFFFFt'><br>- </font><font class='verdana80FFFFFFt'><a href="#barraalto" class='verdana80FFFFFFt'>Upper Bar<br></a></font>
well a clean version of this would be :
<span class='verdana80FFFFFFt'><br>
<br>- <a href="#introduzione" class='verdana80FFFFFFt'>Introduction</a>
<br>- <a href="#strumenti" class='verdana80FFFFFFt'>The Toolbar</a>
<br>- <a href="#barraalto" class='verdana80FFFFFFt'>Upper Bar<br></a>
</span>
The reason I am showing this is to justify me talking about big and messy files...
It could potentially double or triple filesize ... not very nice.
Also one more thing is the special characters. Where the text contains characters that
are used in HTML syntax, such as <, >, &, or " it is prefered to use the proper HTML notation
for special characters, such as "<", ">", "&", """ ...
Also it would be nice to have a choice on how the css styles are named so that it would be possible
for someone to have instead of 'verdana80FFFFFFt' something like 'normaltext'
Furthermore, I noticed that the editor generates different css styles for underlined text, bold text, and italic text.
There are tags that can be used for this. <b></b> for bold; <i></i> for italics; <u></u> for underline;
I suppose that could be fixed too. I am talking on text not the links.
One more last thing is the name of the 'Text Tool' it should really be something
like 'Input Field Tool' and the Label Tool should be the real 'Text Tool' as it describes what it does better.
I dont want to pretend to be unsatisfied with this because
I really love this program of yours and I dearly await the new release.
Thank you for reading :) |
| s.dav |
Posted - 30 Jul 2004 : 08:52:24
If you want you should send me a list of the problems that the W3C validator signales. Dynamic HTML Editor 2.0 will produce W3C compatible code but I have to tell you that some tags attributes that I've used (and W3C says not correct) are necessary for a correct conduct of the page. |
| herodes |
Posted - 29 Jul 2004 : 23:12:54
quote:
Originally posted by s.dav
I think Dynamic HTML Editor creates a clean code; validators I've seen don't work very well; the major problem is that this version doesn't create the encoding and the DTD header on top of HTML.
There are some small problems that I've already corrected in version 2.
I'm working for accept encoding different from latin.
I dont think that the code produced is clean ... unless u know what to use where and how... there are rubbish to take out.
as for the w3c validator for HTML 4.01 I dont think that should be neglected ...
Anyhow thanks for the nice program again, and dbl thx for putting an effort with the non-latin encoding... The whole prblem with that is just in the Properties sidetab ... no worries apart from that ...
TIP: Dbl clicking in a drop-down list in the Properties Sidetab loops through the available options in that list ... :) |
| s.dav |
Posted - 29 Jul 2004 : 15:06:56
quote:
Originally posted by herodes
Would it be possible to create cleaner code with Dynamic HTML Editor ?
I found out that it needs tons of work to make a exported file "validated" by the w3c validator ...
I wish this really useful app was able to do that...
--- I just read another post on that issue .. I got the responses from there too... ty
1 more think ... I tried to do a translation in Greek but it wont do it ... the menus, palletes and all is going character crazy. Can u Make the code accept other encoding as well apart from the latin characters ?
I think Dynamic HTML Editor creates a clean code; validators I've seen don't work very well; the major problem is that this version doesn't create the encoding and the DTD header on top of HTML.
There are some small problems that I've already corrected in version 2.
I'm working for accept encoding different from latin. |
|
|
