How can I expose a multi-image field to the Views module such that different formatters can be used?

I’m building a custom query plugin for the Views module that uses JSON data from a web API, inspired by this article. I’ve created a series of field handlers that work fine.

However, I’m struggling with a field that contains an array of image URLs. I’ve worked out how to return the first image as an HTML <img>, or all of the images as a series of HTML <img>s concatenated together, but what I would like to do is expose the images in such a way that the user can choose how they are formatted (e.g. as a FlexSlider).

When a multi-image field from a Drupal content type is added to a view, the user is presented with a dropdown where they can select a formatter. Ideally I would like my multi-image field to work in the same way.

Does the render() function in the field handler need to return the images in a certain way? Or should I not be using the render() function, seeing as I don’t really want to specify how the field should be rendered?

expose your link to 1000000 active and real people for $9

Traffic comes from linkedin and google plus i will show screen shots of posting and other proofAs a bonus i will post 10 classified ads for you at classifiedadsAs a second bonus i will post your link and send it to 4750 classified pages, 2100 blogs, 250 search engines and back links, 300 directories plus 270 social bookmarking sites. 200 article sites and 180 pings.THIS IS GOOD FOR YOUR WEBSITE RANKING I will show proof of work.3RD and last i will create you a viral traffic network so you can make more sales Hi my name is Tim from Australia i work in marketing and i hope you are happy with my work.Also inbox me for a chat

by: Tim21
Created: —
Category: Traffic
Viewed: 216

is it possible to expose dataset sample data(exp first 10 rows) using atlas?

i am new to atlas and i am wondering if there is a solution making atlas expose, in addition to a dataset metadata, a sample data of this dataset ( 10 first rows for example).

for a purpose of data governance, the problem i am solving is that the metadata could not be so comprehensive functionally, and reading a sample data will make more sens to explain a dataset content.

if , actually, there is not a solution please help me find were should i invest my effort ( inner development within atlas, or treat the problem using a third party accessing hive,scoop or hbase directly to get the sample data)

thanks in advance

Should a high-performance API expose low-performance utility functions?

Context: I’m working on an open source project to solve a problem that comes up in ad-tech and social media data mining: indexing boolean expression trees, and matching them against incoming documents. It’s designed to scale up to several million expression trees indexed in memory, matching against hundreds of thousands of documents per second.

The expression trees that come in from the user need to go through some transformations before they can be inserted into the index:

  • Java tree nodes to JSON
  • JSON to C++ tree nodes
  • Tree reduction/simplification
  • Conversion disjunctive normal form (potentially O(2^N))
  • Removal of redundant minterms (O(N^2))
  • Conversion to an internal binary form

I want to encourage users to cache this binary form in case they want to add it again (ie next time their application starts up, or if it’s going to be distributed across several nodes). They would need to cache it in an external data store, since the library itself runs entirely in memory.

Right now there are two methods of adding a rule from the Java API:

// Alternative (A): two-step method byte[] rule = RuleDB.treeToBinary(...);   // static method to encode it (potentially slow) db.addRuleBinary(rule);                   // actually add it (quick)  // Alternative (B): do both at once db.addRuleTree(...); 

Version (B) is almost the same as A. The only difference is that it makes an extra copy of the buffer to pass it back to Java (where it will be GCed), and requires another JNI call. These costs are small compared to the cost of converting a rule, but if you’re adding 2 million rules and aren’t able to cache these intermediate buffers, then they’re still real costs.

I’m wondering whether I should provide (B) at all. It is potentially slightly faster, and a bit more convenient. However, I also want to encourage users to use alternative (A) where possible. Alone, (A) doesn’t do anything special, but it strongly suggests the rule can be cached so the user can make their own conclusions without reading documentation (which, let’s be honest, they probably won’t).

Add granularity year expose filter to a Search API indexed result

I have a search API views that I’d like to add an exposed Date filter so people can have a dropdown with only Year in it

is it possible to achieve that? what field should I index? (Post Created) and should I index that as “Date” ?

Also I can get the normal exposed filter to work on Date: node field but not in Search API views

Also almost similar issue here