Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

garth914
Community profile garth914 Level 2
Job title here
Location here
8 BADGES
Level 2

Level 2

Learn more
Joined the community 21-05-2012 11:24:31 AM
Offline
Top badges earned by garth914
Customize the badges you want to showcase on your profile
Re: How to interact with an existing coralUI component?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Any word from the Touch UI team on examples of how to interact with existing Coral elements generated by the Granite types using the Coral API?

Views

4.5K

Likes

0

Replies

0
Re: How to interact with an existing coralUI component?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Thanks Scott! I was wondering about the difference between the granite/ui/components/foundation and granite/ui/components/coral/foundation folders. Is that particular 6.3/6.4 detail documented anywhere for reference?The documentation at Concepts of the AEM Touch-Enabled UI for AEM 6.3 still references granite/ui/components/foundation.I look forward to hearing the feedback from the Touch UI team!

Views

4.5K

Likes

0

Replies

0
Re: How to interact with an existing coralUI component?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
I agree with Stanleyor, this didn't actually answer the question.As noted in this thread, you can create new instances of components using the Coral API, but I'm not finding a way to initialize a Coral component from existing markup.My dialog uses the "granite/ui/components/foundation/form/select" script to generate the markup for a Coral select box.In my dialog-ready handler, how can I initialize a Coral.Select using this markup? The documentation doesn't appear to cover this.Is it possible? Sh...

Views

4.5K

Likes

0

Replies

3
Re: Icons not loading through CSS in AEM 6.3
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Plus, it appears that the clientlib which references the static resources needs to have @allowProxy set to true (as opposed to relying on allowProxy being set by an embedding clientlib).In other words, if clientlib_A embeds clientlib_B, and clientlib_B references static resources, clientlib_B must set allowProxy = true.It's not enough to rely on clientlib_A setting allowProxy and having that "cascade" through the embedded clientlibs. This turned out to be my problem.

Views

614

Likes

0

Replies

0
Re: Customizing Communities UI - How does We.Retail do it?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Perfect! Thank you, Ashok.

Views

341

Likes

0

Replies

0
Customizing Communities UI - How does We.Retail do it?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Hello everyone,I'm tracing through the source to figure out how the We.Retail communities site customizes its UI and I generally see how it's doing it, except for one key piece.In /libs/social/console/components/hbs/sitepage/sitepage.hbs around line 20, there's the following code:{{#if pageProperties.page-template}} {{include this template=pageProperties.page-template}}{{else}}...{{/if}For We.Retail, pageProperties.page-template is set to "weretail". This, in turn resolves to:/apps/social/consol...

Views

606

Like

1

Replies

3
Re: Can I move anchors generated by the parsys to the included component's ID attribute?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
Ratna Kumar wrote... Hi Garth, Thanks for reaching out to Adobe Community! There is nothing Out of the Box(OOTB) with AEM that will let you move anchors, but you can use Javascript to modify them. Refer this link: http://www.the-art-of-web.com/javascript/remove-anchor-links/ Thanks,Ratna Kumar. Thanks Ratna! That's not what I wanted to hear, but what I expected to hear. Oh well. Thank you for the response!

Views

343

Likes

0

Replies

0
Can I move anchors generated by the parsys to the included component's ID attribute?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
AEM 5.6.1 - I've long wondered whether I can remove the anchors which are generated by the parsys component (for enabling linking down the page) and redefine them as ID attributes on the included resource. The anchors are an unfortunate nuisance when trying to code CSS to handle contextual styling of adjacent components.I see that I can affect the attributes of a component by modifying the cq:htmlTag property, but that doesn't appear to be modifiable during runtime (unlike the option to get/set ...

Views

516

Like

1

Replies

2
Re: design cell path discrepancy between design_dialog and currentStyle.getPath
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
smacdonald2008 wrote... There is a StackOverflow thread that may help: http://stackoverflow.com/questions/19061568/using-currentnode-with-design-dialog Sadly, I don't think this helps me. I'm not trying to use a design_dialog as the sole source of configurable properties for the "quick-links-button" component, just for setting a common property that all the buttons will access. The component also has its own regular dialog for capturing all the properties specific to each instance. (All of which...

Views

264

Like

1

Replies

0
design cell path discrepancy between design_dialog and currentStyle.getPath
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
CQ 5.6.1 - In a nutshell, the design cell path generated by a component's design_dialog doesn't match the component's "currentStyle.getPath()". This makes retrieving properties,via...currentStyle.get(String name, T defaultValue)...always return the default value.I'm trying to figure out if this problem is a conceptual misunderstanding on my part, or a result of how I've set up my hierarchy, or a problem elsewhere.I have a component statically referenced on my page component with:In this "quick-l...

Views

421

Like

1

Replies

4
How does the automatic version numbering work in CQ5?
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
In other systems we've used, the given revision of a page progresses through the minor version (1.1, 1.2, .1.2), until a publishing event creates the next major version 2.0, at which point the minor versioning continues (2.1, 2.2, etc.).I'm trying to figure out what CQ's behavior is. I see that if no label is provided, the next revision is automatically set as the next minor version of 1.0. When I activate the page, it just creates another minor version. When will the page jump to v2.0?As a test...

Views

764

Likes

0

Replies

2
Re: CQ5.6.1 osgi bundle no longer running activate method
Avatar
Ignite 3
Level 2
garth914
Level 2

Likes

4 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Ignite 3
Give Back 5
Ignite 1
Give Back 3
Give Back
View profile
garth914
- Adobe Experience Manager
FYI, I'm using JDK1.7, and adding -XX:UseSplitVerifier helped resolve this same issue for me. Thanks!

Views

312

Likes

0

Replies

0
Likes given to
Likes from