By ica on
Here is a contribution I like to share with fellow Drupallers.
- A method to wrap Google customised content around Drupal!
- Go to your Google 'Personalize Your Homepage' section
http://www.google.com/ig/directory
Find out the content you want to use
Weather GMap, Date & Time, Daily Horoscopes etc.
Google makes avaliable the (source code to public). get the source code from the link below the Google 'module' copy and paste i-ts an XML code (modify the code to your taste, your template and location in terms or Gweathermap)
Go to your Drupal Blocks
add new block -paste the code to Block body: choose (Full HTML)
choose the Block location, save and activate your block
Thats it
I hope further 'hacks/how to do's' examples will be shared on this
Comments
Very interesting
Many thanks !
Bertrand
Further info -Google Modules/Plug-Ins Developer links
Google modules contributed by third party developers, so the further 'Gmodules' 'Plug-ins' submitted to Google possibilites and hacks will grow, so the possibilities to hack/wrap them into Drupal
API - Plug ins, modules
http://www.google.com/apis/homepage/
http://desktop.google.com/plugins/
Google Modules forum
http://www.googlemodules.com/
Todo list hack
http://www.lifehacker.com/software/google-modules/index.php
http://microsoft.weblogsinc.com/2005/12/22/unofficial-google-modules/
Would like to see further Google Modules ideas implemetation/hacks to Drupal :)
An example 'Gmodule' implementation "Send a Free Text Message"
implementation of "Send a Free Text Message"
author="Ryan Jones"
http://www.txt2day.com/
get the XML code here
http://www.txt2day.com/txt2day.xml
+ copy
+ add a new Block into Drupal
+ Paste ~take off (-)'s
+ save
let me know it works for you
Another Gmodule implementation Yahoo! Weather Module
Homepage: http://www.howforge.com/product/yahoo-weather
Author: Sugree Phatanapherom
get the Code +Screenshot
http://base.google.com/base/items?oid=4726150508691049611
+ Find & change your location on the code (default Thailand, Bangkok)
+ follow the steps above
Another way of getting your Flickr photos to your Drupal
Another way of getting your Flickr photos to your Drupal
without Drupal Flickr.module
here is the code
author="Blake Schwendiman"
http://www.blakeschwendiman.com/gh/flickr_random_contacts.xml
+ copy the code
+ add a block on your Drupal
+ paste the code
+change the
UserPref name="username" display_name="Flickr User Name" to your Flickr username -or indeed any other users public flickr set :)
and do other modifications on the code if you like
+ full HTML option
+save
~ hope it will work for you
mind the downside! ~ any content called externally may slow down your site! test and judge/weight pros&cons...
handbook
These are different from the php code snippets in the handbook, but are still really cool and not necessarily obvious. I think they should go in the handbook so they won't get lost in the forums.
What do you think? If yes, then I will figure where to create a section for it, but what to name it?
Perhaps we need to rename the PHP Snippets http://drupal.org/node/39282 to something more generic like Code Snippets or Drupal site snippets and have this in a section under that.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
you are right sepeck,
Yes it would be neater that start a handbook section with for thoseGoogle module hacks or indeed any block/content wrapper hacks
They can be either general Block (wrapper) Hacks
or specific to Google Module hacks
what do you think, how to name/title/categorise them?
block content wrapper snippets?
google modules content wrapper snippets? -as sub category?
(all mouthfull)
other ideas?
-btw- it would be nice to transfer if a node from the forums to HandBooks or any other node type rather than reposting them. is there an option to do this ?
note: I have to remind that I am not a coder.. I might have concepts/ideas and try to implement I barely attempt to hack or offer to the coders to take on..
also i am not sure, that my hacking/coding skills are not enough quality for the Handbooks but i'll have a go...
Comments (which are what
Comments (which are what forum replies are) are not nodes, so nope can't transfer them. I am not a coder either but we can put the warning use at on risk, blah blah blah in the top level intro.
I'll copy them over for you. I'm moving stuff in the handbook this week anyway. After this then we'll have a nice central place where it can grow like the php snippets stuff. Having people see the posibilities makes it click for them and generates others ideas.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
HandBook authoring
I can I have tried to submit an hack entry to the handbook but there is no relevant category for XML/HTML hacks. so i did not want to submit another category
I can submit a child page but not an top level booksection
who can setup a category or how can i get 'privilage' ?
When you setup an category let us know
+ I tried to post a code here -thats for login block to Gmail account by using etc.
............but still its is not allowed.. (code included a form) is there way oaund this to allow post code with foms?I can set up the section.
I can set up the section. Somestuff doesn't get past the input filters. I did succesfully test it with the XML sample though. We can do ascii number stuff for some workaround or put spaces in some spots. We'll have to document it for some stuff.
I'll probably do this on Saturday.
You could volunteer to join up as a site maintainer if you want to do more. Send Dries an email if interested and sign up to the docs list.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Thanks and Thoughts
As a relatively new user who, has spent many hours searching for things in the handbook, and as a user who is recently taking an interest in Drupal documentation, I make these comments:
In the interest of future growth of the docs, I prefer that php code snippets be kept in a separate category as it is now. Its seems a catchall code snippet category might quickly become unwieldy as various kinds of code snippets are contributed.
I think that were I searching for google code snippets it would be easier for me to find them in a category titled "Google Code Snippets".
As other kinds of code snippets are contributed, cateogries can be added to handbook.
If the need for more that three code snippet categories arises, the contents of the handbook might have a "Code Snippets" category that links to a page with subcategories such a s "Php Code Snippets", "Google Code Snippets", etc.
My two cents.
Paul
This doesn't work as in
This doesn't work as in drupal 4.7
followed the steps, removed the - in front of the lines of course and it doesn't work.
it sure doesn't come from me, so obviously there's a problem, with the instructions or something else, could you look into it please?