Is there a method summary (and explanation) for IBM Plugins?

Would be nice if you could share if you have time (If you did not already). Finding around in the APIs is very tough for everyone. So that sounds familiar 8D

Ok, I try to explain that (English isn't my native language so don't judge my use of english :P )

1: I've installed a local RTC Server and an Eclipse with RTC

2: Now it's all about backtracking and reverse-engineering.
The best way to find what you've searching for is watching the main system.
Let me explain that:
If I wanna get some Iterations for my Widget, I best search in "Manage this ProjectArea --> Timelines" because there the server triggers his commands (Now you have to catch them.)

3: I've installed FireBug on my Mozilla (Chrome has something similar) to have a better view of the console etc.

4: Now I have to go to the "NET"-Register in Firebug to watch, whats comming in, and whats going out.
E.g. "GET projectAreaByUUIDWithLimitedMembers"
If I watch the full Link, I see its a child of process (com.ibm.team.process) so I might try the "ProcessClient" class.

5: How to proof I need the "ProcessClient" class.
Console.log it to see ALL of it's methods. But Parameters only called args.
(That's the next problem)
Go Back to the NET-Tab an watch there:Params

Tadaaaa, now i can build my request.
args = {
  maxMembers: number
  processAreaItemId: UUID of PA
}
ProcessClient.projectAreaByUUIDWithLimitedMembers(args, ServiceResponseHandler)

Antoher good trick is the "Debug=true" function.
This allows you to see ALL the loaded scripts in clear-text!
And you also can set BreakPoints and step throught server-intern methods.

Thanks for the explanation.

In https://rsjazz.wordpress.com/2013/03/20/understanding-and-using-the-rtc-java-client-api/ and other blog posts, I explain how to find the API with Java and the SDK installed. This allows finding the Java code and the interfaces the service/client library classes provide. The benefit is, that you can find the client libraries for example, because they are all retrieved using the

getClientLibrary()

this approach works, but it takes a LOT of energy and skill to navigate the large amount of code and missing design information to find something that helps you.

I totally agree with Sam. The most challenging about this approach is that the source code documentation within the SDK is very poor. I personally have learned the most from looking at the unit/integration tests included and from Ralph's blog.

If IBM wants to push their platform, they have to put a lot of work in documentation improvements.

There is a lot of pressure on new features. We are looking into public API's that should be available (also new API) and officially supported, but it takes time.

The only officially supported API right now is where we have JavaDoc for in the Plain Java Client Libraries.

With respect to the SDK, I am torn. On the one hand operational behavior is sometimes the only viable solution. On the other hand we have seen in the past users customizing our tools to an extend where they rendered useless. So, the SDK API so far is considered 'use at own risk'.

However, we are aware that it is sometimes essential. That is why some of us blog about the API to compensate for the lack of documentation.

What do you want to achieve?

 Relatively simple...
I have to gather all "Timelines" (Especially the Main Development) from a specific Project Area.

This should be:

        IDevelopmentLineHandle[] developmentLineHandles = projectArea
                .getDevelopmentLines();

It should be on my blog in the DevelopmentLineHelper, I think.

This can't be what you are looking for. I think you look for the project Area. You could iterate all project areas to find the one you need. E.g. like in http://rsjazz.wordpress.com/2012/12/09/analyzing-a-aroject-areas-members-and-roles-using-the-plain-java-client-libraries/

notice he is using JavaScript.