|
Re: EPF All practices library [message #1417667 is a reply to message #1404532] |
Fri, 05 September 2014 21:38 |
Bruce MacIsaac Messages: 61 Registered: July 2009 |
Member |
|
|
Hi Philipp,
I recommend reviewing the getting started materials here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W6b0a089a62f3_4493_bcc1_ebe60a2ebb41/page/Getting%20Started%20with%20RMC
However, be aware that this getting started material is for RMC, most of it is relevant to EPF Composer as well, and certainly the basics of plugins, categories, and practices is the same, which is where you appear to be struggling. In particular, try the tutorials, especially this one to create a practice:
http://publib.boulder.ibm.com/infocenter/rmc/v7r5m0/topic/com.ibm.rmc.tutorials.doc/learning_labs/practices_abstract.html
To briefly answer your questions:
1. The packages for the method plug-ins are done by naming the plugins using a "." notation.
For example: practice.hello.base and practice.hello.extend will appear in the tree as being two plugins named "base" and "extend" nested in a package "practice > hello"
2. A practice is a kind of method guidance.
Once you have created a practice, then right click on "method content > content packages" to create a package. Then right click on the package to create a practice element.
3. I don't understand your last question.
However, some facts that may help:
a. A published website is self-contained - all links made between elements in a library become links between files in the published website.
b. To publish a website, it needs to have a configuration that selects the plug-ins. The configuration must also have a "view" assigned, which is a custom category that you create that lists the elements you wish to appear in the treebrowser used to navigate the published site.
Hope that helps
Cheers,
Bruce
|
|
|
Powered by
FUDForum. Page generated in 0.03143 seconds