extend it to allow jsp editting

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

extend it to allow jsp editting
by caoilte on Wednesday 11/Jun/2003, @03:00

or even trivialise the process of dtd importing for xml editting and I would use it like a shot. As it is I don't use php and have monkey's with dreamweaver to do html.

I'm sure it's great though, ;-).

Related Links

·   Articles on KDE in the News
·   Also by caoilte
·   Contact author

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

Re: extend it to allow jsp editting
by Eric Laffoon on Wednesday 11/Jun/2003, @08:53

We have some code done starting the process of DTD importing and we will be working on schemas too. The author of that code has been indisposed and we're hoping he comes back to finish it as his DTD knowlege is very good. However I keep putting out the message and it's really difficult to get across. What we have here is free community developed software and lots of people who just use it are so proud... The community aspect means that the person you see in the mirror makes some small contribution. After all it's a small price to pay for something great for free and if nobody did it the software wouldn't be there.

It is very easy to add a language to Quanta. We have made it a matter of writing an rc file and editing XML tag files. We even have a tagxml DTD in Quanta to make it easy to edit. We've done this so that users can add languages. Our W3C DTD guy can add a new HTML dialect in a matter of hours. We generated the PHP tag files with a Perl script from the documentation. It's not difficult and there is some small amount of documentation in the tags area of our source. However we take anyone wishing to add a language and add them to our developers mailing list so they have access to answers and so we can make any adjustments that might be required to our parser.

Currently we are coding on the parser optimizing it for speed and on Visual Page Layout having just finished a frames editor. How many people do JSP? If just one of them steps forward in the community spirit willing to give up their evenings for maybe a week we will fully support JSP. My belief is that if someone who uses it is testing it then it will be better than if we just take a stab without real world tests. Also I would not like to abandon the C++ development of other features to learn and test new languages.

I am very interested in working with people who want support for Java, JSP, Perl and variants like Mason, Zope, ASP and others. Supposedly ColdFusion and Javascript are being worked on but I've not seen the results for some time.

[ Reply To This | View ]

Re: extend it to allow jsp editting
by David on Friday 15/Aug/2003, @10:07

I currently use Dreamweaver MX for editing JSP files. I would be willing test any enhancements that you make in support of JSP. I also have another person in my group who would also like to test it.

[ Reply To This | View ]

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.

[ Reply To This | View ]

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 )


		"My hobbies include, well, coding... and uhm... that's about it." -- Daniel M. Duley
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.