No subject

who use standalone clients in Java prefer this
deployment architecture because it keeps bandwidth
needs low and makes distribution a very easy process.

Every time I do a vlc update the user ends up getting
a jar that is around 9-10MB which is the combined size
of all the windows dlls thus my reason in the past for
asking about reduction in dll size. Since the dlls
need to be in the same folder I have to jar them
together. Thus the reason I wait a month or two before
trying new updates of vlc since it would be a big
download of 9-10MB.

Sorry about the long email but it was a long process
to get vlc bundled and the distribution issues
resolved. They (Sun) have never encountered anything
like what I did.

Regards,
Tony


--- Pierre d'Herbemont <pdherbemont at free.fr> wrote:

> 
> On Apr 3, 2008, at 8:48 PM, jboileau wrote:
> > Hi,
> >
> > I can probably help since I develop on Windows. It
> is true that there
> > is problem loading libvlc-control.dll on Windows.
> Personaly for the
> > moment I am reading the VLC install path from the
> registry, do a set
> > current dir to there, load libvlc and finally load
> libvlc-control (see
> > code below). This is the only way I have found to
> make it work without
> > problems.
> 
> Why don't you package libvlc and plugin with your
> own app?
> 
> Pierre.
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> http://mailman.videolan.org/listinfo/vlc-devel
> 



      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com