I disagree - this would in effect create 'bloatware' that would surely grow into a huge monster, similar to what happened to the doomed Netscape Navigator - performance might also be in issue here. A diversity of small efficient apps is the solution, especially since the type of use of the Freenet network might be very diversified. A backup client for instance would look and act a lot different than a Napster like client. What I do suggest however is to create a set of UI specifications, where some basic practices are being followed, similar to the Mac OS specs, that each Mac developer needs to follow (control-c means copy, etc..). This way we not only improve our user interfaces, but also maybe encourage re-use of components and entire frameworks.
More input on this would be welcome. Michael ----- Original Message ----- From: Alex Barnell <[email protected]> To: <freenet-dev at lists.sourceforge.net> Sent: Friday, July 28, 2000 12:27 PM Subject: Re: [Freenet-dev] Music client > Michael ROGERS wrote: > > > 1) Is a music-only client worth pursuing, given that it may take developer > > time away from freenet proper? > > > > IMO, we should develop flexible clients, that can be upgraded with plug-ins > (ultimately, a plug-in that defines a search template). I don't want to have to > run one client for every media type there is. Separate ones for news etc. are > OK, but not for straight downloading of files. > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
