Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 41CEAE404 for ; Wed, 19 Dec 2012 13:16:09 +0000 (UTC) Received: (qmail 14538 invoked by uid 500); 19 Dec 2012 13:16:09 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 14497 invoked by uid 500); 19 Dec 2012 13:16:08 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 14486 invoked by uid 99); 19 Dec 2012 13:16:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 13:16:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gary.martin@wandisco.com designates 209.85.214.46 as permitted sender) Received: from [209.85.214.46] (HELO mail-bk0-f46.google.com) (209.85.214.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 13:15:57 +0000 Received: by mail-bk0-f46.google.com with SMTP id q16so980730bkw.19 for ; Wed, 19 Dec 2012 05:15:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=8swbQ3Ija9uYfcBcEmWmQRGV3APxh6/hcQI+HVp3CUY=; b=c6d+AkbxvdJ6mXv2aplangkEkv1OtIL8O68Y1+it2w8NipIF/GkwsQLx7LQdpvjyUo E+Vl0FJcAQSS/ydNt26zidV+tzzAz065/gxVL/zszMeShYZ864ZQu7BwWp6aWiECjAhL Cw5UQNlNQEoKG3cd0bOObtLOXxJrU3sB+l0F1/R5ZjJvl4wP874xuC++iXXWFDL9s91G ujHfwJVy76uvF7D9kdTLs+Sh3kdDKGXvlcRUqFt4+yj7AVsg4kfif+ZC2EpkssEYfJCq 4SD7rLxsuB9WDSzondSurguHMqVIeVgIpnxgdPzS58RNCNg8+xNl4GGpQs2fB0dvvDM+ kP9A== X-Received: by 10.152.124.68 with SMTP id mg4mr5145283lab.51.1355922935935; Wed, 19 Dec 2012 05:15:35 -0800 (PST) Received: from [10.2.5.205] ([77.86.30.139]) by mx.google.com with ESMTPS id ft8sm2046856lab.9.2012.12.19.05.15.34 (version=SSLv3 cipher=OTHER); Wed, 19 Dec 2012 05:15:35 -0800 (PST) Message-ID: <50D1BDF3.1090803@wandisco.com> Date: Wed, 19 Dec 2012 13:15:31 +0000 From: Gary Martin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: bloodhound-dev@incubator.apache.org Subject: Re: Ticket #279 - Images rendered in activity feed References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Gm-Message-State: ALoCoQm6THN3UWfsGz1nifLOwGjhQj2HW1ufwS60eirlEjSgO9IJkmLnVkJTW2Ldi8fF4mTAVJxH X-Virus-Checked: Checked by ClamAV on apache.org Great to hear from you Tom! I think for a quick solution I could live with not displaying in the short term. Alternatively, swapping the image for a placeholder image might work. I could see the visibility of images as being something configurable though. For tall images, perhaps we could just scale them back to some maximum height. Cheers, Gary On 19/12/12 12:58, Peter Ko�elj wrote: > I am in favor of keeping images. Normally they should not be to heigh when > resized to fit activity feed width. > In the long run I would like if users have an option on activity widget or > in widget activity setting to show/hide images. > > And... > ... welcome to Bloodhound! > > Peter > > On 19 December 2012 13:05, Tom Kitchin wrote: > >> Hi, >> >> I've been reading the dev mailing list for a while, and I thought it might >> be a time to try and get involved. I took a look at ticket #279 ( >> https://issues.apache.org/bloodhound/ticket/279), in which images in >> ticket descriptions turn up in the activity feed as well. >> >> The first solution (not rendering them) is simple enough as far as I can >> see - I've attached a very simple patch which just sets them display:none >> in CSS. >> >> I've been looking into the second solution (resizing the images to fit >> instead of hiding them) as well. As far as I can tell (prompted by Gary) >> the trick would be to do something with the Image() macro in the specific >> context of the Activity feed to apply the 'span4' class to the img tag. I >> haven't quite worked out how to do that yet, but thought I'd send a message >> here before I persisted. >> >> Which approach is preferred? As far as I can see, the question comes down >> to whether the activity feed could end up misinforming people due to >> missing images, and whether it would look jarring if a referenced image >> wasn't there. On the other hand, even resized images might still be very >> long, taking up a lot of space in the feed. >> >> Incidentally, nice to meet you all. I hope I can be of some help with the >> project. >> >> Tom >>