<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>> Sorry if I missed this, but what is the point of displaying</div><div>> incompatible (wrong arch, wrong platform) Deken packages? What would be</div><div>> harmed if they'd be hidden completely? I fail to see the advantage of</div><div>> having the possibility of downloading a package of wrong arch/platform.</div><div><br></div><div>--like: preparing your patch for offline use on multiple archs, which you</div><div>--currently don't have access to.</div><div><br></div><div>Totally,</div><div><br></div><div>I distribute my patches with all needed externals included, for all platforms, this way the user ONLY have to install pd and its ready to listen. He/she just open the patch and it works, no need to deken or -path or whatever, it just work.</div><div><br></div><div>I think its Ok that other platforms zips are grayed out.</div><div><br></div><div><br></div><br><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font><br><br> </div></body>
</html>