Scott,It's code that I'd seen in several other OOTB components, and I copied it verbatim. They never explicitly set the attribute, (e.g. request.setAttribute("list", list);), so I didn't either. I thought the code would work same as it did in the other OOTB components. It seemed that it was automati...

I have some code in a component where I'm trying to get the list from a request, and it always comes back null. Why is this happening? The other interesting, and probably related, thing, is that when I use a simple " <cq:include script="init.jsp"/>", I get the "Could not find init.jsp" error. When I...

Scott, thanks for the information, but I was talking about having a dialog where the author could either create a list that is a mix of images drug from the CF#, videos supplied by a service, or already located in the dam and selected through a search, and articles that are already a part of the AEM...

How can I allow authors to select other AEM pages through a  multi-mode dialog box, (i.e. use search to find the path to the other articles/pages they want to link), and then access the list using getProperty(), and hopefully, pull off the article/pages they selected as an object and retrieve its pr...

Thanks for the responses. smacdonald, I've seen the series that you linked, and it was my first exposure to developing components, but it is a rather simple example and I'm having trouble translating it to actual components with more robust requirements. I still don't quite understand how I'd change...

I'm a bit confused by the concepts of overriding, inheriting and composition to build components. It would seem that copying code directly from /libs/foundation would be strongly discouraged, (due to the issue that would result after upgrades), so I don't really want to consider that as as option. 1...

What I need to be able to do is the following:1) Retrieve a user supplied List from the component dialog that could contain images, videos and/or hyperlinked web pages from elsewhere on the site2) Use Sightly to take that list and create the correct <div> for the Slick carousel component, (e.g. <ifr...

Thank you so much!, (and to others who have shared ideas as well).

While I definitely do NOT want to recreate the wheel in any way, there should be some long term architectural advantages resulting from the use of Sightly. The components I build will be reusable Enterprise components, and will be built from granular building blocks of other generic components, (i.e...

Thanks to both of you for the responses. I hope the Sightly documentation on the Adobe site is enough for me to use the base component you linked to get this done. Hopefully, I can find most of the core functionality/logic in existing javascript libs.