Skip to main content
Participant
December 23, 2009
Question

Cairngorm 3 & Side effects of Parsley new releases

  • December 23, 2009
  • 2 replies
  • 1120 views

May be I sound like a noob. But I am curious to know that does any new releases of Parsley effect the current infrastructure of Cairngorm 3 ?

Do we always have to point to a specific version of Parsley to utilize the libraries provided by Cairngorm 3 OR the libraries in Cairngorm 3 continue to work with future releases of Parsley.

Thanks,

MD

This topic has been closed for replies.

2 replies

February 22, 2010

I've had some luck getting navigation 0.2 working with parsley 2.2 by tweaking com.adobe.cairngorm.navigation.landmark.AbstractNavigationDecorator. The attached modded class circumvents several changes in the parsley API and avoids issues with the landmark related tags like [Exit].

It's by no means a complete fix - but the way i managed to get the landmark enter/exit functionality to run without throwing errors

Inspiring
February 22, 2010

Nice one. Thanks for posting your fix.

Inspiring
February 5, 2010

Some of the "Cairngorm 3" libraries don't have a dependency on Parsley (such as Observer and PopUp) and so don't break when you upgrade to a new version of Parsley. Others (such as Navigation and Module) do have a dependency on Parsley and may break when you upgrade Parsley. For example Navigation 0.2 doesn't work with Parsley 2.2 since the extension API has changed in 2.2. The good news is that much of the functionality that the Integration library provides is out of the box in 2.2 so you probably don't need Integration any more.

If I was you I'd think hard before using the "Cairngorm 3" libraries that have a dependency on a specific DI implementation.