|
|
|
| Re: Open Existing Project Not a New Feature! [message #646512 is a reply to message #646509] |
Sat, 25 December 2010 22:56   |
|
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 #646579 is a reply to message #646489] |
Tue, 28 December 2010 22:53 |
 Ahmed Metwally
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
|
 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 |
|
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/
|
|
|
Powered by
FUDForum. Page generated in 0.02887 seconds
] 
Search
Help
Register
Login
Home
