Re: [Tools-discuss] Early preview of upcoming changes to the agenda pages

Tero Kivinen <kivinen@iki.fi> Fri, 24 June 2022 11:27 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE479C15D48C for <tools-discuss@ietfa.amsl.com>; Fri, 24 Jun 2022 04:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.985
X-Spam-Level:
X-Spam-Status: No, score=-3.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iki.fi
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DXClyQscnRox for <tools-discuss@ietfa.amsl.com>; Fri, 24 Jun 2022 04:27:33 -0700 (PDT)
Received: from meesny.iki.fi (meesny.iki.fi [195.140.195.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86183C15CF4E for <tools-discuss@ietf.org>; Fri, 24 Jun 2022 04:27:31 -0700 (PDT)
Received: from fireball.acr.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kivinen@iki.fi) by meesny.iki.fi (Postfix) with ESMTPSA id B91052009B; Fri, 24 Jun 2022 14:27:26 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1656070046; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pbV1ssyK48w11uSD2IuWu8qQDo8ffZ2xyiEDFzU9fnQ=; b=tc/ukMCUl0u71LFN6MDMHAyiLqCp0ip1CNaf+7+zMExxQkQeduIRDWI0IS7Cjblpa/5dck HireyBi2qlqyDhOsEO334CUhaYxnWmuQO9yydAJih31d5l8IlkUr1AYCpPp4r5DhlKx3qS DvjXFhM24W41FMeUeqnMuAP9NkyCvvI=
Received: by fireball.acr.fi (Postfix, from userid 15204) id 535F925C12BE; Fri, 24 Jun 2022 14:27:24 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <25269.40860.229242.537715@fireball.acr.fi>
Date: Fri, 24 Jun 2022 14:27:24 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Nick <nick@staff.ietf.org>
Cc: John C Klensin <john-ietf@jck.com>, Jay Daley <jay@staff.ietf.org>, rsalz@akamai.com, Robert Sparks <rjsparks@nostrum.com>, tools-discuss <tools-discuss@ietf.org>
In-Reply-To: <CAEnqrLWfUNFO_Z3ZFnHSpk+4A_fNL2m8WLoGFyCFTpKn4fMgjg@mail.gmail.com>
References: <3ee5bed3-7689-6c45-133e-f2ed0e6fa57e@nostrum.com> <30208595F52209AEC7B07320@PSB> <CAEnqrLWfUNFO_Z3ZFnHSpk+4A_fNL2m8WLoGFyCFTpKn4fMgjg@mail.gmail.com>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 19 min
X-Total-Time: 19 min
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1656070046; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pbV1ssyK48w11uSD2IuWu8qQDo8ffZ2xyiEDFzU9fnQ=; b=fuLBICKOZgJLrtMWF1FkEMiQ6YlxmOggVE6BrwcnnEieLGe4NFEANy/My99gNqDVM8mAG2 ks/EOiLeOnGc9Sm6YIVM3gsw/qVGiIg2N8boGNdpjeXhhkSivOA+B2wHmi1i7RCJ6iZIAL zcIJgIx2mCAgMvks4jAHvu+2VdVV6v8=
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen@iki.fi smtp.mailfrom=kivinen@iki.fi
ARC-Seal: i=1; s=meesny; d=iki.fi; t=1656070046; a=rsa-sha256; cv=none; b=xi/DrQCLjpuTaUl9eqAK4U0RTNMU5Pa8iYqRs2YGqnR56LNeBFuxx4M+kCf2Vq4Rge0Yt5 9A/c2ak6WAYfMJGapLayQNVUGOikDGYVdn6ZZpAG2i+XPYmfMegBPkyKjTNdKxFBPjPgwu ySeiYejyjrVoodlUJIydDfU7u+dvjqY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/kLy28MEKoaR6wMl_vEE0X6lQ2XE>
Subject: Re: [Tools-discuss] Early preview of upcoming changes to the agenda pages
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2022 11:27:35 -0000

Nick writes:
> 1) The current version on the sandbox environment only supports large screens
> with a fully expanded browser window.
> Smaller screens, tablet and mobile sizes are still being worked on.

Funny thing is that my normal laptopt screen was too small to show the
right side menu.... I had to make window wider than normally do to see
it. I usually split my screen in two columns, i.e. have to windows
open side by side, which means my windows are about 1000-1200 pixels
wide. On my desktop I use three windows with similar width etc...

It seems my window was not wide enough to be considered large screen,
either on desktop or on laptop. Need 1400 pixels wide window to see
right side menu, so I guess that is lower limit for "large screens". 

> 3) As for selectable colors, they would be customizable via the "Agenda
> Settings" panel (see screenshot linked above) and can be named to anything you
> want (e.g. Important, Interesting, etc.). These colors/tags can then be
> assigned to individual sessions in the list. The custom colors / names you
> choose would also persist across meetings.

When I was thinking implementing this, I was thinking making named
tags for agenda items. Each agenda item can have multiple tags, and
each tags can have some kind of "decorations" they can add to the
agenda (i.e., background color, text color etc), and tags would most
likely also had priority, i.e, if one item has two tags both setting
background color, the higher priotity one will be the one whose
background color is used.

On the agenda you could filter it by saying that show only those items
which have specific tags, or show everything but add decorations based
on tags (i.e., there would be a way to disable decorations also,
either globally or per tag).

There would have been a way to add tags to either working group or
specific agenda item, and this should be something that is easy to do
while browsing the agenda.

On the tools agenda the colors reset between sessions, so there was no
need to have ability to reset them, but if we have colors/tags etc
peristent then we have we might need to have an easy way to clear some
tags.

Also my coloring method depended what else was in the same slot. I.e.,
some working group might be interesting in one slot, and not really
interesing in another slot (when there were several much more
interesting sessions ongoing in that slot). If we have a way of
setting the colors/tags per agenda item (i.e. specific timeslot for
that wg), then that will allow that kind of usage. And also provide
the ability to mark which sessions you actually participated in... 

> 4) The "Now" link in the "Jump To..." section only appears while the meeting
> is taking place, hence why it's not displayed right now. Same for the red line
> which travels across the list in real time.

Good.
-- 
kivinen@iki.fi