I've set this issue up primarily to keep track of the D7 version of the D6 issue: #382394: Apply ajax pager effects.

I realize its not a huge issue, and for most a non-issue, however as I need this functionality for a project I'm currently working on, so here I will do my part. Follow along if you like, I'm expecting first patch rolled against dev by the end of this week.

Goals:
1. Finite set of "preset" transitions - based off current transitions available
2. Custom transition field - to manually create or even chain transitions - based off current transitions available
3. Some method to allow use of additional plugins (may become part of #2)

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Closed (duplicate)

Please keep one version, otherwise you really get crazy just by managing all issues.
If the patch is ready for d6 and is committed it can be worked on 7.x

Xomby’s picture

Xomby commented
Priority: Normal » Minor
Status: Closed (duplicate) » Active

@Dereine, by putting fixes for multiple versions into the same thread, especially when we're going between core versions, you AND your users are going to go MORE crazy trying to keep things organized within the thread, especially as we move between rolling patches against dev and non-dev versions.

In the effort to keep everything organized, and as non-crazy as possible, and as this REALLY IS a separate issue, as it is for a completely different version, I suggest that this be kept separate.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Closed (duplicate)

Well patches/feature requests are written against a specific version, get some review, get committed and then get backported to previous versions or port forwarded.

This is true for both drupal core and all contrib modules,
i don't see why this issue should be handled special.

If you want to have examples look for any bug in drupal 8.x

Xomby’s picture

Xomby commented
Assigned: Xomby » Unassigned
Status: Closed (duplicate) » Closed (won't fix)

Patches typically don't work cross-version, as code moves around, other changes are made in the meantime, etc, as even "fixed" things tend to break as the thread shifts between different versions.

Once the thread has "moved on" to the next version, going back to a previous one just jumbles the different versions together. Honestly I think its pretty stupid to try to confine multiple version issues to the same issue. If all you care about is keeping the issue count down, I can understand. But you're far from keeping it "simplified" in any way. You're also alienating fresh eyes and new ideas because you're so stuck in your ways, thinking it organized, when it's really just adding complication to a very simple process.

Same issue + separate version = separate solution .: separate issue

It's not a difficult concept, but your approach to this specific issue is perhaps an indicator of why progress is so difficult.

Ultimately, maybe things like this are best set up in a separate module anyway, as it's an aesthetic addon only.

praneeth87’s picture

praneeth87 commented

Any update on this feature for d7?

Fidelix’s picture

Fidelix commented

Maybe the other issue should be set to 7.x-3.x, and after it gets a patch, it would be ported back to 6.x