[Bug 41498] New extension: Image metadata parser functions

2014-03-09 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=41498

Ricordisamoa  changed:

   What|Removed |Added

 CC||ricordisa...@live.it
   See Also||https://bugzilla.wikimedia.
   ||org/show_bug.cgi?id=52522

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 41498] New extension: Image metadata parser functions

2013-08-28 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=41498

--- Comment #10 from Bawolff (Brian Wolff)  ---
(In reply to comment #9)
> The idea of adding yet another parser function, particularly a complex one,
> gives me weird feelings.
> 
> What's the use-case here, exactly? Comment 0 seems to indicate that the goal
> is
> to incorporate EXIF data into file description pages. I'm not sure a parser
> function is the appropriate means of doing so, especially one as
> scary-looking
> as "{{#filemetadata:Property[|R][|file=name of file]}}".
> 


The way I see it, it would be used as follows: If you're on an image page, you
can just write {{#filemetadata:ImageDescription}} and it outputs the image
description from exif. The other options are things I would consider "advanced
options". Most of the time they'd be omitted.

I personally like parser functions, for simple quick jobs, and reserving lua
for complex templates, but I may just be weird.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 41498] New extension: Image metadata parser functions

2013-08-28 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=41498

MZMcBride  changed:

   What|Removed |Added

 CC||b...@mzmcbride.com

--- Comment #9 from MZMcBride  ---
The idea of adding yet another parser function, particularly a complex one,
gives me weird feelings.

What's the use-case here, exactly? Comment 0 seems to indicate that the goal is
to incorporate EXIF data into file description pages. I'm not sure a parser
function is the appropriate means of doing so, especially one as scary-looking
as "{{#filemetadata:Property[|R][|file=name of file]}}".

I haven't looked at any of the code here, to be clear, and I'm sure it's fine.
I'm only speaking as to whether the overall idea here is sound. It'd be helpful
to have a better idea of what this parser function will be used for. If it's
only going to add more magic hackery to Commons, I'd prefer that we ... not.
:-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 41498] New extension: Image metadata parser functions

2013-06-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=41498

Sam Reed (reedy)  changed:

   What|Removed |Added

Summary|New extension: EXIF parser  |New extension: Image
   |functions   |metadata parser functions

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l