Re: Generational Interfaces

I think they can be called "soft interfaces" or "heuristic interfaces", it's an example of machine learning. I think it's not easy to apply such idea to a statically typed language, but probably it can be done on Java. I presume in the future GUI will learn more about the usage patterns of their us

Re: Generational Interfaces

On Jan 26, 3:04 am, Paddy <[EMAIL PROTECTED]> wrote: > I thought a major use of an interface is to allow separate development > that comes together at the interface. If so then such fluid interface > changing would scupper separate development. Yes, this wouldn't be appropriate for that particula

Re: Generational Interfaces

On Jan 26, 5:03 am, Carl Banks <[EMAIL PROTECTED]> wrote: > While thinking about generational garbage collection, the thought of > generational interfaces occurred to me. I'd thought I'd run it by you > guys. I'm curious if there are any examples of this out there. > > I've opined on this chat ro

Re: Generational Interfaces

On Jan 26, 12:32 am, Paul Rubin wrote: > Carl Banks <[EMAIL PROTECTED]> writes: > > AirplaneInterface = InterfaceTracker("Airplane") > > ... > > set_up_initial_state() > > ... > > AirplaneInterface.report(self) > > Thoughts? (Surely someone's thou

Re: Generational Interfaces

Carl Banks <[EMAIL PROTECTED]> writes: > AirplaneInterface = InterfaceTracker("Airplane") > ... > set_up_initial_state() > ... > AirplaneInterface.report(self) > Thoughts? (Surely someone's thought to do this before.) A decorator might express the idea a little more natur