Jose Gonzalez wrote:
>> > >However you have it (though rel coords would seem best),
>> > > if you really want ewl to be a flexible tool for building
>> > > artistic, rich apps, then you'll want a natural way to
>> > > arbitrarily position child *widgets* - not just evas objects..
>> > > an
On Thu, Mar 20, 2008 at 6:56 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
> Just to make it a bit more flexible though, let's also
> allow for 'importing' evas objects - if possible (not sure if ewl
> has this at the moment, but just in case).
The way we usually do this is outlined in the
> > >However you have it (though rel coords would seem best),
> > > if you really want ewl to be a flexible tool for building
> > > artistic, rich apps, then you'll want a natural way to
> > > arbitrarily position child *widgets* - not just evas objects..
> > > and to allow for custom kin
> >However you have it (though rel coords would seem best),
> > if you really want ewl to be a flexible tool for building
> > artistic, rich apps, then you'll want a natural way to
> > arbitrarily position child *widgets* - not just evas objects..
> > and to allow for custom kinds of chil
Jose Gonzalez wrote:
> > You can do this now with Ewl. The only problem being, everything
> > is absolute coordinates which is a bit strange for this kind of
> > widget. If you want to do this, inherit ewl_box, remove configure
> > event, add your own configure and use ewl_object_place to put
On Wed, Mar 19, 2008 at 11:42 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote:
>
> However you have it (though rel coords would seem best),
> if you really want ewl to be a flexible tool for building artistic,
> rich apps, then you'll want a natural way to arbitrarily position
> child *widgets*
> You can do this now with Ewl. The only problem being, everything
> is absolute coordinates which is a bit strange for this kind of
> widget. If you want to do this, inherit ewl_box, remove configure
> event, add your own configure and use ewl_object_place to put the
> widgets where you wan
Peter Wehrfritz wrote:
> dan sinclair schrieb:
>> Currently Ewl positions widgets based on absolute coordinates. This
>> works but isn't unnecessarily optional. Thoughts on changing the
>> internals of Ewl to use parent relative placement of widgets?
>>
>> This would, hopefully, simplify some of
Jose Gonzalez wrote:
> Dan wrote:
>
> > Currently Ewl positions widgets based on absolute coordinates. This
> > works but isn't unnecessarily optional. Thoughts on changing the
> > internals of Ewl to use parent relative placement of widgets?
> >
> > This would, hopefully, simplify some
dan sinclair schrieb:
> Currently Ewl positions widgets based on absolute coordinates. This
> works but isn't unnecessarily optional. Thoughts on changing the
> internals of Ewl to use parent relative placement of widgets?
>
> This would, hopefully, simplify some of the container code and allow
Dan wrote:
> Currently Ewl positions widgets based on absolute coordinates. This
> works but isn't unnecessarily optional. Thoughts on changing the
> internals of Ewl to use parent relative placement of widgets?
>
> This would, hopefully, simplify some of the container code and allow
>
11 matches
Mail list logo
