As I said in IRC, I also prefer the first. (And update the docs).
On Fri, Feb 11, 2011 at 2:50 AM, Daniel Juyung Seo
<[email protected]>wrote:
> > Since it is released already, how about keep the both of them for now?
> > ('elipsis' can be removed only in documents and keep it compiling
> available for now and then clear it perfectly later)
>
> Hmm that sounds reasonable.
> So we have below options.
>
> 1. Add 'ellipsis' so maintain both 'elipsis' and 'ellipsis' but remove
> 'elipsis' from document.
> 2. Fix 'elipsis' to 'ellipsis' (maybe not possible)
> 3. Do nothing.
>
> Any ideas?
> Thanks.
>
> Daniel Juyung Seo (SeoZ)
>
> -----Original Message-----
> From: ChunEon Park [mailto:[email protected]]
> Sent: Friday, February 11, 2011 9:02 AM
> To: Daniel Juyung Seo; [email protected]
> Subject: Re: [E-devel] elipsis typo in edje_cc_handlers.c
>
>
> Hi,
>
>
> I prefer number 1
>
> Even elipsis is easier for typing and users know it,
>
> It may cause confusion to users who does not familiar with edje script.
>
>
> Since it is released already, how about keep the both of them for now?
>
> ('elipsis' can be removed only in documents and keep it compiling
> available
> for now
>
> and then clear it perfectly later)
>
>
> Thanks.
>
>
> ------- Original Message -------
>
> Sender : Daniel Juyung Seo<[email protected]>
>
> Date : 2011-02-11 01:56 (GMT+09:00)
>
> Title : [E-devel] elipsis typo in edje_cc_handlers.c
>
>
> Hello,
> I found a typo 'elipsis' in edje_cc_handlers.c
> 'elipsis' should be changed to 'ellipsis'
> EDC reference document also has typo.
> http://docs.enlightenment.org/auto/edje/edcref.html
> We, however, can't remove this because it's in EFL 1.0.
> Anyhow, I think we should have a right one, 'ellipsis'.
> How do you guys think?
> 1. Add 'ellipsis' so maintain both 'elipsis' and 'ellipsis'
> 2. Fix 'elipsis' to 'ellipsis' (maybe not possible)
> 3. Do nothing.
> Daniel Juyung Seo (SeoZ)
>
>
> ----------------------------------------------------------------------------
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> enlightenment-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
>
> [cid:[email protected]]
>
>
>
> [SeenTimeChecker?do=764d2c50b23762c0d32cffbe659419f850c4d9ce1f511bc36b754d17
>
>
> d001ca18ba777c355c197185c465c2cf80a2b7ef9aba4bb3b2b5ca43ddd7e184e0604d958075
> b6b33f32d245b7f8aafe245478a5f1d21d5ebee74427cf878f9a26ce15a0]
>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> enlightenment-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
--
Tom.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
