| Lomboz as an eclipse project [message #2440] |
Wed, 11 June 2003 17:01  |
 B. Gorkem ERCAN
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
Lomboz is considering to become an eclipse project. Since the early days of
Lomboz that was the intention. Lomboz is one year old now . We believe it is
mature enough to become an eclipse project. I would like to start a
disscussion if Lomboz should form the basis of the webtools project?
|
|
|
| Re: Lomboz as an eclipse project [message #2471 is a reply to message #2440] |
Wed, 11 June 2003 19:48  |
|
Originally posted by: mail.phase.ws
There are several things I like about Lomboz. But, I have never used it
because it lacks important functionality and imposes one restriction that is
a show stopper for me. I am also a regular part of the Struts User list and
I have asked the question and seen the question asked about J2EE
development. Lomboz is never a strong part of that discussion. Most of the
developers i know are not fully satisfied with tools like Lomboz. I have
some key areas mentioned below that I believe are a good crosscut of many
developers opinions.
Outlined below are some thoughts regarding functionality that is important.
1) Keep it simple. Allow me to adopt portions. I don't want to have to bite
the whole enchilada if I don't want to. If all I want is JSP code completion
and loadable custom tags, then don't make me use the build script, the
compile and your project directory structure.
2) When dealing with tag code completion it would be nice to be able load
tlds on a per project/webapp manner so custom tags could be easilty added to
the project and code completion possible. Perhaps it would be better if jars
in the classpath were automatically scanned for .tld files
3) Be able to use the root context as an application base so that I don't
have to build a webapp with a http://www.mydomain.com/[webappname]. Lomboz
imposes the rule that you have to provide an app name after your domain.
This is a HUGE drawback for me.
4) JSP syntax highliting that works. I've hit a few JSP editors that screw
up the comment spacing. When typing <%-- --%> additional spaces are added to
the end of the comment section. The visisble cursor does not sync with where
the actual cursor is. In other cases the comment highlighting fails when
there is a hard return after the opening comment marker and before the
closing comment marker.
5) JSP Compilation. I like how Lomboz places the compiled jsp into the j2src
folder and identifies the problem area on the jsp page. Very Nice.
6) Individualized Server config files per project. For example, I use Tomcat
and I work on several apps at a time. Each app uses the root context (ie
"/"). It would be nice to have a Server.xml file that is loaded into Tomcat
on a project by project basis. That way I don't have to go and comment out
all of my other projects in server.xml each time I want to work on another
project.
I can't think of anything else at the moment. But, I hope that provides some
insight.
" B. Gorkem ERCAN" <gorkem@objectlearn.com> wrote in message
news:bc85as$jjc$1@rogue.oti.com...
> Lomboz is considering to become an eclipse project. Since the early days
of
> Lomboz that was the intention. Lomboz is one year old now . We believe it
is
> mature enough to become an eclipse project. I would like to start a
> disscussion if Lomboz should form the basis of the webtools project?
>
>
|
|
|
| Re: Lomboz as an eclipse project [message #2497 is a reply to message #2471] |
Wed, 11 June 2003 19:55 |
|
Originally posted by: mxlehma.NO-SPAM.qwest.com
At a minimum, you should post the source code out somewhere like
sourceforce so we can all look at it and contribute to the development
of this product, even if it doesn't become an Eclipse project.
I would like to see some type of jsp editor added to Eclipse by default.
That is the big advantage I see that something like Visual Studio .NET
has that Eclipse is really lacking. The JSP editor that comes with
Lomboz would be a good start. If you could replication most of the
HTML/ASPX editing features the Visual Studio has I'd be doing cartwheels.
Brandon Goodin wrote:
> There are several things I like about Lomboz. But, I have never used it
> because it lacks important functionality and imposes one restriction that is
> a show stopper for me. I am also a regular part of the Struts User list and
> I have asked the question and seen the question asked about J2EE
> development. Lomboz is never a strong part of that discussion. Most of the
> developers i know are not fully satisfied with tools like Lomboz. I have
> some key areas mentioned below that I believe are a good crosscut of many
> developers opinions.
>
--
Michael
|
|
|
| Re: Lomboz as an eclipse project [message #2615 is a reply to message #2471] |
Thu, 12 June 2003 10:06 |
|
Originally posted by: stefan.baramov.trx.com
If you all allow me to extend this list just a little bit:
8) Support for XDoclet attribute programming model. For reference see JBoss
IDE (http://sourceforge.net/projects/jboss)
9) How about easystruts project. Great struct-config editor and a few other
nice things.
- Stefan Baramov
"Brandon Goodin" <mail@phase.ws> wrote in message
news:bc8eqs$qke$1@rogue.oti.com...
> There are several things I like about Lomboz. But, I have never used it
> because it lacks important functionality and imposes one restriction that
is
> a show stopper for me. I am also a regular part of the Struts User list
and
> I have asked the question and seen the question asked about J2EE
> development. Lomboz is never a strong part of that discussion. Most of the
> developers i know are not fully satisfied with tools like Lomboz. I have
> some key areas mentioned below that I believe are a good crosscut of many
> developers opinions.
>
> Outlined below are some thoughts regarding functionality that is
important.
> 1) Keep it simple. Allow me to adopt portions. I don't want to have to
bite
> the whole enchilada if I don't want to. If all I want is JSP code
completion
> and loadable custom tags, then don't make me use the build script, the
> compile and your project directory structure.
> 2) When dealing with tag code completion it would be nice to be able load
> tlds on a per project/webapp manner so custom tags could be easilty added
to
> the project and code completion possible. Perhaps it would be better if
jars
> in the classpath were automatically scanned for .tld files
> 3) Be able to use the root context as an application base so that I don't
> have to build a webapp with a http://www.mydomain.com/[webappname]. Lomboz
> imposes the rule that you have to provide an app name after your domain.
> This is a HUGE drawback for me.
> 4) JSP syntax highliting that works. I've hit a few JSP editors that screw
> up the comment spacing. When typing <%-- --%> additional spaces are added
to
> the end of the comment section. The visisble cursor does not sync with
where
> the actual cursor is. In other cases the comment highlighting fails when
> there is a hard return after the opening comment marker and before the
> closing comment marker.
> 5) JSP Compilation. I like how Lomboz places the compiled jsp into the
j2src
> folder and identifies the problem area on the jsp page. Very Nice.
> 6) Individualized Server config files per project. For example, I use
Tomcat
> and I work on several apps at a time. Each app uses the root context (ie
> "/"). It would be nice to have a Server.xml file that is loaded into
Tomcat
> on a project by project basis. That way I don't have to go and comment out
> all of my other projects in server.xml each time I want to work on another
> project.
>
> I can't think of anything else at the moment. But, I hope that provides
some
> insight.
>
> " B. Gorkem ERCAN" <gorkem@objectlearn.com> wrote in message
> news:bc85as$jjc$1@rogue.oti.com...
>
> > Lomboz is considering to become an eclipse project. Since the early days
> of
> > Lomboz that was the intention. Lomboz is one year old now . We believe
it
> is
> > mature enough to become an eclipse project. I would like to start a
> > disscussion if Lomboz should form the basis of the webtools project?
> >
> >
>
>
|
|
|
| Re: Lomboz as an eclipse project [message #2673 is a reply to message #2471] |
Thu, 12 June 2003 15:33 |
|
Originally posted by: tnodari.uol.com.br
I agree with all the point Brandon made. The application I work on has to
be the ROOT, because ppl here made serveral mistakes that dont let it work
on any other context. I only use the Code Completion, the rest I use ant
to do the job for me. I havent tried to debug JSPs or anything like
that...
Also if the source code was available, i think you could get more ppl
involved...
Brandon Goodin wrote:
> There are several things I like about Lomboz. But, I have never used it
> because it lacks important functionality and imposes one restriction that is
> a show stopper for me. I am also a regular part of the Struts User list and
> I have asked the question and seen the question asked about J2EE
> development. Lomboz is never a strong part of that discussion. Most of the
> developers i know are not fully satisfied with tools like Lomboz. I have
> some key areas mentioned below that I believe are a good crosscut of many
> developers opinions.
> Outlined below are some thoughts regarding functionality that is important.
> 1) Keep it simple. Allow me to adopt portions. I don't want to have to bite
> the whole enchilada if I don't want to. If all I want is JSP code completion
> and loadable custom tags, then don't make me use the build script, the
> compile and your project directory structure.
> 2) When dealing with tag code completion it would be nice to be able load
> tlds on a per project/webapp manner so custom tags could be easilty added to
> the project and code completion possible. Perhaps it would be better if jars
> in the classpath were automatically scanned for .tld files
> 3) Be able to use the root context as an application base so that I don't
> have to build a webapp with a http://www.mydomain.com/[webappname]. Lomboz
> imposes the rule that you have to provide an app name after your domain.
> This is a HUGE drawback for me.
> 4) JSP syntax highliting that works. I've hit a few JSP editors that screw
> up the comment spacing. When typing <%-- --%> additional spaces are added to
> the end of the comment section. The visisble cursor does not sync with where
> the actual cursor is. In other cases the comment highlighting fails when
> there is a hard return after the opening comment marker and before the
> closing comment marker.
> 5) JSP Compilation. I like how Lomboz places the compiled jsp into the j2src
> folder and identifies the problem area on the jsp page. Very Nice.
> 6) Individualized Server config files per project. For example, I use Tomcat
> and I work on several apps at a time. Each app uses the root context (ie
> "/"). It would be nice to have a Server.xml file that is loaded into Tomcat
> on a project by project basis. That way I don't have to go and comment out
> all of my other projects in server.xml each time I want to work on another
> project.
> I can't think of anything else at the moment. But, I hope that provides some
> insight.
> " B. Gorkem ERCAN" <gorkem@objectlearn.com> wrote in message
> news:bc85as$jjc$1@rogue.oti.com...
> > Lomboz is considering to become an eclipse project. Since the early days
> of
> > Lomboz that was the intention. Lomboz is one year old now . We believe it
> is
> > mature enough to become an eclipse project. I would like to start a
> > disscussion if Lomboz should form the basis of the webtools project?
> >
> >
|
|
|
| Re: Lomboz as an eclipse project [message #3136 is a reply to message #2471] |
Thu, 12 June 2003 19:17 |
|
Originally posted by: kduffey.marketron.com
Along the lines of your working with several applications at once, it would
be nice to be able to select the "root context" for a given application, or
even specify that while within the scope of a given app, deploy it as the
root app. That is, if you have open the xxx project, when you are ready to
test it, have the webtools automatically deploy it (configure the app server
if need be) to use it as the root, so that you don't have to run
www.xxx.com/mywebapp. That would be nice.
"Brandon Goodin" <mail@phase.ws> wrote in message
news:bc8eqs$qke$1@rogue.oti.com...
> There are several things I like about Lomboz. But, I have never used it
> because it lacks important functionality and imposes one restriction that
is
> a show stopper for me. I am also a regular part of the Struts User list
and
> I have asked the question and seen the question asked about J2EE
> development. Lomboz is never a strong part of that discussion. Most of the
> developers i know are not fully satisfied with tools like Lomboz. I have
> some key areas mentioned below that I believe are a good crosscut of many
> developers opinions.
>
> Outlined below are some thoughts regarding functionality that is
important.
> 1) Keep it simple. Allow me to adopt portions. I don't want to have to
bite
> the whole enchilada if I don't want to. If all I want is JSP code
completion
> and loadable custom tags, then don't make me use the build script, the
> compile and your project directory structure.
> 2) When dealing with tag code completion it would be nice to be able load
> tlds on a per project/webapp manner so custom tags could be easilty added
to
> the project and code completion possible. Perhaps it would be better if
jars
> in the classpath were automatically scanned for .tld files
> 3) Be able to use the root context as an application base so that I don't
> have to build a webapp with a http://www.mydomain.com/[webappname]. Lomboz
> imposes the rule that you have to provide an app name after your domain.
> This is a HUGE drawback for me.
> 4) JSP syntax highliting that works. I've hit a few JSP editors that screw
> up the comment spacing. When typing <%-- --%> additional spaces are added
to
> the end of the comment section. The visisble cursor does not sync with
where
> the actual cursor is. In other cases the comment highlighting fails when
> there is a hard return after the opening comment marker and before the
> closing comment marker.
> 5) JSP Compilation. I like how Lomboz places the compiled jsp into the
j2src
> folder and identifies the problem area on the jsp page. Very Nice.
> 6) Individualized Server config files per project. For example, I use
Tomcat
> and I work on several apps at a time. Each app uses the root context (ie
> "/"). It would be nice to have a Server.xml file that is loaded into
Tomcat
> on a project by project basis. That way I don't have to go and comment out
> all of my other projects in server.xml each time I want to work on another
> project.
>
> I can't think of anything else at the moment. But, I hope that provides
some
> insight.
>
> " B. Gorkem ERCAN" <gorkem@objectlearn.com> wrote in message
> news:bc85as$jjc$1@rogue.oti.com...
>
> > Lomboz is considering to become an eclipse project. Since the early days
> of
> > Lomboz that was the intention. Lomboz is one year old now . We believe
it
> is
> > mature enough to become an eclipse project. I would like to start a
> > disscussion if Lomboz should form the basis of the webtools project?
> >
> >
>
>
|
|
|
| Re: Lomboz as an eclipse project [message #3170 is a reply to message #2497] |
Thu, 12 June 2003 19:18 |
|
Originally posted by: kduffey.marketron.com
Is there anything like a visual drag/drop build tool for web pages that can
result in JSP pages being created, such that you could have a menu bar with
your favorite tag-libs, your favorite components, etc, drag/drop them onto a
visual web page, and edit them inline as needed. And more so, if you
manually edit the page, the visual editor doesn't break! IT can reverse
engineer your manual changes as necessary?
"Michael" <mxlehma@NO-SPAM.qwest.com> wrote in message
news:bc8fhj$r1d$1@rogue.oti.com...
> At a minimum, you should post the source code out somewhere like
> sourceforce so we can all look at it and contribute to the development
> of this product, even if it doesn't become an Eclipse project.
>
> I would like to see some type of jsp editor added to Eclipse by default.
> That is the big advantage I see that something like Visual Studio .NET
> has that Eclipse is really lacking. The JSP editor that comes with
> Lomboz would be a good start. If you could replication most of the
> HTML/ASPX editing features the Visual Studio has I'd be doing cartwheels.
>
> Brandon Goodin wrote:
>
> > There are several things I like about Lomboz. But, I have never used it
> > because it lacks important functionality and imposes one restriction
that is
> > a show stopper for me. I am also a regular part of the Struts User list
and
> > I have asked the question and seen the question asked about J2EE
> > development. Lomboz is never a strong part of that discussion. Most of
the
> > developers i know are not fully satisfied with tools like Lomboz. I have
> > some key areas mentioned below that I believe are a good crosscut of
many
> > developers opinions.
> >
>
> --
> Michael
>
|
|
|
| Re: Lomboz as an eclipse project [message #3301 is a reply to message #2471] |
Fri, 13 June 2003 06:38 |
Naci Dai
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
> 3) Be able to use the root context as an application base so that I don't
> have to build a webapp with a http://www.mydomain.com/[webappname]. Lomboz
> imposes the rule that you have to provide an app name after your domain.
> This is a HUGE drawback for me.
I have to admit this request tops the feature-requests for Lomboz, primarily
from people who would just like to have the JSP Editor component without the
extra baggage.
I have been opposing it for a few reasons:
- JSP editor is nice but it is not everything.
- There is soo much in a JSP that has to do with the application context
that it is in. Making a JSP editor that automatically pick/decide where to
find information about the application context, classpath, tag libraries,
etc., will create many dangerous developers. Especially, it will be the
rookie ones who suffer the most. They will be able to make things work in
Lomboz but not in the runtime. It was one of the main philosophies behind
Lomboz: Develop the way you will run it. Do it right.
I symphatize the needs of people, but I also would like to keep the tool in
the right lane.
Having said that, there is a feature in the next release of Lomboz that
will ask you to determine the application context if it cannot find one...
Also, JSP editor will multiple panes: Java Editor, HTML Editor and
Preview... This is primarily due to different views serving different needs
and makes parsing and coloring much less painful :-)
Finally, about donating code to webtools, I would like to hear a bit more
from OTI, more than the paragraph on the web page.
|
|
|
Powered by
FUDForum. Page generated in 0.02146 seconds
] 
Search
Help
Register
Login
Home
