I am currently doing a lot of work on Field Tool, but I do not have the time (and perhaps intelligence) to get my head around Transformations. I'm working towards a 1.0 release of Field Tool which aims to be completely backwards compatible with earlier releases by @jpetso. New features I've added will probably not be exposed to Transformations, mainly because I've no idea what a "transformations slot property callback" is supposed to do, but if you're using Transformations and Field Tool 1.0-beta2 was working for you, nothing in releases up to and including Field Tool 1.0 should break anything for you.

That guarantee does not hold for Field Tool 1.1 and later, so if you're working on Transformations (or anything else depending on Field Tool) please, please jump into the Field Tool issue queue and help out, or at least make your expectations known.

Comments

jpetso’s picture

jpetso commented

Hi Matthew, thanks again for taking care of Field Tool. I did not get back into developing Transformations, so I finally updated the project page to reflect that fact. I'm basically obsoleting Transformations because I moved on to other ventures, so don't hold back to take whatever direction you feel is best for Field Tool. As far as I know, my previous company's "successor module" for Transformations, Rules Transformers, uses Rules' built-in actions to access node fields, so this particular functionality of Transformations seems to get discontinued for now.

By the way, I discovered a new "Administer maintainers" checkbox in the project pages, so you can now add co-maintainers for Field Tool if necessary.

Matthew Davidson’s picture

Matthew Davidson commented

Hi Jakob,

I'm not sure how much additional functionality will get into Field Tool as it currently exists. @fago approached me a while ago about merging Field Tool with his Entity API for D7. I've not had time to look at this, or indeed any D7 stuff, but it does look like Entity API does a lot of the stuff Field Tool is intended to do.

At this stage I'm thinking that for D7 either what Field Tool does that Entity API doesn't (if anything) will get merged into Entity API, or maybe there'll be a smaller D7 Field Tool that depends on Entity API. Whatever happens, the future looks pretty darn cool.