On Mon, Dec 11, 2017 at 3:36 PM, Simon Lees wrote:
> On 11/12/17 14:41, Jean-Philippe André wrote:
> > Cedric mentioned to me a couple of times how long it took large projects
> > using Qt4 to finally move on to Qt5. So we're trying to avoid that
> > bottleneck.
>
> I don't think for most large p
On 11/12/17 14:41, Jean-Philippe André wrote:
> Cedric mentioned to me a couple of times how long it took large projects
> using Qt4 to finally move on to Qt5. So we're trying to avoid that
> bottleneck.
I don't think for most large projects it wasn't that long for Qt4-Qt5,
the API changes were
On Mon, Nov 27, 2017 at 9:43 PM, Jean-Philippe André
wrote:
> Amitesh, please fix it!
>
>
Sungtaek has fixed it. :)
On Mon, Nov 27, 2017 at 8:49 PM, Andrew Williams
> wrote:
>
> > Hi,
> >
> > I have looked further and cannot find any evidence of efl.ui.panes in our
> > theme.
> > Can someone h
On Wed, Dec 6, 2017 at 3:39 AM, Andrew Williams
wrote:
> Hi,
>
> Looking at the API we have aggregated over the year and thinking about our
> chance to clean things up right now I can't help but feel uncomfortable
> about the following:
>
> eina_str_*
> eina_stringshare_*
> eina_slstr_*
>
+ eina_
Hi,
Just a word about panes and other new widgets: yes they got broken at some
point but should be fixed now that the "EO" theme API has been merged.
I think most of the existing Efl.Ui.Xxx widgets should soon become usable.
But I am not ready to commit yet for all of elementary (note: the model
On Sun, 10 Dec 2017 23:41:20 + Andrew Williams said:
> Hi,
>
> I had not intended to seem like I was giving up - I am pushing hard to try
> and have this discussion as I think it is important. The paragraph you
> referenced was intending to point out that our mailing list discussions do
> no
Hi,
I had not intended to seem like I was giving up - I am pushing hard to try
and have this discussion as I think it is important. The paragraph you
referenced was intending to point out that our mailing list discussions do
not have an open nature to them so others feel it is not worth
contributi
> Original Message
> Subject: Re: [E-devel] Interfaces API not in EFL namespace
> Local Time: December 9, 2017 1:01 AM
> UTC Time: December 9, 2017 9:01 AM
> From: a...@andywilliams.me
> To: Enlightenment developer list
>
> Hi,
>
> That makes sense, thanks.
> I’d like the API doc
On Sun, 10 Dec 2017 09:35:05 + Andrew Williams said:
> Hi,
>
> Apologies I was not aware of these plans that everyone agreed on. Can you
> please point me to this plan? It is very difficult to make a case for
> change without knowing the preceding plan that would need to change.
that all of
Hi,
Apologies I was not aware of these plans that everyone agreed on. Can you
please point me to this plan? It is very difficult to make a case for
change without knowing the preceding plan that would need to change.
To require irc logs or ML emails asking for this change is to imply that
we, the
10 matches
Mail list logo