🚀 go-pugleaf

Richard Wilkman wrote:
> 
> Ross:
> 
> In 2.0, if you place your images as nodes in the project they will be
> copied into the outpath as members of the package.  Outpath and
> classpath are, effectivly, the same thing.  You can also store all
> your images in a folder in the project and have them copied.  The plus
> for having the folder is that the folder shows up in the deployment
> wizard and you can archive it all up in one shot.
> 
> -Rich
> 
> Ross M. Dukeshier wrote:
> >
> > St�phane Bonnet wrote:
> > >
> > > .. when starting the application from MSDos Prompt
> > >
> > > hi,
> > >
> > > what a surprise !!!! for the first time today i tried to start from the
> > > DOS windows one Java Application, already compiled under JBuilder.
> > >
> > > And then... all my icons, displayed within JLabels are not visible. No
> > > exception is raised, we just can't see them. Anyone has any kind of idea
> > > of same experience ? I'm using JDK1.1.6
> > >
> > > Of course, when i start the application with JBuilder, no problem,
> > > everything is perfect... But i need to start from DOS...
> > >
> > > Thank you very much for your help...
> > >
> > > Stephane.
> > >
> > > _______________________________________________________
> > > Stephane Bonnet
> > > _______________________________________________________
> > > Address -> Mikontalo C 155, 33720 TAMPERE, FINLAND
> > > Mobile  -> (+358)(0)40 7270601
> > > E-mail  -> steph@cs.tut.fi, bonnet@tre.ntc.nokia.com
> > > Web     -> http://www.cs.tut.fi/~steph
> > > _______________________________________________________
> > A little insight, I hope.  My group had this problem about 2 weeks ago.
> > What we figured out was that JBuilder's project looks in the project
> > directory for the images (if you are using a relative path).  When you
> > run it for real, however, Java, as at least I would expect it to, looks
> > in your classes location.  Putting the images location in your classpath
> > is one solution, but if/when you deploy it, you will probably want them
> > with your classes rather than having to set up special directory
> > structures so they'll be found.
> >
> > Since we kinda wanted to see the GIFs in the designer as well as when we
> > ran them, we set our source and classes locations for the project to the
> > same directory and may also have set the convention that the project
> > would include only java files for the package it was named for (i.e. one
> > project = one package).  That way, the package and the classes location
> > are the same so JBuilder and Java will both speak the same language, so
> > to speak.  I suppose you could set the source to a different location...
> >
> > Hope it helps...
> >
> > Ross Dukeshier
> 
> --
> 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Rich Wilkman
> Senior Quality Assurance Engineer
> Borland JBuilder Team
> 
> If you see something that looks like an opinion up there,
> it's mine and mine alone.
> 
> Mail sent to me from the newsgroups won't bounce but will
> be ignored.  If I have time, I'll respond, but you  have
> a better chance if you confine your posts to the newsgroups
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The project directory was the absolute last place I expected JBuilder to
look - I only figured out where it was looking by accident.  Since the
project could be anything and not necessarily even in the same path as
the source, having it there doesn't make much sense to me.  The only way
it makes any sense is if you do it the way it should be done (put the
source path as the project directory) rather than the convention
JBuilder seems to push (myprojects, myclasses directories).  

What you're saying makes some sense, I suppose.  But, unless I missed
something along the way, when I run the application (through JBuilder or
otherwise) I still won't have them displayed.  I added the images to the
project but they didn't move to the classpath during normal operation
(e.g. telling it to execute the application).  Bottom line is that Java
is going to look for them with your classes whether you're using
JBuilder or not.  Going that route, I'd have to deploy it just to see
the real appearance.  

My preference would be that it let me store them with the source (not
the project) and have it move them to the classpath as if they were
compiled entities.  Put the same restrictions on them as Java did the
source - make it follow the right directory structure so it translates
well (designer and Java would either both find it or both not find it).
The biggest nuisance to me (other than the significant bugs that make it
difficult to use the designer like the "red beans" and Proxies) is when
I do one thing in JBuilder and get different results in Java.  To me,
that's a bad thing under any circumstances.  
  
On that note - any way to get JBuilder to show me a JTable and header in
the designer (as if it were running)?  I've tried many things, but it
just doesn't seem to want to show me it.

Ross