Mined Opinions For API: eclipse-tools

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing".. details
  • There do appear to be URL_http://sourceforge.net/projects/jaxb-builder/ [Eclipse-tools] that automate this manual drudgery.. details
Summaries the opinions about eclipse-tools using topic modeling.
  • 0. result write structure plumbing logic lot real call business invest: 1
    • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing".. details
  • 0. drudgery manual automate: 1
    • There do appear to be Eclipse-tools that automate this manual drudgery.. details
Summaries of the opinions about eclipse-tools using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing" .
  • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing" .
  • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing" .
  • There do appear to be Eclipse tools that automate this manual drudgery .
  • There do appear to be Eclipse tools that automate this manual drudgery .
  • There do appear to be Eclipse tools that automate this manual drudgery .
Summaries of the opinions about eclipse-tools using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about eclipse-tools using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Usability:
  • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing".
  • There do appear to be URL_http://sourceforge.net/projects/jaxb-builder/ [Eclipse-tools] that automate this manual drudgery.
  • Usability: 1
    1. general: 1
      • The net effect is that rather than writing lots of little getJSONObject() calls, you invest in setting up corresponding classes, this should result in nicely structured code, where the processing of the data, that is the real business logic, is separated from the parsing code, which I view as "plumbing".. details
  • Usability: 1
    1. general: 1
      • There do appear to be URL_http://sourceforge.net/projects/jaxb-builder/ [Eclipse-tools] that automate this manual drudgery.. details