> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Walter Harley > Sent: Sunday, June 22, 2008 1:55 PM > To: 'E4 developer list' > Subject: RE: [eclipse-incubator-e4-dev] Some food for thought > > Eric said: > > I too would like to be able to -quickly- fire up eclipse to > accomplish > > a task and shut it down...the startup times for Word and PPoint are > > essentailly sub-second on my box but eclipse > > takes...um...significantly more time. > > > AFAIK the reason Word and PPoint start quickly is that they are > registered to preload significant parts of themselves upon Windows > startup, regardless of whether they'll be needed. Note also that Word > and PPoint aren't editing projects with distributed > typesystems, they're > just editing single files with very little in the way of semantics. > > That said, if I want to "just edit some text", Eclipse is not a good > tool, for sure - I'll usually fire up TextPad, which launches in a > second or two. > > It would be cool if Eclipse were able to start up as "just an editor" > (with syntax-based chromacoding, e.g., but no > typesystem-based features) > - that is, if I could say "eclipse somefile.java" and have a > Java-colored GUI text editor in two seconds - but it seems like the > tradeoffs to get that kind of agility might be... um... significant.
Doesn't hurt to find out. This may not be significant for the Java world. But for the C/C++ world, this is actually a significant requirement and one that is obstructing adoption of Eclipse in our world. As such, it is a higher priority for some than others. The beauty of e4 is that it is giving us who have this as a higher priority a shot at actually trying to solve it. Doug. _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
