Hi Sebastien,
is was looking at your code and setting the binary.location hard, is
the one i struggle with.
A storage.configuration on each field i see the advantage, but i should
be a default value, that you need not redefine on every field.
What i think about instead of choosing it on
Hi Paul and Markus.
I did some update on my code
https://code.launchpad.net/~akretion-team/server-env-tools/server-env-tools
And I start to refactor the product image module based on it
https://code.launchpad.net/~akretion-team/openerp-product-attributes/openerp-product-attributes-product-image
Hi Sebastien,
we just looking on your solution to get ideas how to implemented a
Attachment field with additional meta data. This helps us a lot, thank
you for sharing your work.
So i just want to share my thoughts about your implementation. So you
solve two problems in one module. I suggest to
Hello Sebastien,
I was just trying to find a solution for this yet again and I noticed there
is no complete module out there for product images that is accessible to
everyone (you are right about the default_code)
This is an interesting project and I hope to contribute to it if I can,
code,
Hi all,
If like me you want to store image and binary in you file system instead of
the database this mail can interest you.
Since version 6 we make some improvement in the product image module in
order to be able to store image in the file system (
Hi, after some discution with Raphael
I decide to remove the object binary.binary
So now the data model is simplier.
When you create the field image_test = 2 new fields will be added
automatically
image_test_uid : used for storing the uid of the image
image_test_file_size : used for storing the
6 matches
Mail list logo
