See #396380: Enhance Views to support proper GROUP BY queries. Looks like Views may soon incorporate this module's features?

I ask because, if there is no differentiation, further work on Views Calc will just duplicate other efforts.

Comments

aren cambre’s picture

http://drupal.org/node/649642 says Views 3 goes to beta in spring 2010.

karens’s picture

Status: Active » Fixed

No, there are a number of other things this module does, it creates custom calculation fields, adds css to right-align number columns, and more, it does much more than add in aggregation.

Plus this module has been in use for a couple years and there are people depending on it, so we can't just pull it.

Is this really critical, asking if this should be abandoned only a couple weeks after another module adds in some overlapping code? I haven't even had time yet to see how much duplication there is.

karens’s picture

Also, those new features will only be in Views 3, which doesn't even have an official release yet. People using Views 2 will still need everything this modules does.

aren cambre’s picture

Title: Should Views Calc be abandoned? » Should Views Calc be superseded by Views 3?
Priority: Critical » Normal
Status: Fixed » Postponed

I haven't even had time yet to see how much duplication there is.

Then let's postpone until Views 3 beta?

Look towards the bottom of http://drupal.org/files/issues/group-by_0.patch. It's gonna do group, count, sum, avg, min, and max, which is all that views calc appears to do, too.

Sorry about "critical"--inadvertent. And sorry if I'm being aggressive, but you do so much good work on so many modules that I was trying to help you by pointing out where your load could be relieved.

karens’s picture

Title: Should Views Calc be superseded by Views 3? » Create new version adapting to Views 3
Category: support » task

See the project page for Views Calc: "You can also create custom dynamic fields that can be used in any view using SQL snippets like CONCAT('field_first_name', ' ', 'field_last_name') or DATE_FORMAT(node.created, '%m/%%d/%Y'). The custom fields are set up in admin/settings/views_calc."

It doesn't appear the new patch to Views does anything about that, nor does any other module I've seen, and many of the people using this module use it for that feature.

I need to keep the current version available for people using D5 and Views 2 for D6. We can leave this issue open because I need to create a new version to work with Views 3 that removes things that Views does and adapts the rest to work with the new Views code.

aren cambre’s picture

Title: Create new version adapting to Views 3 » Create new Views Calc version adapting to Views 3

Clarifying title because it appears in another issue.

jpstrikesback’s picture

Really looking forward to a version that works with views3, does anyone have an idea of what is required to update this to work with views3? If there was a todo list I would do my best to help.

podarok’s picture

+ subscribe

danny englander’s picture

subscribe

luco’s picture

+1

miro_dietiker’s picture

Subscribe this.

We might take the ball and help to port Views Calc. Still depends some final customer needs and possibly funds provided.

karens’s picture

@miro_dietiker, that would be much appreciated :)

DaPooch’s picture

subscribe
+1

khosman’s picture

subscribe

miro_dietiker’s picture

Status: Postponed » Needs work

We have an initial working 6.x-3.x and a 7.x here.
Will take some more days to commit and make em available to you all.

shags_j’s picture

+1 subscribe

roball’s picture

Does views_calc 6.x-3.x-dev work with both Views 6.x-3.x and 6.x-2.x or just with 6.x-3.x?

roball’s picture

Title: Create new Views Calc version adapting to Views 3 » Support for Views 2 & 3
Version: 6.x-1.x-dev » 6.x-3.x-dev
Component: Code » Documentation
Category: task » support
Priority: Normal » Major

Please can you just clarify which version of Views Calc supports which version of Views?

karens’s picture

Issue summary: View changes
Status: Needs work » Closed (won't fix)

The D6 version is no longer supported.

Pierre.Vriens’s picture

Status: Closed (won't fix) » Needs work

Undo last comment ... Anybody (like Miro?) who can answer the question in #17?

miro_dietiker’s picture

Status: Needs work » Closed (won't fix)

Uh that's like YEARS ago...
If i remember properly, 6.x-3.x was started to create a branch that is compatible with views 3.x... By then this was a common pattern to deal with the Views situation.

The whole 6.x world just feels like from a different age and i'm pretty disconnected from it due to our primary Drupal 8 focus.
And yeah, see KarenS statement.

Pierre.Vriens’s picture

Thank you Miro. Just in case you wonder where my previous comment originates from: checkout #2198015-37: Support D6 for as long D6 core will be supported, and look at the current D6 usage statistics.

The question I keep asking myself: what to do with the 6.x-3.x-dev version (used in 139 sites)?