Menu
▾
▴
Re: [Tiki-devel] Tracker Query Template Plugin
|
From: Xavier de P. <xav...@vh...> - 2012-08-31 08:19:01
|
+1 to have that committed t trunk, as far a the 3 rules are followed, as
usual.
Thanks Robert for your nice work. It will be complementary to plugin
list, and trackerlist. Nesting tracker data in a plugin is a missing
feature.
And yes, allowing the usage of permnames will make it more robust for
trackers with similar names i fields.
Cheers
Xavi
On 30/08/12 19:08, Robert Plummer wrote:
> I thought about this, and actually I don't feel we need to worry, the
> reason is that we don't just do a search and replace over all the
> data, this plugin acts as a parser extension without touching the
> parser, if that makes since.
>
> So just before this plugin executes we check for a stack of tracker
> query items that are currently processing, we do a search and replace
> ONLY FROM THE CURRENT ITEM'S FIELDS and not from all the items as a
> whole. We then parse the nested data before returning back to the
> parser for further processing. We then wrap the returned data from
> the nested parse in ~np~~/np~ so that it is protected and the parser
> can keep parsing as it does. It is a simple concept, but man it hurt
> my brain putting it into action. So each execution of the plugin and
> the search and replace that happens therein are have a "firewall" from
> each other, NEAT!
>
> On Thu, Aug 30, 2012 at 12:04 PM, Robert Plummer
> <rob...@gm... <mailto:rob...@gm...>>
> wrote:
>
> Agreed, we do need perm name in tracker query lib, but it is a
> start at least.
>
>
> On Thu, Aug 30, 2012 at 12:01 PM, Sylvie Greverend
> <sgr...@gm... <mailto:sgr...@gm...>> wrote:
>
> Field name is not an Id. It is a label. You can have 2 fields
> "Address" for instance. Need to be careful for this one.
>
>
> On Thu, Aug 30, 2012 at 11:49 AM, Robert Plummer
> <rob...@gm...
> <mailto:rob...@gm...>> wrote:
>
> Put it simply: We can access trackers by id, name, and
> eventually perm name (not yet integrated), we can nest (or
> join) trackers together. Why is there a space in the
> tracker field? Because I'm using the name feature, and
> the name has a space it in. Also, there is a space there
> to show flexibility. AND like I said you may use the id
> interface by simply using 'byname="n"' parameter.
> Unlike the list plugin, there isn't a ton a plugins that
> need to be learned and executed, just simple values. They
> use tracker query lib. Tracker query lib is like an ORM
> for trackers.
>
> I do not understand the list plugin very well, I don't
> understand why I have to learn all these id's when I want
> to do is use the name of the field. For example: 18
> What is 18?
> There is no description of it.
> But if I say "User Name", then it becomes apparent what
> I'm trying to access.
>
>
> On Thu, Aug 30, 2012 at 10:11 AM, Jonny Bradley
> <jo...@ti... <mailto:jo...@ti...>> wrote:
>
>
> Not sure i really follow - have you looked at the
> {list} plugin? Doesn't that do this already?
>
> I'm rather muddled about why your itemId seems to be a
> field name, and the field names seem to have spaces in
> them (fields already have "permanent" names which
> don't allow spaces... and i don't really see where the
> wiki syntax comes into it, sorry - just don't get it.
>
> I guess i'm missing something...
>
> jb
>
>
> On 30 Aug 2012, at 14:50, Robert Plummer wrote:
>
> > I have a project with Bernard Sfez that we needed to
> use the flexibility of Tracker Query. Anyway, I built
> a very simple plugin that uses tracker query with wiki
> syntax. I wanted to do some probing before I went and
> committed it, but in short we can do something like this:
> >
> > {CODE()}
> >
> >
> > {TRACKERQUERYTEMPLATE(tracker="my tracker" byname="y")}
> >
> > $my field1$
> >
> > $itemId$
> > $trackerId$
> >
> >
> >
> > {TRACKERQUERYTEMPLATE(tracker="my tracker"
> byname="y" itemId="$my field2$")}
> > $my field3$
> > $itemId$
> >
> > $trackerId$
> >
> > {TRACKERQUERYTEMPLATE}
> >
> >
> > {TRACKERQUERYTEMPLATE}
> >
> >
> > {CODE}
> >
> > //Output
> > first item in field 1
> > 1
> > 1
> > first item in field 3
> > 2
> > 2
> >
> > second item in field 1
> > 3
> > 1
> > second item in field 3
> > 4
> > 2
> >
> > //End Output
> >
> > In the above example the tracker query is accessing
> trackers by name, and melding wiki syntax with a
> hybrid syntax for tracker query template (which may
> need to change pending what the admins think). The
> template repeats for each item returned from the
> tracker query. At this time the plugin even supports
> nesting, so things like joining trackers together in a
> wiki page not only become easy, but they are almost
> self explanatory. Also, I have the "byname" parameter
> set to "y", but the plugin also supports the standard
> "f_id" syntax we are all used to. So what do you guys
> think? Is this tiki grade material?
> >
> > --
> > Robert Plummer
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's
> security and
> > threat landscape has changed and how IT managers can
> respond. Discussions
> > will include endpoint security, mobile security and
> the latest in malware
> > threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> > TikiWiki-devel mailing list
> > Tik...@li...
> <mailto:Tik...@li...>
> >
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's
> security and
> threat landscape has changed and how IT managers can
> respond. Discussions
> will include endpoint security, mobile security and
> the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> TikiWiki-devel mailing list
> Tik...@li...
> <mailto:Tik...@li...>
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
>
>
> --
> Robert Plummer
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's
> security and
> threat landscape has changed and how IT managers can
> respond. Discussions
> will include endpoint security, mobile security and the
> latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> TikiWiki-devel mailing list
> Tik...@li...
> <mailto:Tik...@li...>
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions
> will include endpoint security, mobile security and the latest
> in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> TikiWiki-devel mailing list
> Tik...@li...
> <mailto:Tik...@li...>
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
>
>
> --
> Robert Plummer
>
>
>
>
> --
> Robert Plummer
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> TikiWiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
|