Search Results

Search found 5 results on 1 pages for 'pradyumna'.

Page 1/1 | 1 

• Difference between chart, plot and graph

  - by Pradyumna

  I'm thinking of what would be the right terms to use in the UI of my new program, when referring to graphical data representations - i.e., whether to call them "charts", "plots" or "graphs". I was wondering how these terms are different, and when is it appropriate to use each of them? Thanks, Pradyumna

  Read the article

• Rich text editor for JSF 2

  - by Pradyumna

  Hi, I searched around for a basic WYSIWYG rich text editor that I can use in a JSF 2 (VDL) application, but found nothing satisfactory.. in the sense that: The editor is very extensive, and not configurable (like PrettyFaces) The editor doesn't work with VDL (like RichFaces) Multiple instances of the editor cannot be used on the same page (like Tomahawk t:htmlArea) I actually don't need all the fancy things like Fonts, Indenting/justification, undo/redo... just Bold, Italic, Lists and Hyperlinks would suffice. Do you know of something that works well in this scenario, as well as gives out XHTML compliant markup, and works well with partial page refreshes(f:ajax), or would you recommend that I write my own? Thank you! Pradyumna

  Read the article

• Are all "GET" requests to JSF "Initial Request"s?

  - by Pradyumna

  Hi, In JSF 1.1, I am assuming that GET requests are treated as initial requests (resulting in the creation of a new view), and POST requests are treated as Postbacks (resulting in the restoration of the old view). However, my application is behaving differently - it restores the same old view even for GET requests. Why does this happen? Is there a way to force the creation of a new view for GET requests? (My state-saving method is 'server'. I'm using MyFaces with JSP, and I have a t:saveState on a managed bean in the view) Regards, Pradyumna

  Read the article

• Can we have a component-scoped bean in a JSF2 composite component?

  - by Pradyumna

  Hi, I was wondering how I could create "component-scoped" beans, or so-to-say, "local variables inside a composite component" that are private to the instance of the composite component, and live as long as that instance lives. Below are more details, explained with an example: Suppose there is a "calculator" component - something that allows users to type in a mathematical expression, and evaluates its value. Optionally, it also plots the associated function. I can make a composite component that has: a text box for accepting the math expression two buttons called "Evaluate", and "Plot" another nested component that plots the function It is evidently a self-contained piece of function; so that somebody who wants to use it may just say <math:expressionEvaluator /> But obviously, the implementation would need a java object - something that evaluates the expression, something that computes the plot points, etc. - and I imagine it can be a bean - scoped just for this instance of this component, not a view-scoped or request-scoped bean that is shared across all instances of the component. How do I create such a bean? Is that even possible with composite components?

  Read the article

• What makes Groovy+Grails a more productive setup than J2EE?

  - by Pradyumna

  I'm coming across references to 'Grails' and 'Groovy' quite often these days.. mostly on how great a productivity booster it is as opposed to standard J2EE, or things like JSF, Struts etc.. And there's also an impressive set of case studies in support of this on their web site too. So I just thought I would explore some of it.. As I start off on this, I was curious if there was any material (link, blog, article, paper..) that explains what are the special features in Grails+Groovy (and not found elsewhere, in the J2EE world) that makes it a more productive environment to work in? Thanks!

  Read the article

1