Re: NAVRAD was: lcb missing manual

[Mike Kerner via use-livecode]

What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:
* an autoHilite boolean, so you can intercept clicks before the selected
icon changes instead of after, and
* icon zoom
Now it's also got margins.
https://github.com/macMikey/LC-NavRad
___
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: [semi-OT] PDF on the fly

[jbv via use-livecode]

I am using Safari 15.6 (15613.3.9.1.7, 15613)

But I finally found the origin of the problem :
  put header "Content-Length: " & number of chars of myPDF

After removing that line from the header, files download and
display fine in Safari, as in other browsers.
So far I have no rational explanation though.

Best,
jbv

Le 2022-09-14 17:00, matthias rebbe via use-livecode a écrit :

I just tested on quartz.on-rev.com  with LC
Server 9.6.0.

I've created a textfile with a size of 1mb.

tested with this script and it worked. I even tested with put header
instead of put new header.
put new header "Content-Disposition: attachment; FileName=" & 
"justsomeText.txt"

put URL("binfile:" & "justsomeText.txt")
?>

Which version of Safari do you have?



Am 14.09.2022 um 22:44 schrieb jbv via use-livecode 
:


Hi guys,

Thank you for your answers.
No matter what I try, the problem remains the same on Safari.
My LC script runs on my on-rev account, and it uses LC 9.6.
Could this really be the problem ?

Best,
jbv

___
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


___
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


___
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: NAVRAD was: lcb missing manual

[Ralph DiMola via use-livecode]

Also another new feature is the Icon Fill property. If enabled: 1)If there
is no label the icon is enlarged slightly and centered vertically 2) In the
PI the label can be deleted without the "New Item" inserted into the label.
I did this because among others the social media icons don't need labels.

All new features are fully documented.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Mike Kerner via use-livecode
Sent: Thursday, September 15, 2022 10:45 AM
To: How to use LiveCode
Cc: Mike Kerner
Subject: Re: NAVRAD was: lcb missing manual

What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:
* an autoHilite boolean, so you can intercept clicks before the selected
icon changes instead of after, and
* icon zoom
Now it's also got margins.
https://github.com/macMikey/LC-NavRad
___
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


___
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: NAVRAD was: lcb missing manual

[Ralph DiMola via use-livecode]

Docs aside... I still think that widgets and lcb is one of best additions to
LC. Community collaboration like this will make for better documentation and
more new/improved widgets. A robust library of widgets can only help LC to
penetrate the market. If only we had these when I started...

Shout out to Mike K. for all the help!

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


___
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: NAVRAD was: lcb missing manual

[Alex Tweedly via use-livecode]

On 15/09/2022 15:44, Mike Kerner via use-livecode wrote:

What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:


I see the code has an outdated copyright statement, which would (I 
think) currently mean that any app using it would (potentially) become 
open-source (GPL). If that;s not the intent, maybe it could be updated ?


Currently it says


  Copyright (C) 2015-2022 LiveCode Ltd.icon

  This file is part of LiveCode.

  LiveCode is free software; you can redistribute it and/or modify it 
under

  the terms of the GNU General Public License v3 as published by the Free
  Software Foundation.

  LiveCode is distributed in the hope that it will be useful, but 
WITHOUT ANY

  WARRANTY; without even the implied warranty of MERCHANTABILITY or
  FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
  for more details.

  You should have received a copy of the GNU General Public License
  along with LiveCode.  If not see .  */


Alex.




Copyright (C) 2015-2022 LiveCode Ltd.icon



This file is part of LiveCode.



	LiveCode is free software; you can redistribute it and/or modify it 
under


the terms of the GNU General Public License v3 as published by the Free

Software Foundation.



	LiveCode is distributed in the hope that it will be useful, but 
WITHOUT ANY


WARRANTY; without even the implied warranty of MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License

for more details.



You should have received a copy of the GNU General Public License

along with LiveCode. If not see . */



___
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: NAVRAD was: lcb missing manual

[J. Landman Gay via use-livecode]

Legally the only date that matters is the date of creation. Almost everyone 
adds the current date as well, and I keep trying to talk my clients out of 
it but they won't listen. Then I have to keep updating the copyright 
string, knowing it doesn't matter, but if I don't the app looks old and 
unsupported. Some time back I wrote a handler that updates the end date to 
the current year on launch so I don't have to worry about it.


A single copyright creation date is valid for the life of the creator plus 
(in the US) 75 years.


Oh well.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 15, 2022 5:12:59 PM Alex Tweedly via use-livecode 
 wrote:



On 15/09/2022 15:44, Mike Kerner via use-livecode wrote:

What's NavRAD? It's a better version of LiveCode's NavBar widget.
Why "RAD"? Cos Ralph A DiMola said so, since he added the first two nifty
updates to it:


I see the code has an outdated copyright statement, which would (I
think) currently mean that any app using it would (potentially) become
open-source (GPL). If that;s not the intent, maybe it could be updated ?

Currently it says


  Copyright (C) 2015-2022 LiveCode Ltd.icon

  This file is part of LiveCode.

  LiveCode is free software; you can redistribute it and/or modify it
under
  the terms of the GNU General Public License v3 as published by the Free
  Software Foundation.

  LiveCode is distributed in the hope that it will be useful, but
WITHOUT ANY
  WARRANTY; without even the implied warranty of MERCHANTABILITY or
  FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
  for more details.

  You should have received a copy of the GNU General Public License
  along with LiveCode.  If not see .  */


Alex.




Copyright (C) 2015-2022 LiveCode Ltd.icon



This file is part of LiveCode.



LiveCode is free software; you can redistribute it and/or modify it
under

the terms of the GNU General Public License v3 as published by the Free

Software Foundation.



LiveCode is distributed in the hope that it will be useful, but
WITHOUT ANY

WARRANTY; without even the implied warranty of MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License

for more details.



You should have received a copy of the GNU General Public License

along with LiveCode. If not see . */



___
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





___
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: [semi-OT] PDF on the fly

[matthias rebbe via use-livecode]

That is interesting. I tried here with content-length on on-rev and it works 
here with Version 15.6 (17613.3.9.1.5) of Safari.

At least you've found a solution...



> Am 15.09.2022 um 11:36 schrieb jbv via use-livecode 
> :
> 
> I am using Safari 15.6 (15613.3.9.1.7, 15613)
> 
> But I finally found the origin of the problem :
>  put header "Content-Length: " & number of chars of myPDF
> 
> After removing that line from the header, files download and
> display fine in Safari, as in other browsers.
> So far I have no rational explanation though.
> 
> Best,
> jbv
> 
> Le 2022-09-14 17:00, matthias rebbe via use-livecode a écrit :
>> I just tested on quartz.on-rev.com  with LC
>> Server 9.6.0.
>> I've created a textfile with a size of 1mb.
>> tested with this script and it worked. I even tested with put header
>> instead of put new header.
>> > put header "Content-Type: application/text"
>> put new header "Content-Disposition: attachment; FileName=" & 
>> "justsomeText.txt"
>> put URL("binfile:" & "justsomeText.txt")
>> ?>
>> Which version of Safari do you have?
>>> Am 14.09.2022 um 22:44 schrieb jbv via use-livecode 
>>> :
>>> Hi guys,
>>> Thank you for your answers.
>>> No matter what I try, the problem remains the same on Safari.
>>> My LC script runs on my on-rev account, and it uses LC 9.6.
>>> Could this really be the problem ?
>>> Best,
>>> jbv
>>> ___
>>> 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
>> ___
>> 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
> 
> ___
> 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


___
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

iOS 16! It will not do landscape!

[Sannyasin Brahmanathaswami via use-livecode]

Aloha Everyone

Well I was involved in iOS 16. Just yesterday.

It downloaded to my phone (iPhone 13, with Version 16.0 – 20A362) . When I did 
that, none of stacks of my stacks will do landscape!

stack “wordpuzzle”

on preOpenStack

   if isMobile() then

   mobileSetAllowedOrientations "landscape left,landscape right"

   mobileSetFullScreenRectForOrientations "landscape left,landscape 
right","0,0,736,414"

 set the fullscreenmode of this stack to "showAll" -- better 
for wider screens

   end if

   hide grc "blankScreen"

setCardCoords "landscape"

end preOpenStack

stack “view_BrowserLandscape”



on preopenstack

   local tBrowser, tOrientations

   set the fullscreenmode of this stack to empty

   put the short name this stack into tBrowser

   put (tBrowser contains "landscape") into sLandscapeOnly

   put "landscape left,landscape right" into tOrientations

   if sLandscapeOnly then

   put "landscape" into sOrientation

   else

   put "portrait,portrait upside down," before tOrientations

   put "portrait" into sOrientation

   end if

   setCardCoords sOrientation

   if isMobile() then

mobileSetAllowedOrientations tOrientations

   end if

   resetUI

   hide grc "blankImage"

   send "showBrowser" to me in 10 seconds

end preopenstack

Where is the newest download.

https://downloads.livecode.com/livecode/

LiveCode 9.6.9 RC 1, 10 August 2022

RC 1
Release 
Notes
10 August 2


Brahmanathaswami




And it not there!


Did see SivaSiva 1.7.2? It on the iPhone – App Store.

Svasti Astu – Be Well
Brahmanathaswami

Get SivaSiva.app – It free!
https://www.himalayanacademy.com/view/sivasiva




















___
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: Standardize Font Appearance

[Neville Smythe via use-livecode]

Thanks Richard for your comments. Interesting to see comments about font drift 
in a general context

The problems is however not fixed if you add Google fonts to your standalone. 
The problem could probably be fixed (on Mac and Windows anyway) by hacking the 
fonts to change their metadata tables but that is getting into really deep 
water, and may even violate copyright. 

The core of the issue is what I think is a design flaw in the way LC places 
text when it asks the platform OS to render the string.

Experiment 1: Create a standard field. Set the properties to non-3d, draw 
borders with thickness 1 so we can judge the vertical placement. Type the text 
“A standard label”. Set the field font to Arial so we can compare the results 
on Mac and Windows.

Result: On the Mac and Windows we get subtly different results. On Windows the 
capital “A" appears centered in the box; on the Mac the lower case letters 
“san" appear centered. Which means the Windows string is lower than the Mac 
string. As an initialisation of the new field it looks OK on both IDEs. But as 
we have seen we get into trouble when the text uses other fonts or sizes or if 
it interacts visually with nearby objects.

Experiment 2: Now change the font size to 64pt. 

Result: The text disappears. It is now placed way below the bounding box, and 
it is a bit of a hassle to get it back into view. That is a terrible user 
interface. 

The nicest user experience would be if the newly sized string appeared with the 
same baseline as the initial string, and that would certainly make alignment of 
text easier. However, that model wouldn’t quite fit the LC field model with a 
user-settable top margin, as it would necessitate overriding the top margin. If 
the top margin is to be honoured, the two obvious choices are to place the text 
so the top of the capital A appears at the bottom of the top margin (perhaps 
the Windows viewpoint?) or if the top of the lowercase letters appear at the 
top margin, allowing cap letters and risers such as h to bleed into the top 
margin (let us call this the Mac viewpoint). But neither of these two are what 
actually happens.

I can confirm that LC actually places the text (the first line, for a field 
with fixedLineHeight false - that is another story) so that the baseline is set

top margin of the field + fontAscent of the font - 6

pixels below the top of the field. This formula holds precisely over all the 
fonts and sizes I have tested and on all 3 platforms.

It appears what was intended, probably way back in Hypercard when fonts were 
bitmaps, was to drop the string below the top margin by the height of capitals 
(the ascent) and then pull back by 6 pixels so that the top of the lowercase x 
is at the top margin (the Mac viewpoint). It works well enough on the common 
initial fonts and sizes for fields because  6 is about the difference in letter 
heights at these sizes.

However the fontAscent returned by measureText is quite evidently not the 
height of the letter A above the baseline, it is more like the maximum font 
height above the baseline, so the string disappears in Experiment 2. And the 
two platforms return different values for fontAscent anyway, leading to the 
alignment problems in Experiment 1. Furthermore that constant 6 is of course 
grossly wrong for other font sizes. What was meant surely was

 top margin + x-ascent of the font

(Which was possibly computational more expensive bearing in mind various font 
formats?)

It would now be impossible for LC to change how it places text in fields, to 
either the Mac or Windows viewpoint, because that would break every stack 
having a text field!

What could be done however would be to add a couple of field properties which 
would enable baselines to be aligned, as I suggested in a previous post.

Neville


___
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