Ok.
The next version is around the corner, so when you update your plugin once it is reworked, give us a yell to look at it again. We are not doing new features anymore in the 3.2 series.

About the date, several people have requested this, and using the preferences is a bit of a workaround, but trying to outsmart the datedisplayer is dangerous. As long at that module is used in a generic way to change the date format, a patch for that is welcome. I don't think however it makes sense to change dateformat for every report, it seems more sensible to me to have in the preferences a date for GUI display, and one for reports.

Benny

2011/2/28 Adam Stein <adam@ppdev.mc.xerox.com>
It's quite possible that I added things that were already planned for a
future release.

In the case of Date, turns out my change is moot as Craig Anderson is
coming out with something better anyway
(http://www.gramps-project.org/wiki/index.php?title=Display_formatting3_3) which would eliminate the need for my enhanced SubstKeywords when it's available.  The point of my change is to get the date in the specific format that I wanted (which was <Month> <Day>, <Year>).  I didn't realize the date format specified in the preferences were to be used by all reports.  I can imagining wanting the date in one format for display within the Gramps application and another format used in reports.

In the case of Endnotes, it looks like what I did is already planned for
a future release and that will make what I did obsolete.

I figured, as new released come out that contains the functionality the
plugin needs, I will be removing it from my plugin and use what's in the
Gramps core.

My plugin plus enhancements were made to work with the current released
stable version and the "link" button is only available in trunk, so I
didn't know it was coming.

Thanks for looking the plugin over.  As you ask questions or give me
more knowledge, the plugin will improve to a point where I can say it's
done (at least for a given version :-{})

On Sat, 2011-02-26 at 09:49 +0100, Benny Malengier wrote:
> I see in the diferrence:
>
> Date: Gramps behavior is that users select a date format according to
> their locale in the preferences. Reports should not deviate from this.
> This feature from your report is a typical thing that is nice for the
> creator, but breaks Gramps common behavior. I don't know what you try
> to fix with this feature.
>
> Clickable links in endnotes: in trunk if you open a note, you seen in
> the toolbar a 'link' button. So for trunk, this feature you added
> should be replaced with the global way of adding links to notes. I
> think in trunk the odf backend supports this already.
>
> Benny
>
> 2011/2/15 Adam Stein <adam@ppdev.mc.xerox.com>
>         Just created a wiki page and added my report plugin (for
>         Gramps v3.2)
>         for FilteredReports.  This first version is more of a
>         proof-of-concept
>         than a fully featured plugin (even though it does work given
>         the
>         limitations specified on the page).  I'm posting this to
>         developers
>         since I include modified versions of some core Gramps code
>         with the
>         plugin (the wiki page details what I did) so that the plugin
>         can work
>         without the core changing.
>
>         You can find the description at:
>
>         http://www.gramps-project.org/wiki/index.php?title=Filtered_Reports
>
>         If there is interest, maybe my Gramps code modifications can
>         find there
>         way into the core.
>
>         --
>         Adam Stein @ Xerox Corporation       Email:
>         adam@ppdev.mc.xerox.com
>
>         Disclaimer: Any/All views expressed
>         here have been proven to be my own.
>          [http://www.csh.rit.edu/~adam/]
>
>
>         ------------------------------------------------------------------------------
>         The ultimate all-in-one performance toolkit: Intel(R) Parallel
>         Studio XE:
>         Pinpoint memory and threading errors before they happen.
>         Find and fix more than 250 security defects in the development
>         cycle.
>         Locate bottlenecks in serial and parallel code that limit
>         performance.
>         http://p.sf.net/sfu/intel-dev2devfeb
>         _______________________________________________
>         Gramps-devel mailing list
>         Gramps-devel@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/gramps-devel
>

--
Adam Stein @ Xerox Corporation       Email: adam@ppdev.mc.xerox.com

Disclaimer: Any/All views expressed
here have been proven to be my own.  [http://www.csh.rit.edu/~adam/]