Guymon

CSS Architecture in Views

How we architected the CSS for Views on D7  erklärt die CSS Struktur in Views und die Intention bei der Aufteilung auf die unterschiedlichen CSS Dateien.

For the CSS in Views, I went back to a proposal by Jacine Rodriguez: The Future of CSS in Drupal. In it, Jacine describes a method of breaking apart CSS declarations into files that target:

• The basic implementation of a module: positioning and layout, if any is needed
• Presentation styling: colors, fonts, border, backgrounds
• Styles needed to style to or override a specific theme: Seven, Bartik, Garland or Stark
• Styles needed to style to or override another module

Edit Content links in Views

Dan Linn zeigt wie man “Edit Content Links” in Views unabhängig von row style einfügen kann.

Using this method creates a handy little gear button when you roll over the content, with a link that says “Edit Content” when you click on it.

Anscheinend klappt das nicht nur mit der aktuellsten Version von Views. Das Feld “Edit Link” habe ich wohl immer übersehen

Neuerungen in Views 3

Tony Rasmussen beschreibt 5 Neuerungen in Views 3 die man zuvor selbst über diverse hooks vornehmen musste.

1. Create custom exposed form filters, via hook_form_alter() and/or hook_views_handlers()
2. Create “Sort By” exposed form fields.
3. Create aggregates by adding GROUP BY via hook_views_query_alter() or hook_views_pre_execute()
4. Create WHERE clauses what support OR via hook_views_query_alter() or hook_views_pre_execute()
5. Hack up the pager to match client comps

Neues UI für Views unter Drupal 7

Merlin of Chaos vermittelt schon mal einen Eindruck was mit Views 7.x-3.x passieren wird:

• View creation was replaced with a wizard, written by Peter Wolanin. Most of the wizard is entirely optional. With a couple of checkboxes, it can be reduced to what you get now. Alternatively, with the checkboxes you can create a simple view (a la simple views) that does a lot of the basics, just by making some simple choices. Then you can immediately use the view, or go into the editor and tweak it. Plus, this wizard is plugin. That’s right. Make more wizards.
• A lot of terminology has been changed or updated to try to match Drupal core usage, or to be more obvious. I think this will be a little tricky for users entrenched in the current UI at first, but it’s not difficult.
• Someone with artistic skill spent a LOT of time providing a clean look and clean CSS for the new system, and it was designed to look right at home in Seven. Sadly right now it looks bad in Bartik, but we’re hoping we’ll get some contributions to clean that up.
• The live preview was integrated more fully into the editing experience. In many cases, you can go to the preview, use the contextual links and add things in ways that make a lot of sense to people unfamiliar with the system.
• The entire UI has been reorganized to try and bring forward the things everyone wants to use right away, and push to the side (but not actually hide) the things that you don’t need until you’re more familiar with the system. So fields and filters are front and center, but relationships and arguments are a little deeper in.
• The edit area that often fell below the fold has been replaced by a modal.
• Lots and lots and lots of streamlining and simplification to forms everywhere.
• Real templates, which are different from default views, have been introduced. The only difference between a template and a default view is that you never activate a template. You literally only start with a template and tweak it, much like you would in Word or any other application like that.
• An attempt to smooth out issues with overriding settings has been done. I think we may still have a way to go here, but I won’t know for sure until it’s been out there for awhile and I’ve received a lot of feedback from people in the wild.
• Views now integrates more tightly with CTools, and it uses CTools export.inc (and partially uses its export UI tool) which means that Views no longer has its own exportable mechanism. It should be able to more tightly integrate with anything that utilizes this, such as features, and CTools’ bulk export tool.

Drupal: Views Slideshow 3.x

Ein Posting auf LongLake erklärt die Änderungen in Views Slideshow 3.x. Da hat sich einiges getan, sehr cool!

The biggest change you will probably experience is the change in the widget management. Widgets are the bits and pieces that are NOT the main slideshow frame, for example pagers are such widgets. But you can also implement widgets that simply show the progress of a slideshow - nothing can stop you now, its really, really easy.

Now custom modules can implement different widget related hooks both in PHP and in javascript to declare their control, or progress display. In contrast to the old views slideshow code, where you practically had to duplicate the whole slideshow code, now you only define widgets.