Re: [jug-discussion] Eclipse question

2004-09-01 Thread Eddie Dimond




I have a book at home titled "Contributing to Eclipse: Principles,
Patterns, and Plugins". It was written by Eric Gamma and Kent Beck.  So
far, I've only read the intro and part of the first chapter but, based
on that small sample, it looks like a thorough example-driven
explanation of the plugin development process.

William H. Mitchell wrote:

  At 09:50 PM 8/31/2004 -0700, Tim wrote:
  
  
Is there a "quick and dirty" tutorial on creating plug-ins so I can start to
understand this code without reading the 979 page PDF on plug-in
development?

  
  
I think I recently saw a book on Eclipse plug-ins at B&N on Broadway.  It
might be (via Amazon search) "Eclipse: Building Commercial-Quality
Plug-ins" by Clayberg and Rubel.  (It's only 800 pages!)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  






Re: [jug-discussion] Eclipse question

2004-09-01 Thread Dennis Sosnoski
Dennis Sosnoski wrote:
Hi Vincent,
Not sure if we've met or not - I'm up in Seattle, but get down to 
Tucson periodically. I'll be there for this month's meeting for a 
short presentation on SWT. ...
Shucks, caught by the reply-to. I meant to send direct to Vincent...
Tim, for the plugin help a lot depends on what you want to do in your 
plugin. There are some related articles linked from the Eclipse site, 
including one on the PDE (Plugin Development Environment): 
http://www.eclipse.org/articles/Article-PDE-does-plugins/PDE-intro.html 
The actual PDE documentation included with Eclipse covers the basics 
(Help/Help Contents/Platform Plug-in Developers Guide and PDE Guide), 
and with the wizards provided it's easy to create basic plugins of 
several flavors. I've found the learning curve gets very steep once 
you're past the basics, though, especially if you're picky about how you 
want things to work.

On the book topic, I've got the "Eclipse: Building Commercial-Quality 
Plug-ins" one. It looks pretty good to me, though I haven't dived into 
the in-depth plugin development parts yet.

 - Dennis
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: [jug-discussion] Eclipse question

2004-09-01 Thread Tim Colson
> I think you are thinking of Simon -- he's the man that knows 
> about writing Plugins and using SWT.  
> Unfortunately he is off 
> to New Zealand for a couple weeks, so it looks like you get 
> to read that big PDF.

Crikey. No shortcuts for me. :-(

I probably won't have finished reading the doc before Simon returns. ;-)


> For your CVS issue, you might try the Filters option on 
Yeah, already did that. ;-)

"The filter by name *.CVS did the trick too, but again, seems like I might
be
missing something. I looked in the preferences:Team:CVS but found no love
there."


> I have searched my configuration and 
> don't see anything special that I have set up to exclude the 
> CVS files, but they do not show on my system.

Thanks... it's really kind of odd. 

I'd check the project out directly with Eclipse... except I'd like to be
able to use any editor/ide interchangeably, and I have a LOT of projects
already checked out that I would like to leverage.

Cheers,
Timo

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [jug-discussion] Eclipse question

2004-09-01 Thread Tim Colson
> I think as long as the project is shared, eclipse won't show 
> .CVS.  The 
> only time you'll see them if i'm right is if you check out a project 
> from cvs using a cvs client other than eclipse and create an eclipse 
> project based on those files.  Tim, if that's basically how 
> you ended up 
> with your project, you'll probably want to right click on 
> your project, 
> team -> sharing and enter your cvs information or something 
> along those  lines.

Andy hit the nail on the head. I did exactly that, checked it out with
WinCVS, then imported it into Eclipse. 

So I tried the Team sharing... Eclipse automagically determined the CVS
server settings, allows me to update from the repository. :-)

But -- it didn't make the .CVS packages go away in the Package explorer.
:-(

It took me a little bit, but I found that the change flag ">" and "(ASCII
-kkv)" at the end are configurable in the Team preferences. 

Timo -- riding low on the Eclipse learning curve. 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jug-discussion] Eclipse question

2004-09-01 Thread Andrew Huntwork
[EMAIL PROTECTED] wrote:
For your CVS issue, you might try the Filters option on Package
Explorer title bar pull down menu (the little down arrow).  It has a
bunch of options to control the types of resources that display.  I
have searched my configuration and don't see anything special that I
have set up to exclude the CVS files, but they do not show on my
system.
I think as long as the project is shared, eclipse won't show .CVS.  The 
only time you'll see them if i'm right is if you check out a project 
from cvs using a cvs client other than eclipse and create an eclipse 
project based on those files.  Tim, if that's basically how you ended up 
with your project, you'll probably want to right click on your project, 
team -> sharing and enter your cvs information or something along those 
lines.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [jug-discussion] Eclipse question

2004-09-01 Thread William H. Mitchell
At 09:50 PM 8/31/2004 -0700, Tim wrote:
>
>Is there a "quick and dirty" tutorial on creating plug-ins so I can start to
>understand this code without reading the 979 page PDF on plug-in
>development?

I think I recently saw a book on Eclipse plug-ins at B&N on Broadway.  It
might be (via Amazon search) "Eclipse: Building Commercial-Quality
Plug-ins" by Clayberg and Rubel.  (It's only 800 pages!)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jug-discussion] Eclipse question

2004-09-01 Thread Dennis Sosnoski
[EMAIL PROTECTED] wrote:
I think you are thinking of Simon -- he's the man that knows about writing Plugins and using SWT.  Unfortunately he is off to New Zealand for a couple weeks, so it looks like you get to read that big PDF.
 

Hi Vincent,
Not sure if we've met or not - I'm up in Seattle, but get down to Tucson 
periodically. I'll be there for this month's meeting for a short 
presentation on SWT.

Two things caught my attention in your reply: I'm interested in what 
people are doing with SWT/Plugins, and also in moving to New Zealand. 
It's unclear from your reply if Simon is with your company or you just 
know him, but if it's the same company can you tell me anything about 
the work you're doing with SWT/Plugins, and also if you have business 
contacts with New Zealand?

Thanks for any info,
 - Dennis
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [jug-discussion] Eclipse question

2004-09-01 Thread Vincent . Greene
I think you are thinking of Simon -- he's the man that knows about writing Plugins and 
using SWT.  Unfortunately he is off to New Zealand for a couple weeks, so it looks 
like you get to read that big PDF.

For your CVS issue, you might try the Filters option on Package Explorer title bar 
pull down menu (the little down arrow).  It has a bunch of options to control the 
types of resources that display.  I have searched my configuration and don't see 
anything special that I have set up to exclude the CVS files, but they do not show on 
my system.--- Begin Message ---
So after a bit of work, I've got Eclipse 3.0 running, compiling and building
the TimTam plugin.

I've got some newbie questions which I'm sure Vince will be happy to answer.


Is there a way to magically hide all of the *.CVS entries in the src tree? 
Note: I created a working set, but that seems like the long way around. The
filter by name *.CVS did the trick too, but again, seems like I might be
missing something. I looked in the preferences:Team:CVS but found no love
there.

Is there a "quick and dirty" tutorial on creating plug-ins so I can start to
understand this code without reading the 979 page PDF on plug-in
development?

Thanks,
Tim




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--- End Message ---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]