Home » Eclipse Projects » Eclipse Platform » Standalone Vs Eclipse Platform
| Standalone Vs Eclipse Platform [message #261314] |
Tue, 13 July 2004 16:58  |
Eclipse User |
|
|
|
Hi,
I am reading on using SWT/JFace as the potential libary for developing
tools for one of our depts - I understand that I can use the SWT/JFACE
libraries along with the standard Java SDK, standalone and have no
dependency on eclipse platform.
However, I have been told that there maybe benefits in developing on the
top of an eclipse platform - does that make sense, if so, what does that
exactly means?
I am familiar with the IDE and the plug-in aspects of eclipse. I would use
eclipse as an "IDE" for the actual development. But right now there is no
need to deploy the product as a plug-in. In such situation, what is the
benefit of developing the GUI desktop application on the top of an eclipse
platform rather than a standalone. Please let me know.
Thanks.
Anima.
|
|
| |
| Re: Standalone Vs Eclipse Platform [message #261362 is a reply to message #261332] |
Tue, 13 July 2004 18:54  |
| Eclipse User |
|
|
|
Hi Scott, thanks for the link.
Correct me if I am wrong here, but this means, that the using the eclipse
framework during development using SWT will help me accelarate the process
and have a unified approach - but once my tool is ready - when I deploy it
to the users desktop - all I would need is the java runtime, swt.jar and
native gui library available - nothing else of eclipse would be needed
right?
What I am trying to understand is when we say building on an eclipse
platform - does that just mean serving as a good framework for development
OR is there some part of eclipse (besides the gui libraties ofcourse) that
needs to exist on the users desktop.
Hope my questions make sense. Please let me know.
Anima.
Scott Anderson wrote:
> The case for this approach was made very well (IMHO) in the EclipseCon
> presentation available here:
>
http://www.eclipsecon.org/EclipseCon_2004_TechnicalTrackPres entations/17_Williams_May_Dovich.pdf
> "Anima Gupta" <agupta@netflix.com> wrote in message
> news:cd1ict$3mg$1@eclipse.org...
> > Hi,
> >
> > I am reading on using SWT/JFace as the potential libary for developing
> > tools for one of our depts - I understand that I can use the SWT/JFACE
> > libraries along with the standard Java SDK, standalone and have no
> > dependency on eclipse platform.
> >
> > However, I have been told that there maybe benefits in developing on the
> > top of an eclipse platform - does that make sense, if so, what does that
> > exactly means?
> >
> > I am familiar with the IDE and the plug-in aspects of eclipse. I would use
> > eclipse as an "IDE" for the actual development. But right now there is no
> > need to deploy the product as a plug-in. In such situation, what is the
> > benefit of developing the GUI desktop application on the top of an eclipse
> > platform rather than a standalone. Please let me know.
> >
> > Thanks.
> >
> > Anima.
> >
|
|
|
| Re: Standalone Vs Eclipse Platform [message #261370 is a reply to message #261362] |
Tue, 13 July 2004 20:17 |
| Eclipse User |
|
|
|
Originally posted by: scott.anderson.genuitec.com
Anima,
In short, you'll have to deploy as much of Eclipse as you use. If you only
use SWT, then that's all you need to deploy. If you use more, like the rich
client platform (RCP) then you'll need to deploy that as part of your
application. If you use the RCP and some of the pieces of the Eclipse IDE
also, then you'll need to deploy all of that.
You see, Eclipse technology is modular and reusable so you get to pick how
much you need. In general, the RCP is the kernal upon which Eclipse-based
applications are built. For more information, there are some great RCP
presentations here:
http://www.eclipsecon.org/presentations.htm
(look for all talks labeled with Rich Client Platform in the top right
corner)
and some lightweight overview tutorial articles here:
http://www.eclipse.org/articles/index.html
to help you get started.
--Scott
"Anima Gupta" <agupta@netflix.com> wrote in message
news:cd1p7n$di3$1@eclipse.org...
> Hi Scott, thanks for the link.
>
> Correct me if I am wrong here, but this means, that the using the eclipse
> framework during development using SWT will help me accelarate the process
> and have a unified approach - but once my tool is ready - when I deploy it
> to the users desktop - all I would need is the java runtime, swt.jar and
> native gui library available - nothing else of eclipse would be needed
> right?
>
> What I am trying to understand is when we say building on an eclipse
> platform - does that just mean serving as a good framework for development
> OR is there some part of eclipse (besides the gui libraties ofcourse) that
> needs to exist on the users desktop.
>
> Hope my questions make sense. Please let me know.
>
> Anima.
>
>
>
> Scott Anderson wrote:
>
> > The case for this approach was made very well (IMHO) in the EclipseCon
> > presentation available here:
> >
>
http://www.eclipsecon.org/EclipseCon_2004_TechnicalTrackPres entations/17_Williams_May_Dovich.pdf
>
>
> > "Anima Gupta" <agupta@netflix.com> wrote in message
> > news:cd1ict$3mg$1@eclipse.org...
> > > Hi,
> > >
> > > I am reading on using SWT/JFace as the potential libary for developing
> > > tools for one of our depts - I understand that I can use the SWT/JFACE
> > > libraries along with the standard Java SDK, standalone and have no
> > > dependency on eclipse platform.
> > >
> > > However, I have been told that there maybe benefits in developing on
the
> > > top of an eclipse platform - does that make sense, if so, what does
that
> > > exactly means?
> > >
> > > I am familiar with the IDE and the plug-in aspects of eclipse. I would
use
> > > eclipse as an "IDE" for the actual development. But right now there is
no
> > > need to deploy the product as a plug-in. In such situation, what is
the
> > > benefit of developing the GUI desktop application on the top of an
eclipse
> > > platform rather than a standalone. Please let me know.
> > >
> > > Thanks.
> > >
> > > Anima.
> > >
>
>
|
|
|
| Re: Standalone Vs Eclipse Platform [message #261547 is a reply to message #261370] |
Wed, 14 July 2004 14:07 |
| Eclipse User |
|
|
|
Thanks scott, I have started looking into RCP.
Scott Anderson wrote:
> Anima,
> In short, you'll have to deploy as much of Eclipse as you use. If you only
> use SWT, then that's all you need to deploy. If you use more, like the rich
> client platform (RCP) then you'll need to deploy that as part of your
> application. If you use the RCP and some of the pieces of the Eclipse IDE
> also, then you'll need to deploy all of that.
> You see, Eclipse technology is modular and reusable so you get to pick how
> much you need. In general, the RCP is the kernal upon which Eclipse-based
> applications are built. For more information, there are some great RCP
> presentations here:
> http://www.eclipsecon.org/presentations.htm
> (look for all talks labeled with Rich Client Platform in the top right
> corner)
> and some lightweight overview tutorial articles here:
> http://www.eclipse.org/articles/index.html
> to help you get started.
> --Scott
> "Anima Gupta" <agupta@netflix.com> wrote in message
> news:cd1p7n$di3$1@eclipse.org...
> > Hi Scott, thanks for the link.
> >
> > Correct me if I am wrong here, but this means, that the using the eclipse
> > framework during development using SWT will help me accelarate the process
> > and have a unified approach - but once my tool is ready - when I deploy it
> > to the users desktop - all I would need is the java runtime, swt.jar and
> > native gui library available - nothing else of eclipse would be needed
> > right?
> >
> > What I am trying to understand is when we say building on an eclipse
> > platform - does that just mean serving as a good framework for development
> > OR is there some part of eclipse (besides the gui libraties ofcourse) that
> > needs to exist on the users desktop.
> >
> > Hope my questions make sense. Please let me know.
> >
> > Anima.
> >
> >
> >
> > Scott Anderson wrote:
> >
> > > The case for this approach was made very well (IMHO) in the EclipseCon
> > > presentation available here:
> > >
> >
>
http://www.eclipsecon.org/EclipseCon_2004_TechnicalTrackPres entations/17_Williams_May_Dovich.pdf
> >
> >
> > > "Anima Gupta" <agupta@netflix.com> wrote in message
> > > news:cd1ict$3mg$1@eclipse.org...
> > > > Hi,
> > > >
> > > > I am reading on using SWT/JFace as the potential libary for developing
> > > > tools for one of our depts - I understand that I can use the SWT/JFACE
> > > > libraries along with the standard Java SDK, standalone and have no
> > > > dependency on eclipse platform.
> > > >
> > > > However, I have been told that there maybe benefits in developing on
> the
> > > > top of an eclipse platform - does that make sense, if so, what does
> that
> > > > exactly means?
> > > >
> > > > I am familiar with the IDE and the plug-in aspects of eclipse. I would
> use
> > > > eclipse as an "IDE" for the actual development. But right now there is
> no
> > > > need to deploy the product as a plug-in. In such situation, what is
> the
> > > > benefit of developing the GUI desktop application on the top of an
> eclipse
> > > > platform rather than a standalone. Please let me know.
> > > >
> > > > Thanks.
> > > >
> > > > Anima.
> > > >
> >
> >
|
|
|
Goto Forum:
Current Time: Tue Jul 22 13:48:16 EDT 2025
Powered by FUDForum. Page generated in 0.07690 seconds |
Home