Guys, I'll just put that there, in no particular order: * doubles are a floating-point representation (on 64 bits), i.e. the "fractional" part has variable precision; yet overall "significand" precision is up to approximately 16 decimal digits. —Long story short, it's far more than enough for typical GPS coordinates. * via JCR spec 3.6.1.5: DOUBLE properties store instances of the Java primitive type `double`—in other words Jackrabbit stores double properties (such as 10.123456789) just fine. Rich also mentioned the DECIMAL (BigDecimal) property type as well, should you need "more".
Now Vaadin and NumberFormat come into play: * Vaadin TextFields bound to number properties get a converter automatically assigned (e.g. StringToDoubleConverter). * When applying the new value back on the server-side, Vaadin's AbstractTextField does this thing of beauty: [code]T doubleConvertedFieldValue = convertFromModel(convertToModel(newFieldValue))[/code] immediately updating the presentation to however this value would be rendered at a later point. Haven't dug yet why the approximated presentation value bubbles back to the model though. * Anyway, said-converter (AbstractStringToNumberConverter) uses NumberFormat's default "general-purpose instance" both ways (parse to model & format to presentation). Default value of its "maximumFractionDigits" is 3. Back to Magnolia, it's possible to override Vaadin's StringToDoubleConverter #getFormat() and setMaximumFractionDigits() to whatever more meaningful. Then configure that as your TextFieldDefinition's converterClass. Cheers, Mika -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=fb6148c5-9687-45db-9f07-8570c9a8c364 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
