From: John R. <jr...@ce...> - 2013-01-05 22:17:13
|
Image comes from http://www.pythonware.com/products/pil/ for python2.x, but there have been no releases since 2009 and it doesn't support python3. What, if anything, have others been using? PyExif was added as a dependency for a plugin in the main source tree that Rob wrote last year. Their latest release also doesn't support python3, but they at least have an active bug and apparently a fix in SVN. But Rob never really pushed the plugin to a point where it's useful in a genealogy context and the ability to edit Exif data in images is provided in most image editing programs. Is anyone interested in maintaining this plugin or should we just remove it? Regards, John Ralls |
From: Doug B. <dou...@gm...> - 2013-01-06 00:46:51
|
On Sat, Jan 5, 2013 at 5:17 PM, John Ralls <jr...@ce...> wrote: > Image comes from http://www.pythonware.com/products/pil/ for python2.x, > but there have been no releases since 2009 and it doesn't support python3. > What, if anything, have others been using? > I don't know about this one. > PyExif was added as a dependency for a plugin in the main source tree that > Rob wrote last year. Their latest release also doesn't support python3, but > they at least have an active bug and apparently a fix in SVN. But Rob never > really pushed the plugin to a point where it's useful in a genealogy > context and the ability to edit Exif data in images is provided in most > image editing programs. Is anyone interested in maintaining this plugin or > should we just remove it? > I am interested in incorporating Exif data (and meta data in general) better into gramps. But that doesn't necessarily mean using PyExif2 as Rob originally used. Now that some time has passed since Rob's decision, is it clear what the best supported method of getting/setting meta data from Python is? Is there a battery already included in Python's stdlib that can do this across platforms? So, don't remove it yet. If someone is interested in stepping into the maintainer's role, this might be a good project for you. But if no one else does, I will. I hope that we can keep refining it, and adding functionality (such as moving GIS data in and out of Gramps better). -Doug > > Regards, > John Ralls > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: John R. <jr...@ce...> - 2013-01-06 04:32:25
|
On Jan 5, 2013, at 4:46 PM, Doug Blank <dou...@gm...> wrote: > On Sat, Jan 5, 2013 at 5:17 PM, John Ralls <jr...@ce...> wrote: > Image comes from http://www.pythonware.com/products/pil/ for python2.x, but there have been no releases since 2009 and it doesn't support python3. What, if anything, have others been using? > > I don't know about this one. > > PyExif was added as a dependency for a plugin in the main source tree that Rob wrote last year. Their latest release also doesn't support python3, but they at least have an active bug and apparently a fix in SVN. But Rob never really pushed the plugin to a point where it's useful in a genealogy context and the ability to edit Exif data in images is provided in most image editing programs. Is anyone interested in maintaining this plugin or should we just remove it? > > I am interested in incorporating Exif data (and meta data in general) better into gramps. But that doesn't necessarily mean using PyExif2 as Rob originally used. Now that some time has passed since Rob's decision, is it clear what the best supported method of getting/setting meta data from Python is? Is there a battery already included in Python's stdlib that can do this across platforms? > > So, don't remove it yet. If someone is interested in stepping into the maintainer's role, this might be a good project for you. But if no one else does, I will. I hope that we can keep refining it, and adding functionality (such as moving GIS data in and out of Gramps better). The only alternative to exiv2 that comes up on a quick Google is ImageMagick, which could also be used to replace PIL. Like Graphviz, we'd end up using only a tiny fraction of its feature set.. but that's probably true of PIL and exiv2, too. The main problem with pyexiv2, aside from that they're just as tardy as we are on Python3, is that they chose two less-used (at least by the Gnome community) facilities: Boost-python and Scons -- and Scons is also not making much progress on Python3. If I were to take it on (which I won't, I'm over-committed already), I'd probably wrap it with SWIG and ignore the pyexiv2 project. GIS is a totally different kettle of fish. Reg |
From: Jérôme <rom...@ya...> - 2013-01-06 09:17:44
|
Not certain, but it seems that PIL is (was?) also used for cropping images into textual reports? Le 06/01/2013 01:46, Doug Blank a écrit : > On Sat, Jan 5, 2013 at 5:17 PM, John Ralls <jr...@ce... > <mailto:jr...@ce...>> wrote: > > Image comes from http://www.pythonware.com/products/pil/ for > python2.x, but there have been no releases since 2009 and it doesn't > support python3. What, if anything, have others been using? > > > I don't know about this one. > > PyExif was added as a dependency for a plugin in the main source > tree that Rob wrote last year. Their latest release also doesn't > support python3, but they at least have an active bug and apparently > a fix in SVN. But Rob never really pushed the plugin to a point > where it's useful in a genealogy context and the ability to edit > Exif data in images is provided in most image editing programs. Is > anyone interested in maintaining this plugin or should we just > remove it? > > > I am interested in incorporating Exif data (and meta data in general) > better into gramps. But that doesn't necessarily mean using PyExif2 as > Rob originally used. Now that some time has passed since Rob's decision, > is it clear what the best supported method of getting/setting meta data > from Python is? Is there a battery already included in Python's stdlib > that can do this across platforms? > > So, don't remove it yet. If someone is interested in stepping into > the maintainer's role, this might be a good project for you. But if no > one else does, I will. I hope that we can keep refining it, and adding > functionality (such as moving GIS data in and out of Gramps better). > > -Doug > > > Regards, > John Ralls > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET <http://ASP.NET>, C# > 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > <mailto:Gra...@li...> > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Tim L. <guy...@gm...> - 2013-01-06 16:32:45
|
John Ralls-2 wrote > Image comes from http://www.pythonware.com/products/pil/ for python2.x, > but there have been no releases since 2009 and it doesn't support python3. > What, if anything, have others been using? As far as I can see, this is used (as Jérôme says) in cropping images in reports. That is a pretty essential function, so we need to find some upgrade path or replacement. (It is also used in LaTeXDoc to open media objects, but I don't see what it is doing there - looks like a piece of historic cruft). John Ralls-2 wrote > PyExif was added as a dependency for a plugin in the main source tree that > Rob wrote last year. Their latest release also doesn't support python3, > but they at least have an active bug and apparently a fix in SVN. But Rob > never really pushed the plugin to a point where it's useful in a genealogy > context and the ability to edit Exif data in images is provided in most > image editing programs. Is anyone interested in maintaining this plugin or > should we just remove it? I personally think that the ability to edit Exif data within Gramps is completely unnecessary in a genealogy program, it contributes to additional maintenance load, and contributes to general bloat. If you want to manipulate Exif data, then use a specific program for that purpose. So I wouldn't object at all to its removal. But that is just a personal view, so if anyone is keen to maintain it, good luck! I would think that the main use in a genealogy context would be to extract GPS location data and add that to appropriate events, but it doesn't actually seem to do that. -- View this message in context: http://gramps.1791082.n4.nabble.com/import-Image-pyExif-tp4657986p4657993.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Doug B. <dou...@gm...> - 2013-01-06 19:28:02
|
On Sun, Jan 6, 2013 at 11:32 AM, Tim Lyons <guy...@gm...> wrote: ... > I personally think that the ability to edit Exif data within Gramps is > completely unnecessary in a genealogy program, it contributes to additional > maintenance load, and contributes to general bloat. If you want to > manipulate Exif data, then use a specific program for that purpose. So I > wouldn't object at all to its removal. But that is just a personal view, so > if anyone is keen to maintain it, good luck! I would think that the main > use > in a genealogy context would be to extract GPS location data and add that > to > appropriate events, but it doesn't actually seem to do that. > Oh, right, it is part of Gramps-core; I would be fine with it being moved to gramps-addons. And I, too, am personally really only interested in what it doesn't yet do, interfacing the GPS media metadata to Gramps' mapping support. -Doug > -- > View this message in context: > http://gramps.1791082.n4.nabble.com/import-Image-pyExif-tp4657986p4657993.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2013-01-06 18:42:12
|
John, There are actually two plugins that use pyexiv2: EditExifMetadata and MetadataViewer. Rob wrote the gramplet to edit exif metadata in images. I got involved to help him out, and wrote the metadata viewer. I use the metadata viewer and am happy to maintain it. Rob was keen on the editing facilities, but was also looking at developing the functionality to integrate better with genealogical data. The pyexiv2 package does not support python3 yet, but has good functionality. We did have a discussion on the list about what packages to use. It was decided to use PIL for image manipulation, which was already used in Gramps. Rob was asked not to use ImageMagick or jhead, which he was using in earlier versions of his gramplet. If anyone has any good ideas then I am interested in extending the existing functionality. Nick. On 05/01/13 22:17, John Ralls wrote: > Image comes from http://www.pythonware.com/products/pil/ for python2.x, but there have been no releases since 2009 and it doesn't support python3. What, if anything, have others been using? > > PyExif was added as a dependency for a plugin in the main source tree that Rob wrote last year. Their latest release also doesn't support python3, but they at least have an active bug and apparently a fix in SVN. But Rob never really pushed the plugin to a point where it's useful in a genealogy context and the ability to edit Exif data in images is provided in most image editing programs. Is anyone interested in maintaining this plugin or should we just remove it? > > Regards, > John Ralls > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: John R. <jr...@ce...> - 2013-01-06 19:04:21
|
On Jan 6, 2013, at 10:42 AM, Nick Hall <nic...@ho...> wrote: > John, > > There are actually two plugins that use pyexiv2: EditExifMetadata and > MetadataViewer. Rob wrote the gramplet to edit exif metadata in > images. I got involved to help him out, and wrote the metadata viewer. > > I use the metadata viewer and am happy to maintain it. > > Rob was keen on the editing facilities, but was also looking at > developing the functionality to integrate better with genealogical data. > > The pyexiv2 package does not support python3 yet, but has good > functionality. We did have a discussion on the list about what packages > to use. It was decided to use PIL for image manipulation, which was > already used in Gramps. Rob was asked not to use ImageMagick or jhead, > which he was using in earlier versions of his gramplet. > > If anyone has any good ideas then I am interested in extending the > existing functionality. Nick, Thanks for the recap and clarification, but it doesn't answer the question: What are you using for testing with python3, particularly for PIL? Regards, John Ralls |
From: Nick H. <nic...@ho...> - 2013-01-06 19:31:52
|
On 06/01/13 19:04, John Ralls wrote: > Thanks for the recap and clarification, but it doesn't answer the question: What are you using for testing with python3, particularly for PIL? I haven't done any testing with python3 yet. Nick. |
From: Benny M. <ben...@gm...> - 2013-01-06 21:03:36
|
I added PIL to README couple of days ago because I saw latex output used it to create correct images (as latex only supports some image types). It is not essential, and I fixed bug in latex generator, but did not test yet if images actually show (my test famtree of the moment did not have images). So, not having PIL will just mean in latex output less pictures are available. Then Doug uses it in webapp for something. So, this is not really a blocking issue, at most a minor feature we might loose. As always in open source, for non-core functionality, it depends on developers interested in the functionality to maintain it going forward. If nobody does, exiv and PIL will be removed in the future. Benny 2013/1/6 Nick Hall <nic...@ho...> > On 06/01/13 19:04, John Ralls wrote: > > Thanks for the recap and clarification, but it doesn't answer the > question: What are you using for testing with python3, particularly for PIL? > I haven't done any testing with python3 yet. > > Nick. > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Adam S. <ad...@cs...> - 2013-01-06 22:19:58
|
On Sun, 2013-01-06 at 22:03 +0100, Benny Malengier wrote: > I added PIL to README couple of days ago because I saw latex output > used it to create correct images (as latex only supports some image > types). > > It is not essential, and I fixed bug in latex generator, but did not > test yet if images actually show (my test famtree of the moment did > not have images). > > So, not having PIL will just mean in latex output less pictures are > available. > Not having PIL will also remove the cropped images in the output reports (that includes any output format that supports images, not just LaTeX). > Then Doug uses it in webapp for something. So, this is not really a > blocking issue, at most a minor feature we might loose. > > As always in open source, for non-core functionality, it depends on > developers interested in the functionality to maintain it going > forward. If nobody does, exiv and PIL will be removed in the future. > > Benny > > > > 2013/1/6 Nick Hall <nic...@ho...> > On 06/01/13 19:04, John Ralls wrote: > > Thanks for the recap and clarification, but it doesn't > answer the question: What are you using for testing with > python3, particularly for PIL? > > I haven't done any testing with python3 yet. > > Nick. > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, > HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your > skills current > with LearnDevNow - 3,200 step-by-step video tutorials by > Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_123012 > _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Adam (ad...@cs...) |
From: Benny M. <ben...@gm...> - 2013-01-07 09:01:06
|
2013/1/6 Adam Stein <ad...@cs...> > On Sun, 2013-01-06 at 22:03 +0100, Benny Malengier wrote: > > I added PIL to README couple of days ago because I saw latex output > > used it to create correct images (as latex only supports some image > > types). > > > > It is not essential, and I fixed bug in latex generator, but did not > > test yet if images actually show (my test famtree of the moment did > > not have images). > > > > So, not having PIL will just mean in latex output less pictures are > > available. > > > > Not having PIL will also remove the cropped images in the output reports > (that includes any output format that supports images, not just LaTeX). > > Ok. On linux, relying on imagemagick is not difficult. On other platforms that might be a problem? Benny |