Creating a library that has only pde files

neurogami

Creating a library that has only pde files

in Library and Tool Development • 3 months ago

I have some code that I find myself reusing in many different sketches. It's a .pde file defining some OSC (Open Sound Control) handling.

I'd like to turn it into a library that I can just reference from any sketch that needs it, but I ca't find anything that shows how to create a pde-only library and how one would reference that from a sketch.

Is this even possible?

How would I do this?

Thank you!

James

Replies(5)

GoToLoop

Re: Creating a library that has only pde files

3 months ago

Perhaps this wiki link can guide you thru' it:

http://wiki.processing.org/w/Create_Libraries

neurogami

Re: Creating a library that has only pde files

3 months ago

I looked at that already, and it describes using Java, generating class files, and jarring them up. I saw nothing about creating a library using plain Processing code. It keeps referring to having code inside a package.

Perhaps I missed it. Is there a section on creating libraries without a Java classes or a jar, just pde files?

GoToLoop

Re: Creating a library that has only pde files

3 months ago

I've never delved into any of that advanced stuff.

But I'm pretty sure a Java library must be compiled and packaged!

Lest you wouldn't be able to use import keyword to use it.

Another option is copy & paste each class of your "library" in other tabs

w/ the same name as the class itself ending w/ .java.

Like some snippet code you add to your programs.

quarks

Re: Creating a library that has only pde files

3 months ago

It is not possible to create a library from pde files.

A library executable is a jar file!

You could import the pde files through the IDE then it would just add them to your sketch.

neurogami

Re: Creating a library that has only pde files

3 months ago

You could import the pde files through the IDE then it would just add them to your sketch.

That's exactly what I'm trying to avoid. I don't want multiple copies of the same code spread across numerous projects.

Top Reply