Couple of HTML questions

[Colin Holgate via use-livecode]

I want to have an online text editor, that can post some styled text, that then 
gets read into a desktop stack. There are a lot of HTML styled text editors 
around, but I thought I may as well try using LiveCode for that part as well.

Two issues I’ve hit are the setting of the style of the text, and then posting 
the text to a PHP script, that stores the HTML changes.

Can these lines work in an HTML published stack?:

post data to URL theurl

and:

set the textstyle of the selection to bold



___
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: LiveCode Community - anyone up for maintaining the community edition?

[Paul McClernan via use-livecode]

Thank you very much for the info and advice Mark, very much appreciated. 
This is all entirely new ground for me and so I may make mistakes going 
forward, just let me know and I’ll do my best to correct them ASAP!
I hope certainly hope anyone else trying to do anything with the legacy code 
base would respect LC Ltd’s iP / copyrights as well.

> With all that said, I wish you, and anyone who joins you, well with your 
> endeavour.
> 
> Have fun!
> 
> Warmest Regards,


Having fun IS one of the primary goals!
Good luck and Thanks again.

> On Sep 9, 2021, at 10:18 AM, Mark Waddingham via use-livecode 
>  wrote:
> 
> On 2021-09-08 22:54, Paul McClernan via use-livecode wrote:
>> I've already fixed a bug that I reported back in April in my fork(s) and
>> added a link to my fix to that bugzilla report.
>> https://github.com/PaulMcClernan/LiveCodeCommunity-IDE-DontPanicEdition
> 
> At this point in any changed relationship, it’s necessary to set out the new 
> terms, as amicably as possible. Each side needs to clearly understand where 
> they can and cannot go now. As our move away from supporting Open Source 
> LiveCode is still very new, it’s likely the ramifications are not as yet 
> understood.
> 
> I have to ask you (and anyone involved in that project, or any other forks) 
> politely not to submit any changes back to bugzilla or anywhere else 
> associated with LiveCode Ltd. as it creates a business risk for us.
> 
> We (LiveCode Ltd.) cannot take any code changes you make to your project's 
> version of the LiveCode source-code and use them in our commercial code as 
> (by default) it will be GPLv3 licensed, and the copyright of that will be 
> held by the person who authored the changes; just as you cannot change the 
> license from GPLv3 nor copyright attribution (LiveCode Ltd.) - whether 
> explicit or implicit - of any existing line of code in your project's fork of 
> the LiveCode repositories, nor take any changes which appear from now onwards 
> in any commercial edition to incorporate into your project.
> 
> When we were running the open source project, we had in place a Contributor's 
> License Agreement which meant that the copyright of any code authored by a 
> contributor in any patch submitted to LiveCode Ltd was assigned to us. 
> However, this only extended to contributions submitted through GitHub, where 
> there was an appropriate immutable record of such submissions and it was 
> universally clear what changes were being made. For obvious reasons, this no 
> longer exists.
> 
> More generally, I must also ask you not to use the LiveCode mailing list, bug 
> reporting system or LiveCode forums for discussions surrounding your fork - 
> particularly related to plans, ideas, developments and changes which are 
> being or have been made.
> 
> At no point do I want us to be the target of any sort of public ill-will or 
> indeed lawsuit due to assertions of copyright theft, or appropriation of 
> other people's ideas that were not clearly (whether implicitly or explicitly) 
> proffered to us directly.
> 
> The only way to ensure that is for any forks (yours included) to stand 
> completely independently and by themselves - with their own communication 
> forums, distinctive product name and distinct branding so there can be no 
> risk of confusion nor appropriation of anything from either side.
> 
> I should point out that recent events are actually nothing to do with my 
> above words - I would have said the same to any fork maintainer who actively 
> sought to advertise their fork within the existing LiveCode community - as 
> defined by LiveCode's mailing lists, forums, bug reporting system, or any 
> other forum owned and run by LiveCode Ltd. for the purposes of public 
> interaction - or posted links to code changes from that project or on any 
> such forum/system. Indeed, ensuring complete independence really is standard 
> practice when forks are made of open source projects - OpenOffice and 
> LibreOffice spring to mind.
> 
> We fully respect the legacy we have created in terms of the GPLv3 
> source-code, copyrighted to LiveCode Ltd., which is forever preserved in the 
> archived GitHub repositories in the LiveCode GitHub account which carry the 
> LiveCode name. We have no issue with any or all forks or open-source 
> GPLv3-based projects which might arise from that legacy.
> 
> All we ask is that any such project ensures that it respects LiveCode Ltd.'s 
> intellectual property as embodied within that (through its GPLv3 licensed, 
> copyrighted source-code) and also respects LiveCode Ltd.'s right to assert 
> itself as the only entitled user of the LiveCode name, trademarks and brand 
> identity.
> 
> With all that said, I wish you, and anyone who joins you, well with your 
> endeavour.
> 
> Have fun!
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> 

Alternative to Nabble for RSS for this list

[Richard Gaskin via use-livecode]

The old Nabble RSS feed for this died some time ago. So far the only 
alternative I've found is the RSS from mail-archive.com, which is darn 
near useless because it contains no body info from a post, not even the 
first sentence or two, just the title and the sender.


Is there another RSS feed for the use-livecode list?

--
 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: Sorting text is *VERY* slow in LC9 on Windows (Re: Accumulating text is *VERY* slow in LC9 on Windows)

[Mark Waddingham via use-livecode]

On 2021-09-10 19:10, Ben Rubinstein via use-livecode wrote:

The other was
The only caveat is that it might cause apps mutating lots of 
medium->large strings concurrently to take up more memory in 
general... > ... (and any issue arising from that could be resolved by 
moving to the 64-bit

windows engine).


I have been doing my tests on the 64-bit Windows engine. What am I 
missing?


The change I am making to the buffer extension rules means that mutable 
strings (i.e. those which the last action was modifying them, rather 
than copying them / fetching them) will take up more space than they did 
before to allow for possible extension (previously the maximum 'just in 
case' space which was allocated was 63 bytes).


This means that applications may take up more memory as a result (if 
they happen to have lots of large mutable strings in play at any one 
time).


32-bit windows engines have a maximum address space of 3Gb - so if an 
app was already approaching that limit, this might tip them over to 
start causing out of memory errors.


However, in this case, switching to use the 64-bit windows engine would 
resolve the problem as 64-bit address space is substantially larger.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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] Organize 1.1 now in App Store

[Mark Smith via use-livecode]

Hi Kelly, just wondering if you could expand a bit more on the use of iCloud 
for syncing, and how that would work?

Thanks,
Mark


> On Sep 10, 2021, at 9:42 PM, Dev  wrote:
> 
> Just downloaded it and will give it a look. When you get around to the iPad- 
> please sync through iCloud. It’s the Apple way and works seamlessly for so 
> many apps I have. I even have my LC prefs and plug-ins on iCloud so that they 
> are accessible everywhere easily. 
> 
> Kelly 
> 
> Sent from an iDevice on the go, please excuse brevity & any errors
> 
>> On Sep 10, 2021, at 2:24 PM, Mark Smith via use-livecode 
>>  wrote:
>> 
>> Thanks Bill, I’ll add that to the request list. I developed it on a 6S but 
>> went out and bought a 12 today so I could tackle the issue of resizing it 
>> for larger devices (something I know I don’t handle very well at the 
>> moment). My first reaction after installing Organize on the 12 was “holy 
>> crap” this thing is fast. It just transformed the whole experience for me. 
>> (And made LC shine as well I might add). Anyway, once I work how to resize 
>> for a 12, I am sure the same method can be applied to things like an iPad. 
>> Of course, the request after that will be “can I sync my iPhone and iPad 
>> to-do’s?”. That is the fun of this though, isn’t it, once you get started it 
>> never ends 
>> 
>> Thanks for the suggestion, its a good one.
>> 
>> Mark
>> 
>> 
>>> On Sep 10, 2021, at 8:58 PM, proth...@earthlearningsolutions.org wrote:
>>> 
>>> Thanks, Mark. I was thinking about it as a scheduler instead of a task 
>>> reminder. I use the Apple calendar for reminders of appointments mostly. It 
>>> is a nice job.
>>> 
>>> For me, I have 2 ipads, an iPhone, and a desktop Mac. I like to use my iPad 
>>> whenever possible because of the screen size. It could be nice if you had 
>>> an ipad version too and for Apple, it probably wouldn’t require a lot of 
>>> extra coding, but organizing for a larger screen could be a bit of work.
>>> 
>>> Nice work and it’s great that you had an easy time with the Apple store.
>>> 
>>> Best,
>>> Bill P.
>>> 
 On Sep 10, 2021, at 12:16 PM, Mark Smith >>> > wrote:
 
 Interesting question Bill. I guess the biggest difference is it does not 
 require you to “sequence” activities according to time (although, yes, 
 scheduling will be in a subsequent version). For now, a typical page might 
 look something like the following…
 
 
 
 i
 
 
 And, as the reorder “action” on the page suggests, you can re-arrange 
 items as you want. It’s a list, and a flexible one at that. Don’t get to a 
 task? There is a row menu that lets you move it to another day/date. Often 
 I find if I don’t get to it today, and tomorrow is not looking any better, 
 I’ll just throw it forward a week and deal with it then.
 
 It’s primarily a list of tasks you constantly add to, rearrange, reorder, 
 finish, etc. 
 
 Hope that helps. 
 
 Mark
 
 
> On Sep 10, 2021, at 6:55 PM, ELS Prothero via use-livecode 
> mailto:use-livecode@lists.runrev.com>> 
> wrote:
> 
> Sorry, I started but didn’t continue to participate in the feedback 
> request for your app. My question, though, is “what does this app do that 
> just using the calendar can’t?” It could help to state it’s unique 
> capabilities in the app description.
 
>>> 
>>> William A. Prothero, Ph.D.
>>> University of California, Santa Barbara Dept. of Earth Sciences (Emeritus)
>>> Santa Barbara, CA. 93105
>>> http://earthlearningsolutions.org/ 
>> 
>> ___
>> 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