On Tue, 12 May 2015 04:55:40 + Sebastian Dransfeld
said:
> tir. 12. mai 2015, 01:13 skrev Carsten Haitzler :
>
> On Mon, 11 May 2015 17:06:36 +0200 Stefan Schmidt
> said:
>
> > Hello.
> >
> > On 11/05/15 16:57, Stefan Schmidt wrote:
> > > Hello.
> > >
> > > On 09/04/15 14:34, Stefan Schmid
tir. 12. mai 2015, 01:13 skrev Carsten Haitzler :
On Mon, 11 May 2015 17:06:36 +0200 Stefan Schmidt
said:
> Hello.
>
> On 11/05/15 16:57, Stefan Schmidt wrote:
> > Hello.
> >
> > On 09/04/15 14:34, Stefan Schmidt wrote:
> >> Hello.
> >>
> >> On 01/04/15 14:30, Stefan Schmidt wrote:
> >>> Hello.
On Mon, 11 May 2015 17:06:36 +0200 Stefan Schmidt said:
> Hello.
>
> On 11/05/15 16:57, Stefan Schmidt wrote:
> > Hello.
> >
> > On 09/04/15 14:34, Stefan Schmidt wrote:
> >> Hello.
> >>
> >> On 01/04/15 14:30, Stefan Schmidt wrote:
> >>> Hello.
> >>>
> >>> I brought this up during the recent EF
Le 11 mai 2015 18:33, "Tom Hacohen" a écrit :
>
> On 11/05/15 17:11, Cedric BAIL wrote:
> > Hello,
> >
> > On Mon, May 11, 2015 at 5:06 PM, Stefan Schmidt
wrote:
> >> On 11/05/15 16:57, Stefan Schmidt wrote:
> >> Some pieces are still missing as I have nothign to compare them against
> >> ecore-d
On 11/05/15 17:11, Cedric BAIL wrote:
> Hello,
>
> On Mon, May 11, 2015 at 5:06 PM, Stefan Schmidt
> wrote:
>> On 11/05/15 16:57, Stefan Schmidt wrote:
>> Some pieces are still missing as I have nothign to compare them against
>> ecore-drm and I need to check why elua does not show up)
>>
>> For
Hello,
On Mon, May 11, 2015 at 5:06 PM, Stefan Schmidt wrote:
> On 11/05/15 16:57, Stefan Schmidt wrote:
> Some pieces are still missing as I have nothign to compare them against
> ecore-drm and I need to check why elua does not show up)
>
> For the rest I see this new APIs:
[snip]
> evas_3d_te
On 11/05/15 16:06, Stefan Schmidt wrote:
> Hello.
>
> On 11/05/15 16:57, Stefan Schmidt wrote:
>> Hello.
>>
>> On 09/04/15 14:34, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 01/04/15 14:30, Stefan Schmidt wrote:
Hello.
I brought this up during the recent EFL Dev Day and we discussed
Hello.
On 11/05/15 16:57, Stefan Schmidt wrote:
> Hello.
>
> On 09/04/15 14:34, Stefan Schmidt wrote:
>> Hello.
>>
>> On 01/04/15 14:30, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> I brought this up during the recent EFL Dev Day and we discussed it a bit.
>>>
>>> Now I want to bring it here for wider
Hello.
On 09/04/15 14:34, Stefan Schmidt wrote:
> Hello.
>
> On 01/04/15 14:30, Stefan Schmidt wrote:
>> Hello.
>>
>> I brought this up during the recent EFL Dev Day and we discussed it a bit.
>>
>> Now I want to bring it here for wider discussion and give everybody a
>> chance to have its say.
>>
Hello.
On 01/04/15 14:30, Stefan Schmidt wrote:
> Hello.
>
> I brought this up during the recent EFL Dev Day and we discussed it a bit.
>
> Now I want to bring it here for wider discussion and give everybody a
> chance to have its say.
>
> Background is that we struggle to have a good testing cove
Hello,
On Wed, Apr 1, 2015 at 2:30 PM, Stefan Schmidt
wrote:
> I brought this up during the recent EFL Dev Day and we discussed it a bit.
>
> Now I want to bring it here for wider discussion and give everybody a
> chance to have its say.
>
> Background is that we struggle to have a good testing c
Hello,
I totally agree with this idea. It can take more time to write test cases,
but we will get more benefit from it.
Regards,
Thiep Ha
On Wed, Apr 1, 2015 at 10:54 PM, Tom Hacohen
wrote:
> On 01/04/15 14:33, Jonathan Aquilina wrote:
> >
> >
> > I think before anything gets merged they shoul
On 01/04/15 14:33, Jonathan Aquilina wrote:
>
>
> I think before anything gets merged they should be accompanied by unit
> tests.
Yes, that's what Stefan is talking about. I've already had this policy
with Eo, Eolian and everything Text for a few years, and to some extent
Eina too. It works grea
I think before anything gets merged they should be accompanied by unit
tests.
---
Regards,
Jonathan Aquilina
Founder Eagle Eye T
On 2015-04-01 15:26, Tom Hacohen wrote:
> On 01/04/15 13:58, Jonathan Aquilina wrote:
>
>> I couldn't agree more, I am not an E developer, but would eventually l
On 01/04/15 13:58, Jonathan Aquilina wrote:
>
>
> I couldn't agree more, I am not an E developer, but would eventually
> like to become one. Unit testing not only for the new API features, but
> for any feature of E unit tests should be applied. I think if someone
> comes up with a use case even if
I would make it requirement on all new applications that are created for
E they should be developed with taking advantage of unit tests.
---
Regards,
Jonathan Aquilina
Founder Eagle Eye T
On 2015-04-01 15:05, Stefan Schmidt wrote:
> Hello.
>
> On 01/04/15 15:01, Stefan Schmidt wrote:
> Hel
I couldn't agree more, I am not an E developer, but would eventually
like to become one. Unit testing not only for the new API features, but
for any feature of E unit tests should be applied. I think if someone
comes up with a use case even if its a corner case a test case should be
written for
Hello.
On 01/04/15 14:58, Jonathan Aquilina wrote:
>
> I couldn't agree more, I am not an E developer, but would eventually
> like to become one. Unit testing not only for the new API features,
> but for any feature of E unit tests should be applied. I think if
> someone comes up with a use case e
Hello.
On 01/04/15 15:01, Stefan Schmidt wrote:
> Hello.
>
> On 01/04/15 14:58, Jonathan Aquilina wrote:
>> I couldn't agree more, I am not an E developer, but would eventually
>> like to become one. Unit testing not only for the new API features,
>> but for any feature of E unit tests should be a
19 matches
Mail list logo
