Yes and no.  The same function is used for each silo and setting it's
icon in Media::dir(), however it's also used for adding each "asset"
to each silo, like here in the flickr silo plugin:

---
550                 case 'photos':
[...]
563                         $results[] = new MediaAsset(
564                             self::SILO_NAME . '/photos/' . $photo['id'],
565                             false,
566                             $props
567                         );
568                     }
---

It's this usage case that I'm referring to.

In this case the icon can be passed as an argument, but it's not
actually used anywhere, though I stand to be corrected.

This is a great place to actually use the icon functionality to
provide a bit of visual feedback about the asset in question, for
example it's accessibility or type in the case of other silos that
offer multiple media types.

Cheers,
Colin


On Wed, Feb 18, 2009 at 6:05 PM, Arthus Erea <[email protected]> wrote:
>
> To clarify, this isn't the "silo" icon, right?
>
> On Feb 18, 2009, at 7:59 AM, Colin wrote:
>
>>
>> Hi all
>>
>> I was browsing through the mediaasset.php file last night and I
>> noticed that the constructor takes $icon as an argument, however I
>> can't find any use of this argument anywhere in the source code.
>>
>> I've got a use for this "feature" (to mark galleries and images as
>> private by providing an icon) and was contemplating implementing the
>> necessary code and feeding it back via a ticket.
>>
>> Before I dive in, I wanted to see if anyone knew what the original
>> intentions of this argument were or if someone else has already made a
>> start on putting this argument to use.
>>
>> Cheers,
>> Colin
>>
>> --
>> Colin Seymour
>> Blog: http://www.colinseymour.co.uk
>> Tech Stuff: http://www.lildude.co.uk
>>
>> >
>
>
> >
>



-- 
Colin Seymour
Blog: http://www.colinseymour.co.uk
Tech Stuff: http://www.lildude.co.uk

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to