public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Olivier Fisette <ribosome@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] New category proposal - sci-vis
Date: Mon, 30 Jan 2006 16:21:57 -0500	[thread overview]
Message-ID: <200601301622.01106.ribosome@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.56L0.0601300219230.27126@toucan.gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

On Sunday, 29 January 2006 09:29 pm, Markus Dittrich wrote:
> I would tend to say yes, since molecular graphics programs can vizualize
> everything from small molecules to large biomolecular systems.
> Hence, I would have a hard time deciding if, e.g. VMD should
> be sci-biology or sci-chemistry, whereas sci-visualization seems
> natural. I would really like to hear opinions before I commit
> VMD to portage.

Personally, I would rather keep the specialised visualisation applications in 
their respective categories and use sci-visualisation for general-purpose 
tools. Doing otherwise would create confusion, I think. For instance, should 
TreeViewX be moved to sci-visualisation? After all, it is a visualisation 
program for phylogenies produced by other tools, such as PHYLIP. However, 
users are more likely to search for that tool in sci-biology. Does a genome 
browser belong in sci-visualisation? What about packages such as EMBOSS, that 
propose a few visualisation programs, along with analysis tools?

I think it is better to classify packages according to their field of 
application, and keep visualisation packages that are not tied to a 
particular field in sci-visualisation (ie. statu quo).

Regards,

-- 
Olivier Fisette (ribosome)
Gentoo Linux Developer
Scientific applications, Developer relations

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2006-01-30 21:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 20:53 [gentoo-science] New category proposal - sci-vis Marcus D. Hanwell
2005-11-27 21:40 ` Olivier Fisette
2005-11-27 21:51 ` Holger Peters
2005-11-27 22:05   ` Marcus D. Hanwell
2005-11-27 22:11 ` [gentoo-science] " George Shapovalov
2005-11-27 23:05   ` Marcus D. Hanwell
2005-11-28  0:12     ` Donnie Berkholz
2005-11-27 22:47 ` Markus Dittrich
2005-11-27 23:00   ` Marcus D. Hanwell
2005-11-28  0:05   ` Donnie Berkholz
2005-11-28  1:01     ` M. Edward (Ed) Borasky
2005-11-28  5:36     ` Markus Dittrich
2005-11-28  5:40       ` Donnie Berkholz
2005-11-28  0:43 ` [gentoo-science] " M. Edward (Ed) Borasky
2006-01-29 21:16   ` Marcus D. Hanwell
2006-01-29 22:15     ` Donnie Berkholz
2006-01-29 22:23       ` Marcus D. Hanwell
2006-01-29 22:41         ` M. Edward (Ed) Borasky
2006-01-30  2:29       ` Markus Dittrich
2006-01-30  6:35         ` M. Edward (Ed) Borasky
2006-01-30  8:38           ` Marcus D. Hanwell
2006-01-30 14:51             ` M. Edward (Ed) Borasky
2006-01-30 21:21         ` Olivier Fisette [this message]
2006-01-30 22:26           ` Markus Dittrich
2006-01-29 22:53     ` jak
2006-01-30  8:59       ` Marcus D. Hanwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200601301622.01106.ribosome@gentoo.org \
    --to=ribosome@gentoo.org \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox