Shawn Walker wrote: > Bart Smaalders wrote: >> Shawn Walker wrote: >>> Bart Smaalders wrote: >>>> Shawn Walker wrote: >>>>> client/variant.py: >>>>> Is this module really client specific? Doesn't it belong under >>>>> modules/ instead? I would like to have the web interface present >>>>> the effect of variants on a package. >>>> >>>> Interesting; what about facets & filters as well? >>> >>> Definitely. I want the user to be able to go to the page for a given >>> package and then select variants, filters, facets, etc. to apply and >>> see the resulting installed set. >>> >> >> This appears to me to suggest that the web interface should be importing >> client modules rather than moving those modules... > > Right, but my question was whether these modules were really client > specific? If they have a possible application on server or client side, > aren't they really common to both? > > Cheers,
The question is this: does the client directory contain modules that are loaded only into the client, or modules that are loaded into programs that act like a client? - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
