Hi all- as you may already know, The Google Summer of Code is about to get started for 2010. At the moment we are trying to come up with ideas that students can craft proposals around, and I was hoping that we could get a few Views related proposals. IMO- nothing can raise your community profile, outside of working a lot on core, like Views related work, and it also happens to be one of the most marketable skills within the thriving Drupal ecosystem. So- it would be great if we could get a couple of Views related projects proposed.
Please, please, please, if you have any ideas for how a student could spend three months working on views related tasks, please add ideas to the Google Summer of Code Group (and consider mentoring as well- it's an awesome way to help out, meet up and coming developers, and increase your standing within the community).
dereine already put forth a few ideas for backends for Views as a wiki on SoC group (http://groups.drupal.org/node/57168 ), which is quoted below. Because that post is a wiki I thought we could move the discussion for his proposal to this thread.
Thanks for chiming in and helping out!
Overview: Since the query part of views is pluggable there could be created connections, for examples to a lot of services of the web 2.0
Description:
Some examples of services/apis which could be included
* RDF
http://en.wikipedia.org/wiki/Resource_Description_Framework
* XML
http://en.wikipedia.org/wiki/Xml
Availible informations about it: http://wiki.developers.facebook.com/index.php/Fql.queryAdditional views could be used to import data with feeds. Then feeds could import from facebook, for example.
Mentors:
Difficulty: Medium
Comments
Since views3 is totally
Since views3 is totally pluggable other plugins could be created as well.
Pluggable systems which has not real implementation yey:
Figure out some pager systems from scalable platforms like facebook etc. and implement them.
Since views3 header/footer/empty text is pretty much the same. There things can be embedded: For example every ctools content type could be included by writing a handler.
Additional views could get some help as well:
Afaik i know a bit about views, so i could try to help mentoring.
Ajax Load
I like the idea of implementing Facebook-style pagers.
The first 5 or 6 rows are visible on load. As you scroll down, "?page=1" loads.
Or twitter-style pager:
Click the "more" button, and "?page=n+1" loads.
Also Amazon-style:
Content doesn't appear until that area is visible in the browser (i.e. similar to Facebook-style pager, but no content is visible at first). This is useful for blocks, regions, attachments, panel panes, etc.
Haven't played with Views3 yet, but I would bet this is still applicable: while the AJAX pager is really great, it's fairly one-dimensional at present. What if you could load the Argument view or filters in a block, and have the #content (or other selectable element) change when a new argument is clicked, or new filters are selected?
Ryan Price
DrupalEasy Podcast
If my affiliate proposal
If my affiliate proposal doesn't pull through, I would be interested in a views related project.
My Drupal work always includes Views (and I've written a fair share of custom handlers), so it could be fun.
http://groups.drupal.org/node
http://groups.drupal.org/node/57223 went to a total different project :)
But it would be cool if someone wants to work on query plugins.
@bojanz
Did you created some views handlers/plugins already? But it wouldn't be hard to learn.
good idea
This is a good idea. Wish I would of thought of it :D but if you need help I am happy to even if I am not an official GSoC student.
Monster Energy DRINKS!
@dereine Yes. Did it first
@dereine
Yes. Did it first when developing image_upload (http://drupal.org/project/image_upload)
My newest project (soon to be launched, depending on the client and his designer) is/was a video sharing site, where the video is associated with a server and a game (one game can have multiple servers). All users have profiles where they select the servers and games which they want to follow, and the views are automatically filtered through two handlers:
One limits the content to the user's servers+games, the other limits it to the user's username (a taxonomy field in his profile) as well as servers+games (the second one is used for special views where the user wants to see activity that concerns him directly).
It's been an interesting project, I hope to write a showcase once it's live.
I did find the views documentation to be fuzzy and unhelpful (I gave up once and just read the source code. The existing handlers for core modules were the most helpful), I promised myself I would write some tutorials once I find the time.
Sorry for the long post, I tend to do that.
I have enthusiasm, but I don't really know what I would do on views (the posted ideas look nice), with a patient mentor I could do some nice work...