I'd say go with Joda now, as it's already in ERJars anyway, so there's no
dependency to add. Even if Java 8 appears in 2013, it will still be a long time
until we can make Java 8 a requirement to use Wonder for everybody.
Am 16.11.2012 um 20:28 schrieb Johann Werner :
> Then perhaps we should
+1
Envoyé de mon iPhone
Le 2012-11-16 à 14:29, "Johann Werner" a écrit :
> Then perhaps we should make an ERXDateTimeFormatter that encapsulates a
> SimpleDateFormat object now and later on we can replace it with something
> from Joda/Java 8+/… without changing the outer class / API.
>
>
>
Then perhaps we should make an ERXDateTimeFormatter that encapsulates a
SimpleDateFormat object now and later on we can replace it with something from
Joda/Java 8+/… without changing the outer class / API.
Am 16.11.2012 um 18:11 schrieb Chuck Hill :
> Easiest migration would be a SimpleDateFor
If all goes well, Java 8 will have a new Date/Time API that's based on Joda
Time. JSR-310 project lead is the author of Joda Time.
http://jcp.org/en/jsr/detail?id=310
https://github.com/ThreeTen/threeten
Am 16.11.2012 um 18:11 schrieb Chuck Hill :
> Easiest migration would be a SimpleDateForm
On 2012-11-15, at 4:19 PM, Johnny Miller wrote:
> I should for my own betterment...
>
> I wonder what would be the smart way to do it?
This one might not be too hard. And the community does need more people who
can make changes to the plugin.
> In the API editor you do get a list of choices
Easiest migration would be a SimpleDateFormat that was extended or wrapped to
understand the NSTimestampFromatter symbols. Or perhaps the same for
DateTimeFormatter from Joda Time? I am not sure if we should stick with core
Java classes for the core functionality, or go for fancy with Joda and
In my opinion, go for Joda Time, but perhaps wait how the integration of that
in Java 8 turns out in detail.
Am 16.11.2012 um 10:17 schrieb Johann Werner :
> That's true but it is probably good to move to something "supported" as Apple
> must have had a good reason to deprecate that class. The
That's true but it is probably good to move to something "supported" as Apple
must have had a good reason to deprecate that class. The community will have to
decide which class should take its succession though:
SimpleDateFormat from standard Java (not thread safe)
FastDateFormat from commons-la
Am 16.11.2012 um 00:52 schrieb Michael Sharp :
> They seem to be defined in code in WOLips. The possible values for "defaults"
> here:
>
> org.objectstyle.wolips.bindings.api.IApiBinding
>
> public static final String[] ALL_DEFAULTS = new String[] { "Undefined",
> IApiBinding.ACTIONS_DEFAULT,
I should for my own betterment...
I wonder what would be the smart way to do it?
In the API editor you do get a list of choices that corresponds to the list in
Sharpy's email. Maybe if one of the choices was "Custom" a table could appear,
not unlike the bindings, where you could add the sugges
You could always extend WOLips!
:-)
On 2012-11-15, at 3:57 PM, Johnny Miller wrote:
> Bummer...
>
> Thanks anyway!
>
> On Nov 15, 2012, at 1:52 PM, Michael Sharp wrote:
>
>> They seem to be defined in code in WOLips. The possible values for
>> "defaults" here:
>>
>> org.objectstyle.wolips
Bummer...
Thanks anyway!
On Nov 15, 2012, at 1:52 PM, Michael Sharp wrote:
> They seem to be defined in code in WOLips. The possible values for "defaults"
> here:
>
> org.objectstyle.wolips.bindings.api.IApiBinding
>
> public static final String[] ALL_DEFAULTS = new String[] { "Undefined",
They seem to be defined in code in WOLips. The possible values for "defaults"
here:
org.objectstyle.wolips.bindings.api.IApiBinding
public static final String[] ALL_DEFAULTS = new String[] { "Undefined",
IApiBinding.ACTIONS_DEFAULT, "Boolean", "YES/NO", "Date Format Strings",
"Number Format St
I think what you are referring to is hard coded for specific binding types in
the component editor.
Chuck
On 2012-11-15, at 3:39 PM, Johnny Miller wrote:
> Hi Lon,
>
> Actually, I'm wondering how to add code completion to the value of the
> binding.
>
> i.e. when you set value of the datef
Ah, gotcha…yeah for values like dateformat there isn't any completion (that
I know of). For other values like "value" it will complete after the $.
So http://www.kahalawai.com> | e-mail <+jlmil...@kahalawai.com>
>
> On Nov 15, 2012, at 1:30 PM, Lon Varscsak wrote:
>
> Create an .api file (it's a
I've wondered myself, so I just had a sniff around some API files.
e.g. ERXEditDateJavascript.api contains the following:
… and offers the right hand side completion of exactly that in the wod editor
- date format strings. Changing this to:
has the expected effect - number
Hi Lon,
Actually, I'm wondering how to add code completion to the value of the binding.
i.e. when you set value of the dateformat binding for WOString the code
completion will give you a suggested list of possible date formats i.e. %m/%d/%y
I image that could also be set in the .api file but I
Create an .api file (it's a tab in WOLips on the component) and put what
bindings you want in there.
-Lon
On Thu, Nov 15, 2012 at 3:14 PM, Johnny Miller wrote:
> Hi,
>
> I would like to add code completion to a component the way in WOString it
> will give you a list of suggested number or date f
Hi,
I would like to add code completion to a component the way in WOString it will
give you a list of suggested number or date formats for the respective binding.
How do you declare this in your component?
Thanks in advance,
Aloha,
Mr. Johnny Miller
Web Development Manager
Kahalawai Media Comp
19 matches
Mail list logo
