| Visual JSP editing [message #21121] |
Tue, 04 May 2004 15:13  |
Eclipse User |
|
|
|
Originally posted by: joleonard.kinzan.com
Kinzan is a software product company that has built a set of plugins for
Eclipse that allow for visually assembly of web applications based on a MVC
component framework. We've also implemented the same framework inside
Visual Studio for .NET apps.
One of the areas that we noticed a huge gap between Eclipse and Visual
Studio was the availability of a Visual JSP/ASP editor. In Visual Studio we
were able to take advantage of their editor. In Eclipse we had to build our
own.
We would like to give back to the community and think that our Visual JSP
editor would be very useful outside of the context of our own framework.
Granted the project scope is already large but we have a solid base
implementation done that extends Mozilla's rendering and html composer
capabilities to handle JSP 2.0.
In our experience JSP editing is one area where there is a lot of pain. How
do others on this group feel?
|
|
|
|
|
|
|
|
|
|
|
| Re: Visual JSP editing [message #22172 is a reply to message #21816] |
Mon, 10 May 2004 16:27  |
| Eclipse User |
|
|
|
Originally posted by: joleonard.kinzan.com
Jeff,
Here are the comments from our development lead on why Mozilla was chosen:
We looked at a few options initially, Internet Explorer MSHTML control,
Amaya Web browser, Mozilla web browsers. The rendering of HTML elements are
very complex - (the way tags are nested, the grammar, compliance, graphics,
CSS support, DOM support, etc.). Making GEF and EMF render HTML/JSP, would
be very difficult.
Mozilla has a powerful Gecko engine (XPCOM Layer in C++) that can render
HTML, which also provides API's for editing capabilities. It also has a XUL
(Javascript like) language, which can help you quickly design UI on top of
the Gecko API's. So implementing JSP constructs was possible.
"Jeff Duska" <Jeff.Duska@noaa.gov> wrote in message
news:c7oe7h$3qa$1@eclipse.org...
> I'm curious why you chose to use Mozilla's designer instead of GEF and
> EMF like the VE project does? When I considered this type of project it
> seemed like these tools would best starting point. Were they not
> available when you started? Or did you try to use them and found problems?
>
> Regards,
>
> Jeff Duska
>
> James O'Leonard wrote:
> > Jeff:
> >
> > It offers much more than just a preview mode. Certainly not as strong
as
> > Dreamweaver yet, but with the Eclipse community's help it could be.
> >
> > -James
> >
> > "Jeff Duska" <Jeff.Duska@noaa.gov> wrote in message
> > news:c78urs$4m4$1@eclipse.org...
> >
> >>This sounds very cool. I curious of what you mean by visual editor. I'm
> >>thinking of something like Dreamweaver MX and as you mentioned the
> >>ASP.NET editor in VisualStudio.NET. I've also seen people call a preview
> >>mode a visual editor.
> >>
> >>Regards,
> >>
> >>Jeff
> >>
> >>James O'Leonard wrote:
> >>
> >>>Kinzan is a software product company that has built a set of plugins
for
> >>>Eclipse that allow for visually assembly of web applications based on a
> >
> > MVC
> >
> >>>component framework. We've also implemented the same framework inside
> >>>Visual Studio for .NET apps.
> >>>
> >>>One of the areas that we noticed a huge gap between Eclipse and Visual
> >>>Studio was the availability of a Visual JSP/ASP editor. In Visual
> >
> > Studio we
> >
> >>>were able to take advantage of their editor. In Eclipse we had to
build
> >
> > our
> >
> >>>own.
> >>>
> >>>We would like to give back to the community and think that our Visual
> >
> > JSP
> >
> >>>editor would be very useful outside of the context of our own
framework.
> >>>Granted the project scope is already large but we have a solid base
> >>>implementation done that extends Mozilla's rendering and html composer
> >>>capabilities to handle JSP 2.0.
> >>>
> >>>In our experience JSP editing is one area where there is a lot of pain.
> >
> > How
> >
> >>>do others on this group feel?
> >>>
> >>>
> >>
> >
> >
|
|
|
Powered by
FUDForum. Page generated in 0.38638 seconds
Home