DF
command-line tools that are around, like the free PDFtk for example.
On Thu, Oct 17, 2019 at 12:28 PM FlexibleLearning.com via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Has anyone got an LC-based method to merge pdf files?
>
> Just
> Richard H. wrote:
> Silly question now that I think of it . . . does t avoid
> the pixelization that the pdf widget performs?
> And for that matter, does it work with cropped sections,
> or just full pages?
The PDf-lib doesn't use image snapshots. It is true PDF:
Copied are pages and all it need
Silly question now that I think of it . . . does t avoid the pixelization that
the pdf widget performs?
And for that matter, does it work with cropped sections, or just full pages?
—
Richard E. Hawkins, Esq.
The Hawkins Law Firm
3430 E. Flamingo Rd.
Suite 232
Las Vegas, NV 89121
(702) 508-846
On Oct 21, 2019, at 10:55 AM, hh via use-livecode
wrote:
>
> I had it ready yesterday for Mac and tried a full day to work
I’ll start pounding the mac version was soon as I get my hands on it . .
—
Richard E. Hawkins, Esq.
The Hawkins Law Firm
3430 E. Flamingo Rd.
Suite 232
Las Vegas, NV 8
It is dependant on using JS from LC, by that it is dependant
on a browser widget.
I had it ready yesterday for Mac and tried a full day to work
around the deficiencies of the browser widget on linux and win
but had no success, sorry.
The stack will be published as "PDF-Tools" (Merge
doc hawk wrote:
> On Oct 17, 2019, at 12:04 PM, hh wrote:
>> I'll publish this weekend on SampleStacks a pdfLib (split and merge)
>> based on a JS library (via a browser widget). Already 95% are done.
>
> Did it publish?
>
> And will this only be for server?
If it
On Oct 17, 2019, at 12:04 PM, hh via use-livecode
wrote:
> I'll publish this weekend on SampleStacks a pdfLib (split and merge)
> based on a JS library (via a browser widget). Already 95% are done.
Did it publish?
And will this only be for server?
Do I so
> Hugh Senior wrote:
> Has anyone got an LC-based method to merge pdf files? Just asking...
I'll publish this weekend on SampleStacks a pdfLib (split and merge)
based on a JS library (via a browser widget). Already 95% are done.
___
u
On Oct 17, 2019, at 9:27 AM, FlexibleLearning.com via use-livecode
wrote:
>
> Has anyone got an LC-based method to merge pdf files?
LC business can’t even output a pdf widget save as low density raster at the
moment.
I’m currently working on an interim solution that creates a PyPdf2
Has anyone got an LC-based method to merge pdf files?
Just asking...
Hugh Senior
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http
-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay via use-livecode
Sent: Wednesday, September 11, 2019 4:54 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Merge and unicode
On 9/11/19 12:28 AM, Richard Gaskin via use-livecode wrote:
> I'll wager using a styledText a
On 9/11/19 12:28 AM, Richard Gaskin via use-livecode wrote:
I'll wager using a styledText array for this will be fun to write and will
perform very well.
I took a look. You'd win that wager. I didn't test performance (haven't
written the handler yet) but getting the styledText of an existing
I'll wager using a styledText array for this will be fun to write and will
perform very well.Richard GaskinFourth World Systems
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your su
I wondered about using htmltext in the merge too, but before I started
using merge I was setting the properties one by one in a handler. Here's
part of my original handler, where pResults is a list of lines that
match search criteria:
repeat for each line l in pResults
put item 1
problems with UTF-8
>> decode. Check encoding.
>> 3. Field, line and character metadata are interfering. Clear all, then set
>> and get consistently.
>> 4. Merge is not handling binary data as text. Use textDecode first.
>> Dar Scott
>> Mad Scient
I looked at this some more on OS X. I'm not seeing a problem with merge. And
I'm not seeing a problem with metadata per se, I don't think. But I am seeing a
problem with setting metadata with htmlText.
> On Sep 10, 2019, at 1:32 PM, J. Landman Gay via use-livecode
> wro
On 9/10/19 1:47 PM, J. Landman Gay via use-livecode wrote:
:)
1. Jacque is very confused too, but is afraid of big sticks.
2. Encoding should be identical throughout. I'm working with a large
text block, pulling out sections to create a list. All data is retrieved
from othe same variable, which
etadata are interfering. Clear all, then set and
get consistently.
4. Merge is not handling binary data as text. Use textDecode first.
Dar Scott
Mad Scientist
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software |
I extracted an example. The main issue is curly quotes. The text came
from FileMaker in UTF8, which I textDecode to UTF16. You can assume that
all text is LC native throughout the app.
Here is the template I use for merge:
size="16" color="#C77C02">[[tSECTION]][[tCONCEPT
. Clear all, then set and
get consistently.
4. Merge is not handling binary data as text. Use textDecode first.
Dar Scott
Mad Scientist
> On Sep 10, 2019, at 11:04 AM, Dar Scott Consulting via use-livecode
> wrote:
>
> Trusting...
>
> Also, interpreting Latin-1 as UTF-8 can g
Trusting...
Also, interpreting Latin-1 as UTF-8 can generate some weird characters and lots
of ?-diamond symbols.
> On Sep 10, 2019, at 8:36 AM, Bob Sneidar via use-livecode
> wrote:
>
> Trust me it's better than a feral gander persuit.
>
> Bob S
>
>
>> On Sep 9, 2019, at 17:23 , Dar Scot
Trust me it's better than a feral gander persuit.
Bob S
> On Sep 9, 2019, at 17:23 , Dar Scott Consulting via use-livecode
> wrote:
>
> Sorry, if I am off on a bunny trail...
>
> Dar
___
use-livecode mailing list
use-livecode@lists.runrev.com
Pl
I think I'm doing this wrong. This seems to work, too.
on mouseup
put empty into field 1
put numToCodepoint(0x2200) into x
put numToCodepoint(0x1040F) & "V-" into y
put merge(" é{ [[x]] }é [[y]]") into field 1
end mouseup
> On Sep 9, 2019, at 1
p
I guess the problem is in the merge as you thought.
I did notice in the dictionary that setting the metadata of a line is not the
same as setting the metadata of all of the characters of the line.
Dar Scott
> On Sep 9, 2019, at 8:58 PM, Dar Scott Consulting via use-livecode
> wrote:
&
Well, I've made some changes to the code since I started urlEncoding the text
> before merging so I'll check that again. Paul is right that unicode in
> htmltext needs to be in hex, but the numbers I'm getting back are very high
> (8,000+) and render in the field as s
aphs. Elsewhere where
there is no merge, curly quotes translate to the named quote or apostrophe
entities and are correct.
By metadata I mean the LC term (see the dictionary) that allows you to
attach some text to a field text chunk. The metadata isn't displayed in the
field but you can use
ferring to HTTP content-type?
Sorry, if I am off on a bunny trail...
Dar
> On Sep 9, 2019, at 4:38 PM, J. Landman Gay via use-livecode
> wrote:
>
> It's UTF8 text from a server, which I textDecode to UTF16. When I use the
> UTF16 text in a merge, diacriticals and/or curl
Paul Dupuis via use-livecode wrote:
On 9/9/2019 2:13 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does
anyone have a workaround? The text I'm inserting is already decoded
It's UTF8 text from a server, which I textDecode to UTF16. When I use
the UTF16 text in a merge, diacriticals and/or curly quotes get mangled.
(Same with setting metadata on field text too.)
On 9/9/19 4:16 PM, Dar Scott Consulting via use-livecode wrote:
I'm not sure I understan
On 9/9/19 2:39 PM, Paul Dupuis via use-livecode wrote:
On 9/9/2019 2:13 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting
I'm not sure I understand.
Do you mean "encoded to UTF-16"? In that case you should decode that to convert
it to internal text. And then try merge. (Which still might have problems, I
suppose.)
> On Sep 9, 2019, at 12:08 PM, J. Landman Gay via use-livecode
> wrote:
&
On 9/9/2019 2:13 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
I misspoke, sorry
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
I misspoke, sorry. It's the metadata that doesn't respect unicode.
--
Ja
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperac
Folks:
I’m looking at Jan Schenkel’s posting on the “Power of Merge”.
I can’t make any of the examples work.
Obviously, there is some code or some very basic thing that everybody (but me)
knows, but ??
Please illuminate me. I see the " placeholder in some of the lessons. The
dictionary
Thanks everyone. Templates makes sense.
Just for grins, perhaps the dictionary entry could be enhanced with Jacque’s
example.
It makes sense to me now.
Kee
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscrib
Kee,
I can spend hours on why merge is useful and underappreciated but I will
boil it down to one use case only: templates.
Merge is crucial if you're assembling some textual template that is not
LiveCode but want to generate parts of it in LiveCode. For example, the
first st
> Kee N. wrote:
> I’m confused. Can someone explain why merge function exists when
> the put function works just as well?
> merge([[ 1 + 2 ]] = 3) vs put 1 + 2 && “= 3”
merge([[ 1 + 2 ]] = 3) produces a script error,
this should read merge("[[ 1 + 2 ]] = 3").
Merg
kee nethery wrote:
> I’m confused. Can someone explain why merge function exists when the
> put function works just as well?
>
> merge( [[ 1 + 2 ]] = 3)
> vs
> put 1 + 2 && “= 3”
>
> What is it that merge can do that a put cannot do? Just asking because
> I
On 1/18/19 12:33 PM, kee nethery via use-livecode wrote:
I’m confused. Can someone explain why merge function exists when the put
function works just as well?
merge( [[ 1 + 2 ]] = 3)
vs
put 1 + 2 && “= 3”
What is it that merge can do that a put cannot do?
For me, it'
Folks,
I’ve been following this discussion, barely. I don’t use merge, but when I need
to form a command from several variables, I create the command as a text string
and use do to execute it.
So, when I look it up in the dictionary, I see a fairly simplistic description
with nothing
There's some overlap, but merge has (at least) one feature that put
doesn't: the ability to run code within its statement. A simple example:
put merge("The coin came up .")
The equivalent might be:
put "The coin came up" && item random(2) of
On Fri, Jan 18, 2019 at 3:23 AM Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 2019-01-18 06:48, Geoff Canyon via use-livecode wrote:
> > I was in the same position with merge(). If you haven't seen it
> > already,
> > format() has
I’m confused. Can someone explain why merge function exists when the put
function works just as well?
merge( [[ 1 + 2 ]] = 3)
vs
put 1 + 2 && “= 3”
What is it that merge can do that a put cannot do? Just asking because I don’t
want LiveCode to end up like Perl where there are
Until parametrization is implemented for LC 9 one could use
the following generalization of Andre's method for David.
This is still fast enough because replace is so fast in LC.
David would call merge2(string, "{{", "}}").
To make merge xml safe use e.g. merge2(string,
Until parametrization is implemented for LC 9 one could use
the following generalization of Andre's method for David.
This is still fast enough because replace is so fast in LC.
David would call merge2(string, "{{", "}}").
To make merge xml safe use e.g. merge2(string,
also allows the slow
building up of quality regExp for specific purposes without constantly
changing the underlying code. I'm sure there are faster and leaner
approaches though.
An extension to merge() along the lines that Mark suggested would cut down
on quite a lot of the use-cases i&#
On 2019-01-18 09:01, David Bovill via use-livecode wrote:
I would love to be able to change the characters that merge uses -
especially from “[[..]]” to “{{...}}”.
Quite a lot of templating uses curly brackets - and I especially want
to
use it for wiki style templates which can’t use square
eheheheheh let me throw this hack in here and run
function davidsMerge pText
replace "[[" with "[safe[" in pText
replace "]]" with "]safe]" in pText
replace "{{" with "[[" in pText
replace "}}" with "
On 2019-01-18 06:48, Geoff Canyon via use-livecode wrote:
I was in the same position with merge(). If you haven't seen it
already,
format() has some pretty amazing capabilities as well.
To answer your question about escaping - yes there is:
[[[]] -> [
[[]]] -> ]
Also the mer
David Bovill wrote:
>
> > I would love to be able to change the characters that merge uses -
> > especially from “[[..]]” to “{{...}}”.
> >
> > Quite a lot of templating uses curly brackets - and I especially want
> > to use it for wiki style templates which can’t
David Bovill wrote:
> I would love to be able to change the characters that merge uses -
> especially from “[[..]]” to “{{...}}”.
>
> Quite a lot of templating uses curly brackets - and I especially want
> to use it for wiki style templates which can’t use square brackets as
>
I would love to be able to change the characters that merge uses -
especially from “[[..]]” to “{{...}}”.
Quite a lot of templating uses curly brackets - and I especially want to
use it for wiki style templates which can’t use square brackets as they are
used for internal links.
Not sure of the
On Thu, Jan 17, 2019 at 2:27 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> 6 years with LC...never used the value or merge commands . never even
> came across them.
>
> mind blown.
>
I was in the same position with merge(). If you haven'
6 years with LC...never used the value or merge commands . never even
came across them.
mind blown.
On Thu, Jan 17, 2019 at 3:46 PM Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On Thu, Jan 17, 2019 at 11:01 AM hh via use-livecode <
> use-livecode@l
function call or perform the test twice. And of course in this instance it
would be easy enough to simply use:
", & the name of tID & ""
else return the name of tID?>
But it would become unwieldy for more complex strings.
>
> 2. Also array-things work with merge, li
function tag s,o,c
return o & s & c
end tag
And both, tag("inner") and tag("inner","left-","-right") work.
2. Also array-things work with merge, like [[a[1]]].
___
use-livecode mailing list
us
On Thu, Jan 17, 2019 at 4:36 AM hh via use-livecode <
use-livecode@lists.runrev.com> wrote:
> > Geoff wrote:
> > using value():
> > the name of tID && "[" & the id of tID & "]"
> > using merge():
> > [[the name of tID]] - (
> Geoff wrote:
> using value():
> the name of tID && "[" & the id of tID & "]"
> using merge():
> [[the name of tID]] - ([[the id of tID]])
> (is there a way to escape the "["?)
You could use with merge not only variables but a
In Navigator I use the value() function in several ways. In particular, I
use it as a way for users to customize Navigator's list display. For some
reason I've managed to go all these years blissfully unaware of the merge()
function, which is seemingly superior to value() for this
Cool, thanks!
On Fri, Jun 15, 2018 at 7:58 PM Brian Milby wrote:
> I think that as long as you control the string that is passed to merge you
> should be fine. But if the user were able to directly influence the string
> that is passed to merge, then they certainly could inject
I think that as long as you control the string that is passed to merge you
should be fine. But if the user were able to directly influence the string
that is passed to merge, then they certainly could inject something.
put the text of field 1 into tMerge
put merge(tMerge) into tDangerousUse
put
I just had a thought while pondering some code from another thread. I have
done things like put merge("This is a random number: [[random(tNum)]]")
Since merge can do what do can, is there a way this method could be taken
advantage of using an injection type of attack? I'm thin
On Wed, Aug 2, 2017 at 1:00 PM, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> If you evaluate the second expression in that merge in the context (i.e.
> Same handler) of the call to merge does it throw an error?
>
Ahh, it was viciously subtle (and v
If you evaluate the second expression in that merge in the context (i.e. Same
handler) of the call to merge does it throw an error?
If a compile or runtime error occurs in any [[ ... ]] bracketed part of the
merge string, then it gets rendered literally and not the value of it (as it
can'
pears to be blocking evaluation of the second
bracketed term; the first is correctly taken from a variable, but the
second retains that literal text.
I don't believe that LiveCode should be treating a single-quoted range as
a literal in merge(), should it?
For that matter, nothing in the d
Monte Goulding wrote:
>> On 22 Sep 2016, at 8:03 AM, Richard Gaskin wrote:
>>
>> Either way, seems worth exploring, either refining the behavior
>> or the token's documentation.
>
> I personally don’t see any harm in throwing a general merge
> evaluation er
> On 22 Sep 2016, at 8:03 AM, Richard Gaskin wrote:
>
> Either way, seems worth exploring, either refining the behavior of the
> token's documentation.
I personally don’t see any harm in throwing a general merge evaluation error
and it would be relatively easy to imple
Monte Goulding wrote:
>> On 22 Sep 2016, at 6:51 AM, Richard Gaskin wrote:
>>
>> Interesting. If merge is indeed thwarting normal error handling
>> then that may be related.
>
> Has merge ever thrown errors on invalid expressions? It seems to be
> deliberatel
> On 22 Sep 2016, at 6:51 AM, Richard Gaskin wrote:
>
> Interesting. If merge is indeed thwarting normal error handling then that
> may be related.
Has merge ever thrown errors on invalid expressions? It seems to be
deliberately implemented so it doesn’t and I don’t recall i
Interesting. If merge is indeed thwarting normal error handling then
that may be related.
I just filed a report on this:
http://quality.livecode.com/show_bug.cgi?id=18457
I added a second test in which the merge call is within a try block,
with even weirder results than the first exercise
e-livecode on behalf of Richard Gaskin"
wrote:
This suggests that not only are errors within merge operations ignored
(something worth exploring in itself), but once an error is encountered
in a merge operation execution seems to stop, but silently.
__
Try this:
on mouseUp
put "This is [[ foo() ]] a test" into s
put merge(s)
put foo()
end mouseUp
function foo
return 1 + "string"
end foo
Observed result:
"This is a test" appears in the Message Box
Expected result:
LC would throw an error in the foo
On 2015-06-05 17:22, Ali Lloyd wrote:
On 5 June 2015 at 16:13, Dr. Hawkins wrote:
On Fri, Jun 5, 2015 at 7:31 AM, Peter Haworth wrote:
> Well I missed the countdown so I'll +1your post.
>
and I'll +2.
The things that I would most like to add to livecode would be strict
compilation being th
On June 5, 2015 10:13:03 AM CDT, "Dr. Hawkins" wrote:
>
>The things that I would most like to add to livecode would be strict
>compilation being the default, absolute case sensitivity (unless turned off
>for comparisons), and strong typing of variables. Oh, and c-style
>variable scoping.
In that
In that case I can highly recommend trying LiveCode Builder ;-)
On 5 June 2015 at 16:13, Dr. Hawkins wrote:
> On Fri, Jun 5, 2015 at 7:31 AM, Peter Haworth wrote:
>
> > Well I missed the countdown so I'll +1your post.
> >
>
> and I'll +2.
>
> The things that I would most like to add to livecode
On Fri, Jun 5, 2015 at 7:31 AM, Peter Haworth wrote:
> Well I missed the countdown so I'll +1your post.
>
and I'll +2.
The things that I would most like to add to livecode would be strict
compilation being the default, absolute case sensitivity (unless turned off
for comparisons), and strong ty
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of Mike Bonner
> Sent: Friday, June 05, 2015 9:42 AM
> To: How to use LiveCode
> Subject: Re: arrays wi
onner
Sent: Friday, June 05, 2015 9:42 AM
To: How to use LiveCode
Subject: Re: arrays with merge
As ali said, the unquoted key is only an issue if there is a declared
variable, at which point the key becomes whatever is in that variable. (or
if its a keyword of course)
I use the "store the s
As ali said, the unquoted key is only an issue if there is a declared
variable, at which point the key becomes whatever is in that variable. (or
if its a keyword of course)
I use the "store the string elsewhere" method. When creating merge strings
for later use, I either create them
d as strings.
On 5 June 2015 at 10:26, Terence Heaford wrote:
> Interestingly it works without quotes around test.
>
> It does work but should it?
>
> This suggests the only reason for quotes in array keys is in case you have
> a two word key?
>
> put merge("
Interestingly it works without quotes around test.
It does work but should it?
This suggests the only reason for quotes in array keys is in case you have a
two word key?
put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[myArray[test]]]
[[tSortOrder]]") into tSQL
All the
Hi,
The reason
put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[myArray["test"]]]
[[tSortOrder]]") into tSQL
doesn't work is the double quote around "test". Merge should work fine
with arrays (I should know because bug 11274 was one of the first I
> function myArray pString
> return myArrayTest[pString]
> end myArray
Small typo:
myArrayTest[pString]
should of course be:
myArray[pString]
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscr
> Terence Heaford wrote:
>
> This line gives a syntax error, obviously because an array does not work in
> merge?
>
> put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[myArray["test"]]]
> [[tSortOrder]]") into tSQL
>
> Is there a way
Did this and I still get a syntax error.
put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[ myArray["test”] ]]
[[tSortOrder]]") into tSQL
Any ideas
Thanks
Terry
> On 5 Jun 2015, at 07:42, Monte Goulding wrote:
>
> Add a space between the array bracket and
Also tried it with one space after array as
put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[myArray["test”] ]]
[[tSortOrder]]") into tSQL
Still got a syntax error.
LC 6.7.5 Mac.
Is there a solution?
All the best
Terry
> On 5 Jun 2015, at 07:55, Terence H
Add a space between the array bracket and the merge brackets
> On 5 Jun 2015, at 4:27 pm, Terence Heaford wrote:
>
> This line gives a syntax error, obviously because an array does not work in
> merge?
>
> put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[
This line gives a syntax error, obviously because an array does not work in
merge?
put merge("SELECT [[tColumns]] FROM '[[tTable]]' [[myArray["test"]]]
[[tSortOrder]]") into tSQL
Is there a way around this or do I have to resort to
Hi all
I have a Kickstarter reward that entitles me to one free mergExt iOS external.
As I'm a mergExt subscriber I don't really need it so if you want it email me
direct at gerry [dot] orkin {at} gmail (dot) com with "mergExt" in the subject
line - I'll accept requests for 24 hours (given the
90 matches
Mail list logo
