hh wrote:
> Richard.
>
> Thanks for your engagement. I would like to second this with 98%.
>
> Let me correct two of your statements (the missing 2%).
>
> 1.
>> RG wrote:
>> The last RPi build was v704, which is generally good with one
>> critical issue: a bug in the menu handling routine causes a crash
>> when clicking in a menubar.
> That's wrong in that generality. I have four Raspi's running
> (one A with Debian, two B+ with Lubuntu or Debian resp., one 3 with
> Xubuntu or Debian resp., the Debian needs to be first installed on
> a 2B+, see forum). So install an appropriate OS and it works. Though
> 3-5 imes slower than v651.
It's nice to know it can work well with certain distros, but for myself
(focused on a goal of adoption) an "appropriate OS" is the one most
commonly used. I ran my tests on the latest stock Raspian most
prominently available at raspberrypi.org at the time.
If LC won't run on the most common build (and it seems to except for
that one bug), it's time for a fresh compile. Hopefully it won't be
much longer.
> 2.
>> RG wrote:
>> So for me, if I had to deliver a GUI for RPi I'd much rather use a
>> workflow similar to what we do with mobile: develop on a fully-
>> spec'd desktop machine, and deploy to the device.
>
> If "I'd" means "I would" then I'd say once again (I told you in the
> forum):
> This is the way I did from the beginning of the existence of __LC
> 704__, which is the only one that has a Raspi-deployment option
> (Linux ARMv6-HF).
> Simply copy the standalone created on your desktop box to your Raspi
> via sftp (what may be even scripted) or via an USB stick.
>
> So if developers optimize for speed (as LC 7 is 3-5 times slower than
> LC 6) they can have this, since years. By ONE click and ONE data
> transfer.
When we get a fresh build with v9 I think we'll see many speed
improvements in the RPi engine (see earlier reply to jonathandlynch).
V6 is nice, but old. It would be ideal to keep formats and features in
sync with the rest of the LC world.
And the work Fraser and other have done in v7 and v8 for better GTK
integration has been superb, at least in the Gnome-based DE's I'm using
(Unity in Ubuntu and LXDE in Lubuntu).
But regardless of version, it seems we're on the same page with a
worklow that favors building on the desktop and running on the RPi.
In fact, this morning I was curious about Xojo's system requirements for
their RPi deployments, and it seems Xojo isn't available for RPi - that
is, not the IDE. They have a runtime engine only, so the workflow they
require is the same one you and I recommend with LC, building on desktop
to run on RPi.
Still, given the many EDU use cases where having an IDE on the RPi would
be desirable, I'd like to explore options for a lightweight IDE down the
road (though probably way down the road for me; lots of other priorities
before that).
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://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
