From: Doug B. <dou...@gm...> - 2010-05-08 13:59:21
|
As I was finishing up the known little issues with the new object links, I was fixing a bug in making sure that notes in NarWeb give the correct path. Sometimes a note can appear in a toplevel page, and sometimes it appears in an object page. There is a variable that determines the right path for either of those (variable is "up"). This is a bit limiting, but it works for the current uses. Unfortunately, notes get render as StyledText just once in the Note constructor (of course, this is good, as it saves much time if the note appears in multiple places, as it is only rendered once). So, notes get their link information when it is rendered. Thus, gramps:// links that get rendered as a webpage need to either be absolute URLs, or the styled text needs to be re-rendered if the path in the url changes. I'll try to fix this over the next few days, but if anyone has ideas on good solutions, please let be know. -Doug |
From: Jon C. <jo...@go...> - 2010-05-08 14:17:32
|
I haven't had a huge time to look at this so forgive my naivety -- if the devs are working on something like this, why not go for a reST/markdown kind of approach? In addition to linking, the notes can then be properly parsed for printing/display etc.... (maybe using Sphinx ->HTML etc...). Then there's also the possibility to customise directives for family groups or some such. It would also mean the text could stay, even if the link were invalid. I'm really not sure if the average user would be familiar with that though (or even want to bother with it). >From a UI point of view, I would imagine the 'link' to be an 'attach file' kind of thing in <name your favourite email client here>. When the target is gone, it's effectively a no-op. Anyway, enough rambling, Jon. On 8 May 2010 14:59, Doug Blank <dou...@gm...> wrote: > As I was finishing up the known little issues with the new object > links, I was fixing a bug in making sure that notes in NarWeb give the > correct path. Sometimes a note can appear in a toplevel page, and > sometimes it appears in an object page. There is a variable that > determines the right path for either of those (variable is "up"). This > is a bit limiting, but it works for the current uses. > > Unfortunately, notes get render as StyledText just once in the Note > constructor (of course, this is good, as it saves much time if the > note appears in multiple places, as it is only rendered once). So, > notes get their link information when it is rendered. Thus, gramps:// > links that get rendered as a webpage need to either be absolute URLs, > or the styled text needs to be re-rendered if the path in the url > changes. > > I'll try to fix this over the next few days, but if anyone has ideas > on good solutions, please let be know. > > -Doug > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-05-08 14:31:57
|
On Sat, May 8, 2010 at 10:17 AM, Jon Clements <jo...@go...> wrote: > I haven't had a huge time to look at this so forgive my naivety -- if the > devs are working on something like this, why not go for a reST/markdown kind > of approach? Jon, I think we will look at this more closely, especially as you're the third person to mention this when we have started to talk about linking in notes. But, I think that what you are describing is another note format, rather than what we are currently implementing. We are implementing the backend link infrastructure, and adding a frontend to the markup. We can add a frontend markdown format, perhaps, after we have the infrastructure, and a working markup. > In addition to linking, the notes can then be properly parsed for > printing/display etc.... (maybe using Sphinx ->HTML etc...). Then there's > also the possibility to customise directives for family groups or some such. > It would also mean the text could stay, even if the link were invalid. Yes, we already have this, as this comes from the backend. Links can (in trunk) be rendered in HTML (as links to webpages or not), and in the UI. Links can be made to the eight primary objects, Person, Family, Media, Event, etc. Text always remain, even if a link is stale. > I'm really not sure if the average user would be familiar with that though > (or even want to bother with it). > > From a UI point of view, I would imagine the 'link' to be an 'attach file' > kind of thing in <name your favourite email client here>. When the target is > gone, it's effectively a no-op. Haven't looked at what we could do with other media like email, but I suspect that this would be possible. It would just have to be meaningful. But this thread is about what to change regarding how StyledText is represented in Gramps. -Doug > Anyway, enough rambling, > > Jon. > > On 8 May 2010 14:59, Doug Blank <dou...@gm...> wrote: >> >> As I was finishing up the known little issues with the new object >> links, I was fixing a bug in making sure that notes in NarWeb give the >> correct path. Sometimes a note can appear in a toplevel page, and >> sometimes it appears in an object page. There is a variable that >> determines the right path for either of those (variable is "up"). This >> is a bit limiting, but it works for the current uses. >> >> Unfortunately, notes get render as StyledText just once in the Note >> constructor (of course, this is good, as it saves much time if the >> note appears in multiple places, as it is only rendered once). So, >> notes get their link information when it is rendered. Thus, gramps:// >> links that get rendered as a webpage need to either be absolute URLs, >> or the styled text needs to be re-rendered if the path in the url >> changes. >> >> I'll try to fix this over the next few days, but if anyone has ideas >> on good solutions, please let be know. >> >> -Doug >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Doug B. <dou...@gm...> - 2010-05-08 15:15:40
|
Nevermind! I realized that I had a tiny little typo, and a misunderstanding about the StyledText. Everything is working fine, or will with a slight fix. Sorry for wasting your time. -Doug On Sat, May 8, 2010 at 9:59 AM, Doug Blank <dou...@gm...> wrote: > As I was finishing up the known little issues with the new object > links, I was fixing a bug in making sure that notes in NarWeb give the > correct path. Sometimes a note can appear in a toplevel page, and > sometimes it appears in an object page. There is a variable that > determines the right path for either of those (variable is "up"). This > is a bit limiting, but it works for the current uses. > > Unfortunately, notes get render as StyledText just once in the Note > constructor (of course, this is good, as it saves much time if the > note appears in multiple places, as it is only rendered once). So, > notes get their link information when it is rendered. Thus, gramps:// > links that get rendered as a webpage need to either be absolute URLs, > or the styled text needs to be re-rendered if the path in the url > changes. > > I'll try to fix this over the next few days, but if anyone has ideas > on good solutions, please let be know. > > -Doug > |
From: Benny M. <ben...@gm...> - 2010-05-09 17:52:06
|
2010/5/8 Doug Blank <dou...@gm...> > Nevermind! I realized that I had a tiny little typo, and a > misunderstanding about the StyledText. Everything is working fine, or > will with a slight fix. Sorry for wasting your time. > Ok. Do code this beautifully please (had no time to look at it yet). That is, this up stuff should be narweb only, and not really a thing of the lower level writing stuff. So, I would expect a report to pass a function or so to determine how gramps links must be resolved for this report. Alternative is one way of doing this, and any reports using this functionality must do it like the defined way. We could eg change the narweb to have content pages on the same level always, so that this up and down is no longer a problem. Anyway, I just mean, even if you have got this working, try to determine if it is the most 'optimal' way of doing it, and if you kept separation of objects good. Conceptually it looks like a difficult thing to implement in a generic way. Benny > > -Doug > > On Sat, May 8, 2010 at 9:59 AM, Doug Blank <dou...@gm...> wrote: > > As I was finishing up the known little issues with the new object > > links, I was fixing a bug in making sure that notes in NarWeb give the > > correct path. Sometimes a note can appear in a toplevel page, and > > sometimes it appears in an object page. There is a variable that > > determines the right path for either of those (variable is "up"). This > > is a bit limiting, but it works for the current uses. > > > > Unfortunately, notes get render as StyledText just once in the Note > > constructor (of course, this is good, as it saves much time if the > > note appears in multiple places, as it is only rendered once). So, > > notes get their link information when it is rendered. Thus, gramps:// > > links that get rendered as a webpage need to either be absolute URLs, > > or the styled text needs to be re-rendered if the path in the url > > changes. > > > > I'll try to fix this over the next few days, but if anyone has ideas > > on good solutions, please let be know. > > > > -Doug > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-05-09 21:47:32
|
On Sun, May 9, 2010 at 1:51 PM, Benny Malengier <ben...@gm...> wrote: > > > 2010/5/8 Doug Blank <dou...@gm...> >> >> Nevermind! I realized that I had a tiny little typo, and a >> misunderstanding about the StyledText. Everything is working fine, or >> will with a slight fix. Sorry for wasting your time. > > > Ok. > > Do code this beautifully please (had no time to look at it yet). That is, > this up stuff should be narweb only, and not really a thing of the lower > level writing stuff. To make this beautiful, NarWeb and the docgen interface will need some refactoring. > So, I would expect a report to pass a function or so to determine how gramps > links must be resolved for this report. Alternative is one way of doing > this, and any reports using this functionality must do it like the defined > way. Currently, if a docgen backend has a format_link method, then it will use that. However, the docgen has no idea of context the note is being render in (up is true?). That is currently a property of the report object, that the HTML backend uses to add the correct path. So, no this is not beautiful. But it makes it clear what the features are, and now we can refactor these somehow to make keep it flexible and general, but make it nice. > We could eg change the narweb to have content pages on the same level > always, so that this up and down is no longer a problem. That won't be able to work around this issue, we need to solve it. > Anyway, I just mean, even if you have got this working, try to determine if > it is the most 'optimal' way of doing it, and if you kept separation of > objects good. Conceptually it looks like a difficult thing to implement in a > generic way. Yes. But NarWeb has three major issues: 1) The data included/not included is a bit random. The plugin extension system should help this: http://www.gramps-project.org/wiki/index.php?title=GEPS_020:_Plugin_Extensions There is a list of bug issues requesting different data to be included, or for existing data to be formatted differently. 2) We need to know what objects are included, so we know whether we should create links or not: http://www.gramps-project.org/bugs/view.php?id=3953 Currently, this only works for people (in trunk and gramps32). Other objects can generate bogus links to non-existent webpages. 3) When we generate a link from the styledtext notes (and elsewhere), we need to know how to form the URL. This currently works, but is built on some non-beautiful code. I suspect that a gramps33 will address all of these. -Doug > Benny > > >> >> -Doug >> >> On Sat, May 8, 2010 at 9:59 AM, Doug Blank <dou...@gm...> wrote: >> > As I was finishing up the known little issues with the new object >> > links, I was fixing a bug in making sure that notes in NarWeb give the >> > correct path. Sometimes a note can appear in a toplevel page, and >> > sometimes it appears in an object page. There is a variable that >> > determines the right path for either of those (variable is "up"). This >> > is a bit limiting, but it works for the current uses. >> > >> > Unfortunately, notes get render as StyledText just once in the Note >> > constructor (of course, this is good, as it saves much time if the >> > note appears in multiple places, as it is only rendered once). So, >> > notes get their link information when it is rendered. Thus, gramps:// >> > links that get rendered as a webpage need to either be absolute URLs, >> > or the styled text needs to be re-rendered if the path in the url >> > changes. >> > >> > I'll try to fix this over the next few days, but if anyone has ideas >> > on good solutions, please let be know. >> > >> > -Doug >> > >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |