apply patch, and create file tagadelic.info with the following content:

name = Tagadelic
description = A module to make little, pretty clouds.

Comments

Bèr Kessels’s picture

I need some reviews, since I don't use any 5.0 sites yet.

Please test the code, and check the install/info system too.

beginner’s picture

StatusFileSize
new2.82 KB

5.0 is currently in use here:
http://demexp.ouvaton.org/demexp_tags
(this is a temporary, testing website)
the site is running fine and tagadelic was configured using the first patch.

Since then, I found out about the function system_settings_form() while updating another module which simplify the code a bit. This new patch makes use of this. It works fine on my local site, too.

This patch is really RTBC.

Egon Bianchet’s picture

StatusFileSize
new3.68 KB

- removed case 'admin/modules#description' from hook_help, looks like it's no longer needed with .info files
- made menu callbacks use function arguments instead of arg()

Egon Bianchet’s picture

StatusFileSize
new4.83 KB

Keeping it up to date

Bèr Kessels’s picture

I am holding this off, until:
* The branch for 5.0 is made ready.
* Core is more stable.
* We have more bugs fixed.

I want to prepare a new (bugfree) release for 4.7 first, then branch that off to 5.0. Until today, HEAD tagadelic has lots of nice new features /and/ works on 4.7.

Bèr Kessels’s picture

Status: Needs review » Needs work

- made menu callbacks use function arguments instead of arg()

This is a different isseu, please remove.

Bèr Kessels’s picture

Also: in future please be aware of spaces. Your patch contained some spaces on the end of the lines. This makes it harder to read, because the patch contains differences due to these spaces.

Bèr Kessels’s picture

+      '#default_value' => isset($voc) ? variable_get('tagadelic_block_title_'. $delta, t('tags in %voc', array('%voc' => $voc->name))) : '',

Is this needed for an upgrade to 5.0?

Bèr Kessels’s picture

 /**
- * Implementation of hook_settings
+ * Menu callback. Admin setting page for tagadelic.
  */
 function tagadelic_settings() {
+  return drupal_get_form('tagadelic_settings_form');
+}
+ 
+/**
+ * Form builder for the tagadelic settings.
+ */
+function tagadelic_settings_form() {

And this is really the last comment ;) Why spread this out over three functions? Is it better to have the tagadelic_settings() as a wrapper around one line? Or was that just lazy coding?

Egon Bianchet’s picture

Status: Needs work » Needs review

Honestly, I don't remember :-)

I rolled it again changing just the strict necessary. It's much cleaner this time.

Egon Bianchet’s picture

StatusFileSize
new6.17 KB

Yeah, sure

Egon Bianchet’s picture

StatusFileSize
new5.26 KB

Ups, I left the escaped dollars signs in the comment. Apparently jEdit can't handle variables inside comments :-\ ...

Bèr Kessels’s picture

Status: Needs review » Needs work

I don't like using @tag instead of %tag tokens.
%tokens are a decfacto standard in Drupal, a standard that I am not about to change, because jEdit cannot handle them properly :)

Egon Bianchet’s picture

Well, I made some unnecessary confusion: jEdit has nothing to do with tokens insite t()'s! That's the way Drupal 5 works, see here: http://drupal.org/node/64279#t-placeholders

jEdit was messing up with multiline php comments containing $ signs, so I escaped them with a backslash to be able to work. But I forgot to remove them before rolling the patch, that resulted unclean (#11).

So I rolled it again, see #12

Bèr Kessels’s picture

Status: Needs work » Needs review

My mistake!

Bèr Kessels’s picture

Status: Needs review » Fixed

Committed a modified version to HEAD. Please test the new version on HEAD. once I get some positive feedbacks I will branch off the version.

http://cvs.drupal.org/viewcvs/drupal/contributions/modules/tagadelic/tag...

Anonymous’s picture

Status: Fixed » Closed (fixed)