Sannyasin Brahmanathaswami wrote:
> A lot of the "flak" I hear about using LC is "but it's not
> responsive, at that so easy with HTML5" They gloss over the
> depth of javascript skills required to actually program the UI
> to do anything other than look pretty. However easy it may be
> to make
+1
The whole point, or one of the points to object oriented development was to
de-centralize the code base. As stated in other posts it really comes down to
how complex your app is. I have cards that can be used in any stack, and cards
that are very specific to the app. Same with different stac
@ trevor: OK, understood. In fact we are doing a similar/ almost same thing
though calling it "SivaSiva.json" which is read on start up,
re the stack files for the components: interesting…
We have been adding *all* behaviors for all modules in the main stack, since
many of these are reused
On Sun, Feb 5, 2017 at 9:00 PM, Sannyasin Brahmanathaswami via use-livecode
wrote:
> In line
> On 2/5/17, 3:41 PM, "use-livecode on behalf of Trevor DeVore via
> use-livecode" use-livecode@lists.runrev.com> wrote:
>
> With Levure adding stack files won't cause any conflicts. Each stack
>
I personally don't like everything in one file. I conceptualize things
better if I can think of them as being separate. When I'm building
interfaces, I could lay everything out on one card and use groups to
show/hide the relevant controls, but in my head they're all still there.
In interfaces tha
In line
On 2/5/17, 3:41 PM, "use-livecode on behalf of Trevor DeVore via use-livecode"
wrote:
With Levure adding stack files won't cause any conflicts. Each stack
is an independent file and the file that specifies which stacks to load is
a text file.
BR: I must be missing somethin
ieOn Sun, Feb 5, 2017 at 12:03 PM, Sannyasin Brahmanathaswami via
use-livecode wrote:
>
> 2) building UI from script: every now and the notion passes by that
> perhaps building UI from script has advantages of the LC WSIWIG model. I
> was intrigued in your to see in the background in sublime te
Ali, thanks for chiming in… in the current app we stayed away from any
resizing, the Design passed down from our team which has years of experience in
print graphics (but zero in digital UX/UI) would have been a challenge to get
responsive. It could be done of course, anything can be done in Liv
Heh, I somehow missed the para where you made this comment already Brahma!
Sorry.
On Sun, Feb 5, 2017 at 6:21 PM Ali Lloyd wrote:
> On the subject of building UI from script, I generally think it boils down
> to whether you already have a good resizeStack handler implemented. If you
> do, you'v
On the subject of building UI from script, I generally think it boils down
to whether you already have a good resizeStack handler implemented. If you
do, you've done all the hard work already - you can just create all the
objects with their required properties before the card opens and delete
them
Trevor, thanks for that intro to the new tools in LC9
I'm already using libraries and behaviors extensively, but still find my self
build LC stack binaries with a full stack script or, quite often, 95% of the
code in the card script (if the UI can all be done on a single card)
The other day
Thank you Trevor - a really nice video!
I’ve been using script-only stacks for a while for code libraries, never
realised how easy it was to use them to effectively make ‘script-only
behaviors’ :)
Kind regards
Dave
___
use-livecode mailing list
use
I created a screencast showing how you can convert the scripts in your
stacks to script only behavior stacks using a new Property Inspector
feature in LiveCode 9 (still in early development). Storing your code in
script only stacks allows you to manage your application with source
control software
13 matches
Mail list logo
