Well if you like your MB and your current json/xml file solution but just
want them tied together so they don't get disconnected you may want to
consider just using a .zip to bind them. Uncompressed they can be very fast
and you can access files directly (to query your metadata etc) without
having
Marcus: MA not an option, so no comment blocks, but thanks, good idea.
However, I like your idea of just writing data to somewhere on the server
that corresponds to the Maya file in question. That could be a legit
answer. not tagging the file with metadata itself, but the data isn't
living
YouTube videos of
U.S. Congress money laundering hearing
of
Saudi Billionaire " Maan Al sanea"
with *bank of America*
and The owner of Saad Hospital and Schools
in the Eastern Province in *Saudi Arabia*
and the Chairman of the Board of Directors of Awal Bank in *Bahrain*
following your attempts at using cPickle in mb files which seems
interesting to me... Cant you just append a binary datablock with your
data at the end of the .mb file and just preprocess the file reading and
deleting that appended block of data before opening the file in Maya? If
you do it
following your attempts at using cPickle in mb files which seems
interesting to me... Cant you just append a binary datablock with your
data at the end of the .mb file and just preprocess the file reading and
deleting that appended block of data before opening the file in Maya? If
you do it
If .ma is an option, then it supports comment blocks.
// Comment here
...
addAttr ...
connectAttr..
A perhaps more common approach might be to store metadata relative an
absolute path in a database.
{
"c:\path\to\some\file.mb": {
"any": "data",
"here": True
}}
Then you can query
I'd be curious to find something as well ! I had a quick look at it ages ago,
and couldn't find anything robust. If you're on Unix, you can attach infos
against a file (including a .mb), but that doesn't seem to exist on windows.
And I'd like to find something cross-platform
You can also write
