- This topic has 12 replies, 4 voices, and was last updated 18 years, 12 months ago by
.
-
Posts
-
Great job on 4.0!
I was, however, very disappointed to find that the nice shiny new Visual Designer uses the defunct HTML 4.01 standard. It’s dead! Now, I do realize that some people still do HTML (they should not, but…), and support for it is a nice extra if you, say, supply an HTML DOCTYPE I guess, but standards support should come first. Not only that, but it put font tags in my html(!), rather than using an included or external stylesheet.
I know you guys have a zillion requests, but ME is primnarily about distributed apps, right? And markup is the underpinning of the whole view portion of an app. Therefore I think that proper support for XHTML should be implemented in all applicable editors. It would be nice to have it in the visual designer first. I have seen requiests for XHTML support in the forums since at least 2003, and possibly earlier. Can this be made a priority? It should work in static docs and jsp both.
Thanks, and please note that this is a request and not a real gripe. Killer software, guys…
Chris
🙂I was, however, very disappointed to find that the nice shiny new Visual Designer uses the defunct HTML 4.01 standard. It’s dead! Now, I do realize that some people still do HTML (they should not, but…), and support for it is a nice extra if you, say, supply an HTML DOCTYPE I guess, but standards support should come first. Not only that, but it put font tags in my html(!), rather than using an included or external stylesheet.
XHTML support along with good AJAX is very high on our list, this is just the first itteration of the designer, there are many more miles to go. Sorry for the delay. Some folks have actually had better experience using the XML editor to edit their XHTML pages, this might be a good temporary workaround for you until we get full XHTML support in.
I know you guys have a zillion requests, but ME is primnarily about distributed apps, right? And markup is the underpinning of the whole view portion of an app. Therefore I think that proper support for XHTML should be implemented in all applicable editors. It would be nice to have it in the visual designer first. I have seen requiests for XHTML support in the forums since at least 2003, and possibly earlier. Can this be made a priority? It should work in static docs and jsp both.
There is no argument here, we agree with you.
Excellent, glad to hear it’s a priority. I can def. do xhtml in the xml editor, I do this often as I like the control you get over your markup. I was looking forward to the designer for some rapid prototyping work as well as for some quick and dirty site work that can stand until time is given for a proper setup. As a developer myself I really do understand that everyone wants everything from you, I was just hoping for some priority 😉 , which it seems I’m getting, so I’m happy…thx!
-Chris
I don’t have anything major to add to this discussion, other than to say I also really want XHTML support. XHTML is a lot more established than many of the technologies you already support, and is a highly recommended best practice in the industry.
I hope it’s added soon.
Thanks,
Ken
—
Ken Kousen
President
Kousen IT, Inc.
http://www.kousenit.com
ken.kousen@kousenit.comXHTML is a lot more established than many of the technologies you already support, and is a highly recommended best practice in the industry.
Ken you will hear no argument from us. AJAX is going to be a big focus of ours moving forward, and as a requirement the XHTML/JSP editor will get a lot of work as well to support all that working together nicely.
Is this supported in 4.1 m2? If so how can I enabled it so the editor defaults to xhtml?
Regards,
Olivier
Olivier,
No XHTML support isn’t fully supported in 4.1 yet, the requirement is a big change to the underlying HTML/XML editor that we are most likely going to put into the 5.0 release. However in the 4.1 and rest of 4.x the AJAX support directly will get stronger.There is no promise from management, but we *know* it needs to get in there ASAP, so that’s our timeline… ASAP.
Thanks, Riyad. Perhaps you could gently remind management that at the end of the day, everything that all this J2EE stuff amounts to is markup pushed to/from the browser. Therefore, using modern markup is crucial 😉
If they weren’t all developers that were smarter than me, I would remind them 🙂
Honestly the commitment level to XHTML first and foremost, and then Facelets and technologies that build on it is high. You are correct when you said HTML 4 is outdated. With all the AJAX work our there, and our support for it, fully validated XHTML docs is really the only way to develop moving forward. Not to say we will exclude legacy support, just that we are making support for the advanced technologies priority.
<Laugh>, I know what you mean – I’m a seasoned developer and there is always someone smarter than me too. 😆
Thanks for your insight into the XHTML/Facelets/etc. plans, that’s great to hear, and I’m excited about the facelets part too as that is the next tech bit on my radar. From my readings, it’s quite a boon to JSF developers.
Keep up the good work over there, you guys are amazing with your attention to the forums – more than literally any other project I’ve worked with in my 19 professional years. And of course the product is good enough for me to be a repeat subscriber 😉
