Mined Opinions For API: vanilla

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations.I'll check it out though, thanks.. details
  • JSON.stringify(jsonObj) before passing it to the query string, a la CODETERM4 - which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor-like event to let me change the query parameters.. details
  • It turns out that vanilla Struts2 doesn't accept query strings in the format CODETERM1 (feel free to correct me on this).. details
  • Gson 1.7.1 and 2.0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered.. details
  • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps.. details
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.. details
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.. details
Summaries the opinions about vanilla using topic modeling.
  • 0. query final assignment property pass gson parameter hashmaps change forgo: 5
    • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations.I'll check it out though, thanks.. details
    • It turns out that vanilla Struts2 doesn't accept query strings in the format obj[idx][property] (feel free to correct me on this).. details
    • JSON.stringify(jsonObj) before passing it to the query string, a la &jsonData=[{property:'value'}] - which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor-like event to let me change the query parameters.. details
    • Gson 1.7.1 and 2.0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered.. details
    • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps.. details
  • 0. practicable forsmall model lot allocate hog amount supply unfortunatelyit full: 1
    • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.. details
Summaries of the opinions about vanilla 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.
  • Gson 1 7 1 and 2 0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered .
  • It turns out that vanilla Struts2 doesn't accept query strings in the format obj[idx][property] (feel free to correct me on this) .
  • JSON stringify(jsonObj) before passing it to the query string, a la &jsonData=[{property:'value'}] which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor like event to let me change the query parameters .
  • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps .
  • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations I'll check it out though, thanks .
  • Gson 1 7 1 and 2 0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered .
  • It turns out that vanilla Struts2 doesn't accept query strings in the format obj[idx][property] (feel free to correct me on this) .
  • JSON stringify(jsonObj) before passing it to the query string, a la &jsonData=[{property:'value'}] which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor like event to let me change the query parameters .
  • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps .
  • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations I'll check it out though, thanks .
  • Gson 1 7 1 and 2 0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered .
  • It turns out that vanilla Struts2 doesn't accept query strings in the format obj[idx][property] (feel free to correct me on this) .
  • JSON stringify(jsonObj) before passing it to the query string, a la &jsonData=[{property:'value'}] which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor like event to let me change the query parameters .
  • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps .
  • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations I'll check it out though, thanks .
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory .
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory .
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory .
Summaries of the opinions about vanilla using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about vanilla 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).
Performance:
  • N/A
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.
Usability:
  • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations.I'll check it out though, thanks.
  • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.
  • Usability: 5
    1. general: 5
      • Everything has worked really well so far with the vanilla setup and the JsonProperty, JsonIgnore, and JsonFilter annotations.I'll check it out though, thanks.. details
      • JSON.stringify(jsonObj) before passing it to the query string, a la CODETERM4 - which in this case, I can't do since Kendo UI grid doesn't seem to have an interceptor-like event to let me change the query parameters.. details
      • It turns out that vanilla Struts2 doesn't accept query strings in the format CODETERM1 (feel free to correct me on this).. details
      • Gson 1.7.1 and 2.0 both respect final field assignments during vanilla deserialization operations, and the initial final field assignments are not altered.. details
      • Its the same reason you wouldn't forgo classes in a java program in favor of passing around a bunch of HashMaps.. details
  • Performance: 1
    1. general: 1
      • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.. details
  • Usability: 1
    1. general: 1
      • vanilla JSON parser supplied with android can parse data, unfortunatelyit builds full JSON model in memory (like DOM parser for XML ) - this works fine forsmall data amounts, but is not practicable for slightly bigger data as it allocates and hogs a lot of memory.. details