# How to find information in 'Processing Core Javadoc'?

**URL:** <https://discourse.processing.org/t/how-to-find-information-in-processing-core-javadoc/7236>\
**Category:** Processing\
**Created:** [January 5, 2019, 11:12pm UTC](https://discourse.processing.org/t/how-to-find-information-in-processing-core-javadoc/7236 "2019-01-05T23:12:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![amaia](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/amaia/32/3012_2.png) [@amaia](https://discourse.processing.org/u/amaia)\
**Post date:** [January 5, 2019, 11:12pm UTC](https://discourse.processing.org/t/how-to-find-information-in-processing-core-javadoc/7236/1 "2019-01-05T23:12:54Z")

</div>

Hello:

In ‘Processing Core Javadoc’ I can read about IntList, PImage, or Table even if I don’t understand everything (I´m newbie…), but sometimes it is very difficult to find what I want  
Imagine the last scenario:

1. I’m reading in the reference about [createFont](https://processing.org/reference/createFont_.html).

2. I copy the example and run it .

3. Now I can see my font-list starts at index 479

4. So what I want is to look for information to change the index in printArray(fontList) and see the first font

5. I click on ‘[Processing Core Javadoc](https://processing.github.io/processing-javadocs/core/)’, but there is nothing that says _printArray_ in all classes… none that says _array_ ???; 🧐

6. Ahhhhh…okay, is that I’m in _CreateFont_.

7. I go back to the [reference](https://processing.org/reference/) to find [printArray](https://processing.org/reference/printArray_.html). There is nothing about my question, so I click again on the link ‘[Processing Core Javadoc](https://processing.github.io/processing-javadocs/core/)’…IT shows the same page 😶

This example is only one… I suppose it’s not easy to explain for newbies the structure of the javadoc… If you think so, the easy question is about the index of printArray  
In the end I always end up there, and then here, the last chance

Thank you and very happy for your help 😃 🙃 learning Processing, OOP and English at the same time!!

---

<div class="post-metadata">

**Author:** ![kll](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/kll/32/964_2.png) [@kll](https://discourse.processing.org/u/kll)\
**Post date:** [January 6, 2019, 2:13am UTC](https://discourse.processing.org/t/how-to-find-information-in-processing-core-javadoc/7236/2 "2019-01-06T02:13:26Z")

</div>

if you expected that that link on the reference header to  
[http://processing.github.io/processing-javadocs/core/](http://processing.github.io/processing-javadocs/core/)  
is a item specific link, we have bad luck.

but right, how to search anything in there?  
top middle you find the  
[INDEX] tab ( button)  
now can use the browser find [ctrl][f]  
and type in that little window

> printArray

you find it and it links to  
[http://processing.github.io/processing-javadocs/core/processing/core/PApplet.html#printArray-java.lang.Object-](http://processing.github.io/processing-javadocs/core/processing/core/PApplet.html#printArray-java.lang.Object-)

but i think this is even less helpful as

> **[printArray() / Reference](https://processing.org/reference/printArray_.html)**
>
> The printArray() function writes array data to the text area of the Processing environment's console. A new line is put between each element of the array. This function can only print one dimen…

if you want to see what is behind it:

> <https://github.com/processing/processing/blob/master/core/src/processing/core/PApplet.java#L4275>

---

<div class="post-metadata">

**Author:** ![amaia](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/amaia/32/3012_2.png) [@amaia](https://discourse.processing.org/u/amaia)\
**Post date:** [January 9, 2019, 1:08pm UTC](https://discourse.processing.org/t/how-to-find-information-in-processing-core-javadoc/7236/3 "2019-01-09T13:08:50Z")

</div>

Thank for the help: the way to look for information will be useful for me, I hope;)… the code is totally out of my reach, but thanks anyway  
I was watching your blog: very cool…