Hi Pavel,
I did not understood the intention in ShoreComponent file libraries at #selectorsToInclude. I saw there is a kind of optimization there. Are you planning to use shore components libraries in production from the image?
Rigth now that optimization makes ShoreComponents libraries incompatible with Jetsam and the "write to disk" feature added to Seaside for libraries.
As apache is no match for comanche for serving files, I'm sending a package version that has stripped the optimizations meant to be deployed as files (writed to disk) and copied to the site document root. Maybe is also useful for someone else using ShoreComponents
cheers,
Sebastian Sastre
Wow man look at this email. I was giving it for lost and it still managed to reach the list for more than a month! I it comes from another system than the solar would be comprehensible but.. so long
Anyway.. about the matter I manage libraries totally out of the image now. It's cheaper
Sebastian Sastre
_____
De: seaside-bounces@lists.squeakfoundation.org [mailto:seaside-bounces@lists.squeakfoundation.org] En nombre de Sebastian Sastre Enviado el: Miércoles, 22 de Agosto de 2007 18:58 Para: 'Seaside - general discussion' Asunto: [Seaside] ShoreComponents and resources
Hi Pavel,
I did not understood the intention in ShoreComponent file libraries at #selectorsToInclude. I saw there is a kind of optimization there. Are you planning to use shore components libraries in production from the image?
Rigth now that optimization makes ShoreComponents libraries incompatible with Jetsam and the "write to disk" feature added to Seaside for libraries.
As apache is no match for comanche for serving files, I'm sending a package version that has stripped the optimizations meant to be deployed as files (writed to disk) and copied to the site document root. Maybe is also useful for someone else using ShoreComponents
cheers,
Sebastian Sastre
seaside@lists.squeakfoundation.org