Re: LC Roadmap

2021-02-17 Thread prothero--- via use-livecode
Andre:
I think if your chapters offered several ways of organizing a project, starting 
with beginners, and then discussing the various philosophies, say how to name 
variables, using Levure, setting up MVC, etc, etc.

And you are right to be concerned with how quickly the information gets out of 
date and new capabilities are introduced. When I think of “book”, I think of a 
paper based document that sits on my bookshelf. I think, these days, especially 
with such a dynamic product, new resources are going to be coming out all the 
time and the idea of a “book” that sits on a shelf is going to limit you.

I know I’m probably stating what you already know, but what I know is that your 
writings are first rate and I and others have a lot to learn from them.

BTW, I looked at https://livecloud.io 
Very impressive as an example of livecode going big!

Best,
Bill


> On Feb 17, 2021, at 4:16 AM, Andre Garzia via use-livecode 
>  wrote:
> 
> 
> 
>> On 16 Feb 2021, at 15:26, Alex Tweedly via use-livecode 
>>  wrote:
>> 
>> A sample 'skeleton' app - i.e. complete but not fleshed-out. Initially it 
>> would be for a desktop app (the first sequel will cover mobile). It would 
>> implement "good practices" for many of the common features, with enough code 
>> being there to do something - but the focus should be on the architecture 
>> rather than on doing anything useful.
> 
> I released:
> 
> https://andregarzia.com/books/livecode-advanced-application-architecture.html 
> 
> 
> To cover as much of this topic as I felt comfortable doing. The main issue is 
> that different experienced developers have different opinions about what is 
> the best way to organise an app. LiveCode is very versatile and you can do a 
> really great app organisation that is completely different than another great 
> app. We don’t have a mothership preferred way of doing that, and I didn’t 
> want to force my own bias into people.
> 
> I know that some people are deriving great value from Levure, others prefer 
> using something else. It is a tricky topic to cover because once you release 
> such book, you’re kinda telling all newcomers that the way described in the 
> book is the best way to do it. For example, if I went ahead and added a way 
> of doing all that without Levure, then some people would think that Levure is 
> useless because the only book we have tells you do use something different; 
> if I used Levure, then people would think that if you’re not using it, you’re 
> doing it wrong.
> 
> That is way I stayed into safe topics in that book, I covered stuff that 
> should be applicable to many ways of organising your code. Still, I really 
> think you’ve surfaced an important vacuum in our community, we lack good and 
> documented skeleton apps. The main challenge here is the wording on the 
> e-book, it should be clear that there are other equality valid ways of doing 
> things, and that is OK to tweak the presented approach or even come up with 
> your own.
> 
> Since a lot of this work would involve manipulating stacks and their 
> properties, I suspect that this would work better as a multimedia product 
> with videos and articles.
> ___
> 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

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


Re: Livecode IDE question

2021-02-17 Thread David Squance via use-livecode
Thanks for the suggestion, Martin. I will see if that sticks. I knew about 
Cmd-M once, but I use LC so little, and while I’ve had RR and LC since RR 1.?, 
I’ve almost only ever done small apps for my own use.

Dave

> On Feb 17, 2021, at 5:00 AM, Martin Koob via use-livecode 
>  wrote:
> 
> Hi David
> 
> Welcome, I think your question is totally appropriate here.
> 
> I occasionally have the same problem and I use Roger’s solution below.  You 
> may already know this but a quick way to open the message box where you need 
> to type the script to reposition the message box is to use the keyboard 
> shortcut
> Mac: command M
> Win: alt M
> 
> For the last while  the tool bar has been staying nicely in place at the top 
> of the screen.  Not sure what I did that made it stick again.
> One thing to try so It stays permanently in place is in the ‘View’ menu of 
> the IDE unchecking the ‘Tool bar text', and ‘Tool bar icons’ and then 
> rechecking them again.
> 
> Martin
> 
> 
>> On Feb 12, 2021, at 4:21 PM, Roger Guay via use-livecode 
>>  wrote:
>> 
>> I’m having a similar problem on my new MBP, and haven’t figured out  the 
>> cause yet. Just type this in the message box for an temporary fix:
>> 
>>  set the top of stack revMenubar to 25 - - - or so
>> 
>> 
>> Roger
> 
> ___
> 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: Wasm and the LC Roadmap

2021-02-17 Thread Richard Gaskin via use-livecode

David Bovill wrote:

> Anyone know the wasm plans?
>
> I’m Woking on a project in collaboration with a number of other
> platforms and partners that are using wasm. Would like to play
> in the same place with LiveCode.

Given the vast gulf between the browser DOM and LC's object model, and 
the limited role of WASM for GUIs as Andre reminded us, WASM output 
alone is likely an improvement but not likely a game-changer.


It may be useful to evaluate how your app performs and behaves under the 
current HTML output, and then imagine that with a bit shorter download 
and a bit better performance. I'd be surprised if it cuts either 
download or overall execution speed by as much as half.


How well does your app work when exported using the current LC HTML option?



Could there be a place in your plans for streaming apps, a net-savvy 
standalone that gives you nearly all the same benefits of web deployment 
outside the confines of a browser window?


True, it does mean a one-time install, but a web deployment means 
downloading the engine again and again every time you go to the page 
using it; easier but far more tediously impactful over the lifecycle of 
the user's relationship with your app.


Distributing LC-native stack files lets us deliver a dedicated user 
experience (e.g. relevant menus and no fear of the Back button), with 
ultra-rapid development cycles using the LiveCode we know and love 
today, with all the performance we enjoy in any LiveCode standalone.




Porting directly from desktop to browser is not an easy task. I can 
remember when the Apple Developer List exploded with rage demanding 
Apple add a feature to XCode to provide a one-click way to port iOS and 
macOS apps to the Web, and how everyone stopped using Swift and 
Objective C when Apple didn't deliver. ;)


--
Richard Gaskin
Fourth World Systems


___
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: LC Roadmap

2021-02-17 Thread Bob Sneidar via use-livecode
I found your approach to publish and subscribe incredibly useful. I have an app 
that has data grids in multiple sub stacks that each can be open or no. Many of 
these data grids display data from the same database table but in different sub 
stacks.

For example, I have a devices and an accessories table. One sub stack is for 
maintaining the devices at a particular site, another is for maintaining the 
accessories attached to a given device. There is a devices data grid on both of 
these.

The quandary is how to reliably tell all open sub stacks with data grids 
containing identical table data to update when any of the others are updated. 
Your Publish and Subscribe method is tailor made for such a scenario. I am in 
the process of converting all my data grid code over to using that.

Bob S


On Feb 17, 2021, at 4:16 AM, Andre Garzia via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:


On 16 Feb 2021, at 15:26, Alex Tweedly via use-livecode 
mailto:use-livecode@lists.runrev.com>> wrote:

A sample 'skeleton' app - i.e. complete but not fleshed-out. Initially it would 
be for a desktop app (the first sequel will cover mobile). It would implement 
"good practices" for many of the common features, with enough code being there 
to do something - but the focus should be on the architecture rather than on 
doing anything useful.

I released:

https://andregarzia.com/books/livecode-advanced-application-architecture.html

To cover as much of this topic as I felt comfortable doing. The main issue is 
that different experienced developers have different opinions about what is the 
best way to organise an app. LiveCode is very versatile and you can do a really 
great app organisation that is completely different than another great app. We 
don’t have a mothership preferred way of doing that, and I didn’t want to force 
my own bias into people.


___
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: Wasm and the LC Roadmap

2021-02-17 Thread David Bovill via use-livecode
Wasm is a pretty mature target by now. Most of the projects I work with already 
have deployments using wasm on either the server side or the client side. 
ASP.NET and Blazer is making quite a stir. It’s not the sort of - let’s deploy 
it now thing - but when looking at a partnership between several institutions 
each with their own projects - wasm provides a relatively solid basis fir 
glueing the pieces together - regardless (more or less) of the language if 
choice of the collaborator.

   
 
   ***
   

   \\   //  
\\\//  ***
  \\\
   |||//   ,
   |__/
,,,//\,,o==o
;

Schedule a meeting using this link.
Writing and media work on Media Garden.

LinkedIn: David Bovill
Twitter: @fortyfoxes
On 17 Feb 2021, 15:44 +, Andre Garzia via use-livecode 
, wrote:
> Let me begin by saying that WASM is not a silver bullet. I know this doesn’t 
> happen on our community, and that David is not mentioning WASM as a magical 
> solution for HTML5 deployment.
>
> A bit of context is needed to understand why WASM is important and cool. In 
> the past, many C/C++ to Web solutions were based on emscripten which is a 
> toolset based on LLVM that can output C/C++ code in something called “ASM.js” 
> which is a very compact JavaScript source code that kinda does what the C/C++ 
> was doing. This is how people ported the “Unreal Engine” to the web for 
> example. Be aware that ASM.js doesn’t deal with graphics and stuff, that 
> still web technologies. It is just very good at number crunching and makes it 
> possible to reuse C/C++ code.
>
> The main drawbacks from ASM.js (which can be felt on the HTML5 deployment) is 
> that the file sizes are huge. Just imagine a compiler that instead of 
> generating native binary code is generating actual equivalent JavaScript 
> code. This presents two problems for the user, first is the lengthy file 
> transfer needed to download all that content to the users browser, second is 
> the time it takes for the JS engine to actually parse those large files.
>
> These problems are mitigated by WASM. WebAssembly grew out of the working 
> groups that were developing ASM.js. It is a bytecode format, so it is smaller 
> than the equivalent JS file. It is also a standardized VM, which means it 
> executes the same in all browsers that support it. Another cute trick it can 
> do is that is can start loading the bytecode in the VM while it is 
> transferring (aka loading while streaming) which means that by the time the 
> transfer completes, a huge portion of that code is already loaded.
>
> Not only this speeds up the user experience, but having a well-defined VM 
> makes it easier for language developers to target it instead of the ASM.js 
> hacks.
>
> The same toolset that produces ASM.js can produce WASM. It should be natural 
> evolution for the HTML5 deployment to switch from ASM.js based to WASM based. 
> This doesn’t make it magical though, this switch alone will not make LC work 
> on the browser beyond what they’re currently doing. It needs more work, but 
> it should yield smaller files which makes it a better experience.
>
> > On 17 Feb 2021, at 15:30, Graham Samuel via use-livecode 
> >  wrote:
> >
> > Well done Klaus, I was still Googling it! I am in fact looking at articles 
> > (e.g. https://blog.bitsrc.io/whats-wrong-with-web-assembly-3b9abb671ec2 
> > ) that 
> > suggest that despite some very significant users (Google Earth is one), 
> > wasm hasn’t exactly conquered the universe in the three years since it was 
> > launched.
> >
> > Would LC users benefit and/or would it be a massive diversion of scarce 
> > development effort? Anyone have any idea?
> >
> > Graham
> >
> > > On 17 Feb 2021, at 15:19, Klaus major-k via use-livecode 
> > >  wrote:
> > >
> > > To all who are also not familiar witht the gazillion abbreviations,
> > > David is talking about -> WebaSseMbly :-)
> > >
> > > > Am 17.02.2021 um 16:13 schrieb David Bovill via use-livecode 
> > > > :
> > > >
> > > > Anyone know the wasm plans?
> > > >
> > > > I’m Woking on a project in collaboration with a number of other 
> > > > platforms and partners that are using wasm. Would like to play in the 
> > > > same place with LiveCode.
> > > >
> > > > 
> > > > 
> > > > ***
> > > > 
> > > > 
> > > > \\ // 
> > > > \\\// ***
> > > > \\\
> > > > |||// ,
> > > > | __/
> > > > ,,,//\,,o==o
> > > > ;
> > > >
> > > > Schedule a meeting using this link.
> > > > Writing and media 

Re: Wasm and the LC Roadmap

2021-02-17 Thread Andre Garzia via use-livecode
Let me begin by saying that WASM is not a silver bullet. I know this doesn’t 
happen on our community, and that David is not mentioning WASM as a magical 
solution for HTML5 deployment.

A bit of context is needed to understand why WASM is important and cool. In the 
past, many C/C++ to Web solutions were based on emscripten which is a toolset 
based on LLVM that can output C/C++ code in something called “ASM.js” which is 
a very compact JavaScript source code that kinda does what the C/C++ was doing. 
This is how people ported the “Unreal Engine” to the web for example. Be aware 
that ASM.js doesn’t deal with graphics and stuff, that still web technologies. 
It is just very good at number crunching and makes it possible to reuse C/C++ 
code.

The main drawbacks from ASM.js (which can be felt on the HTML5 deployment) is 
that the file sizes are huge. Just imagine a compiler that instead of 
generating native binary code is generating actual equivalent JavaScript code. 
This presents two problems for the user, first is the lengthy file transfer 
needed to download all that content to the users browser, second is the time it 
takes for the JS engine to actually parse those large files.

These problems are mitigated by WASM. WebAssembly grew out of the working 
groups that were developing ASM.js. It is a bytecode format, so it is smaller 
than the equivalent JS file. It is also a standardized VM, which means it 
executes the same in all browsers that support it. Another cute trick it can do 
is that is can start loading the bytecode in the VM while it is transferring 
(aka loading while streaming) which means that by the time the transfer 
completes, a huge portion of that code is already loaded.

Not only this speeds up the user experience, but having a well-defined VM makes 
it easier for language developers to target it instead of the ASM.js hacks.

The same toolset that produces ASM.js can produce WASM. It should be natural 
evolution for the HTML5 deployment to switch from ASM.js based to WASM based. 
This doesn’t make it magical though, this switch alone will not make LC work on 
the browser beyond what they’re currently doing. It needs more work, but it 
should yield smaller files which makes it a better experience.

> On 17 Feb 2021, at 15:30, Graham Samuel via use-livecode 
>  wrote:
> 
> Well done Klaus, I was still Googling it! I am in fact looking at articles 
> (e.g. https://blog.bitsrc.io/whats-wrong-with-web-assembly-3b9abb671ec2 
> )  that 
> suggest that despite some very significant users (Google Earth is one), wasm 
> hasn’t exactly conquered the universe in the three years since it was 
> launched.
> 
> Would LC users benefit and/or would it be a massive diversion of scarce 
> development effort? Anyone have any idea?
> 
> Graham
> 
>> On 17 Feb 2021, at 15:19, Klaus major-k via use-livecode 
>>  wrote:
>> 
>> To all who are also not familiar witht the gazillion abbreviations,
>> David is talking about -> WebaSseMbly :-)
>> 
>>> Am 17.02.2021 um 16:13 schrieb David Bovill via use-livecode 
>>> :
>>> 
>>> Anyone know the wasm plans?
>>> 
>>> I’m Woking on a project in collaboration with a number of other platforms 
>>> and partners that are using wasm. Would like to play in the same place with 
>>> LiveCode.
>>> 
>>> 
>>>   
>>> ***
>>> 
>>>  
>>> \\   //  
>>>  \\\//  ***
>>>\\\
>>> |||//   ,
>>> |__/
>>> ,,,//\,,o==o
>>> ;
>>> 
>>> Schedule a meeting using this link.
>>> Writing and media work on Media Garden.
>>> 
>>> LinkedIn: David Bovill
>> 
>> 
>> --
>> Klaus Major
>> https://www.major-k.de
>> https://www.major-k.de/bass
>> kl...@major-k.de
>> 
>> 
>> ___
>> 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: Wasm and the LC Roadmap

2021-02-17 Thread Graham Samuel via use-livecode
Well done Klaus, I was still Googling it! I am in fact looking at articles 
(e.g. https://blog.bitsrc.io/whats-wrong-with-web-assembly-3b9abb671ec2 
)  that 
suggest that despite some very significant users (Google Earth is one), wasm 
hasn’t exactly conquered the universe in the three years since it was launched.

Would LC users benefit and/or would it be a massive diversion of scarce 
development effort? Anyone have any idea?

Graham

> On 17 Feb 2021, at 15:19, Klaus major-k via use-livecode 
>  wrote:
> 
> To all who are also not familiar witht the gazillion abbreviations,
> David is talking about -> WebaSseMbly :-)
> 
>> Am 17.02.2021 um 16:13 schrieb David Bovill via use-livecode 
>> :
>> 
>> Anyone know the wasm plans?
>> 
>> I’m Woking on a project in collaboration with a number of other platforms 
>> and partners that are using wasm. Would like to play in the same place with 
>> LiveCode.
>> 
>>  
>>
>>  ***
>>  
>>   
>>  \\   //  
>>   \\\//  ***
>> \\\
>>  |||//   ,
>>  |__/
>> ,,,//\,,o==o
>> ;
>> 
>> Schedule a meeting using this link.
>> Writing and media work on Media Garden.
>> 
>> LinkedIn: David Bovill
> 
> 
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> 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: Wasm and the LC Roadmap

2021-02-17 Thread Klaus major-k via use-livecode
To all who are also not familiar witht the gazillion abbreviations,
David is talking about -> WebaSseMbly :-)

> Am 17.02.2021 um 16:13 schrieb David Bovill via use-livecode 
> :
> 
> Anyone know the wasm plans?
> 
> I’m Woking on a project in collaboration with a number of other platforms and 
> partners that are using wasm. Would like to play in the same place with 
> LiveCode.
> 
>   
> 
>   ***
>   
>
>   \\   //  
>\\\//  ***
>  \\\
>   |||//   ,
>   |__/
> ,,,//\,,o==o
> ;
> 
> Schedule a meeting using this link.
> Writing and media work on Media Garden.
> 
> LinkedIn: David Bovill


--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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


Wasm and the LC Roadmap

2021-02-17 Thread David Bovill via use-livecode
Anyone know the wasm plans?

I’m Woking on a project in collaboration with a number of other platforms and 
partners that are using wasm. Would like to play in the same place with 
LiveCode.

   
 
   ***
   

   \\   //  
\\\//  ***
  \\\
   |||//   ,
   |__/
,,,//\,,o==o
;

Schedule a meeting using this link.
Writing and media work on Media Garden.

LinkedIn: David Bovill
Twitter: @fortyfoxes
___
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: [OT] Poll: What does it mean for 1 rect to be 'within' a certain distance of another rect?

2021-02-17 Thread Paul Dupuis via use-livecode

Thank you.

I think it is an example of a LiveCode built app that uses many (I'd say 
most) of LiveCode's features all in one application. It was originally 
built in HyperCard around 1990 with a Windows version in Toolbook and 
then the Mac version migrated to SuperCard (waiting on the never 
released Windows version of SuperCard), and then was migrated to 
MetaCard, and then Revolution, and then Revolution became LiveCode. The 
HyperCard version used a ton of Externals (XCMDs) to get the flavor of a 
real application (vs a stack). Over time more and more functions and 
commands became part of the xTalk language.



On 2/17/2021 7:13 AM, David V Glasgow via use-livecode wrote:

Double [OT], but I just want to say that I have looked at HyperRESEARCH several 
times over the years, and have been hugely impressed with its features.

In fact, it is too feature rich for my needs, but it looks like a really great 
piece of work.

Cheers,

David G


On 16 Feb 2021, at 9:43 pm, Paul Dupuis via use-livecode 
 wrote:

  company Researchware produces called HyperRESEARCH for performing qualitative 
data analysis.

___
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: Livecode IDE question

2021-02-17 Thread Martin Koob via use-livecode
Hi David

Welcome, I think your question is totally appropriate here.

I occasionally have the same problem and I use Roger’s solution below.  You may 
already know this but a quick way to open the message box where you need to 
type the script to reposition the message box is to use the keyboard shortcut
Mac: command M
Win: alt M

For the last while  the tool bar has been staying nicely in place at the top of 
the screen.  Not sure what I did that made it stick again.
One thing to try so It stays permanently in place is in the ‘View’ menu of the 
IDE unchecking the ‘Tool bar text', and ‘Tool bar icons’ and then rechecking 
them again.

Martin


> On Feb 12, 2021, at 4:21 PM, Roger Guay via use-livecode 
>  wrote:
> 
> I’m having a similar problem on my new MBP, and haven’t figured out  the 
> cause yet. Just type this in the message box for an temporary fix:
> 
>   set the top of stack revMenubar to 25 - - - or so
> 
> 
> Roger

___
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: LC Roadmap

2021-02-17 Thread Andrew at MidWest Coast Media via use-livecode
This is an excellent idea. Provide the basic skeleton, but then demo a couple 
completed concepts as well to show what could be done. I would be willing to 
collaborate to make a finished example and document the process.

LiveCode is extremely powerful, but as others have noted some of these advanced 
features tend to roam from the “simple English” syntax. A little sample content 
goes a long way. You still need a paid version of LC to get iOS deployment, at 
least Community Plus: it seems like a starter stub project could pay for itself 
in subscription fees.

—Andrew Bell

> Date: Tue, 16 Feb 2021 15:26:49 +
> From: Alex Tweedly 
> To: use-livecode@lists.runrev.com
> Subject: Re: LC Roadmap
> 
> On 15/02/2021 12:55, Andre Garzia via use-livecode wrote:
>> It is with this in mind, that I decided to create content for our 
>> community. Books are an easy value proposition. Most of our community 
>> is beyond their thirties and have a fondness (and experience) for the 
>> written word and documentation. It is easy to sell books here, way 
>> easier than in other communities which are younger and prefer videos. 
>> That doesn?t mean that I can?t provide videos as well, damn I?ve 
>> graduated with a BA in filmmaking, I?m geared to start filming too. 
>> Books were the first step. I see myself more as a storyteller than a 
>> developer, that is why I want to focus on content for my own career 
>> moving forward. But that is only my own personal journey, other people 
>> here have a different path. I just wish that more people here decide 
>> to share their knowledge (and code) so that we can become a more 
>> vibrant community. 
> 
> Then I have a concrete suggestion for what would, I think, be a very 
> useful e-book + stack.
> 
> A sample 'skeleton' app - i.e. complete but not fleshed-out. Initially 
> it would be for a desktop app (the first sequel will cover mobile). It 
> would implement "good practices" for many of the common features, with 
> enough code being there to do something - but the focus should be on the 
> architecture rather than on doing anything useful.
> 
> It should include (most of):
> 
> ?- splash stack, with checks for updated versions, background 
> downloading & installing them, etc.
> 
> ?- proper locations for libraries, prefs files, other config data, 
> other data, etc. as well as loading the libraries.
> 
> ?- simple preferences handling (i.e. library which will store, retrieve 
> and allow basic user interaction to view/update preferences - given some 
> description of the preferences)
> 
> ?- a menu, ready to extend or remove, with abstraction of the functionality
> 
> ?- maybe a status bar
> 
> ?- some groups that handle resizing well
> 
> ?- multiple cards should be involved
> 
> ?- probably simple SQL (i.e. sqlite + your DBLib)
> 
> And of course the most difficult part will be writing the e-book that 
> describes the app, what it does, and maybe why those particular methods 
> were chosen over some of the alternatives.
> 
> Then the sequel would cover mobile, so adding features like a Header 
> Bar, segmented control, using library to overlay controls with native 
> controls as needed, ... as well as describing the hoops one needs to 
> jump through to actually do mobile developments.
> 
> Further sequels could then cover additional features - again for 
> architecture and example, not just to make it a more complicated app. 
> For example: toolbar, pane splitter, data grid, ...
> 
> Alex.
> 
> P.S. I'd be happy to collaborate on doing the development part - but I 
> suspect you'd be quicker without me :-)
> 
> P.P.S title suggestion "The Soul of a New App".
> 


___
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: LC Roadmap

2021-02-17 Thread Andre Garzia via use-livecode


> On 16 Feb 2021, at 15:26, Alex Tweedly via use-livecode 
>  wrote:
> 
> A sample 'skeleton' app - i.e. complete but not fleshed-out. Initially it 
> would be for a desktop app (the first sequel will cover mobile). It would 
> implement "good practices" for many of the common features, with enough code 
> being there to do something - but the focus should be on the architecture 
> rather than on doing anything useful.

I released:

https://andregarzia.com/books/livecode-advanced-application-architecture.html 


To cover as much of this topic as I felt comfortable doing. The main issue is 
that different experienced developers have different opinions about what is the 
best way to organise an app. LiveCode is very versatile and you can do a really 
great app organisation that is completely different than another great app. We 
don’t have a mothership preferred way of doing that, and I didn’t want to force 
my own bias into people.

I know that some people are deriving great value from Levure, others prefer 
using something else. It is a tricky topic to cover because once you release 
such book, you’re kinda telling all newcomers that the way described in the 
book is the best way to do it. For example, if I went ahead and added a way of 
doing all that without Levure, then some people would think that Levure is 
useless because the only book we have tells you do use something different; if 
I used Levure, then people would think that if you’re not using it, you’re 
doing it wrong.

That is way I stayed into safe topics in that book, I covered stuff that should 
be applicable to many ways of organising your code. Still, I really think 
you’ve surfaced an important vacuum in our community, we lack good and 
documented skeleton apps. The main challenge here is the wording on the e-book, 
it should be clear that there are other equality valid ways of doing things, 
and that is OK to tweak the presented approach or even come up with your own.

Since a lot of this work would involve manipulating stacks and their 
properties, I suspect that this would work better as a multimedia product with 
videos and articles.
___
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: [OT] Poll: What does it mean for 1 rect to be 'within' a certain distance of another rect?

2021-02-17 Thread David V Glasgow via use-livecode
Double [OT], but I just want to say that I have looked at HyperRESEARCH several 
times over the years, and have been hugely impressed with its features.

In fact, it is too feature rich for my needs, but it looks like a really great 
piece of work.

Cheers,

David G

> On 16 Feb 2021, at 9:43 pm, Paul Dupuis via use-livecode 
>  wrote:
> 
>  company Researchware produces called HyperRESEARCH for performing 
> qualitative data analysis.

___
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