[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] First "history as revision graph" screenshot

From: Eugene Kuleshov <eu_at_md.pp.ru>
Date: Mon, 16 Jun 2008 10:48:41 -0400

Alberto Gimeno wrote:
> By the way, the graph shown in the screenshot is based on Draw2d, not
> GEF. However GEF is based on Draw2d. I think that GEF may not be
> needed because the graph is read-only, we don't need to add, remove or
> edit nodes. What do you think? GEF is an "editing framework" and we
> don't need such editing capacities.
>
  +1 for not using GEF.
> And a second thing, The graph is now shown in a separate window.
> Should I show it in an Eclipse View instead? I think so but I'm not
> sure... If shown in an Eclipse View it should refresh when the user
> selects a different resource and I don't know if this will be ok for
> the user experience since the graph may take some time to be drawn.
> Although it runs in a separate thread it could be annoying.
>
  This is the same question I just sent in other email. Here are few
thoughts:

- if graph takes time to be drawn or calculate it probably better to use
explicit action to open it.
- it may also make sense to consider using editor and not view. So
you'll have more screen real estate and also can easily open more then
one instance of the graph. The latter even more important if creating a
graph is time consuming.

  As a future extension, History view could be linked to selection in
the graph and show corresponding nodes. Also, you could allow to select
nodes on the graph and run some operations on selected nodes, such as
comparison or creating a patch.

  regards,
  Eugene

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-06-16 16:49:05 CEST

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.