Module development and code questions

Hi everyone,

Just got through building my first public Drupal site. Very fun stuff. Anyway, I'm working on a project now where we'd like to have sections of the site that are completely re-styled in CSS but structurally identical in XHTML (sort of a minature version of the CSS Zen Garden, but less theoretical). Assumably, you could use taxonomy categorizations to make the styling determination, either by setting body class selectors, importing additional css files, or both.

The taxonomy_theme module could accomplish something similar, but there are two pitfalls I see in that approach:

1) Taxonomy_theme means for such a scenario, you have to maintain a lot more code than is really necessary if the only thing that needs to change is the css
2) Taxonomy_theme, by definition, cannot provide a mix-and-match approach, whereas you could combine multiple stylesheets however you wanted per-term, or even when creating a node.

Anyway, I was wondering if creating such a module would be a useful excercise. Part of me thinks you should just do it in the theme itself and be done, which doesn't provide a nice UI or the per-node options, but skips out on a lot of troubles that building such a module would entail (you'd need well-defined rules for preference, CSS load order, etc) and the added complexity for content creators -- I shudder to think about calls from the client saying "what does this 'inherit default styles from taxonomy term or select from available stylesheets below' box mean?"

Hello,

I have some problems with translating my image nodes. Translating an image node actually results in the creation of an entirely new node. The problem is that the new node does not link automatically to the image of the translated node, but requires that the same image be uploaded again. This will unnecessary eat up disk space and therefore I am looking for a solution or at least a workaround.

The relevant mysql query from the files table gives:

mysql>  select * from files;
+-----+-----+-----------+---------------------------------+------------+----------+
| fid | nid | filename  | filepath                        | filemime   | filesize |
+-----+-----+-----------+---------------------------------+------------+----------+
|   1 |   1 | _original | images/IMG_3002.JPG             | image/jpeg |  1930295 |
|   2 |   1 | thumbnail | images/IMG_3002.thumbnail.JPG   | image/jpeg |     1854 |
|   3 |   1 | preview   | images/IMG_3002.preview.JPG     | image/jpeg |    21818 |
|   4 |   2 | _original | images/IMG_3002_0.JPG           | image/jpeg |  1930295 |
|   5 |   2 | thumbnail | images/IMG_3002_0.thumbnail.JPG | image/jpeg |     1854 |
|   6 |   2 | preview   | images/IMG_3002_0.preview.JPG   | image/jpeg |    21818 |
+-----+-----+-----------+---------------------------------+------------+----------+

You can see that the filepath points to duplicate JPG's for the fid's 4, 5 and 6.

I just want to put a node into a block... I can't figure it out...

ie:
or even better a ?q=taxonomy/term/x inside a block...

instead of using a "Taxonomy Block" which strips my teaser of all HTML code...

which i need in order to display images...

guys,

im working on a module that needs execute a php code stored in database, like:

<?
$variable1 = 1;
?>

i figured a way: print the code as a page something like

function foo () {
print db_fetch_object(db_query('SELECT ...'))->code;
}

and then 'include' this 'file' in my code

I do wonder if there is a way to display a player with flash video contend? Dreamweaver for example creates a Java script and uses a swf player skin to uver lay flash video. Would something like this be possible in the Video Module? My goal is to have hundreds of small clips but I dont want to go into flash add a player skin and export a video with player, there must be a easier solution... any info on this??

Thanks so much
Thomas

This module allows lexicons/dictionaries import and search. Automatic installer, import and customization interface is provided.

Project page, demo and enabled block at http://para.ro/project/lexicon.