On Thu, 25 Jun 2015 00:31:56 +0900
JoonCheol Park wrote:
> Thanks pq and all,
>
> I didn't think this would be hot topic :-) All reply from all in this
> thread was very very helpful to understand current weston project for me.
>
>
> 2015-06-24 16:52 GMT+09:00 Pekka Paalanen :
>
> > Hi all
>
Thanks pq and all,
I didn't think this would be hot topic :-) All reply from all in this
thread was very very helpful to understand current weston project for me.
2015-06-24 16:52 GMT+09:00 Pekka Paalanen :
> Hi all
>
> TL;DR:
>
> Everything is open, let's make small steps only, in priority ord
Hi all
TL;DR:
Everything is open, let's make small steps only, in priority order
determined by the intended audience. We have as many release cycles of
time to use for improving the code and interfaces as we want.
On Wed, 24 Jun 2015 02:40:08 +0900
JoonCheol Park wrote:
> Hi Giulio, pq!
>
>
On Tue, 23 Jun 2015 11:22:18 -0700
Bill Spitzak wrote:
> On Tue, Jun 23, 2015 at 10:49 AM, Giulio Camuffo
> wrote:
>
> > Well, but you are adding weston specific stuff into the backends code,
> > that is the options handling. In libweston the backends do not parse
> > the command line or the co
On Tue, Jun 23, 2015 at 07:29:17PM +0900, JoonCheol Park wrote:
> Instead of adding available backends and usage outputs at build time,
> this patch finds all available backend plugins in MODULEDIR and prints
> them. It also prints usage output for selected backend by calling
> "backend_usage()" in
On Tue, Jun 23, 2015 at 12:48:13PM -0700, Jon A. Cruz wrote:
> Actually... yesterday I was just bouncing off of Bryce some ideas in
> regards to tuning up the options parser to clean up a bit of the current
> mess in regards to params, help messages, keeping multiple areas in
> sync, etc.
Yeah at
Actually... yesterday I was just bouncing off of Bryce some ideas in
regards to tuning up the options parser to clean up a bit of the current
mess in regards to params, help messages, keeping multiple areas in
sync, etc.
I *think* I've been starting to see some of the same issues that
JoonCheol is
2015-06-23 21:22 GMT+03:00 Bill Spitzak :
> On Tue, Jun 23, 2015 at 10:49 AM, Giulio Camuffo
> wrote:
>>
>> Well, but you are adding weston specific stuff into the backends code,
>> that is the options handling. In libweston the backends do not parse
>> the command line or the config file, so all
2015-06-23 21:57 GMT+03:00 JoonCheol Park :
>
>
> 2015-06-24 2:49 GMT+09:00 Giulio Camuffo :
>>
>> 2015-06-23 20:40 GMT+03:00 JoonCheol Park :
>> > Hi Giulio, pq!
>> >
>> >
>> > 2015-06-23 20:57 GMT+09:00 Pekka Paalanen :
>> >>
>> >> On Tue, 23 Jun 2015 14:14:53 +0300
>> >> Giulio Camuffo wrote:
>
2015-06-24 2:49 GMT+09:00 Giulio Camuffo :
> 2015-06-23 20:40 GMT+03:00 JoonCheol Park :
> > Hi Giulio, pq!
> >
> >
> > 2015-06-23 20:57 GMT+09:00 Pekka Paalanen :
> >>
> >> On Tue, 23 Jun 2015 14:14:53 +0300
> >> Giulio Camuffo wrote:
> >>
> >> > Hi,
> >> >
> >> > This kinda goes in the opposite
On Tue, Jun 23, 2015 at 10:49 AM, Giulio Camuffo
wrote:
> Well, but you are adding weston specific stuff into the backends code,
> that is the options handling. In libweston the backends do not parse
> the command line or the config file, so all the backend options are
> weston specific.
>
This
2015-06-23 20:40 GMT+03:00 JoonCheol Park :
> Hi Giulio, pq!
>
>
> 2015-06-23 20:57 GMT+09:00 Pekka Paalanen :
>>
>> On Tue, 23 Jun 2015 14:14:53 +0300
>> Giulio Camuffo wrote:
>>
>> > Hi,
>> >
>> > This kinda goes in the opposite direction to my libweston patches. In
>> > that series i move the c
Hi Giulio, pq!
2015-06-23 20:57 GMT+09:00 Pekka Paalanen :
> On Tue, 23 Jun 2015 14:14:53 +0300
> Giulio Camuffo wrote:
>
> > Hi,
> >
> > This kinda goes in the opposite direction to my libweston patches. In
> > that series i move the command line handling away from the backends
> > code to mak
On Tue, 23 Jun 2015 14:14:53 +0300
Giulio Camuffo wrote:
> Hi,
>
> This kinda goes in the opposite direction to my libweston patches. In
> that series i move the command line handling away from the backends
> code to make them work in multiple compositors. This moves even more
> compositor-speci
Hi,
This kinda goes in the opposite direction to my libweston patches. In
that series i move the command line handling away from the backends
code to make them work in multiple compositors. This moves even more
compositor-specific stuff in the backends so we need to decide if we
want this or libwe
Instead of adding available backends and usage outputs at build time,
this patch finds all available backend plugins in MODULEDIR and prints
them. It also prints usage output for selected backend by calling
"backend_usage()" in the plugin.
By this patch, we can remove all hardcode for backends fro
16 matches
Mail list logo
