[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Background



On Thu, Sep 22, 2011 at 9:13 AM, Peter Slegg <p.slegg@scubadivers.co.uk> wrote:
> On Mon, 19 Sep 2011 20:08:12 , "Jean-François Lemaire" <jflemaire@skynet.be> wrote:
>> On Monday 19 Sep 2011 19:41:07 Peter Slegg wrote:
>> > On Thu, 15 Sep 2011 19:04:57 , "Helmut Karlowski" <helmut.karlowski@ish.d
>> > > Jo Even Skarstein wrote:
>> > > > > It is up to applications to use that facility to draw a desktop.
>> > > >
>> > > > This is not how it works. The AES draws the desktop. Period. The
>>
>> > How it works is irrelevant. Users don't care about the inplementation.
>> > They DO care that their desktops are broken.
>>
>> What Jo Even is saying is that GEM has been working like this for 25 years.
>>
>> It's the way it was designed, as far as I know.
>
> So why did it turn my Thing background yellow ?!
>
> It surely wasn't designed to do that and has ever done it before.
>
we are still talking about daily builds here are we not, so I would
say to expect certain issues as you found, especially while new parts
are being added to the system..

As long as Helmut/others are still using the bugtracker, posting for
daily build should be acceptable only if build filename is supplied,
as the bugs may already be gone before posted and next build

..

This does beg the question of another stable release, as all these new
bits are all well and good, but if you cant guarantee th stability of
a release, it is no good for promotion, demonstration or daily use
testing

I can guarantee that if there was a point release, that a lot of
things unrelated to the new additions will turn up too, and overall
the fixing of those issues will only help the stability of daily
builds..

I request a point release, that will have bug fixes applied, to be
made after the current desktop & shortcuts issues are ironed out.
These must also include:
define desktop from config
define shortcuts from config
failover to defaults on files defined in config
hard fail only if xaaes can not run without specific default
define img folder in config (done?)
define gradient in config file (done?)
define xaobj in config (done?)
define widgets in config (done)

ATM I would not include in this list any inter app talk, and any
special fs entries that require too much time/code/testing, unless
they are simple additions (ie gradients is already done) that can
successfully be tested from an external app..

That should allow for a point release (that can be updated with bug
fixes) within about a week (right Helmut :)

Actually timeframe should not be limit per se, but sett of some hard
limits should be

>
> How about using the Task Mgr to start the Desktop ?
>
> Regards,
>
> Peter
>
as an option, some people might use this, but remember this is "not
the fuji way".. but as long as it is an option

Paul