last i checked, the trunk targets .NET 2.0

there was a thread about just a few days ago:
http://groups.google.com/group/nhibernate-development/browse_thread/thread/73d9634269dbcd7b

On Wed, Nov 26, 2008 at 3:54 PM, HappyNomad <[EMAIL PROTECTED]> wrote:

>
> I would like to point out that NH 2.1 itself targets .NET 3.5.  And
> INotifyCollectionChanged is part of .NET 3.5. INotifyPropertyChanged
> and INotifyCollectionChanged is a general mechanism in .NET for making
> objects observable.  It is NOT part of a "specific UI model".  Sure,
> WPF uses these interfaces, but it could be used for other GUI
> frameworks as well.  It could even be used for non-GUI frameworks
> which observe the domain model.
>
> In any case, the bare minimum I am asking at the moment is add this
> template method to AbstractPersistentCollection:
>  protected abstract void OnCollectionChanged
> ( NotifyCollectionChangedAction action, object changedItem, int
> index );
> and then call it from all of its subclasses, whenever the collection's
> contents are modified.  This wouldn't be adding observability per se
> (although it's not far from it I admit).
>
>
> On Nov 26, 9:33 pm, "Gustavo Ringel" <[EMAIL PROTECTED]> wrote:
> > I think the task of the persistence layer is not to be bindable to an
> > specific UI model...or to inform about something to an specific UI model.
> > So for sure it is not part of the core.
> > It may be an extension to put in the contributions...
> >
> > Gustavo.
> >
> > On Wed, Nov 26, 2008 at 4:29 PM, Fabio Maulo <[EMAIL PROTECTED]>
> wrote:
> > > 2008/11/26 HappyNomad <[EMAIL PROTECTED]>
> >
> > >>  NH 2.1 targets .NET 3.5, and
> > >> observability is a fundamental feature of .NET 3.x, so I think the
> > >> best way to solve this problem is to incorporate observability into
> > >> the NH core.
> >
> > > Sure... and sure we will add INotifyProperyChanged, and a base class to
> > > work with lazy-loading and INotifyCollectionChanged and probably
> > > IBindingList implementation.
> > > Be sure about that.
> > > --
> > > Fabio Maulo
> >
> >
>

Reply via email to