Re: extend it to allow jsp editting

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: extend it to allow jsp editting
by Peter Joanes on Monday 01/Sep/2003, @16:56

I haven't used Quanta much, and currently write JSPs for my webapps in Emacs which can be a little featureless.
A visual page layout tool would be useful, but JSPs can contain many types of custom tags which are generally used instead of the normal ones (i.e. a JSTL input tag instead of an html input tag), so I think that there would have to be integration with a servlet container to generate the tag output.

Related Links

·   Articles on KDE in the News
·   Also by Peter Joanes
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: extend it to allow jsp editting
by Charles Tse on Friday 20/Aug/2004, @11:08

Looks like this thread has died. However, I'm am using JSP on opensource other things.( linux, tomcat, postgresql ). Just finished a web site www.chumsnet.com. Notice the visual mis-alignment. I definitely want a good HTML editor in Linux. The custom tags of JSP should not be an issue. All tag things in JSP are done with XML. As long as Quanta can recognize the JSP tags and ignore them, things will be just fine. And there is no avoidance of invoking the JSP/Servlet container. But Quanta needs not worry about it. Quanta only has to provide a button to invoke the scripts( in Ant or Make ) to compile the JSPs, and another button to invoke the web page under development. The beauty of the new Tomcat container is that it can automatically detect new WAR files, and rebuild the webapps.

The displayed web page( or generated HTML code ) can then obtain the HTML source from the IExplorer( or interface api from other browsers ) interface, and Quanta should then do a diff between this generated source and that of the invoking JSP. Highlight the difference, and this will make it much easier for the user to edit the JSP. It won't be WYSIWYG. But, good enough for intermediate to experienced developers. Even expensive JBuilder relies on having a Tomcat engine, and it is not WYSIWYG( but close ).

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"If there is smoke, there could be a fire." -- Konqi
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.