Re: Adding Effects to widgets

2016-11-20 Thread Sannyasin Brahmanathaswami
HH: what is one or two examples of an "astounding visual effect" that you 
achieved?

I'm looking at putting these on top of photos, looking for the most elegant 
integration…. 

The group will automatically be an ugly rectangle/square, (which doesn't help) 

try this:

go stack url "http://wiki.hindu.org/uploads/P2SPickPathDesign.livecode;



On 11/2/16, 6:38 AM, "use-livecode on behalf of hh" 
 wrote:

>Jeanne D. wrote:
>Can you put it in a group and set a drop shadow for the group?

This is a real smart trick: Grouping (one or more) widgets.

Not only for "adding" bitmap-effects to the widget, also for
astounding visual effects by certain combinations of the widget's
ink and the group's ink.



___
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: Type on an angle

2016-11-20 Thread Scott Rossi
This is great.  True, it runs a bit slowly in 7/8, but scripted image
calculations have always been this way, and having any option at all in LC
to do this type of manipulation is very welcome.  A few of us have been
wanting something like this for years.

Thanks for this great example.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 11/20/16, 9:11 AM, "use-livecode on behalf of hh"
 wrote:

>** Perspective Distortion of an image **
>available (fast) at "Sample stacks" of the IDE toolbar or (slower) at
>http://livecodeshare.runrev.com/stack/812/Perspective-Image-Distortion
>
>The stack includes is an example for (close to) live-distorting a field's
>image, uses font 'Aclonica' at 48 point.



___
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: Type on an angle

2016-11-20 Thread Scott Rossi

On 11/20/16, 5:36 PM, I wrote:

>The embedded screen capture below may not arrive on the list intact, but
>illustrates the point.

Well, I tried.

http://tactilemedia.com/download/rotated_text.gif

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design



___
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: Type on an angle

2016-11-20 Thread Scott Rossi

On 11/20/16, 1:42 AM, "use-livecode on behalf of hh"
 wrote:
> 
> Adding a 'native' angle property doesn't turn a bitmap display into a
> raster display based on postscript/pdf.
> Adobe Photoshop and Illustrator use postscript/pdf for each and every
> single glyph. They dont have rotated fields (seen as controls). They even
> don't have a rotated _postscript_ insertion cursor for 'rotated editing'.

Just for the record, the above may be correct from a technical standpoint,
but is inaccurate with regard to what is presented to users.
The embedded screen capture below may not arrive on the list intact, but
illustrates the point.

Also provided is the option to assign orientation to text.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




___
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: GUI Design Tasks Send Back - Bring Forward

2016-11-20 Thread Sannyasin Brahmanathaswami
roger.e.el...@sealedair.com> wrote:

pressing Control-[ or Control-].

OH ..duh! yes completely forgot about those key board shortcuts!

___
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: Compound Path SVG Breaks in Widget?

2016-11-20 Thread Paul Hibbert
Just re-created your SVG from the SVG text and opened the file in Affinity 
Designer, then exported it as SVG, converted back to text and then extracted 
the SVG paths:

M112,0l-100,0c-6.583,0 -12,5.417 -12,12c0,6.583 5.417,12 12,12l100,0c6.583,0 
12,-5.417 12,-12c0,-6.583 -5.417,-12 -12,-12Zm0,44l-100,0c-6.583,0 -12,5.417 
-12,12c0,6.583 5.417,12 12,12l100,0c6.583,0 12,-5.417 12,-12c0,-6.583 
-5.417,-12 -12,-12Zm0,44l-100,0c-6.583,0 -12,5.417 -12,12c0,6.583 5.417,12 
12,12l100,0c6.583,0 12,-5.417 12,-12c0,-6.583 -5.417,-12 -12,-12Z

Pasted that into an SVG Icon widget and it works fine, so I guess it’s 
something to do with the way Illustrator exports the data, are there any 
options to try? Maybe compression?

Paul

> On Nov 20, 2016, at 2:11 PM, Sannyasin Brahmanathaswami  
> wrote:
> 
> 
> 1)  3 bar menu (hamburger menu" download SVG icon from  
> http://www.flaticon.com/
> 2) open in Illustrator
> 3) select all
> 4) Make compound path
> 
> save as SVG
> 
> file looks like this:
> 
> http://www.w3.org/2000/svg; 
> viewBox="0 0 124 112">three-horizontal-lines_compound d="M112,6H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,6Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,50Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,94Z"
>  transform="translate(0 -6)" style="fill:none"/>
> 
> 
> Pasting this into the widget generates an error.
> 
> M112,6H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,6Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,50Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,94Z
> 
> Any Clues?
> 
> already entered here:
> 
> http://quality.livecode.com/show_bug.cgi?id=18884
> 
> ___
> 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: Swipe gestures on a mobile scroller

2016-11-20 Thread J. Landman Gay
I wish. :) I'm hoping the LC team will fix it. Apparently that would 
solve problems for a lot of us.



On 11/20/16 3:53 PM, Scott Morrow wrote:

Jacque,

I had intermittent luck with touchMove as well. I was using it to
swipe open a “delete” button. In the app that uses this feature there
is another way to accomplish the same thing so I settled for
intermittent.

Selfishly, hoping it was something I did wrong and that you would
solve it  :- )

— Scott

On Nov 20, 2016, at 11:34 AM, J. Landman Gay
 wrote:

On 11/20/16 12:36 PM, Paul Hibbert wrote:

It is only a workaround implemented by intercepting the
scrollerDidScroll message


I just tried both Scott's touchMove solution and Paul's
scrollerDidScroll suggestion but neither seem to work on Android.

I'm not surprised there was no scrollerDidScroll message, because
the field width fits the scroller contentRect, so there is nothing
to scroll. It may be working on iOS because there you have a
"bounce" option which allows overscrolling. Android doesn't have
that.

I had hopes for the touchMove solution because that message does
fire sporadically but it failed also. In my tests yesterday I saw
that the message fired fitfully, but even when it did the mouse
position was wrong. I attributed that to the fact that I was
logging the coords to a field, but maybe there's more to it because
after a few responses the logging stopped completely.

-- Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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



___ 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




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: external for an Android mobile app

2016-11-20 Thread J. Landman Gay

On 11/20/16 11:40 AM, jbv wrote:

Hi list
When one needs an external for an Android version
of an app for mobile, where is the best place to
turn to ?


I contacted support to have the LC team do one for me. There are people 
on the list here who might be able to do one too, depending on what you 
need.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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


Compound Path SVG Breaks in Widget?

2016-11-20 Thread Sannyasin Brahmanathaswami

1)  3 bar menu (hamburger menu" download SVG icon from  http://www.flaticon.com/
2) open in Illustrator
3) select all
4) Make compound path

save as SVG

file looks like this:

http://www.w3.org/2000/svg; 
viewBox="0 0 124 112">three-horizontal-lines_compound


Pasting this into the widget generates an error.

M112,6H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,6Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,50Zm0,44H12a12,12,0,0,0,0,24H112A12,12,0,0,0,112,94Z

Any Clues?

already entered here:

http://quality.livecode.com/show_bug.cgi?id=18884

___
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: Swipe gestures on a mobile scroller

2016-11-20 Thread Scott Morrow
Jacque,

I had intermittent luck with touchMove as well. I was using it to swipe open a 
“delete” button. In the app that uses this feature there is another way to 
accomplish the same thing so I settled for intermittent. 

Selfishly, hoping it was something I did wrong and that you would solve it  :- )

—
Scott
> On Nov 20, 2016, at 11:34 AM, J. Landman Gay  wrote:
> 
> On 11/20/16 12:36 PM, Paul Hibbert wrote:
>> It is only a workaround implemented by intercepting the scrollerDidScroll 
>> message
> 
> I just tried both Scott's touchMove solution and Paul's scrollerDidScroll 
> suggestion but neither seem to work on Android.
> 
> I'm not surprised there was no scrollerDidScroll message, because the field 
> width fits the scroller contentRect, so there is nothing to scroll. It may be 
> working on iOS because there you have a "bounce" option which allows 
> overscrolling. Android doesn't have that.
> 
> I had hopes for the touchMove solution because that message does fire 
> sporadically but it failed also. In my tests yesterday I saw that the message 
> fired fitfully, but even when it did the mouse position was wrong. I 
> attributed that to the fact that I was logging the coords to a field, but 
> maybe there's more to it because after a few responses the logging stopped 
> completely.
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.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


___
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: Type on an angle

2016-11-20 Thread BNig
Sannyasin Brahmanathaswami wrote
> Thanks everyone my responses is 
> 
> "All of the above"
> 
> -- @ Bernd: your HTML5 demo is amazing! Where can I can we get the source?
> BR
> 
> On 11/20/16, 12:52 AM, "use-livecode on behalf of BNig" wrote:
> 
> Elanor has a simple and bare bones LCB file for a widget that can
> rotate one
> line of text in the attachement of 
> http://quality.livecode.com/show_bug.cgi?id=17782
> 
> The widget I did turns one line of text horziontally

Hi BR,
You can download the widget at

http://berndniggemann.on-rev.com/turnwidget/turnText.zip

I recompiled the widget to make sure it works with LC 8.1.1 and up (built
using LC 8.1.2 DP2)

There is a text file explaining how to install and a stack that uses the
widget.
That stack is the basis for the HTMLversion.

>From that stack you can built a HTML version.

>From inside a browser you can download the source for opensource HTML LC
stuff at the bottom right. There is a small LC icon that lets you download a
zip.

Kind regards
Bernd




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Type-on-an-angle-tp4710431p4710465.html
Sent from the Revolution - User mailing list archive at Nabble.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: Type on an angle

2016-11-20 Thread Sannyasin Brahmanathaswami
Thanks everyone my responses is 

"All of the above"

-- snapshot really has major issues with returning bit map
-- widgets all look great and I think they all have their use cases.
-- @ HH stack with perspectives is awesome, thank you!
-- @ Bernd: your HTML5 demo is amazing! Where can I can we get the source?
-- @ Richard: hmmm I have to agree that if it's a matter of HQ resources the 
angle prop should be at the bottom of the list as I also would want all the 
formatting to a "regular" field that is up for what we need.
-- @ Richard: yes of course we can do things in external editors.
-- Still wish I could just  "set the angle of fld YY to 60"

BR

On 11/20/16, 12:52 AM, "use-livecode on behalf of BNig" 
 
wrote:

Elanor has a simple and bare bones LCB file for a widget that can rotate one
line of text in the attachement of 
http://quality.livecode.com/show_bug.cgi?id=17782

The widget I did turns one line of text horziontally


http://runtime-revolution.278305.n4.nabble.com/widget-that-turns-text-horizontal-td4705280.html

Kind regards
Bernd

___
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: Swipe gestures on a mobile scroller

2016-11-20 Thread J. Landman Gay

On 11/20/16 12:36 PM, Paul Hibbert wrote:

It is only a workaround implemented by intercepting the scrollerDidScroll 
message


I just tried both Scott's touchMove solution and Paul's 
scrollerDidScroll suggestion but neither seem to work on Android.


I'm not surprised there was no scrollerDidScroll message, because the 
field width fits the scroller contentRect, so there is nothing to 
scroll. It may be working on iOS because there you have a "bounce" 
option which allows overscrolling. Android doesn't have that.


I had hopes for the touchMove solution because that message does fire 
sporadically but it failed also. In my tests yesterday I saw that the 
message fired fitfully, but even when it did the mouse position was 
wrong. I attributed that to the fact that I was logging the coords to a 
field, but maybe there's more to it because after a few responses the 
logging stopped completely.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: Swipe gestures on a mobile scroller

2016-11-20 Thread Paul Hibbert

> On Nov 20, 2016, at 11:03 AM, J. Landman Gay  wrote:
> 
> does that mean the hscroll property of the mobile scroller must be true?

Just tried this simplified version and it works fine too:

on scrollerDidScroll hOffset, vOffset // Scroll Detect //
 
   if hOffset <0 then ##-->> Detects the Horiz swipe <<--##
  moveBack
   else if hOffset >0 then
  moveForward
   end if
   
   set the vScroll of group "scrollArea" to vOffset ##-->> Scroll the field 
vertically <<—##

end scrollerDidScroll

___
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: Swipe gestures on a mobile scroller

2016-11-20 Thread Paul Hibbert

> On Nov 20, 2016, at 11:03 AM, J. Landman Gay  > wrote:
> 
> does that mean the hscroll property of the mobile scroller must be true?

No, the hScroll prop is still false, you are just detecting and using 
(diverting) the information that the scrollerDidScroll message would have used 
to set the hScroll, but it never gets set.

This is the handler:

on scrollerDidScroll hOffset, vOffset // Scroll or Swipe Detect //
 
   if the hScroll of group "scrollArea" <0 then ##-->> Detects the Horiz swipe 
<<--##
  moveBack
   else if the hScroll of group "scrollArea" >0 then
  moveForward
   end if
   
   set the vScroll of group "scrollArea" to vOffset ##-->>  Scroll the field 
vertically <<—##

end scrollerDidScroll


It is just a workaround, and it’s not perfect, but may keep you going until the 
main problem is fixed.

Paul
___
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: Swipe gestures on a mobile scroller

2016-11-20 Thread J. Landman Gay

On 11/20/16 12:36 PM, Paul Hibbert wrote:



On Nov 19, 2016, at 8:06 PM, J. Landman Gay
 wrote:

I'm not sure how it could work, since the horizontal scroll of my
field is always zero. It doesn't scroll horizontally at all.


The actual hScroll of the field isn’t set, only the vScroll is set in
this example, but it can detect that you are attempting to scroll
horizontally and so you can use that info to initiate a swipe.

It is only a workaround implemented by intercepting the
scrollerDidScroll message, you don’t need to ‘set' the scroll sent by
the message, but you can detect it and use it to swipe.


Right, but does that mean the hscroll property of the mobile scroller 
must be true? Right now mine's false so I assumed it wouldn't even try 
to detect scrolling horizontally. I can change that setting of course.


But your solution and Scott's are very similar so it must work. I'll 
experiment with both. Thanks for the ideas, both of you, but I sure wish 
we could use a simple mouseUp to detect it. It would save a lot of trouble.



--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: Swipe gestures on a mobile scroller

2016-11-20 Thread Paul Hibbert

> On Nov 19, 2016, at 8:06 PM, J. Landman Gay  wrote:
> 
> I'm not sure how it could work, since the horizontal scroll of my field is 
> always zero. It doesn't scroll horizontally at all.

The actual hScroll of the field isn’t set, only the vScroll is set in this 
example, but it can detect that you are attempting to scroll horizontally and 
so you can use that info to initiate a swipe.

It is only a workaround implemented by intercepting the scrollerDidScroll 
message, you don’t need to ‘set' the scroll sent by the message, but you can 
detect it and use it to swipe.

Paul
___
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

external for an Android mobile app

2016-11-20 Thread jbv
Hi list
When one needs an external for an Android version
of an app for mobile, where is the best place to
turn to ?

Thanks
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


Re: Type on an angle

2016-11-20 Thread Richmond

Very true.

On 20.11.2016 18:04, Dr. Hawkins wrote:

On Sun, Nov 20, 2016 at 4:14 AM, Richmond 
wrote:


To turn a textField should be no more complicated than:

1. export snapshot of textField (border? backGroundColor? textColor?
font?),


At which point you have a bitmap not an image.  Fine for the screen but not
for printing.





___
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: Type on an angle

2016-11-20 Thread hh
BR wrote:
> Working on GUI today I created a field and thinking it would be cool
> to have it run sideways at an angle along the edge of an element in
> the background photo ... Any solutions?

You may use my gift for the community (to X-mas or New year's evening or
similar):

** Perspective Distortion of an image **
available (fast) at "Sample stacks" of the IDE toolbar or (slower) at
http://livecodeshare.runrev.com/stack/812/Perspective-Image-Distortion 

The stack includes is an example for (close to) live-distorting a field's
image, uses font 'Aclonica' at 48 point.

___
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: Type on an angle

2016-11-20 Thread Dr. Hawkins
On Sun, Nov 20, 2016 at 4:14 AM, Richmond 
wrote:

> To turn a textField should be no more complicated than:
>
> 1. export snapshot of textField (border? backGroundColor? textColor?
> font?),
>

At which point you have a bitmap not an image.  Fine for the screen but not
for printing.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: Which widgets would YOU want to build?

2016-11-20 Thread hh
> combobox ...

There is, connected to that, already a list widget and a multilist widget
https://github.com/livecode/livecode/tree/develop/extensions/widgets

There is, also connected to that, no 'pure' field object in LC Builder.



___
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: Type on an angle

2016-11-20 Thread zryip theSlug
Hi,

The only widget I created so far is an orientable text with the
following properties:
- label
- angle
- font name
- font size
- font color
- font color opacity
- background color
- background opacity

I created it long time ago with the very first LC version supporting
widgets and have updated the code for following the LCB syntax
changes. I've stopped to play with widgets after this, so the code is
far to be neat but I can share it if someone need it or want to
improve it.

Where can I share it?


Best Regards,



On Sun, Nov 20, 2016 at 1:14 PM, Richmond  wrote:
> I do ALL my graphics externally except for snapshots of textFields.
>
> To turn a textField should be no more complicated than:
>
> 1. export snapshot of textField (border? backGroundColor? textColor? font?),
>
> 2. rotate it in graphics package of choice (GIMP, Photoshop, etc.),
>
> 3. import into stack as an image.
>
> Typing "at an angle" is probably more trouble than it's worth in terms of
> developer
> time.
>
> Richmond.
>
>
> On 20.11.2016 14:07, Malte Brill wrote:
>>
>> Sorry for hijacking the thread...
>>
>> TL/DR: Do we have Text input into widgets? How can we get our feet wet
>> easier with that stuff?
>>
>> ———
>>
>> Richard wrote:
>>
>>> I have maybe two apps across all my computing devices that let me edit
>>> rotated text, but I have dozens that display text in a variety of
>>> formats (date, phone number, currency, etc.).
>>>
>> Well, if we had a means of textinput inside a widget, this would be easy
>> enough to implement I guess, I may just have overlooked it if it exists.
>> Is text input into a widget possible right now? If so, where do I find
>> documentation on that?  If not is that on the roadmap?
>> I would be really interested going there. Frankly, the first widget that
>> peeked my interest was the calendar that was posted by Bernd. I follow what
>> Herrmann does, but still for what I would need / want to do, I would require
>> a means of keyboard input into the widget.
>>
>> Of course it is possible to code your way around this using what we have
>> right now. A field and making clever use of the message path. This has not
>> gone away (yet). However for me widgets appeared as the way forward to
>> creating custom objects that appear as ONE object to the engine instead of
>> using groups, which are frankly a tad bit brittle as it stands. Oh how often
>> have I screwed up a template group I created that then should have been
>> cloned into a dynamically created UI. Headaches I would have hoped to save
>> myself from with widgets by now.
>> I still do not see builder being at the point where it might be usefull
>> for me. Still in the interim. Still too early. Still not enough learning
>> material on how to get your feet wet with this stuff. Creating a pink circle
>> is good. What are the next steps? I miss easy to follow tutorials to find
>> that information! What is in the Roadmap and expected to arrive when? Those
>> are the questions that keep me from being bothered looking into that stuff
>> yet. I trust myself that I could contribute one widget or the other to the
>> community if it was easier to find the hows! This is not meant as a rant. I
>> still considder the transition to next gen LiveCode to be in progress. That
>> is fine. It looks like it is getting somewhere. Still, and I hope you do not
>> mind me saying that, I considder everything that followed 6.x being interims
>> versions that needed to be released to keep the userbase from tapping their
>> feet too much and keep the boat afloat financially. That is ok for me. Some
>> of the new stuff is really useful already but it comes for a price. LC is
>> not yet in a state of optimization. Pet peeve, benchmarking, but we had that
>> already. Fact is my apps got a whole lot slower with 7 and 8 compared to 5.x
>> and 6.x.. Upside is that this exposed quite a few places where my scripts
>> were inefficient. Doing my part in fixing my stuff. This makes it tolarable
>> in 7 and 8, but the petty is, blazingly fast in 5 / 6. I would rather see
>> stuff we have now being optimized and in turn live with a slower path of Dev
>> releases, which frankly I do not get around testing much anyways these days.
>> Once I find the time to test 8.X 8.Z is released already. I then run my
>> benchmarking on the areas I know affect my apps, see not much of a change
>> there, shrug it off and go back to daily business.This is not yet the next
>> gen livecode I have been kissing in my dreams. It might become it once it
>> matures, but for now I think it still needs to go out a bit and play on the
>> lawn, before I can ask it on a date. ;-)
>>
>> Cheers,
>>
>> Malte
>>
>>
>> ___
>> 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: Macintosh support

2016-11-20 Thread Richmond

"LiveCode 9 may still run on OS X 10.7, for the time being"

It does, cheers, cheers!

Having just invested 190 Euros in a 2006 Intel iMac (max OS 10.7) I am 
extremely

happy about this.

Personally I couldn't care less about "Official Support": if I make a 
c*ck up I'll take the

responsibility.

"highly-exploitable vulnerabilities": possibly; but on a limited budget 
I'm very excited about my "new" Mac, and as it is not going to be 
connected to the internet . . . and why on earth would a hacker waste 
his/her time exploiting vulnerabilities of an antiquated OS anyway? . . 
. I really could not care less

about them.

There is a little bird that keeps whispering in my lug that 
"highly-exploitable vulnerabilities" is a phrasae
that is largely of value insofar as it keeps driving people to shell out 
more money to buy more

machines:

as the cheapest iMac on the European market currently retails at 1,250 Euros

[ http://www.apple.com/de/shop/buy-mac/imac ]

and runs an OS (10.11 ~ 10.12) that has a GUI I just do not like
(Steve Jobs died, and while he went, arguably, to heaven, the Mac GUI 
went to hell)


and I don't have 1,250 Euros extra dosh, 190 Euros for a lovely, 
polycarbonate 21 inch
iMac that runs 10.7 (sits right next to my G5 iMac that runs 10.4 so I 
can dig in Hypercard
stacks and copy code directly into LC stacks, and use Appleworks) seems 
pretty good,

even at the risk of "highly-exploitable vulnerabilities".

As I often check my email and so on using Classilla

[ http://www.floodgap.com/software/classilla/ ]

on my G3 iMac running Mac OS 9, I feel that 10.7 is "way ahead" :)

This afternoon (Sunday) I have a load of hippy-trippy teenagers who I 
have, somehow, got hooked
on Livecode, coming over to my flat for coffee, coding and a look at the 
"new" Mac, as my favourite
importer (who has supplied all the machines for my school over the last 
10 years) has just got
a job lot (possibly a "Jobs" lot . . .) of 2006 iMacs (17 inch screens 
for 125 Euros, 20 inch screens for
190 Euros), and those kids would love an iMac, but are, in Bulgaria, at 
the bottom of the European
financial treacle well, I am very happy that I can tell them that the 
machines will work with the LC 8 series, and witht he currect LC 9 dp 
release.


I have had reports of my Devawriter Pro screwing up on Macs, so I shall 
now be building my Mac builds on the Intel iMac rather than on the Linux 
box.


Richmond.

On 19.11.2016 18:22, Peter TB Brett wrote:



On 19/11/2016 15:13, Richmond wrote:

I would like to know why Livecode 9 has dropped support for all versions
of Mac OS before 10.9.


LiveCode 9 may still run on OS X 10.7, for the time being -- we just 
don't provide any official support for (or run tests on) that platform 
any more.


The development team has to regularly move the LiveCode build system 
to newer versions of Xcode and newer versions of the MacOS SDK, so 
that they can keep LiveCode working well with new versions of MacOS 
and add new features requested by users.  Occasionally this means that 
older versions of OS X won't run LiveCode any more.


With a very small development team and quality assurance team, we have 
to be careful to keep the number and variety of supported platform 
configurations for LiveCode within a manageable limit. Occasionally 
this means we have to stop providing technical support for running 
LiveCode on older versions of OS X.


Apple stopped providing any patches or security fixes for OS X 10.8 
over a year ago, and it contains many highly-exploitable 
vulnerabilities.  I *very strongly* recommend against using versions 
of OS X prior to OS X 10.10.  If your hardware can't run OS X 10.12, I 
recommend upgrading its operating system to Linux.


You can find more information on our platform support plans in my 
recent-ish blog post [1], and in due course we will be adding some 
pages to the website that show the same information in a 
quicker-to-find way.


Peter

[1] https://livecode.com/updated-platform-support-policy/




___
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


Which widgets would YOU want to build? [WAS] Type on an angle

2016-11-20 Thread Malte Brill
I do not want to capture the rotation thread…

I went into more details on what is keeping me back from going through the 
headaches of learning builder at the moment in my previous mail. I think it 
would be a good idea to desribe what I would be wanting to build (well actually 
I want to use it, but nothing comes without an effort )

In many of my UIs I need what I would call an intelligent combobox.

Just like the combobox you know, but reacting on the text input and thus 
filtering the otions being displayed in the dropdown, based on whatever you 
have put into the field part of the combo box. The whole thing must be 
skinnable. So it needs to be possible to style the button part with the 
disclosing arrow. I have implemented such a beast as a group. Works somewhat, 
but is very brittle. If you start working on the template you can easiely screw 
things up. Also, changes are not being inherited to existing instances. Able to 
live with that, but wishful thinking for a better solution. One problem that is 
not solvable in a good manner is the layering of the „popup listfield“ that 
shows the options. More often that not it dispalys underneath other elements of 
the UI if you are not careful. Also it is hard to make it behave as one would 
expect it to work. I would have hoped to being able to solve this as a widget 
somehow. Would that be possible now?

What would you want to create?

Cheers,

Malte


___
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: Type on an angle

2016-11-20 Thread Richmond

I do ALL my graphics externally except for snapshots of textFields.

To turn a textField should be no more complicated than:

1. export snapshot of textField (border? backGroundColor? textColor? font?),

2. rotate it in graphics package of choice (GIMP, Photoshop, etc.),

3. import into stack as an image.

Typing "at an angle" is probably more trouble than it's worth in terms 
of developer

time.

Richmond.

On 20.11.2016 14:07, Malte Brill wrote:

Sorry for hijacking the thread...

TL/DR: Do we have Text input into widgets? How can we get our feet wet easier 
with that stuff?

———

Richard wrote:


I have maybe two apps across all my computing devices that let me edit
rotated text, but I have dozens that display text in a variety of
formats (date, phone number, currency, etc.).


Well, if we had a means of textinput inside a widget, this would be easy enough 
to implement I guess, I may just have overlooked it if it exists.
Is text input into a widget possible right now? If so, where do I find 
documentation on that?  If not is that on the roadmap?
I would be really interested going there. Frankly, the first widget that peeked 
my interest was the calendar that was posted by Bernd. I follow what Herrmann 
does, but still for what I would need / want to do, I would require a means of 
keyboard input into the widget.

Of course it is possible to code your way around this using what we have right 
now. A field and making clever use of the message path. This has not gone away 
(yet). However for me widgets appeared as the way forward to creating custom 
objects that appear as ONE object to the engine instead of using groups, which 
are frankly a tad bit brittle as it stands. Oh how often have I screwed up a 
template group I created that then should have been cloned into a dynamically 
created UI. Headaches I would have hoped to save myself from with widgets by 
now.
I still do not see builder being at the point where it might be usefull for me. 
Still in the interim. Still too early. Still not enough learning material on 
how to get your feet wet with this stuff. Creating a pink circle is good. What 
are the next steps? I miss easy to follow tutorials to find that information! 
What is in the Roadmap and expected to arrive when? Those are the questions 
that keep me from being bothered looking into that stuff yet. I trust myself 
that I could contribute one widget or the other to the community if it was 
easier to find the hows! This is not meant as a rant. I still considder the 
transition to next gen LiveCode to be in progress. That is fine. It looks like 
it is getting somewhere. Still, and I hope you do not mind me saying that, I 
considder everything that followed 6.x being interims versions that needed to 
be released to keep the userbase from tapping their feet too much and keep the 
boat afloat financially. That is ok for me. Some of the new stuff is really 
useful already but it comes for a price. LC is not yet in a state of 
optimization. Pet peeve, benchmarking, but we had that already. Fact is my apps 
got a whole lot slower with 7 and 8 compared to 5.x and 6.x.. Upside is that 
this exposed quite a few places where my scripts were inefficient. Doing my 
part in fixing my stuff. This makes it tolarable in 7 and 8, but the petty is, 
blazingly fast in 5 / 6. I would rather see stuff we have now being optimized 
and in turn live with a slower path of Dev releases, which frankly I do not get 
around testing much anyways these days. Once I find the time to test 8.X 8.Z is 
released already. I then run my benchmarking on the areas I know affect my 
apps, see not much of a change there, shrug it off and go back to daily 
business.This is not yet the next gen livecode I have been kissing in my 
dreams. It might become it once it matures, but for now I think it still needs 
to go out a bit and play on the lawn, before I can ask it on a date. ;-)

Cheers,

Malte


___
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: Type on an angle

2016-11-20 Thread Malte Brill
Sorry for hijacking the thread...

TL/DR: Do we have Text input into widgets? How can we get our feet wet easier 
with that stuff?

———

Richard wrote:

> I have maybe two apps across all my computing devices that let me edit 
> rotated text, but I have dozens that display text in a variety of 
> formats (date, phone number, currency, etc.).
> 

Well, if we had a means of textinput inside a widget, this would be easy enough 
to implement I guess, I may just have overlooked it if it exists. 
Is text input into a widget possible right now? If so, where do I find 
documentation on that?  If not is that on the roadmap? 
I would be really interested going there. Frankly, the first widget that peeked 
my interest was the calendar that was posted by Bernd. I follow what Herrmann 
does, but still for what I would need / want to do, I would require a means of 
keyboard input into the widget. 

Of course it is possible to code your way around this using what we have right 
now. A field and making clever use of the message path. This has not gone away 
(yet). However for me widgets appeared as the way forward to creating custom 
objects that appear as ONE object to the engine instead of using groups, which 
are frankly a tad bit brittle as it stands. Oh how often have I screwed up a 
template group I created that then should have been cloned into a dynamically 
created UI. Headaches I would have hoped to save myself from with widgets by 
now. 
I still do not see builder being at the point where it might be usefull for me. 
Still in the interim. Still too early. Still not enough learning material on 
how to get your feet wet with this stuff. Creating a pink circle is good. What 
are the next steps? I miss easy to follow tutorials to find that information! 
What is in the Roadmap and expected to arrive when? Those are the questions 
that keep me from being bothered looking into that stuff yet. I trust myself 
that I could contribute one widget or the other to the community if it was 
easier to find the hows! This is not meant as a rant. I still considder the 
transition to next gen LiveCode to be in progress. That is fine. It looks like 
it is getting somewhere. Still, and I hope you do not mind me saying that, I 
considder everything that followed 6.x being interims versions that needed to 
be released to keep the userbase from tapping their feet too much and keep the 
boat afloat financially. That is ok for me. Some of the new stuff is really 
useful already but it comes for a price. LC is not yet in a state of 
optimization. Pet peeve, benchmarking, but we had that already. Fact is my apps 
got a whole lot slower with 7 and 8 compared to 5.x and 6.x.. Upside is that 
this exposed quite a few places where my scripts were inefficient. Doing my 
part in fixing my stuff. This makes it tolarable in 7 and 8, but the petty is, 
blazingly fast in 5 / 6. I would rather see stuff we have now being optimized 
and in turn live with a slower path of Dev releases, which frankly I do not get 
around testing much anyways these days. Once I find the time to test 8.X 8.Z is 
released already. I then run my benchmarking on the areas I know affect my 
apps, see not much of a change there, shrug it off and go back to daily 
business.This is not yet the next gen livecode I have been kissing in my 
dreams. It might become it once it matures, but for now I think it still needs 
to go out a bit and play on the lawn, before I can ask it on a date. ;-)

Cheers,

Malte


___
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: Type on an angle

2016-11-20 Thread BNig
Elanor has a simple and bare bones LCB file for a widget that can rotate one
line of text in the attachement of 
http://quality.livecode.com/show_bug.cgi?id=17782

The widget I did turns one line of text horziontally

http://runtime-revolution.278305.n4.nabble.com/widget-that-turns-text-horizontal-td4705280.html

Kind regards
Bernd



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Type-on-an-angle-tp4710431p4710448.html
Sent from the Revolution - User mailing list archive at Nabble.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: Type on an angle

2016-11-20 Thread hh
Roger E. wrote:
> I would much rather have a native angle property as a part of the text
> field.  Live text on an angle like Adobe Photoshop and Illustrator have
> would enable a whole world of design apps with LiveCode.  I've used the
> snapshot workaround for 15 years, and it has never impressed anyone.

Adding a 'native' angle property doesn't turn a bitmap display into a
raster display based on postscript/pdf.
Adobe Photoshop and Illustrator use postscript/pdf for each and every
single glyph. They dont have rotated fields (seen as controls). They even
don't have a rotated _postscript_ insertion cursor for 'rotated editing'.

But you could use right now LC Builder:
If taking an SVG Font (as I do in the SVG-Text widget) you can have more
affine transforms than only rotating.

___
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: Swipe gestures on a mobile scroller

2016-11-20 Thread Scott Morrow
I used touchMove and found it at least partially reliable for horizontal swipes 
on iOS (not tried on Android)
Something like:

global gHorizontalSwipeDistance
local lMouseStartH
local lMouseStartV


-- put 80 into gHorizontalSwipeDistance -- depending on the resolution during 
startup

on touchStart pID
   put the mouseV into lMouseStartV
   put the mouseH into lMouseStartH
end touchStart

on touchMove pTouchID, pTouchH, pTouchV
   -- see if there was a horizontal swipe
   if (abs(pTouchH - lMouseStartH) > gHorizontalSwipeDistance) AND\
   (abs(pTouchV - lMouseStartV) < gVerticalSwipeDistance) then
  -- they swiped

   end if
end touch


Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   http://elementarysoftware.com/
email sc...@elementarysoftware.com
office 1-800-615-0867
--








> On Nov 19, 2016, at 8:13 PM, J. Landman Gay  wrote:
> 
> BTW, there appears to be a related bug that got fixed:
> 
> 
> MouseUp wasn't being sent when a native scroller was active. It looks like 
> they fixed that one but forgot to check related swipe mouseUps. Hopefully the 
> team can use the same fix again.
> 
> 
> On 11/19/16 10:06 PM, J. Landman Gay wrote:
>> Well, it's good to know I'm not alone I guess. ;) I just wish I'd asked
>> earlier, before I spent some hours tracking down the problem. I'd like
>> to think the omission of mouseUp/touchEnd messages was an oversight,
>> since we do get all the other mouse messages.
>> 
>> I haven't tried Paul's workaround. I'm not sure how it could work, since
>> the horizontal scroll of my field is always zero. It doesn't scroll
>> horizontally at all.
>> 
>> The fix should really be in the engine though.
>> 
>> On 11/19/16 8:53 PM, Terry Judd wrote:
>>> Hi Jacque - I struggled with this for ages on an iOS and android app
>>> earlier in the year (vertical scrolling content with side-to-side
>>> swiping for navigation (a la iCal). After trying a truckload of
>>> different approaches (hacks) I mostly got it to work on iOS (I still
>>> got intermittent failures) and I eventually gave up altogether on
>>> android and used left and right buttons instead. Things might have
>>> improved then but based on your experience it sounds unlikely. Happy
>>> to dig out my hacky iOS code if that helps but engine level fixes
>>> would be better.
>>> 
>>> Terry...
>>> 
>>> Sent from my iPad
>>> 
 On 20 Nov 2016, at 6:39 AM, J. Landman Gay
  wrote:
 
> On 11/19/16 2:18 AM, J. Landman Gay wrote: I have a native mobile
> scroller handling the vertical scroll of a field. I want to add
> swipe gestures to change cards. When swiping, I get a mouseDown,
> sporadic mouseMoves (the logging might be interfering, not sure,
> but after a couple they stop) and no mouseUp at all.
> 
> I tried using touchStart/touchMove/touchEnd instead and the
> result is the same. TouchStart always fires, touchMove is iffy,
> and touchEnd never happens.
> 
> Without the end message I can't calculate the direction. Plain
> taps work fine with either set of messages, I do get
> mouseUp/touchEnd if it's a tap. It's only swipes that don't
> report.
> 
> The scroller has its hScroll property set to false if that
> matters, as I don't want horizontal scrolling but I do want to
> track the touch direction.
 
 The problem has apparently been around for quite some time:
 
 
 Anyone have a workaround?
 
 -- Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software   | http://www.hyperactivesw.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
>>> 
>>> 
>>> ___ 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
>>> 
>> 
>> 
> 
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.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


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