I am looking for a solution to Redux token import (of which I only learned today). I am attempting to write a Redux expression into a chrome extension called "Highlight This" (found here https://www.highlightthis.net/).
It appears the extension takes Redux "tokens", whatever that might be, and I need it to highlight a filed only if populated and have attempted to wrap my head around the expression would be and got as far as probably needs to be a if/then but not much further than that as I have absolutely no previous experience with Redux expressions.
I need the extension to highlight a specific field that happens in the middle of a page, and the filed is either blank or has a date.
Looks like this:
description
value
Irrelevant 1
yyyy-mm-dd hh:mm:ss AM
Most Recent Flag Time
blank or yyyy-mm-dd hh:mm:ss AM
Irrelevant 2
yyyy-mm-dd hh:mm:ss AM
If someone can either point me in the right direction of what I should look at to write my own expression or show me an example I want to basically have the extension check the field right after "Most Recent Flag Time" and if it contains anything to simply highlight that date as it would as if I gave it a specific word to search and highlight automatically.
Related
I am currently trying to create my own Google Agent using DialogFlow and while everything is going fine, I am finding myself unable to solve the smallest of problems.
Google has a tendency to add an additional year to the datetime object whenever I state a date. An example:
If I say "How much did we produce 29/6?" (6/29 doesn't work either) it will grab the date and format it correctly to the 6th of June, however it will make it year 2021 instead of 2020... Is there any way to make it default to our current year, unless I specifically say a different year?
Can you try saying "How much did we produce on June 29th?" I think it may have some issue processing the string "29/6" and somehow it gets translated to 6th of June.
You had mentioned "6th of June" is formatted correctly when giving "29/6", shouldn't it be "29th of June"?
I'm coming from a SCORM end and trying to figure out two related issues with how to do update and find the most recent data (ie, looking for best practices).
In SCORM I'd have a set of activities that would all store their answers and scores (easily understandable from the docs etc). The "how" I'm after is specifically related to resuming the set of activities multiple times, and hitting "reset" and submitting a different answer to a single activity after a statement has been sent in.
From what I read with xAPI it states that statements are immutable - so how would I go about this.
My first thought was that I'd make the statement id generated from the activity id and void the old answer when it changes - but that sounds wrong (not least because it reads like you can't re-use the id even with voiding).
So it looks like the Statement id needs to be unique, which would mean that multiple identical Objects would be found - so would I have to look through every attempt and check for the latest one?
I'm currently looking at using xAPIWrapper in the middle.
Moving from SCORM to xAPI requires a change of mindset. SCORM deals with statuses which get updated; xAPI logs events like a journal.
You can think of it like Facebook. You post a photo of your new cat; a month later you post a photo of your cat 1 month older. There's no need to go back and delete the old post. If you want the latest photo of your cat you just go and get the most recent photo tagged "Ryochet's cat". You can also look at older photos to see how your cat developed. xAPI is like that activity stream on Facebook.
So, if somebody scores 10 points on their first attempt, then 20 points on their second attempt, you'd simply send a second set of statements about the 2nd attempt. There's no need to get rid of the statements about the old attempt, that happened and is useful data to see how the learner developed.
What does the following patterm means in the URL, these pattern seen on variety of url like Linkedin
Enpv_301654428_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1
is this sparse Matrix representation ?
For example
https://www.linkedin.com/groups?gid=5010991&goback=%2Enpv_301654428_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1&trk=prof-groups-membership-name
I know it's the value passed to the parameter goback, but what's the point to use this kind of strange looking values?
You may want to check this
this link!
It's basically a method to allow the system remember steps to go forward\backward in the navigation.
EDIT:
When you perform a search on LinkedIn, there are a number of facets on the left hand side of the search results page that you can use to refine your search, like company and location. When you click on a search result, it turns all of those facets into the *1_s and *2_s that you see in the URL. Those are used to construct the "Go back to Search Results" link, which will restore the facets you had selected.
This stackoverflow previous question may also help you.
I've got a situation where I want the user to enter a start date and end date for report data. In addition there should be a drop down which allows the user to choose one of the following:
last 7 days
last 14 days
last 30 days
If the user selects one of these values, the datepickers should adjust there values? I can't quite figure out how to approach this. Anyone have any ideas.
This isn't possible solely from within SSRS. However, you can still achieve your goal with a bit of extra work. Here's a bit of pseudocode to get you going. This technique works and we use it in our organization often.
In SSRS, hide the report parameters
Create a new blank HTML/ASPX page
Using only HTML, create create your own datapickers and custom "last 7 days" dropdown.
Use Javascript/jQuery on the client to handle your custom logic.
Place a "Generate Report" button on the page.
Insert a hidden iFrame on the page
When the user clicks "Generate Report", perform an HTTP POST passing the report parameters in the URL (something like http://server/reportserver?/dir/Report&rs:Command=Render&Parm1=VALUE1&Parm1=VALUE2&Parm1=VALUE3)
Display the report in the iFrame
Your users won't know the difference and this will give you total control over the layout and presentation of your report parameters.
You can do this within in SSRS. Not great but acceptable.
Have the first parameter be a pick list with two choices.
Pick Dates or Last X Days.
Have the next parameter be the start date.
The third parameter is another pick list. It is either a list of dates or a list of numbers depending on the choice they made in the beginning.
Another way would be to have two reports displayed to the user. one with an open date range and one with a predefined pick list of dates. These would be linked reports that call the same underlying report but display different parameters. This is the approach I would take for such a user request.
I am working on a project using Drupal 6 (6.11 at the moment, haven't yet upgraded to 6.12) and part of the core functionality is the ability to vote on nodes. I'm having some rather weird behaviour that has taken me an age to track down and now I have, I still can't fix it.
This is what I've managed to figure out so far:
The template file sites/default/modules/vote_up_down/theme/vote_up_down_points.tpl.php automatically calls the function template_preprocess_vote_up_down_points() from vote_up_down.module.
vote_up_down.module then queries the database using the values stored in the $variables array that is passed to it
On only one of the 3 occasions this is called on a typical node (in this case forum posts) $variables doesn't have a value for $variables['cid'].
That one occasion is when it reads the score so as to display it below the post itself. And, instead of locating the current post's score, it locates the first-ever-voted-on post's score. (This is because instead of returning the score of one post, it returns the score of all posts and then uses the first one from the list).
I am assuming that $variables is a system-wide constant (looking at the content of it using print_r seems to confirm that) and so perhaps this is a core bug as it should always be the same. I checked the contents of $variables and the only 4 parts of around 50 that are different in the one that doesn't work are: cid - blank, tag - blank (although this is discovered by the function and correctly substituted as 'vote'), zebra - even & id - 2. I imagine the last 2 are not really important for this, so the key must be in why $variables['cid'] is not being passed through.
So, my questions are:
Has anyone had this problem before and how did you fix it?
If not, do you have any tips as to how I can figure out why this is not working correctly?
I can't tell you the answer, but you'll probably have better luck posting this in the module's issue queue, since then the maintainer and others using it will see it.
I can't believe I didn't try this before, but I just upgraded to the latest development snapshot of vote_up_down and the problem went away. A 2 minute fix in the end vs about 6 hours of trying to tie the problem down.
Lesson learnt!