My employer has installed two large LCD panels to display build health and statistics.
I'd like to display Sonar graphs which update intra-day. How's the best way of going about this? I've had a look through the available plugins and haven't found a "wall display" facility yet
No such plugin currently exists, and actually I'm not sure that this could be achieved with a plugin - as plugins can only contribute to the current Sonar UI.
Maybe you could send a mail on our mailing-list (user#sonar.codehaus.org) to tell your interest in such a feature for a future release of Sonar? Basically, this would be something like the possibility to ask the UI to show a Sonar dashboard outside of the standard layout and with a specific refresh rate.
FYI, we have planned a work on the UI for the next version of Sonar - 3.3, so this could be the opportunity to see if your need can be addressed within this sprint.
Related
I am wondering that how to find the eVar names that are already implemented in the Adobe analytics.
Please let me know how to find in the bulk of all implemented eVars that will help me better understand user flows and build the charts efficiently.
There are a few ways to get bulk settings info. The most comprehensive is the Adobe Health Dashboard- https://express.adobe.com/page/tnNQGNlfzta3b/. Thisnot only tells you what each variable is named and what its settings are, but also shows you what type of data it is receiving. The downside is it requires adobe.io authorization, which can be a pain to get set up. It also only runs on PCs (because of its excel macros). I believe it also really only shows one report suite at a time.
You can also use tools like https://reportsuites.com/ to just get an export of variables and their settings.... it's particularly useful if you want ot compare across report suites. The main downside there is that adobe has made it hard to find the web services API credentials you need in order to run it.
I hope this is not a duplicate, but I couldn't find what I'm interested in.
I'm trying to build some automated tests that will use an iPhone. The best tool I can find for this seems to be UI Automation, but from what I can tell so far, I need to run it against a specific app. My tests need to be more general. For example, I want to be able to answer an incoming call in the default dialer.
I would like to be able to automate the iPhone itself, not a specific app. My tests might involve switching between apps or making calls. The main features I need are to be able to take a screenshot and touch certain coordinates on the screen, regardless of what is on the screen and running at the time.
Can anyone suggest the proper way to set this up? I'd like to use the supported UI Automation tools, but would like to use them in a more general way.
Thanks
How do you handle a bug in a specific SDK version in a released application? Say for example I've reported and received notification that a bug is known in a specific version of an SDK. Say the SDK engineers fix the problem in the next release. Do I then need to check if the user is running the buggy release and display an error message that they can't use a specific feature with a bug in it because it will crash their hardware? Is there a more graceful way? Do you display an alert and tell them to upgrade to the latest SDK? Do you completely remove the feature? Advice would be appreciated.
This is phrased to be agnostic as possible, but I am asking for the purposes of iPhone application development at this time. General answers for other platforms would be nice as well.
It depends on the nature of the bug and on the nature of the platform. With the iPhone, for example, you cannot just tell the user to upgrade his or her phone. If your goal is to support iPhone version X.Y, then you will need to support the corresponding SDK; whereas, targeting browser X version Y.Z or Java version X.Y, it may sometimes be acceptable to tell users to upgrade.* Giving the impression that your application can do something only to give an error message saying that it cannot support it for that version of the platform does not make for a good user experience. If possible, try to work around the deficiency in the platform (by possibly reimplementing code that supposedly works in the SDK) and provide the feature to the user. If that isn't possible, then disable it when running on the deficient version of the platform, but be sure to remove all traces of that feature from the application (so that users don't click on a button only for it to tell them that the button is completely useless). I should add that conditionally enabling/disabling features is only sensible in the case where the feature is not essential to application; if a feature is a core aspect of the application, then you'd better find a workaround or raise the minimum requirements as it would not be appropriate to ship a deficient application to your users.
*An example where telling users to upgrade is not reasonable would be business applications, since business sys admins tend to be unusually lazy and users have no power to upgrade by themselves.
I want to build a search engine for my project this year, so what I
need to implement in my project to get best grade (I need new ideas
for search for video or audio...). How and where can I start to learn
about this topic. I want to use Java and any framework on it. I know
that I can't build a Google Search, but I need to implement a new idea
in my project to get best grade.
I'd suggest that you start with an open source search engine like Lucene (Java or .NET) and start adding features on top of the plaform. Perhaps you could build a plugin for searching camera meta data (I.E., EXIF)?
PS. You might want to start marking the correct answers for the 20 questions you've already asked. Having an acceptance rate of 21% doesn't really give the recognition to those who work hard to answer your questions.
With JIRA, there are features that allow you to Start Progress and Stop Progress on an issue or various issues at any given time. Is there a way for me to go back and see a chart or a graphical representation of how my time was spent over a set period of time?
If I wanted to see how many bugs I worked on in April, and see how much time (graphically) was spent on each bug, could that be done, and if so, which version of JIRA would allow me to do that?
I dont think you can see for a given month how much time was spend on a task. You can see how much time was spent on a task, but not what time period it was for.
I'm sure you've already seen this:
http://www.atlassian.com/software/jira/docs/v3.13.3/timetracking_report.html
There's a Time Sheet Summary report that comes with the Timesheet Report and Portlet plugin - it shows you a list of the JIRA issues you've been working on together with the time per day for a configurable period. No charts, though, I'm afraid.
I think in general that time tracking is ripe for someone to write a really good JIRA plugin; I'm not totally happy with any of the current ones.
Go with the Tempo plug-in for jira. It is brilliant.
You can implement this visualization with the JIRA PDF View Plugin, like this:
Create a filter that returns the issues to be used for this visualization. Run it and invoke the plugin from the "View" dropdown menu.
Write a little Groovy script that iterates over the returned collection of issues, and:
Builds a mapping from "month" (key) to a data structure which holds a triplet of "totalTimeSpent, issuesWorkedOn, issuesFixed" (value).
At each issue compute the sum of the "time spent" records and add it to "totalTimeSpent".
Increment the two other counters accordingly.
When your script completes you have all input data to draw a timeseries chart.
Generate a JFreeChart TimeSeriesCollection dataset. It should contain 3 TimeSeries (3 lines) for the 3 types of values.
Create a simple PDF template that displays a single timeseries chart, which takes the dataset returned by the previous script to render a timeseries chart. Check the timeseries chart example in the tutorial for directions.
The final chart will be something like this:
Disclaimer: this is a paid add-on for JIRA, and I'm a developer working on it.