Re: changing the size of the image that's combined with text

[Scott Rossi]

Hi Matt:

The imageSource property is the one you're looking for, and AFAIK, using a
hidden or offscreen image is the way to adjust what is displayed in the
field.  If you have an image in a field whose imageSource is assigned to
an imported image, and you resize the imported image, you should see the
image reference in the field update as well.

It would be a good feature request for the imageSource property to accept
width/height values.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 2/15/16, 10:32 PM, "use-livecode on behalf of Matt Maier"

wrote:

>This is one of those times when I end up sending an hour just trying to
>find out if I know what keywords to search for.
>
>Anywho, I want to combine images with text in a field.
>
>I found the right syntax for writing html that will combine text and
>images:
>lerg
>and also that the char reference isn't necessary, so this works
>
>It's a bit tedious to code, since you have to escape the quotes like this:
>put "quote & ">" into tHTML
>but whatevs, it works.
>
>Livecode doesn't care about the height & width information that normally
>go
>along with an  tag in html. I can't find a way to control the
>size
>when using imageSource either.
>
>Is there a way to adjust the size of the image that's in the text field?
>I'm hoping I don't have to create a temporary image of the adjusted size,
>put it somewhere, and then reference the temporary image instead of the
>actual image.
>___
>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

changing the size of the image that's combined with text

[Matt Maier]

This is one of those times when I end up sending an hour just trying to
find out if I know what keywords to search for.

Anywho, I want to combine images with text in a field.

I found the right syntax for writing html that will combine text and images:
lerg
and also that the char reference isn't necessary, so this works

It's a bit tedious to code, since you have to escape the quotes like this:
put "" into tHTML
but whatevs, it works.

Livecode doesn't care about the height & width information that normally go
along with an  tag in html. I can't find a way to control the size
when using imageSource either.

Is there a way to adjust the size of the image that's in the text field?
I'm hoping I don't have to create a temporary image of the adjusted size,
put it somewhere, and then reference the temporary image instead of the
actual image.
___
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: create field suddenly not a good chunk

[Scott Rossi]

Did you include "stack" in the variable name?  Pretty sure you just need
the stack's name, so maybe that was causing a failure.

As a quick and dirty test, I tried creating 3 new stacks, and executed
variations of this line from  the message box: set defaultStack to
"untitled 3";create fld

When running this here, switching the number after "untitled" causes a
field to be created in the designated stack as expected.  Maybe some other
part of your script is forcing a change of the defaultStack.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 2/15/16, 10:16 PM, "use-livecode on behalf of Matt Maier"

wrote:

>It didn't. I set the defaultstack once when the whole thing loaded and
>again right before creating the field, then had it put the defaultstack
>into a variable so I could confirm it was correct. The words in the
>variable were exactly what I wrote on the line (stack "HowstrBeta").
>
>On Mon, Feb 15, 2016 at 10:07 PM, Scott Rossi 
>wrote:
>
>> If the goal is create an object in a specified stack, does setting the
>> defaultStack first not work?
>>
>> Regards,
>>
>> Scott Rossi
>> Creative Director
>> Tactile Media, UX/UI Design
>>
>>
>>
>>
>>
>> On 2/15/16, 8:35 PM, "use-livecode on behalf of Matt Maier"
>> >bluebac...@gmail.com>
>> wrote:
>>
>> >As far as I know I didn't make any changes that would explain this.
>> >
>> >All of a sudden this line: "create field stack "HowstrBeta"  is giving
>>me
>> >this error "(Chunk: source is not a container), char 1"
>> >
>> >After some experimentation and googling I discovered that it would work
>> >again if I changed that line to this: "create field (the long ID of
>>stack
>> >"HowstrBeta").
>> >
>> >BTW, it was the same error for two other areas which created graphics
>> >instead of fields.
>> >
>> >Any ideas why Livecode would happily take "create field stack
>>"Whatever""
>> >for many months and then suddenly demand it be phrased differently?
>> >___
>> >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

Re: create field suddenly not a good chunk

[Matt Maier]

It didn't. I set the defaultstack once when the whole thing loaded and
again right before creating the field, then had it put the defaultstack
into a variable so I could confirm it was correct. The words in the
variable were exactly what I wrote on the line (stack "HowstrBeta").

On Mon, Feb 15, 2016 at 10:07 PM, Scott Rossi 
wrote:

> If the goal is create an object in a specified stack, does setting the
> defaultStack first not work?
>
> Regards,
>
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design
>
>
>
>
>
> On 2/15/16, 8:35 PM, "use-livecode on behalf of Matt Maier"
> 
> wrote:
>
> >As far as I know I didn't make any changes that would explain this.
> >
> >All of a sudden this line: "create field stack "HowstrBeta"  is giving me
> >this error "(Chunk: source is not a container), char 1"
> >
> >After some experimentation and googling I discovered that it would work
> >again if I changed that line to this: "create field (the long ID of stack
> >"HowstrBeta").
> >
> >BTW, it was the same error for two other areas which created graphics
> >instead of fields.
> >
> >Any ideas why Livecode would happily take "create field stack "Whatever""
> >for many months and then suddenly demand it be phrased differently?
> >___
> >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: create field suddenly not a good chunk

[Scott Rossi]

If the goal is create an object in a specified stack, does setting the
defaultStack first not work?

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design





On 2/15/16, 8:35 PM, "use-livecode on behalf of Matt Maier"

wrote:

>As far as I know I didn't make any changes that would explain this.
>
>All of a sudden this line: "create field stack "HowstrBeta"  is giving me
>this error "(Chunk: source is not a container), char 1"
>
>After some experimentation and googling I discovered that it would work
>again if I changed that line to this: "create field (the long ID of stack
>"HowstrBeta").
>
>BTW, it was the same error for two other areas which created graphics
>instead of fields.
>
>Any ideas why Livecode would happily take "create field stack "Whatever""
>for many months and then suddenly demand it be phrased differently?
>___
>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: create field suddenly not a good chunk

[Monte Goulding]

> On 16 Feb 2016, at 4:17 PM, Matt Maier  wrote:
> 
> Could this be similar?


If it worked it may have been a result of lax parsing which I think has been 
tightened up a bit in 8. Someone on the core team might be able to comment on 
that.

Cheers

Monte

___
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: create field suddenly not a good chunk

[Matt Maier]

If I'm following that you think it's weird you have to create an object
inside a group, rather than just on a stack/card, then that's weird because
that's exactly what I'm doing. I've been creating bunches of objects and
never bothered with groups.

A while back I was using arbitrary strings of texts as delimiters and the
board thought that was impossible, but went back and confirmed it was
possible. Livecode devs just changed it before I tried it but after more
experienced people had tried it. Could this be similar?

On Mon, Feb 15, 2016 at 9:01 PM, Monte Goulding  wrote:

>
> > On 16 Feb 2016, at 3:56 PM, Matt Maier  wrote:
> >
> > Weird that it would parse for so long and then suddenly stop parsing, but
> > then accept a form that it looks like still shouldn't parse.
>
> On a related note it seems odd to me that you can create an object in a
> group but you can’t specify a card or a stack where the current card might
> be used. I know there’s been cases where I’ve created groups just to
> simplify the creation of objects on the stacks that I wanted them on. I
> think that’s an unnecessary limitation so if I get a chance I might look at
> what it would take to fix.
>
> Cheers
>
> Monte
> ___
> 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: create field suddenly not a good chunk

[Monte Goulding]

> On 16 Feb 2016, at 3:56 PM, Matt Maier  wrote:
> 
> Weird that it would parse for so long and then suddenly stop parsing, but
> then accept a form that it looks like still shouldn't parse.

On a related note it seems odd to me that you can create an object in a group 
but you can’t specify a card or a stack where the current card might be used. I 
know there’s been cases where I’ve created groups just to simplify the creation 
of objects on the stacks that I wanted them on. I think that’s an unnecessary 
limitation so if I get a chance I might look at what it would take to fix.

Cheers

Monte
___
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: create field suddenly not a good chunk

[Matt Maier]

A bunch of the properties of the templateField got set right before that.
Then that line (which was "create field stack 'whatever'" and was working
fine)
Then put "put it into tID" which gave me the ID of the newly created field.

I just needed a field created for each node in the network.

Weird that it would parse for so long and then suddenly stop parsing, but
then accept a form that it looks like still shouldn't parse.

On Mon, Feb 15, 2016 at 8:46 PM, Monte Goulding  wrote:

>
> > On 16 Feb 2016, at 3:35 PM, Matt Maier  wrote:
> >
> > As far as I know I didn't make any changes that would explain this.
> >
> > All of a sudden this line: "create field stack "HowstrBeta"  is giving me
> > this error "(Chunk: source is not a container), char 1"
> >
> > After some experimentation and googling I discovered that it would work
> > again if I changed that line to this: "create field (the long ID of stack
> > "HowstrBeta").
> >
> > BTW, it was the same error for two other areas which created graphics
> > instead of fields.
> >
> > Any ideas why Livecode would happily take "create field stack "Whatever""
> > for many months and then suddenly demand it be phrased differently?
>
> It probably shouldn’t have parsed `create field stack “Whatever”` ever.
> I’m not sure what you are intending myself.
> Do you want a field named `stack “Whatever”` or do you want a field
> created on stack “Whatever”?
>
> For the former then you probably want:
> create field “stack” && quote & “Whatever” & quote
>
> For the latter then you probably want:
> set the defaultStack to “Whatever”
> create field “MyField"
>
> or
>
> create field “MyField” in group “somegroup” of stack “Whatever"
>
> Cheers
>
> Monte
> ___
> 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: create field suddenly not a good chunk

[Monte Goulding]

> On 16 Feb 2016, at 3:35 PM, Matt Maier  wrote:
> 
> As far as I know I didn't make any changes that would explain this.
> 
> All of a sudden this line: "create field stack "HowstrBeta"  is giving me
> this error "(Chunk: source is not a container), char 1"
> 
> After some experimentation and googling I discovered that it would work
> again if I changed that line to this: "create field (the long ID of stack
> "HowstrBeta").
> 
> BTW, it was the same error for two other areas which created graphics
> instead of fields.
> 
> Any ideas why Livecode would happily take "create field stack "Whatever""
> for many months and then suddenly demand it be phrased differently?

It probably shouldn’t have parsed `create field stack “Whatever”` ever. I’m not 
sure what you are intending myself.
Do you want a field named `stack “Whatever”` or do you want a field created on 
stack “Whatever”?

For the former then you probably want:
create field “stack” && quote & “Whatever” & quote

For the latter then you probably want:
set the defaultStack to “Whatever”
create field “MyField"

or

create field “MyField” in group “somegroup” of stack “Whatever"

Cheers

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

create field suddenly not a good chunk

[Matt Maier]

As far as I know I didn't make any changes that would explain this.

All of a sudden this line: "create field stack "HowstrBeta"  is giving me
this error "(Chunk: source is not a container), char 1"

After some experimentation and googling I discovered that it would work
again if I changed that line to this: "create field (the long ID of stack
"HowstrBeta").

BTW, it was the same error for two other areas which created graphics
instead of fields.

Any ideas why Livecode would happily take "create field stack "Whatever""
for many months and then suddenly demand it be phrased differently?
___
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: Free BasicClock desktop clock for OSX

[Kay C Lan]

On Mon, Feb 15, 2016 at 7:47 PM, Peter TB Brett 
wrote:

>
> Is your clock open source?  At the moment it has "All rights reserved" in
> the copyright...
>
> I don't have a Community Edition of LC in front of me but I know for the
other editions:

 All rights reserved worldwide

is the default entry in the Copyright Notice box of the Standalone
Application Settings (Win & Mac only). Is this automatically replaced with
'Licensed under GNU General Public License version 2 - GPL2' (or words to
that effect) for the Community Edition? If not, it should be.
___
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: Signing Identity Issue When Building Standalone

[Scott Rossi]

Hi Pierre:

Apparently, a lot of people (including myself) didn't get or see the
message.
https://www.reddit.com/r/iOSProgramming/comments/45siza/this_certificate_ha
s_an_invalid_issuer/


Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 2/15/16, 1:46 PM, "use-livecode on behalf of Pierre Sahores"
 wrote:

>Scott,
>
>They (Apple) announced this certificate update need (because their own
>switch needs) by email last week.
>
>> Le 15 févr. 2016 à 21:40, Scott Rossi  a écrit :
>> 
>> If any of you are having difficulty building iOS standalones today,
>>you're
>> not alone. Apple's own Worldwide Developer Relations Certificate expired
>> yesterday (Feb 14) which will likely cause your developer certificates
>>to
>> display with an "This certificate has an invalid user" error message,
>>and
>> will prevent LiveCode from generating standalones with a "A valid
>>signing
>> identity could not be found" error.  I was beyond irked trying to figure
>> why I could build standalones last week and not this week.
>> 
>> What solved the problem for me was to delete the Apple Worldwide
>>Developer
>> Relations Certification Authority certificate from Keychain, and then
>> downloading and installing the certificate mentioned here:
>> https://developer.apple.com/support/certificates/expiration/
>> 
>> 
>> Hope this saves a few people some aggravation.
>> 
>> Regards,
>> 
>> Scott Rossi
>> Creative Director
>> Tactile Media, UX/UI Design
>
>Best Regards,
>
>Pierre
>
>--
>Pierre Sahores
>mobile : 06 03 95 77 70
>www.sahores-conseil.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

Fwd: Signing Identity Issue When Building Standalone

[Pierre Sahores]

Scott,

They (Apple) announced this certificate update need (because their own switch 
needs) by email last week.

> Le 15 févr. 2016 à 21:40, Scott Rossi  a écrit :
> 
> If any of you are having difficulty building iOS standalones today, you're
> not alone. Apple's own Worldwide Developer Relations Certificate expired
> yesterday (Feb 14) which will likely cause your developer certificates to
> display with an "This certificate has an invalid user" error message, and
> will prevent LiveCode from generating standalones with a "A valid signing
> identity could not be found" error.  I was beyond irked trying to figure
> why I could build standalones last week and not this week.
> 
> What solved the problem for me was to delete the Apple Worldwide Developer
> Relations Certification Authority certificate from Keychain, and then
> downloading and installing the certificate mentioned here:
> https://developer.apple.com/support/certificates/expiration/
> 
> 
> Hope this saves a few people some aggravation.
> 
> Regards,
> 
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design

Best Regards,

Pierre

--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.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

Rép : some AB testing ...

[Pierre Sahores]

Dear Livecoders,

I promise to be back with some final tests and related thoughts and here they 
are. All tests went carefully done in using both ApacheBench 2.3 Revision 
1528965 and Siege 3.0.5 with same average results. Only the Siege ones are 
reported there to maintain this report as readable as possible.

--

root@pierre-X200CA:/home/pierre# siege -b -c 100 -r 50 -q 
http://192.168.1.15/index.lc
  done.

Transactions:   5000 hits
Availability:   100.00 %
Elapsed time:   85.00 secs
Data transferred:   0.65 MB
Response time:  1.68 secs
Transaction rate:   58.82 trans/sec
Throughput: 0.01 MB/sec
Concurrency:99.03
Successful transactions:5000
Failed transactions:0
Longest transaction:1.84
Shortest transaction:   0.11

code :

put "Hello World from LiveCode CGI Server" && the 
version & \
"on" && the internet date & ""

configuration :

eeePC Asus X200CA Ubuntu 14.04, Openresty 1.9.7.2 + FCGIWrap + .LC script + LC 
CGI Server 7.1.1

— 

root@pierre-X200CA:/home/pierre# siege -b -c 100 -r 50 -q 
http://192.168.1.15/index.php
  done.

Transactions:   5000 hits
Availability:   100.00 %
Elapsed time:   2.26 secs
Data transferred:   0.48 MB
Response time:  0.04 secs
Transaction rate:   2212.39 trans/sec
Throughput: 0.21 MB/sec
Concurrency:97.85
Successful transactions:5000
Failed transactions:0
Longest transaction:0.08
Shortest transaction:   0.00

code :

put "Hello World from LiveCode Application's Server" && 
the version & \
"on" && the internet date & ""

configuration :

eeePC Asus X200CA Ubuntu 14.04, Openresty 1.9.7.2 +FMP/FastCGI + .PHP 5.5.9 
sockets proxy script --> localhost:9578 --> LC 6.1.3 Application’s Server 
launched in -ui mode

— 

root@pierre-X200CA:/home/pierre# siege -b -c 100 -r 50 -q http://192.168.1.15/lc
  done.

Transactions:   5000 hits
Availability:   100.00 %
Elapsed time:   1.29 secs
Data transferred:   0.35 MB
Response time:  0.02 secs
Transaction rate:   3875.97 trans/sec
Throughput: 0.27 MB/sec
Concurrency:95.12
Successful transactions:5000
Failed transactions:0
Longest transaction:0.08
Shortest transaction:   0.00

code :

put "Hello World from LiveCode Application's Server" && 
the version & \
"on" && the internet date & " »

configuration :

eeePC Asus X200CA Ubuntu 14.04, Openresty 1.9.7.2 (Lua 5.1.a, LuaJIT 2.1) + 
ngx.lua sockets proxy --> localhost:9578 --> LC 6.1.3 Application’s Server 
launched in -ui mode

— 
 
root@pierre-X200CA:/home/pierre# siege -b -c 100 -r 50 -q 
http://192.168.1.15/lua
  done.

Transactions:   5000 hits
Availability:   100.00 %
Elapsed time:   0.69 secs
Data transferred:   0.65 MB
Response time:  0.01 secs
Transaction rate:   7246.38 trans/sec
Throughput: 0.94 MB/sec
Concurrency:52.52
Successful transactions:5000
Failed transactions:0
Longest transaction:0.37
Shortest transaction:   0.00

code :

ngx.say("Hello World from Openresty 
"..ngx.config.nginx_version.." / Ngx.Lua "..ngx.config.ngx_lua_version.." 
!on "..ngx.localtime().." +0100 
("..ngx.var.server_port..") ")

configuration :

eeePC Asus X200CA Ubuntu 14.04, Openresty 1.9.7.2 (Lua 5.1.a, LuaJIT 2.1) + 
ngx.lua script

— 

As the tests reports, an Openresty/Lua powered application’s server could be 
twice as fast as a Nginx/Livecode application’s server one but, at this point, 
this assertion still needs to be verified as long as the final performances 
will be directly impacted by the way both solutions handles memory management 
against heavy loads.

At this point, i can confirm that LC application’s server (and before it, MC 
and Rev ones) i had to setup over the 15 last years went always perfectly 
reliables in about this. 

Re: Signing Identity Issue When Building Standalone

[Randy Hengst]

Thanks for the heads-up, Scott.

be well,
randy

Randy Hengst
www.classroomFocusedSoftware.com


> On Feb 15, 2016, at 2:40 PM, Scott Rossi  wrote:
> 
> If any of you are having difficulty building iOS standalones today, you're
> not alone. Apple's own Worldwide Developer Relations Certificate expired
> yesterday (Feb 14) which will likely cause your developer certificates to
> display with an "This certificate has an invalid user" error message, and
> will prevent LiveCode from generating standalones with a "A valid signing
> identity could not be found" error.  I was beyond irked trying to figure
> why I could build standalones last week and not this week.
> 
> What solved the problem for me was to delete the Apple Worldwide Developer
> Relations Certification Authority certificate from Keychain, and then
> downloading and installing the certificate mentioned here:
> https://developer.apple.com/support/certificates/expiration/
> 
> 
> Hope this saves a few people some aggravation.
> 
> 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

___
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

Signing Identity Issue When Building Standalone

[Scott Rossi]

If any of you are having difficulty building iOS standalones today, you're
not alone. Apple's own Worldwide Developer Relations Certificate expired
yesterday (Feb 14) which will likely cause your developer certificates to
display with an "This certificate has an invalid user" error message, and
will prevent LiveCode from generating standalones with a "A valid signing
identity could not be found" error.  I was beyond irked trying to figure
why I could build standalones last week and not this week.

What solved the problem for me was to delete the Apple Worldwide Developer
Relations Certification Authority certificate from Keychain, and then
downloading and installing the certificate mentioned here:
https://developer.apple.com/support/certificates/expiration/


Hope this saves a few people some aggravation.

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: Free BasicClock desktop clock for OSX

[Howard Bornstein]

It's closed source for the time being.

On Mon, Feb 15, 2016 at 3:47 AM, Peter TB Brett 
wrote:

>
> On 14/02/2016 20:55, Howard Bornstein wrote:
> > So many clocks today still employ the flip-clock or 7-segment LED display
> > aesthetic that is at least 20 years old. Given that we now have high
> > resolution displays and very high-quality fonts available, I wanted to
> make
> > a simple clock that took advantage of these improvements as an
> alternative
> > to the “retro” clocks that are mostly available.
> >
> > The clock itself is basic—just time, day, and date. It’s designed to sit
> in
> > the corner of your screen and float over everything else.
> >
> > But you can modify the *look* of the clock in many ways, by using
> different
> > fonts and by modifying the clock and background colors. Other visual
> > options include adding a border, using rounded corners, drop shadows and
> > inner shadows.
> >
> > The clock is also infinitely resizable so you can make it any size you
> need
> > to fit in your work area.
> >
> > Because there can be so many visual options, there is also a mechanism to
> > save your favorites designs and call them up later.
> >
> > You can see the features of BasicClock here: BasicClock Read Me.pdf
> > 
> >
> > and download it here: BasicClock V2.04.zip
> > 
> >
> > Note that you might have to “allow” this clock to run in the Security &
> > Privacy control panel if you have Gatekeeper running on your Mac.
> >
>
> Hi Howard,
>
> Is your clock open source?  At the moment it has "All rights reserved" in
> the copyright...
>
> Peter
>
> --
> Dr Peter Brett 
> LiveCode Open Source Team
>
> LiveCode on reddit: https://reddit.com/r/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
>



-- 
Regards,

Howard Bornstein
---
www.designeq.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: Free BasicClock desktop clock for OSX

[Howard Bornstein]

On Mon, Feb 15, 2016 at 3:25 AM, FlexibleLearning.com <
ad...@flexiblelearning.com> wrote:

> Nice one, Howard. Hopefully your BasicClock will soon be available for
> other
> platforms also.
>

Thanks Hugh. It's OSX only because I don't run any other platforms to test
it on. I suppose if someone was running windows or linux and wanted to test
it, I could build a version, but I know it's difficult to find and correct
those niggling bugs on a platform you don't run.


> 1. Free BasicClock
> You can see the features of BasicClock here: BasicClock Read Me.pdf
> http://designeq.com/deq/software/Welcome%20to%20BasicClock%20V2.04.pdf
>
> and download it here: BasicClock V2.04.zip
> http://designeq.com/deq/software/BasicClock%20V2.04.app.zip
>
>
> 2. Free ClearView Clock with calendar
> Previews and downloads for Windows, Mac OSX and Linux
> http://www.flexiblelearning.com/freeclock/
>
>
> Hugh Senior
> FLCo
>
>
> > Date: Sun, 14 Feb 2016 12:55:26 -0800
> > From: Howard Bornstein 
> > To: How to use LiveCode 
> > Subject: Free BasicClock desktop clock for OSX
> >
> > So many clocks today still employ the flip-clock or 7-segment LED display
> > aesthetic that is at least 20 years old. Given that we now have high
> resolution
> > displays and very high-quality fonts available, I wanted to make a simple
> clock
> > that took advantage of these improvements as an alternative to the
> ?retro?
> > clocks that are mostly available.
> >
> > The clock itself is basic?just time, day, and date. It?s designed to sit
> in the
> > corner of your screen and float over everything else.
> >
> > But you can modify the *look* of the clock in many ways, by using
> different
> > fonts and by modifying the clock and background colors. Other visual
> options
> > include adding a border, using rounded corners, drop shadows and inner
> > shadows.
> >
> > The clock is also infinitely resizable so you can make it any size you
> need to fit
> > in your work area.
> >
> > Because there can be so many visual options, there is also a mechanism to
> > save your favorites designs and call them up later.
> >
> > You can see the features of BasicClock here: BasicClock Read Me.pdf
> >  > 4.pdf>
> >
> > and download it here: BasicClock V2.04.zip
> > 
> >
> > Note that you might have to ?allow? this clock to run in the Security &
> Privacy
> > control panel if you have Gatekeeper running on your Mac.
> >
> > BasicClock is free and currently runs only under OS X.
> >
> > Enjoy.
> >
> > (BasicClock was inspired by the Clearview desktop clock by Hugh Senior.)
> > --
> > Regards,
> >
> > Howard Bornstein
> > ---
> > www.designeq.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
>



-- 
Regards,

Howard Bornstein
---
www.designeq.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

[ANN] This Week in LiveCode 20

[Peter TB Brett]

Hi all,

Read about new developments in LiveCode open source and the open source 
community in today's edition of the "This Week in LiveCode" newsletter!


Read issue #20 here: https://goo.gl/xmg1Rf


This is a weekly newsletter about LiveCode, focussing on what's been 
going on in and around the open source project.  New issues will be 
released weekly on Mondays.  We have a dedicated mailing list that will 
deliver each issue directly to you e-mail, so you don't miss any!


Are you doing something interesting with LiveCode Community Edition? 
Please get in touch and get it featured in "This Week in LiveCode"!


 Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/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: Free BasicClock desktop clock for OSX

[Peter TB Brett]

On 14/02/2016 20:55, Howard Bornstein wrote:
> So many clocks today still employ the flip-clock or 7-segment LED display
> aesthetic that is at least 20 years old. Given that we now have high
> resolution displays and very high-quality fonts available, I wanted 
to make
> a simple clock that took advantage of these improvements as an 
alternative

> to the “retro” clocks that are mostly available.
>
> The clock itself is basic—just time, day, and date. It’s designed to 
sit in

> the corner of your screen and float over everything else.
>
> But you can modify the *look* of the clock in many ways, by using 
different

> fonts and by modifying the clock and background colors. Other visual
> options include adding a border, using rounded corners, drop shadows and
> inner shadows.
>
> The clock is also infinitely resizable so you can make it any size 
you need

> to fit in your work area.
>
> Because there can be so many visual options, there is also a mechanism to
> save your favorites designs and call them up later.
>
> You can see the features of BasicClock here: BasicClock Read Me.pdf
> 
>
> and download it here: BasicClock V2.04.zip
> 
>
> Note that you might have to “allow” this clock to run in the Security &
> Privacy control panel if you have Gatekeeper running on your Mac.
>

Hi Howard,

Is your clock open source?  At the moment it has "All rights reserved" 
in the copyright...


Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/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: Free BasicClock desktop clock for OSX

[FlexibleLearning.com]

Nice one, Howard. Hopefully your BasicClock will soon be available for other
platforms also.

1. Free BasicClock
You can see the features of BasicClock here: BasicClock Read Me.pdf
http://designeq.com/deq/software/Welcome%20to%20BasicClock%20V2.04.pdf 

and download it here: BasicClock V2.04.zip
http://designeq.com/deq/software/BasicClock%20V2.04.app.zip 


2. Free ClearView Clock with calendar
Previews and downloads for Windows, Mac OSX and Linux
http://www.flexiblelearning.com/freeclock/


Hugh Senior
FLCo


> Date: Sun, 14 Feb 2016 12:55:26 -0800
> From: Howard Bornstein 
> To: How to use LiveCode 
> Subject: Free BasicClock desktop clock for OSX
> 
> So many clocks today still employ the flip-clock or 7-segment LED display
> aesthetic that is at least 20 years old. Given that we now have high
resolution
> displays and very high-quality fonts available, I wanted to make a simple
clock
> that took advantage of these improvements as an alternative to the ?retro?
> clocks that are mostly available.
> 
> The clock itself is basic?just time, day, and date. It?s designed to sit
in the
> corner of your screen and float over everything else.
> 
> But you can modify the *look* of the clock in many ways, by using
different
> fonts and by modifying the clock and background colors. Other visual
options
> include adding a border, using rounded corners, drop shadows and inner
> shadows.
> 
> The clock is also infinitely resizable so you can make it any size you
need to fit
> in your work area.
> 
> Because there can be so many visual options, there is also a mechanism to
> save your favorites designs and call them up later.
> 
> You can see the features of BasicClock here: BasicClock Read Me.pdf
>  4.pdf>
> 
> and download it here: BasicClock V2.04.zip
> 
> 
> Note that you might have to ?allow? this clock to run in the Security &
Privacy
> control panel if you have Gatekeeper running on your Mac.
> 
> BasicClock is free and currently runs only under OS X.
> 
> Enjoy.
> 
> (BasicClock was inspired by the Clearview desktop clock by Hugh Senior.)
> --
> Regards,
> 
> Howard Bornstein
> ---
> www.designeq.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