2009/3/17, Joost 't Hart <[email protected]>:
> Pascal Georges wrote:
>>
>>
>> 2009/3/16 Alexander Wagner <[email protected]
>> <mailto:[email protected]>>
>>
>>     Joost 't Hart wrote:
>>
>>     Hi!
>>
>>     >> Ah?! I admit, that I see your point, but you lost me
>>     >> logic-wise here. If I change the base the board should
>>     >> probably show the games of this base. That's why I
>>     >> switched the base for, not?
>>     >>
>>     >
>>     > I feel I understand it.  In other products, the board is a
>>     > mere stand-alone thing, not connected to something like a
>>     > 'current' base. These products have the disadvantage that
>>     > you cannot modify two games simultaneously.
>>
>>     Actually, it was the same way in Scid as well. See my other
>>     mail.
>>
>>
>> Not at all. It has never been so in Scid.
>
> Dunno about your history, but I have been with scid since the very
> beginning. In the past the 'locked' (old semantics) tree view was just a
> (read-only) view on the database for that tree.

No. The "locked" check button meant to keep the display in the Tree
window locked to current base A, and after switching to another base B
don't update the Tree, which will continue to reflect data in base A.
This behavior is the default one today as every base can have its own
Tree window opened.

> It allowed you to edit a
> game in one base, while matching this game against statistics of the
> other. Admittedly, only one tree view could be opened - locked or not
> locked, which was a serious limitation, but it served just the purpose
> that it was meant for.
> The board in display was not related to that tree, and it was simple to
> merge some position from the best-games in the tree into the active game
> (related to the board in display).

It is exactly the same behavior today.

[...]

>> No, the Tree always got a filter set after a search. There has been no
>> change here. Or I did not understood my own changes ?!
>
> To my experience, the tree did not influence any filter at all. This has
> come to me as a usability surprise as well. The current tree is no
> longer completely decoupled from 'base' operations. In the past it was.

Please check filter's state in older versions of Scid. Tree only works
with each base filter.

> And from the way data entities are currently organised in the code, I
> can even understand why this is the case. Tree view has been made
> multiple-instantiatable, but with the (new) restriction that each
> instance shall be coupled to an open database.  In practice, this
> relationship exists rather the other way around, for that matter. A
> Database has a tree view operational, as opposed to that The Tree
> presents a view on some database.
> And in the past, a (single) filter was already coupled to such database.
> This explains a lot...

Not so much. Look at Scid's code.

> Whether you understand "your own changes" is completely irrelevant.

<Sigh>

> I am
> not interested in changes and do not want to discuss them.

Why I am losing my time replying this ?

> It is about
> behaviour as it comes apparent to the end user, not about how this
> behaviour is accomplished.
> And, you are not perfect, right? So sometimes side-effects may be
> introduced that are not expected, even not wanted, I am afraid. This is
> quite natural, especially if we tend to avoid discussion and analysis on
> specifications, and follow the act-before-you-think approach.
>
> Joost.

So please read Scid's code, test various older versions and current
one, then please submit a relevant use case of "things that have
changed in usability".

Pascal

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to