On 02/07/2016 15:46, Mark Waddingham wrote:
I'm really hoping (though I'm not clear if this is true or not) that
the Native Field Object is not implemented as another new widget but
as a new presentation of the LiveCode field object. A new widget would
obviously be better than the using the
On 2016-07-04 13:13, Ben Rubinstein wrote:
On 01/07/2016 17:28, Richard Gaskin wrote:
Buttons are already quite good on macOS, as are fields, tabs, progress
bars,
and most others.
Does that mean that these items are drawn by LiveCode, rather than
using native API calls? If so, couldn't the
On 02/07/2016 14:57, Mark Waddingham wrote:
I'm minded of a well-known proverb:
"Give a man a fish and you feed him for a day; teach a man to fish and you
feed him for a lifetime"
Without suggesting that this detracts from your general remarks, I can't
resist pointing out that in my view
On 01/07/2016 17:28, Richard Gaskin wrote:
Buttons are already quite good on macOS, as are fields, tabs, progress bars,
and most others.
Does that mean that these items are drawn by LiveCode, rather than using
native API calls? If so, couldn't the iOS default to this macOS "theme"
rather
On 2016-07-01 12:33, Ben Rubinstein wrote:
That's why I think "it would be better if" the existing basic controls
worked reasonably well on mobile platforms, and the existence of the
various libraries, widgets, and mobileControlxxx functions - while all
of them being extremely valuable - does
On 2016-07-01 11:49, Terence Heaford wrote:
I think I understand, a native field for iOS (plus other mobile
platforms) is a stretch goal.
Well, actually, the 'stretch goal' (like all of stretches for Infinite
LiveCode) are fully documented examples how to 'do that kind of thing'
with
On 2016-07-01 21:03, Terence Heaford wrote:
The button and popup button/menu. To me the text seems a little low
within the display.
Please report any minor display discrepancies you see in the quality
center with pictures for comparison and OS details.
Fraser has done a lot of work to
> On 1 Jul 2016, at 17:28, Richard Gaskin wrote:
>
> Buttons are already quite good on macOS, as are fields, tabs, progress bars,
> and most others.
I agree but there a subtle display errors.
The button and popup button/menu. To me the text seems a little low
Terence Heaford wrote:
> So with regard to Mac OS if we/I want native controls for:
>
> Buttons,
> Fields,
> Tabs,
> DataGrid (NSTable)
> etc.
>
> I will have to roll my own in LCB (when available for this) or wait
> for LiveCode to require to do it via a stretch goal?
If you're looking for an
Mark Waddingham wrote:
On 2016-06-30 21:25, Richard Gaskin wrote:
OS APIs change out from under the engine with expensive regularity,
and all the while, even as mobile enhancements would indeed be
valuable, there's a rather long list of other things we're asking them
to do as well.
H, at
On 30/06/2016 20:25, Richard Gaskin wrote:
But while it's easy to write a sentence or two of things describing others to
do, it's not quite as easy to actually do the work.
Very true! And I realised after I sent my last email that I was sounding like
one of those people
But:
> On 1 Jul 2016, at 09:13, Mark Waddingham wrote:
>
> On 2016-07-01 00:38, Terence Heaford wrote:
>> Perhaps LiveCode should spend time incorporating the native controls
>> for each platform.
>
> Hence:
>
> - widgets
>
> -
On 2016-06-30 21:25, Richard Gaskin wrote:
OS APIs change out from under the engine with expensive regularity,
and all the while, even as mobile enhancements would indeed be
valuable, there's a rather long list of other things we're asking them
to do as well.
H, at the end of the day,
On 2016-07-01 00:38, Terence Heaford wrote:
Perhaps LiveCode should spend time incorporating the native controls
for each platform.
Hence:
- widgets
- https://livecode.com/project/infinite-livecode/
- https://livecode.com/project/infinite-livecode-native-field-object/
Warmest
: vrijdag 1 juli 2016 00:38
To: How to use LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Controls on mobile apps - am I missing something?
> On 30 Jun 2016, at 20:25, Richard Gaskin <ambassa...@fourthworld.com> wrote:
>
> OS APIs change out from under the engine with
> On 30 Jun 2016, at 20:25, Richard Gaskin wrote:
>
> OS APIs change out from under the engine with expensive regularity, and all
> the while, even as mobile enhancements would indeed be valuable, there's a
> rather long list of other things we're asking them to do
Ben Rubinstein wrote:
On 29/06/2016 00:28, Richard Gaskin wrote:
People do all sorts of things. Some might even have a 45-degree angled
progress bar. Not everything folks might want comes in the tin. :)
Yep, but lots of people want horizontal and vertical progress bars, which do
come in
On 29/06/2016 00:28, Richard Gaskin wrote:
People do all sorts of things. Some might even have a 45-degree angled
progress bar. Not everything folks might want comes in the tin. :)
Yep, but lots of people want horizontal and vertical progress bars, which do
come in our tin - they just
Ben Rubinstein wrote:
> A checkbox on each desktop platform takes on something at least
> approximately akin to the native appearance.
...
> But on iOS there's not the slightest attempt, which seems odd
> considering how much effort has gone into supporting the mobile
> platforms.
>
> And yes,
Richard,
Thanks for your reply (and thanks Mike for the tmControls recommendation). I'm
aware that we can make our own controls; and can use some native ones.
But surely the point of LiveCode being cross platform is that we shouldn't
need to?
A checkbox on each desktop platform takes on
Spend the money and buy tmControls from Scott Rossi. Every app I have
written is skinned the way I want it, and when I want something a little
different, I'm able to customize them as I choose.
On Mon, Jun 27, 2016 at 2:41 PM, Richard Gaskin
wrote:
> Ben Rubinstein
Ben Rubinstein wrote:
> My previous mobile app dabbling had involved entirely custom
> interfaces. Now I'm trying to create a more straightforward app
> with a more conventional interface - and I'm getting a horrible
> dichotomy between the widgets (header bar, navigation bar, switch
> control,
My previous mobile app dabbling had involved entirely custom interfaces. Now
I'm trying to create a more straightforward app with a more conventional
interface - and I'm getting a horrible dichotomy between the widgets (header
bar, navigation bar, switch control, segmented control) and the
23 matches
Mail list logo