|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Carousel BlogBlog Authors: Nathan T Freeman |
Welcome to the Carousel project blog
Nathan T Freeman |
|
Tags: 
swt
lotus911
nathan
carousel
|
Comments (1)
I decided that the easiest and fastest way to track feedback for the Carousel plugin, and keep people abreast of what's going on with it, is to have a project blog.
|
A tag is a keyword that is used to categorize an entry. To view the entries with a particular tag, click a tag name or enter a tag in the box.
The tag cloud indicates the frequency of tag use. Popular tags appear darkest. The slider control adjusts how many tags are displayed in the tag cloud.
1 Niklas Heidloff Permalink Hi Nathan, as you know I really like this carousel component.
Regarding the JSON library. You write you would want to use SNAPPS.
Why SNAPPS and not the one on openntf.org? What are the advantages?
Why haven't you used it directly? Is native LotusScript support for
JSON in 8.5 critical or do you think people can use the external
libraries?
You have a whole bunch of properties but I only see
tellNotesSelectedUNID and tellCarouselSelectedJSON being used. What
are the other ones for?
Both components are basically kept in synch as to what they
display. I saw that if you select another view entry the JSON
property is published, then the UNID comes back and then the JSON
property is published again. I assume that the logic you
implemented is in the carousel: if you get JSON for entry that is
already displayed don't do anything and don't publish UNID again
right? Is that how you avoid endless loops?
I couldn't find the Java code. Will you also make it
available?
I saw you removed certain design notes from the updatesite.ntf,
e.g. forms for features and plugins. Which ones did you remove? By
trial and error?
I understand the use case that you want to pass all configuration
to the carousel everytime the view entry selection changes. You
could also store the configuration in the comp app configuration/ca
xml. In CAE you can set these (static) advanced component
properties and then access them via Java API in your Eclipse
component:
http://www-128.ibm.com/developerworks/blogs/page/CompApps?entry=how_to_pass_context_to
Thanks
Niklas