Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Open Existing Project Not a New Feature!
Open Existing Project Not a New Feature! [message #646489] Sat, 25 December 2010 13:14 Go to next message
Ahmed Metwally is currently offline Ahmed MetwallyFriend
Messages: 8
Registered: December 2010
Junior Member
What is the genius
about open projects by this way
File > Import > General > Existing Projects into Workspace

and what is wrong with this way
File > Open Project

I think it's common in any software
When you need to open the thing that the software create it
you go to "File" menu then you will find "Open something" option
in the menu.

why I need to search in the internet for
"how to open a project in eclipse"
and maybe read a tons of documents
to just find out how to open a project

this is so so silly
Re: Open Existing Project Not a New Feature! [message #646499 is a reply to message #646489] Sat, 25 December 2010 17:10 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 26279
Registered: July 2009
Senior Member
Ahmed,

Comments below.

Ahmed Metwally wrote:
> What is the genius
> about open projects by this way
> File > Import > General > Existing Projects into Workspace
Because things that aren't already in the workspace aren't so likely to
already be Eclipse projects. They'd need to contain a .project file for
example..
>
> and what is wrong with this way
> File > Open Project
Because you're not just opening a project, you're creating one in the
workspace.
>
> I think it's common in any software
Most software deals with opening files, not projects.
> When you need to open the thing that the software create it
> you go to "File" menu then you will find "Open something" option
> in the menu.
There is an Open File... menu but it's not so much used because you
generally need to work with things actually in the workspace.
>
> why I need to search in the internet for "how to open a project in
> eclipse"
Because you didn't search all the menu options and then wizards.
> and maybe read a tons of documents to just find out how to open a project
>
> this is so so silly
You're not in a good mood this morning are you?
Re: Open Existing Project Not a New Feature! [message #646509 is a reply to message #646489] Sat, 25 December 2010 22:36 Go to previous messageGo to next message
Ahmed Metwally is currently offline Ahmed MetwallyFriend
Messages: 8
Registered: December 2010
Junior Member
Quote:
You're not in a good mood this morning are you?

Yes, because of Eclipse
I really want to move to it
and he did not help me
I have to set every thing
define a compiler and point to Include files and other stuff
and to do that I have to navigate through Internet and read a lot of blog posts and forum threads

Why he want me to download a compiler!
Why he just come with his own compiler!!
and set every thing he need to run the program!!!!

Moreover, I get crazy when I can't open the project which I created by it using the normal way Sad

I think It's my fault to start programming with Visual Studio.
Eclipse would be good, if I had started programming using "Notepad" as an Editor and command-line for building the projects.


Thank you ED for your interaction.
Re: Open Existing Project Not a New Feature! [message #646512 is a reply to message #646509] Sat, 25 December 2010 22:56 Go to previous messageGo to next message
Stanimir Stamenkov is currently offline Stanimir StamenkovFriend
Messages: 254
Registered: July 2009
Senior Member
Sat, 25 Dec 2010 17:36:18 -0500, /Ahmed Metwally/:

> Why he want me to download a compiler!
> Why he just come with his own compiler!!
> and set every thing he need to run the program!!!!

Does Visual Studio come with a compiler for every platform you would
try to develop for? If it was like that, I guess you could just use
Visual Studio but no, you would run in the same (if not worse)
situation trying to use Visual Studio to develop for a platform
different than Windows.

You know, Eclipse and CDT are just base for commercial vendors to
provide ready packages (including compilers and complete tool
chains) for specific platforms. If you don't feel knowledgeable
enough to setup an environment on your own, you could search for
commercial product (Eclipse/CDT based or otherwise) which would
supposedly bring you more up to speed.

--
Stanimir
Re: Open Existing Project Not a New Feature! [message #646513 is a reply to message #646489] Sat, 25 December 2010 23:27 Go to previous messageGo to next message
Ahmed Metwally is currently offline Ahmed MetwallyFriend
Messages: 8
Registered: December 2010
Junior Member
Quote:
If you don't feel knowledgeable
enough to setup an environment on your own, you could search for
commercial product (Eclipse/CDT based or otherwise) which would
supposedly bring you more up to speed.


I'm try to know how to setup all things.
And the main purpose to use Eclipse is
"Use Nun Commercial Products"
so I've to be patient till I get it work.

I was just wonder why it's not straight
Re: Open Existing Project Not a New Feature! [message #646564 is a reply to message #646509] Sun, 26 December 2010 17:54 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 26279
Registered: July 2009
Senior Member
Ahmed,

Comments below.

Ahmed Metwally wrote:
> Quote:
>> You're not in a good mood this morning are you?
>
> Yes, because of Eclipse
> I really want to move to it
> and he did not help me
It's always good when newbies document their experience so the next guy
could learn from it. The wiki is good for that. Everyone can help make
things easier to get started.
> I have to set every thing
> define a compiler and point to Include files and other stuff
> and to do that I have to navigate through Internet and read a lot of
> blog posts and forum threads
If only it were all spelled out in easy steps in one central place...
>
> Why he want me to download a compiler!
> Why he just come with his own compiler!!
I think there are issues with the license for some of these things.
I.e., GPL things can't be packaged up and reshipped with EPL. And
Eclipse won't even let LGPL things be redistributed from Eclipse...
> and set every thing he need to run the program!!!!
>
> Moreover, I get crazy when I can't open the project which I created by
> it using the normal way :(
You'll really have to stop thinking of it as opening a project. You'll
not that you can close (and then open) projects that are in your
workspace, but that means something totally different.
>
> I think It's my fault to start programming with Visual Studio.
Certainly learning something that works a certain way sets the
expectation that everything ought to work that way. We tend to call
that intuition and when things don't conform to it, we call it
unintuitive. Another word for it is unfamiliar. But once we learn
something it becomes familiar and intuitive, at which point we wonder
how anyone could argue it's anything but and how another way could be
better...
> Eclipse would be good, if I had started programming using "Notepad" as
> an Editor and command-line for building the projects.
I think a good many of the C++ developers come from that position.
>
>
> Thank you ED for your interaction.
Re: Open Existing Project Not a New Feature! [message #646579 is a reply to message #646489] Tue, 28 December 2010 22:53 Go to previous messageGo to next message
Ahmed Metwally is currently offline Ahmed MetwallyFriend
Messages: 8
Registered: December 2010
Junior Member
Quote:
I think there are issues with the license for some of these things.
I.e., GPL things can't be packaged up and reshipped with EPL. And
Eclipse won't even let LGPL things be redistributed from Eclipse...

When you see some open source projects shipped out with everything,
you start to ask why not the other products do that,

Quote:
You'll really have to stop thinking of it as opening a project

Smile I remembered a quote from Matrix movie when I read this sentence
"Do not try to bend the spoon, only try to realize the truth: there is no spoon"

I have the flexibility to change my thinking way,
but, you know, when they change something that you used to it you get upset.

Quote:
think a good many of the C++ developers come from that position.

Yes, and I feel so bad because I'm not started from this position too
unfortunately I get stuck with Microsoft when I didn't know where to go or what to do
I found everybody say Visual Basic Is your destination,
so I go to VB then after a few months I moved to C#.
Thanks GOD, I can do almost anything with C#.
But, When I found a lot of open source projects which written in C++ and any programmer can modify it
and I can't event understand it
I decided to start to be a real programmer
and use the real programmer tools

But, even the good tools have some weird things.
Re: Open Existing Project Not a New Feature! [message #646872 is a reply to message #646499] Sat, 01 January 2011 20:50 Go to previous message
Hendy Irawan is currently offline Hendy IrawanFriend
Messages: 58
Registered: July 2009
Location: Bandung, Indonesia
Member

Ed Merks wrote:

> Ahmed,
>
> Comments below.
>
> Ahmed Metwally wrote:
>> What is the genius
>> about open projects by this way
>> File > Import > General > Existing Projects into Workspace
> Because things that aren't already in the workspace aren't so likely
to
> already be Eclipse projects. They'd need to contain a .project file
for
> example..

Sorry Ed, but I'm "with him" this time.

Exactly for the fact that Eclipse projects need to contain .project
descriptor, Eclipse projects should be openable using File > Open
Project. (NetBeans has been doing this for ages). Or to distinguish with
open/close, menu item can be titled "Use Project".

"File > Import > General > Existing projects" is not going to work with
non-Eclipse projects anyway. An "Import" generally means "convert from
something that's not native format". It becomes weird you need the
"Import Eclipse project" feature to use an Eclipse project in Eclipse.

Another thing is Import project actually can do two things:
1. "link" to the existing project(s) at the original location
2. copy an existing project(s) to a new project folder inside the
workspace directory

In my POV these are two very different things. In most IDEs (including
but not limited to, Visual Studio, Qt Creator...) Open Project simply
opens the project at the current location. To "import" a project (like
Eclipse does) you generally use a file manager to copy the project
folder to another location and then open it from the IDE.

I think having a File > Open/Use Project will be a great usability boost
to Eclipse IDE. Long time users can just hide the menu item to save
space.


P.S.: It's a *REALLY* nice usability feature that Eclipse (re)uses
(existing) terminology such as "Build", "Run", and "Debug". Of course
you can google or read docs just find out if [an imaginary Eclipse IDE]
uses names like "Construct" for Build, "Takeoff" for Run, and "Exploit"
for Debug.. but don't you just love the principle of least surprise?
Why make it harder?


--
Eclipse Driven Rich Application Development -
http://eclipsedriven.blogspot.com/
Previous Topic:how to save all project specific info of eclipse
Next Topic:Why Not Easy!
Goto Forum:
  


Current Time: Thu Dec 18 13:35:50 GMT 2014

Powered by FUDForum. Page generated in 0.03892 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software