Thread: [Ginp-developers] Annotating pictures
Brought to you by:
burchbri,
dougculnane
From: David K. <dk...@co...> - 2009-08-07 17:01:51
|
I am making progress on my updates to ginp, though I'm finding more rough edges than I expected, particularly in the configuration (Setup) updates. However, I'll get that cleaned up and submitted back when it's done. The other thing I want to work on is to get the picture annotation (description) functions working. For that, I obviously need a place and method to store the information; is there one already defined, or should I go ahead and develop one? My first thought is an .xml file in each picture folder, with the information stored there, but if you have already defined one, or have a better idea, let me know. This is turning into a fun project, though a bit more work than I had initially anticipated. D |
From: Brian B. <br...@Pi...> - 2009-08-10 13:07:47
|
David Kerber wrote: > I am making progress on my updates to ginp, though I'm finding more > rough edges than I expected, particularly in the configuration (Setup) > updates. However, I'll get that cleaned up and submitted back when it's > done. > > The other thing I want to work on is to get the picture annotation > (description) functions working. For that, I obviously need a place and > method to store the information; is there one already defined, or should > I go ahead and develop one? My first thought is an .xml file in each > picture folder, with the information stored there, but if you have > already defined one, or have a better idea, let me know. Perhaps you have already noticed the creating of files called ginpfolder.xml in your subdirectories? You have to create this file manually to anchor the root and first level of your collection, but others are built automatically. I haven't investigated why these files are created, or how to get additional tags into them, but it certainly seems to be the best place to start your research. Brian |
From: Brian B. <br...@Pi...> - 2009-08-10 15:06:31
Attachments:
ginpfolder.xml
|
David... you seem to be sending your emails directly to me - can you send them via the ginp developers mailing list instead? David kerber wrote: > Brian Burch wrote: >> David Kerber wrote: >> >>> I am making progress on my updates to ginp, though I'm finding more >>> rough edges than I expected, particularly in the configuration >>> (Setup) updates. However, I'll get that cleaned up and submitted >>> back when it's done. >>> >>> The other thing I want to work on is to get the picture annotation >>> (description) functions working. For that, I obviously need a place >>> and method to store the information; is there one already defined, or >>> should I go ahead and develop one? My first thought is an .xml file >>> in each picture folder, with the information stored there, but if you >>> have already defined one, or have a better idea, let me know. >>> >> >> Perhaps you have already noticed the creating of files called >> ginpfolder.xml in your subdirectories? You have to create this file >> manually to anchor the root and first level of your collection, but >> others are built automatically. >> >> I haven't investigated why these files are created, or how to get >> additional tags into them, but it certainly seems to be the best place >> to start your research. >> > > I haven't seen that; just the .ginp folder under each main folder, which > holds the thumbnails. The only .xml files I've seen are the main > ginp.xml configuration files; is that the one you're referring to? I > considered putting this data in there, but felt that would overload the > file beyond its intended purpose, and that a separate picinfo (or > whatever) .xml file inside each collection's home folder would be more > logical. Hmmm. I checked my production system. Some of the second (and third) level folders in my collection have a file called ginpfolder.xml, which is world readable. Others do not have one. I presume having one of these files in each directory makes it a suitable repository for annotations to the images held in that folder. I don't know what triggers its creation but there must be existing logic that you could adapt to your own needs. I've attached a copy of one of mine. Don't get excited - the contents are very boring. I'm only mentioning it so you have some clues to use in your investigations. Regards, Brian |
From: David k. <dck...@ve...> - 2009-08-10 15:12:36
|
I'm sorry; I didn't intend to reply directly to you. I just hit "reply", not noticing that the "Reply-to" wasn't set to the dev list, as the other lists I subscribe to are. Thanks for the pointers! D Brian Burch wrote: > David... you seem to be sending your emails directly to me - can you > send them via the ginp developers mailing list instead? > > David kerber wrote: >> Brian Burch wrote: >>> David Kerber wrote: >>> >>>> I am making progress on my updates to ginp, though I'm finding more >>>> rough edges than I expected, particularly in the configuration >>>> (Setup) updates. However, I'll get that cleaned up and submitted >>>> back when it's done. >>>> >>>> The other thing I want to work on is to get the picture annotation >>>> (description) functions working. For that, I obviously need a >>>> place and method to store the information; is there one already >>>> defined, or should I go ahead and develop one? My first thought is >>>> an .xml file in each picture folder, with the information stored >>>> there, but if you have already defined one, or have a better idea, >>>> let me know. >>>> >>> >>> Perhaps you have already noticed the creating of files called >>> ginpfolder.xml in your subdirectories? You have to create this file >>> manually to anchor the root and first level of your collection, but >>> others are built automatically. >>> >>> I haven't investigated why these files are created, or how to get >>> additional tags into them, but it certainly seems to be the best >>> place to start your research. >>> >> >> I haven't seen that; just the .ginp folder under each main folder, >> which holds the thumbnails. The only .xml files I've seen are the >> main ginp.xml configuration files; is that the one you're referring >> to? I considered putting this data in there, but felt that would >> overload the file beyond its intended purpose, and that a separate >> picinfo (or whatever) .xml file inside each collection's home folder >> would be more logical. > > Hmmm. I checked my production system. Some of the second (and third) > level folders in my collection have a file called ginpfolder.xml, > which is world readable. Others do not have one. > > I presume having one of these files in each directory makes it a > suitable repository for annotations to the images held in that folder. > > I don't know what triggers its creation but there must be existing > logic that you could adapt to your own needs. > > I've attached a copy of one of mine. Don't get excited - the contents > are very boring. I'm only mentioning it so you have some clues to use > in your investigations. > > Regards, > > Brian > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ------------------------------------------------------------------------ > > _______________________________________________ > Ginp-developers mailing list > Gin...@li... > https://lists.sourceforge.net/lists/listinfo/ginp-developers |