Re: use-livecode Digest, Vol 163, Issue 13

[Richard Gaskin via use-livecode]

I'm a UX guy, so I advocate for the new user.

If RLE is faster, why penalize IDE users with slow performance?

If PNG is more commonly used, why penalize end-users running standalones?

It may be in the Dictionary, but if we already know the syntax for the 
export command, how would we know that we're also supposed to look up 
another entry for paintCompression?


Questions like this aren't intended to be harsh.  They're intended to 
encourage fresh thinking about things that may improve the user experience.


LC's job is to make the distance between "I want to write an app" and "I 
just shipped an app!" as short and painless as possible.


Remove the wrinkles, soften the rough edges, and delight emerges

- rg


hh wrote:

> Richard,
>
> these are hard words.
>
> 1) The diff is announced _loudly_ in the dict.
> 2) setting the paintcompression to RLE can speed up significantly in
> most cases. More than 16GB of RAM and huge GPUs are not from the time
> when this was introduced (when you was a young boy with curly hair).
>
> They choose simply the faster one for the standalone. And there are
> not this much cases where the diff has such a negative effect like
> for Peter R.
>
>> Richard G, wrote:
>> IMNSHO any differences between IDE and engine defaults should be a
>> preference option or it's a bug.
>>
>> The whole point of using an xTalk is to minimize the differences 
between

>> runtime and development.
>>
>> If the team saw fit to make PNG the default, it should be the
>> default in both environments.
>>
>> If they don't feel strongly enough that it should be the default, it
>> should be a preference option.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: use-livecode Digest, Vol 163, Issue 13

[hh via use-livecode]

Richard,

these are hard words.

1) The diff is announced _loudly_ in the dict.
2) setting the paintcompression to RLE can speed up significantly in
most cases. More than 16GB of RAM and huge GPUs are not from the time
when this was introduced (when you was a young boy with curly hair).

They choose simply the faster one for the standalone. And there are not
this much cases where the diff has such a negative effect like for Peter R.

> Richard G, wrote:
> IMNSHO any differences between IDE and engine defaults should be a 
> preference option or it's a bug.
> 
> The whole point of using an xTalk is to minimize the differences between 
> runtime and development.
> 
> If the team saw fit to make PNG the default, it should be the default in 
> both environments.
> 
> If they don't feel strongly enough that it should be the default, it 
> should be a preference option.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: use-livecode Digest, Vol 163, Issue 13

[Richard Gaskin via use-livecode]

Peter Reid wrote:

> Thanks for the advice, it was the paintCompression that caused the
> problem.  In the IDE it defaults to PNG but in the standalone it
> defaults to RLE instead.  As I didn't set it, the value was the
> default for the environment!  I simply added:
>
>set the paintCompression to png
>
> to my preOpenStack handler and the problem was solved!

IMNSHO any differences between IDE and engine defaults should be a 
preference option or it's a bug.


The whole point of using an xTalk is to minimize the differences between 
runtime and development.


If the team saw fit to make PNG the default, it should be the default in 
both environments.


If they don't feel strongly enough that it should be the default, it 
should be a preference option.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: use-livecode Digest, Vol 163, Issue 13

[Peter Reid via use-livecode]

Hi HH

Thanks for the advice, it was the paintCompression that caused the problem.  In 
the IDE it defaults to PNG but in the standalone it defaults to RLE instead.  
As I didn't set it, the value was the default for the environment!  I simply 
added:

set the paintCompression to png

to my preOpenStack handler and the problem was solved!

Thanks very much for solving this.

Peter
--
Peter Reid
Loughborough, UK

> On 6 Apr 2017, at 9:22pm, use-livecode-requ...@lists.runrev.com wrote:
> 
> Date: Thu, 6 Apr 2017 12:09:13 +0200
> From: hh >
> To: use-livecode@lists.runrev.com 
> Subject: Re: Standalone Magnify Problem
> Message-ID: <3af19fcf-001e-4dd6-a35c-ade7631c9...@hyperhh.de 
> >
> Content-Type: text/plain; charset=us-ascii
> 
>> Peter R. wrote:
>> I have it working fine when I'm in the development environment
>> but it's not working reliably in a standalone app. 
> 
> a) Did you already check to have the same paintcompression in both 
> environments?
> b) If you make such large images (why?) you may get a conflict with the 
> 8bit-coords
> limit. May be the standalone engine has still more of such limits included 
> for 
> 'formatted'-measurements than the IDE.
> c) Did you already check to have the same resizequality in both environments?
> ("best" may create an alphachannel)

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode