The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If
this is deprecated, what should be used instead? Should the methods that
reference this view also be deprecated?
James Foster
This is a discussion on Questions about ChoicePrompter class>>defaultMultipleChoiceView - Smalltalk ; The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If this is deprecated, what should be used instead? Should the methods that reference this view also be deprecated? James Foster...
The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If
this is deprecated, what should be used instead? Should the methods that
reference this view also be deprecated?
James Foster
The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If
this is deprecated, what should be used instead? Should the methods that
reference this view also be deprecated?
James Foster
James,
> The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If
> this is deprecated, what should be used instead? Should the methods that
> reference this view also be deprecated?
I suspect it's an error; the IDE won't work without that view resource -- which
seems suspicious ;-)
Possibly the idea is that that specific view is in the deprecated package
(since it refers to MultipleSelectionListView, which is itself deprecated); but
not actually deprecated. And that it will be replaced in a later release with
a different view (of the same name); and the code which currently uses it
will use the replacement. But that's just guessing.
-- chris
OA:
Chris suggests that this is an error. Comments?
James
"Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> wrote in message
news:457da81b$0$628$bed64819@news.gradwell.net...
> James,
>
>> The "Multiselection choice prompter" is in "Dolphin MVP (Deprecated)". If
>> this is deprecated, what should be used instead? Should the methods that
>> reference this view also be deprecated?
>
> I suspect it's an error; the IDE won't work without that view resource --
> which
> seems suspicious ;-)
>
> Possibly the idea is that that specific view is in the deprecated package
> (since it refers to MultipleSelectionListView, which is itself
> deprecated); but
> not actually deprecated. And that it will be replaced in a later release
> with
> a different view (of the same name); and the code which currently uses it
> will use the replacement. But that's just guessing.
>
> -- chris
>
>
>
James,
> Chris suggests that this is an error. Comments?
I suppose you could look at it as a bug, yes.
Basically, what we have done is to deprecate the
MultipleSelectionListBox and MultipleSelectionListView classes because
mult-selection can better be handled with the newly introduced
#selections and #selectionsByIndex: methods. The same methods can be
used to deal with both multiple and single selection lists.
So the classes MultipleSelectionListBox and MultipleSelectionListView
have been moved to the MVP (deprecated) package. Not only does this
provide an indication to the programmer that these classes shouldn't be
used in new code but it also makes it easier for the image stripper to
remove them completely from applications where the are not used.
The situation breaks down, however, when you spot that we didn't "eat
our own dog food" (a strange Microsoft expression) in that we haven't
actually removed uses of these classes from the development system.
This is obviously something that we need to do before the classes can
be truly deprecated in a future release. The views that currently use
these classes have been moved into the Dolphin MVP (deprecated)
package, not because we intend to imply that they shouldn't be used in
your own code but simply to avoid a cyclic package dependency.
I've created a bug report, #2217, to indicate that this should be fixed
in a future release. Until that time, as Chris suggests, you should
assume that the views in question can be freely used.
--
Best regards,
Andy Bower
Dolphin Support
www.object-arts.com