Re: ANN: FieldGroup - a simple rich text editor field.
Alex Tweedly wrote: On 23/07/2020 17:20, Richard Gaskin via use-livecode wrote: https://www.tweedly.org/downloads/FieldGroupsample.livecode Thanks for posting this, Alex. Super cool. I didn't find license info in the package - did I miss it? What license is this distributed under? Sorry, I should have said. It is released under the MIT license; I've added the license text to the script of the group, and updated the copy on my website (as above) - now at version 0.2 Super - thanks, Alex! -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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: Functions running in IDE, but not running in standalone
> Am 23.07.2020 um 23:16 schrieb Bruce Pokras via use-livecode > : > > Matthias, > > Thanks so much for all of your advice. > > I actually added tsNet as an inclusion very recently when Curry mentioned it, > thinking it might help. I have eliminated it from my last version. Its use > and its non-use did not change anything. > But after you've removed the inclusion of tsNET, did you also unloaded tsNET in the message box before you've created a new standalone? This is important. The only difference between LC7 and LC8.1.9 i could imagine what could be the cause is tsNET which was introduced in 8.1.0. ___ 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: Functions running in IDE, but not running in standalone
Matthias, Thanks so much for all of your advice. I actually added tsNet as an inclusion very recently when Curry mentioned it, thinking it might help. I have eliminated it from my last version. Its use and its non-use did not change anything. At this point the only things that seem to be creating my issues are the libURL commands/functions that I am using: libURLLastHTTPHeaders, libURLLastRHHeaders, and libURLSetSSLVerification. So I am going to slowly go back through all of my scripts, and one-by-one eliminate their usage to see what happens. I will report back what I find. Regards, Bruce > On Jul 21, 2020, at 11:52 AM, matthias rebbe via use-livecode > wrote: > > Bruce, > > i am now almost out of ideas. ;) > > If no one else has an idea, then i would contact Livecode Support. > > But you could try one little thing before sending a support request. > I cannot remember whne tsNet was introduced. But you could try to create a > standalone which does not use tsNET. > > So... > 1. In Standalone Settings under inclusions uncheck tsNET > 2. run dispatch "revunloadlibrary" to stack tsnetliburl in the > message box > This disables tsNET. > 3. Now create a standalone. That standalone will now just use the libURL > library without tsNET. > 4. Test with that standalone > > To enable tsNET again just restart Livecode or executedispatch > "revloadlibrary" to stack tsnetliburl > in the message box > > > - > Matthias Rebbe > Life Is Too Short For Boring Code > >> Am 21.07.2020 um 17:28 schrieb Bruce Pokras via use-livecode >> : >> >> Matthias, >> >> Thanks very much for your interest in helping me with my problems. >> >> 1) Internet library working in the standalone? The Internet library is >> apparently installed and working properly for downloading patent text and >> PDF images with “put URL [web address] into binfile: [local file path and >> name]”. No problems with that. >> >> 2) Savestackrequest message? I do not use that. >> >> Regards, >> >> Bruce >> >>> On Jul 20, 2020, at 7:12 PM, matthias rebbe via use-livecode >>> wrote: >>> >>> Bruce, >>> >>> i just tried with a sample stack where i did not include the Internet >>> library. I get exact the same error in the bugreport (except the line >>> number and stack name and so on). >>> >>> "Executing at 12:58:33 AM on Tuesday, July 21, 2020 >>> Type: Handler: can't find handler >>> Object: button "Button" of card id 1002 of stack >>> "/Users/matthias/Downloads/test5/MacOSX/test.app/Contents/MacOS/test" >>> Line: libURLSetSSLVerification false >>> Line Num: 2 >>> Hint: libURLSetSSLVerification >>> >>> Comments: hm,weird" >>> >>> >>> If Internet library is really selected in under Inclusions in Standalone >>> Settings, then either there is a problem with your Livecode installation or >>> another guess... >>> >>> Are you using the savestackrequest message in your scripts? If so, is it >>> possible by any chance that you did forgot to add "pass savestackrequest" >>> before "End savestackrequest"? >>> >>> I remember that a long time ago i bothered the Support Team with a problem >>> that database functions did not work in my standalone although i had >>> enabled all needed inclusions. >>> The problem was i used the savestackrequest message to cleanup fields and >>> other things in the stack before saving, but forgot to add "pass >>> savestackrequest". >>> The interesting part was, that the standalone was created and although all >>> included externals were added to the standalone, the standalone was not >>> able to communicate with the database. After adding that line, all was fine. >>> >>> - >>> Matthias Rebbe >>> Life Is Too Short For Boring Code >>> Am 21.07.2020 um 00:28 schrieb Bruce Pokras via use-livecode : Matthias, Yes to both Internet and SSL & Encryption libraries. So everything should be running just fine, but are not. Regards, Bruce > On Jul 20, 2020, at 6:04 PM, matthias rebbe via use-livecode > wrote: > > Bruce, > > and according to the dictionary Internet has to be included to use > libURLSetSSLVerification. > > > > - > Matthias Rebbe > Life Is Too Short For Boring Code > >> Am 20.07.2020 um 23:29 schrieb matthias rebbe via use-livecode >> : >> >> Bruce, >> >> i might be wrong, but did you also include SSL in >> StandaloneSettings. >> If i recall it correctly then SSL is needed for https. >> >> Regards, >> >> - >> Matthias Rebbe >> Life Is Too Short For Boring Code >> >>> Am 20.07.2020 um 22:28 schrieb Bruce Pokras via use-livecode >>> mailto:use-livecode@lists.runrev.com>>: >>> >>> Matthias and Curry, >>> >>> Thanks for your responses. I am using Indy for which I apparently do >>> not have access to RemoteDebugger. >>> >>> I did activate
Re: This is what happens when a tech-master is asked to write a 'guide'!
I wouldn’t expect anyone to need to use that guide. I’m not even sure how you
would manually use hand coded LCB bytecode. It probably just needs to be moved
to the end and have a note added indicating that is isn’t intended for general
use.
Sent from my iPhone
> On Jul 23, 2020, at 4:18 PM, Sean Cole (Pi) via use-livecode
> wrote:
>
> Hi all,
>
> Can we have the guides rewritten to be understood by plebs like me please?
> I've re-read this several times, slowly, and still having trouble working
> it out. Is there some Yale course to get a Phd in LCB so we get to
> understand it? I'll put curly braces around everything unintelligible by
> normal human beings without an MS in computer science.
>
> *LiveCode Builder Bytecode Reference*
>> *Introduction*
>> The LiveCode Builder Virtual Machine is a {infinite register machine} with
>> a {high-level and verifiable bytecode}.
>> All bytecode runs in the context of a {module instance} with {executing
>> handlers forming a {stack of {activation frames}}}. Each frame contains an
>> array of registers, the first part of which are parameters followed by
>> {handler-local variables and bytecode block registers}.
>> Most bytecode operations operate directly on registers, {access to module
>> level definitions} (handlers, constants, variables) are {indirected}
>> through the fetch and store operations.
>> Each bytecode operation has an address which can be jumped to using the
>> jump operations.
>
>
> And that's the way to do an introduction! [sarcasm]!
>
> Then we get a bunch of 'Operations' that we have NO CLUE how or where to
> use in any form of context!
>
> Is it just me or is this just very messed up?
>
> Sean Cole
> *Pi Digital *
> ___
> 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
This is what happens when a tech-master is asked to write a 'guide'!
Hi all,
Can we have the guides rewritten to be understood by plebs like me please?
I've re-read this several times, slowly, and still having trouble working
it out. Is there some Yale course to get a Phd in LCB so we get to
understand it? I'll put curly braces around everything unintelligible by
normal human beings without an MS in computer science.
*LiveCode Builder Bytecode Reference*
> *Introduction*
> The LiveCode Builder Virtual Machine is a {infinite register machine} with
> a {high-level and verifiable bytecode}.
> All bytecode runs in the context of a {module instance} with {executing
> handlers forming a {stack of {activation frames}}}. Each frame contains an
> array of registers, the first part of which are parameters followed by
> {handler-local variables and bytecode block registers}.
> Most bytecode operations operate directly on registers, {access to module
> level definitions} (handlers, constants, variables) are {indirected}
> through the fetch and store operations.
> Each bytecode operation has an address which can be jumped to using the
> jump operations.
And that's the way to do an introduction! [sarcasm]!
Then we get a bunch of 'Operations' that we have NO CLUE how or where to
use in any form of context!
Is it just me or is this just very messed up?
Sean Cole
*Pi Digital *
___
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: ANN: FieldGroup - a simple rich text editor field.
On 23/07/2020 17:20, Richard Gaskin via use-livecode wrote: https://www.tweedly.org/downloads/FieldGroupsample.livecode Thanks for posting this, Alex. Super cool. I didn't find license info in the package - did I miss it? What license is this distributed under? Sorry, I should have said. It is released under the MIT license; I've added the license text to the script of the group, and updated the copy on my website (as above) - now at version 0.2 While I was doing that :-), I added a new message sent on updates : fguser.textchange pFiledID, pStartLine, pEndLine This happens after the text has changed, but *before* the undo system records it. It is therefore possible for the app to make further changes, and they will be recorded as part of the singe change operation. As an example, I've updated the sample app to process - #tags - any word beginning with a "#" is set into 'box' style - *bold* (as in Markdown) - text within any paired "*"s is set to bold (note - it's just an example, I don't do the inverse and add "*"s to any bold text ...) Alex ___ 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: ANN: FieldGroup - a simple rich text editor field.
Alex Tweedly wrote: I'd like to announce the Beta (i.e. v0.1) release of my simple rich text field. Currently it's not on Github or anywhere sensible - it's just on my own download site (see URL at end of this email). I'd be happy if anyone finds it useful, and / or has feedback that might make it useful. .. You can download the sample app - which includes the group you ned to copy/paste - from https://www.tweedly.org/downloads/FieldGroupsample.livecode Thanks for posting this, Alex. Super cool. I didn't find license info in the package - did I miss it? What license is this distributed under? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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
hhOText(community.livecode.hermann.orientedtext)
I have been playing around with this community orientedText widget to see if it is suitable to be used for xAxis Labels at 45 degrees in a bar chart. I’m not sure I am using it correctly. I have set it up similar to this: repeat for each line tLabel in tDataLabels create widget (tLabel) as "community.livecode.hermann.orientedtext" in group "generalChart" set the widgetText of widget(tLabel) to tLabel set the widgetFontName of widget(tLabel) to "Lucida Grande" set the widgetFontSize of widget(tLabel) to "15" set the widgetAngle of widget(tLabel) to "-45" set the strokeBack of widget(tLabel) to false set the widgetAdjustSize of widget(tLabel) to true set the right of widget(tLabel) to tX + tGap set the top of widget(tLabel) to tY add tGap to tX end repeat However, widgetAdjustSize does not adjust it’s size unless I go into the property dialog and uncheck/check the setting. Can anyone help with this. Thanks Terry ___ 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: ANN: FieldGroup - a simple rich text editor field.
Hi Alex,
this is really a great contribution. Thank you very much.
-
Matthias Rebbe
Life Is Too Short For Boring Code
> Am 23.07.2020 um 02:08 schrieb Alex Tweedly via use-livecode
> :
>
> I'd like to announce the Beta (i.e. v0.1) release of my simple rich text
> field. Currently it's not on Github or anywhere sensible - it's just on my
> own download site (see URL at end of this email).
>
> I'd be happy if anyone finds it useful, and / or has feedback that might make
> it useful.
>
>
> FieldGroup - a rich text editor field for Livecode.
>
> Actually, as the old joke goes, it's not really "rich" text, just comfortably
> off. :-)
>
> That is, it supports only some fairly basic features compared to a
> fully-featured rich text editor.
>
> Supported features include :
> - multi-level undo/redo
> - 'undo' can be reset (e.g. after 'save', or 'open')
> - set text style of a chunk by tool button or (sample) menu
> - undo includes text style setting
> - simple (enclosed) tool bars with text or icon buttons - optional of course.
> - each kind of button comes in two sizes
> - button tool bars in any one of four placements (top,right,bottom,left)
> - view scaling
> - call-backs to let the app know when undo/redo are available (e.g. to
> adjust menus)
> - no front scripts used.
>
> FieldGroup is a standalone group which can be simply copy/paste'd into your
> own stacks, and provides a (moderately) rich set of text field features. You
> can have as many of these fieldgroups as you want - each is entirely
> self-contained.
>
> Easy to use - handlers/functions are well documented and (I hope)
> straightforward to understand and use. The downloadable stack includes the
> group, ready to be copy/pasted, as part of a simple sample app which shows
> common uses.
>
> The handler definitions are included below - this is also available in the
> sample app. The "fill" button ill give you text to play with, but shift-Fill
> will restore this document.
>
> You can download the sample app - which includes the group you ned to
> copy/paste - from
>
> https://www.tweedly.org/downloads/FieldGroupsample.livecode
>
> This popped out from a simple app I'm writing (actually, just starting to
> write) so I'm sure I will realize I need more features, and they will be
> added. However, I do not intend it to grow to an all-singing, all-dancing
> word processor-like field editor - I have no need for one of those. But it
> might be a staring point for someone else who wants that.
>
> -- Alex.
>
> /Handlers/
>
> In general, these handlers are invoked by 'dispatch'ing the message to the
> group. The sample app shows an example of how to structure the menu items
> (edit and Format menus). It also contains examples of manipulating the text
> (the *Exchange* button), showing different configurations of the buttons (the
> *Snap* button, and capturing the return messages for undo/redo being
> available.
>
> /Handlers/
>
> */fg.init/* pAConfig
>
> Initialize the field, with an optional set of configuration parameters (see
> fg.configChange for details of these).
>
> /dispatch "fg.init" to grp "fldgrp" with "textbuttonsize=large",
> "svgbutton=large"/
>
> */fg.configChange/* pAConfig
>
> Configure the settings for buttons usage, placement, size, etc.
>
> This can be either an array, with the key/value pairs, or any number of
> parameters each being in the form “key=value”.
>
> Examples:
>
> /put "top" into tA["textbuttons"]//
> put "small" into tA["textbuttonsize"]
> dispatch "fg.configChange" to grp "fldgrp" with tA/
>
> or
>
> /dispatch "fg.configChange" to grp "fldgrp" with "textbuttons=top",
> "textbuttonsize=large"/
>
> Parameters that can be set are:
> - textbuttons : top | bottom
> - svgbuttons : top | bottom | right | left
> - textbuttonsize : small | large
> - svgbuttonsize : small | large
> - resizing : true | false (defaults true - if FALSE then the group will not
> adjust for any resizing)
>
> */fg.version/*
>
> Returns the version of the fieldgroup.
>
> /dispatch function "fg.version" to grp "fldgrp"//
> put "Version" && the result into msg
> /
>
> /
> /
>
> */fg.getText/* pType
>
> Retrieve the contents of the field.
>
> /dispatch function "fg.getText" to grp "fldgrp" with "styledtext"/
>
> pType is one of
> - styledtext (the default) : return the complete styledtext /array
> - text : plain text of the field/
> - htmlText : htmltext of the field
> - rtftext : rtfText of the field
>
> */fg.resetUndoSystem/*
>
> Resets all undo info, for example if the app does a save, and if it determins
> that the user should ne bot able to'undo' beyond that point, then it would
> call this handler.
>
> /dispatch function "fg.version" to grp "fldgrp"//
> put the result into URL ("binfile:savedfile.txt")
> dispatch "fg.resetUndoSystem" to grp "fldgrp"/
>
> /
> /
>
> */fg.set.initialText/* pText
>
> Set the initial text for the field (i.e. set the text, an reset the
Re: ANN: FieldGroup - a simple rich text editor field.
Dear Alex,
This is great! Thanks for sharing! :D
On Thu, 23 Jul 2020 at 01:10, Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I'd like to announce the Beta (i.e. v0.1) release of my simple rich text
> field. Currently it's not on Github or anywhere sensible - it's just on
> my own download site (see URL at end of this email).
>
> I'd be happy if anyone finds it useful, and / or has feedback that might
> make it useful.
>
>
> FieldGroup - a rich text editor field for Livecode.
>
> Actually, as the old joke goes, it's not really "rich" text, just
> comfortably off. :-)
>
> That is, it supports only some fairly basic features compared to a
> fully-featured rich text editor.
>
> Supported features include :
> - multi-level undo/redo
> - 'undo' can be reset (e.g. after 'save', or 'open')
> - set text style of a chunk by tool button or (sample) menu
> - undo includes text style setting
> - simple (enclosed) tool bars with text or icon buttons - optional of
> course.
> - each kind of button comes in two sizes
> - button tool bars in any one of four placements (top,right,bottom,left)
> - view scaling
> - call-backs to let the app know when undo/redo are available (e.g. to
> adjust menus)
> - no front scripts used.
>
> FieldGroup is a standalone group which can be simply copy/paste'd into
> your own stacks, and provides a (moderately) rich set of text field
> features. You can have as many of these fieldgroups as you want - each
> is entirely self-contained.
>
> Easy to use - handlers/functions are well documented and (I hope)
> straightforward to understand and use. The downloadable stack includes
> the group, ready to be copy/pasted, as part of a simple sample app which
> shows common uses.
>
> The handler definitions are included below - this is also available in
> the sample app. The "fill" button ill give you text to play with, but
> shift-Fill will restore this document.
>
> You can download the sample app - which includes the group you ned to
> copy/paste - from
>
> https://www.tweedly.org/downloads/FieldGroupsample.livecode
>
> This popped out from a simple app I'm writing (actually, just starting
> to write) so I'm sure I will realize I need more features, and they will
> be added. However, I do not intend it to grow to an all-singing,
> all-dancing word processor-like field editor - I have no need for one of
> those. But it might be a staring point for someone else who wants that.
>
> -- Alex.
>
> /Handlers/
>
> In general, these handlers are invoked by 'dispatch'ing the message to
> the group. The sample app shows an example of how to structure the menu
> items (edit and Format menus). It also contains examples of manipulating
> the text (the *Exchange* button), showing different configurations of
> the buttons (the *Snap* button, and capturing the return messages for
> undo/redo being available.
>
> /Handlers/
>
> */fg.init/* pAConfig
>
> Initialize the field, with an optional set of configuration parameters
> (see fg.configChange for details of these).
>
> /dispatch "fg.init" to grp "fldgrp" with "textbuttonsize=large",
> "svgbutton=large"/
>
> */fg.configChange/* pAConfig
>
> Configure the settings for buttons usage, placement, size, etc.
>
> This can be either an array, with the key/value pairs, or any number of
> parameters each being in the form “key=value”.
>
> Examples:
>
> /put "top" into tA["textbuttons"]//
> put "small" into tA["textbuttonsize"]
> dispatch "fg.configChange" to grp "fldgrp" with tA/
>
> or
>
> /dispatch "fg.configChange" to grp "fldgrp" with "textbuttons=top",
> "textbuttonsize=large"/
>
> Parameters that can be set are:
> - textbuttons : top | bottom
> - svgbuttons : top | bottom | right | left
> - textbuttonsize : small | large
> - svgbuttonsize : small | large
> - resizing : true | false (defaults true - if FALSE then the group will
> not adjust for any resizing)
>
> */fg.version/*
>
> Returns the version of the fieldgroup.
>
> /dispatch function "fg.version" to grp "fldgrp"//
> put "Version" && the result into msg
> /
>
> /
> /
>
> */fg.getText/* pType
>
> Retrieve the contents of the field.
>
> /dispatch function "fg.getText" to grp "fldgrp" with "styledtext"/
>
> pType is one of
> - styledtext (the default) : return the complete styledtext /array
> - text : plain text of the field/
> - htmlText : htmltext of the field
> - rtftext : rtfText of the field
>
> */fg.resetUndoSystem/*
>
> Resets all undo info, for example if the app does a save, and if it
> determins that the user should ne bot able to'undo' beyond that point,
> then it would call this handler.
>
> /dispatch function "fg.version" to grp "fldgrp"//
> put the result into URL ("binfile:savedfile.txt")
> dispatch "fg.resetUndoSystem" to grp "fldgrp"/
>
> /
> /
>
> */fg.set.initialText/* pText
>
> Set the initial text for the field (i.e. set the text, an reset the undo
> system).
>
> /put URL ("binfile:" & sFilename) into tText//
> put arraydecode(tText) into tA
>
