<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">
<pre wrap="">No. We have two ways in general: inline, and metadata. What you propose is
metadata, what Dave wants/needs is inline. Lets not confuse the two.
</pre>
</blockquote>
<br>
Correct, that's why I added this footer to my original message. Just
wanted to throw the metadata approach out there in case he wasn't aware
of it. <br>
<blockquote type="cite">If you need to use img_assist (using inline
images), you could do this in hook_nodeapi() as Steven says and shrink
down any images, but this method is a bit clunkier.
<br>
</blockquote>
In terms of the performance issues, the image regeneration could be in
a form_alter #submit handler before node_submit() fires and then the
processed teaser would overwrite Drupal's generated teaser allowing us
to cache the resized image teaser. Or, am I missing something?<br>
<br>
>From node_submit():<br>
<?php<br>
// Auto-generate the teaser, but only if it hasn't been set (e.g. by a<br>
// module-provided 'teaser' form item).<br>
if (!isset($node->teaser)) {<br>
$node->teaser = isset($node->body) ?
node_teaser($node->body, isset($node->format) ? $node->format
: NULL) : '';<br>
}<br>
?><br>
<pre class="moz-signature" cols="72">Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
<a class="moz-txt-link-freetext" href="http://www.electronicinsight.com">http://www.electronicinsight.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:rob@electronicinsight.com">rob@electronicinsight.com</a></pre>
<br>
<br>
Bèr Kessels wrote:
<blockquote cite="mid200702061255.11086.ber@webschuur.com" type="cite">
<pre wrap="">Op dinsdag 6 februari 2007 08:19, schreef Rob Barreca:
</pre>
<blockquote type="cite">
<pre wrap="">The best way IMO is to use CCK and imagefield/imagecache. Then you have
an "image" field and can call a different imagecache preset in your
node-content_whatever.tpl.php file when $teaser is true/false. This is
what I have used in the past for this functionality and works quite well.
</pre>
</blockquote>
<pre wrap=""><!---->
No. We have two ways in general: inline, and metadata. What you propose is
metadata, what Dave wants/needs is inline. Lets not confuse the two.
The camp that want the node/comment/foobar objects to be passed to the filter
have so far lost the battle (see Stevens comment) for good reasons (IMO).
But.
Right now, you see all the more advanced filters being implemented as
_nodeapi, and not as filters. A bad, bad result, IMO. Much worse then the
argument of 'clean implementation'.
We see (rather popular) modules such as inline.module being real performance
drainers on your site. Also the filter tips can no longer be used properly,
and you don't ave the filter available in filter settings.
I think that Dave is best off using that method too, here. Its unfortunate,
its a performance problemn, and the interface becomes clumsy (filter tips
cannot be reused etc) but at least it works. ;)
Look for an example at inline module. <a class="moz-txt-link-freetext" href="http://drupal.org/project/inline">http://drupal.org/project/inline</a>
Bèr
</pre>
</blockquote>
</body>
</html>