LiveCode Forums.

Clearly they're preoccupied.

"They" have been 'pre-occupied' for a very long time re HC import and video on Linux,
or, just possibly, they don't think the effort to sort those things out is worth the effort
vis-a-vis the time and effort "they" seem to be putting into mobile development.

There are also questions relating to the HTML project
[LC's second attempt at providing a way to produce web-browser standalones].

What would be nice is if "they" would let us know with some sort of statement like this:

"We are not going to do any further development on XXXXX because we feel it is not in our interests."

So those who do feel it is in their interests know that and, should they choose, can go elsewhere.

I've been in the software industry a long time (read, "I have scars from SuperCard for Windows", Apple's SK8, and a dozen others). It really doesn't matter what other people's intentions are with regard to your own business planning. The only thing that matters is working software in hand.

See what works today, and make plans only on that.

If something comes along later, you can change your mind later.

I can't imagine that supporting a 30-year-old product like HC would have any sort of priority at all. But even if "they" did intend to support it eventually it would have a very low priority; I can't believe there are more than two or three of us who'd ever need to use it. I was one of the go-to people for HC conversions and I haven't had a request in years. And there's a work-around anyway.

I didn't need them to make any statement, I would have done the same thing "they" did.

I'm changing the topic title here to keep the conversation from getting hijacked into issues with importing HC stacks.

What I'm reporting here is that LiveCode crashes. Hard. When you attempt this.
I'm fine with not being able to load HC stacks any more.
It shouldn't cause a crash when you attempt it.

Um, Mark, I think you have to go back to the first post and edit it to make it change in the board index. Changing the title of the last post only changes it from there forward, I'm pretty sure.

Richard did put forth a fair suggestion, unfortunately I (currently) don't have the time and possibly not the knowledge to even look into it

Ah, right you are. I fixed it.
Maybe I missed something - what was Richard's suggestion?
Ah... the community-based thing.

There are currently 191 pull requests waiting in the queue on github for the LC engine, many of which have been sitting there for years.
And another 56 waiting in the IDE queue.
Granted some of those are marked WIP and so aren't ready to be merged, but I don't see the point of adding more to the queues.

mwieder wrote: Tue Jun 09, 2020 9:15 pm There are currently 191 pull requests waiting in the queue on github for the LC engine, many of which have been sitting there for years.
And another 56 waiting in the IDE queue.
Granted some of those are marked WIP and so aren't ready to be merged, but I don't see the point of adding more to the queues.

Any sense of the percentage marked "WPI", and the percentage unaddressed?

I'm not sure that's a valid way to think about this.
There are PRs that are still labeled WIP, and some of them depend on others that can't be merged yet.
There are some that can't yet be merged, but aren't WIP because they're finished and just depending on other issues.
There are enhancements and bug fixes

There's at least one of mine that's there in a holding pattern because it fixes a problem but isn't going to be merged in favor of a "better" way of fixing things some day.

But there's a large number of PRs that are ready for review and merging, some of which have been around for years and haven't been merged into either major or minor point releases.

https://github.com/livecode/livecode/pulls
https://github.com/livecode/livecode-ide/pulls

AND . . . re importing HC stacks . . .

I have a G5 iMac 17 inch machine (running MacOS 10.4) that, on the fairly rare occasions I need to look at
'Classic' stuff I pull out from behind all my other 'legacy' machines and put it next to whatever machine I'm currently
working with.

With a Hypercard stack I can open it, read the code, and just type it into a LiveCode stack,
or, being somewhat of a lazy sausage, copy-paste chunks of code into text documents to transfer to
my current machine.

I didn't need them to make any statement, I would have done the same thing "they" did.

Possibly . . .

This is, however, rather misleading:
- -
Documentation LiveCode 9.6.0

"To import a HyperCard stack, use the go command to open the stack. LiveCode automatically converts it to a LiveCode stack."

Just trying to work out HOW to use 'go' to open an HC stack.