A place to discuss any and all xTalk implementations, not just LC LCC Forks, but HyperCard, SuperCard, MetaCard, Gain Momentum, Oracle MediaTalk, OpenXION, etc.
Forum rules
Please limit any bashing/harping on any commercial interests to a minimum, thanks!
richmond62 wrote: ↑Sat Sep 02, 2023 12:31 pm
BUT: on the 'POZZ' side:
#1. The messageBox receives focus. Which makes things a bloody-sight easier in far too many ways to list here.
Yes, the messagebox is a huge bonus now that it seems to behave reliably. So a massive thank you Paul for that. I have a few observations. Please do not see them as criticisms, as I love this is still compatible with Mac OS X 10.9.x
(I'll list them in a new topic called DP4 testing)
I do want Paul to see my observations as criticisms: but as POSITIVE criticisms.
Having produced a "still-born baby" [rmCODE], I am only more appreciative of the work that Paul has done: after all, even if nothing else, if Paul hadn't done that work there would be nothing to criticise.
richmond62 wrote: ↑Sat Sep 02, 2023 12:43 pm
The default backgroundColor of textFields should NOT be 'charcoal':
OXT rc 4
Screen Shot 2023-09-02 at 15.44.04.png
LC 963
Screen Shot 2023-09-02 at 15.42.32.png
That, and that alone is a 'killer' I'm afraid.
Oddly enough, a Macintosh standalone generated in OXT rc 4 results in the TextFields looking "the way they should." :
Screen Shot 2023-09-02 at 15.49.49.png
OK what this is is NOT a change in OXT, what you are seeing here is the IDE using the actual 'native' macOS darkMode, your app's may need to be updated to accommodate Apple's API is you really want to support 'darkMode' (I think all modern apps should).
But you can turn it off, I keep it Dark (great Genisis tune!).
richmond62 wrote: ↑Sat Sep 02, 2023 12:31 pm
BUT: on the 'POZZ' side:
#1. The messageBox receives focus. Which makes things a bloody-sight easier in far too many ways to list here.
Yes, the messagebox is a huge bonus now that it seems to behave reliably. So a massive thank you Paul for that. I have a few observations. Please do not see them as criticisms, as I love this is still compatible with Mac OS X 10.9.x
(I'll list them in a new topic called DP4 testing)
"messagebox is a huge bonus", I'm not even sure what you guys are talking about here, whatever it was must have gotten fixed while doing something else in there .
The thing in the bottom left is there for new users, it's just an AppleScript that creates a dummy 'license' file (which is why I thought I might make OXT install into a .pkg file, which has some advantages). If you already have an installed OXT or LCC on your computer, it doesn't do anything.
To test like a new user, you have to delete several folders from different locations.
On macOS these are in the users:
~/Library/Application Support/
~/Library/Preferences/OpenXTalk/
~/Library/Preferences/RunRev/ <- Where the dummy 'license' file goes.
~/Documents/My OpenXTalk/
You should at minimum reset the preferences, otherwise funky things may happen.
This is because the Home stack, if it doesn't find its preference file, it tries to find OLD preferences files first and then uses those if found, and then creates a new preference file (stack) if it doesn't find any of those.
No there's no legal requirement that I'm aware of to replace those graphics Tools icons.
The icons for the tools palette graphics tools were kind of also a 'down payment' on something (hopefully) better. I didn't like the icons that were there, nor the way it displays Color Swatches (which I want something more Adobe/QuarkXpress like), and finally on a whim started to include some of my vector versions (rasterized to png data) of several Hyper-Icons (the 'fish' for arbitrary shapes for example). My goal for the oxtTools palette remains to replace it with an entirely new one. One that has tabs and uses %100 SVG paths for its icons (fall back to a PNG icon if one is found), and is arbitrarily scalable in size.
Also as a down-payment is the added columns width options (I tend to use 6 for column width and hide the dusty pixel-paint tools) for the palette.
Silly question.
If I want to try editing one of the stacks that make up OpenXTalk / Livecode - how do I do this?
If I find where it is, and try to open it with OpenXTalk or Livecode, I get an error that the stack is already open - which it is, as it's a copy of something already being used. The stacks are seemingly locked and don't allow changes, so how do you make changes to them?
I am extremely wary, because of a variety of events in my life, not least of being a cult member, subsequently deprogrammed, of linear, 'one size fits all' ideas.
I think that tinkering is extremely healthy, and the emergence of some sort of monolithic xTalk 'thang' as not entirely healthy.
I worship in Orthodox churches in Bulgaria, Hindu temples when I am in London, and, from time to time, pop into my local mosque on Bulgaria.
So to with xTalk.
The church, the mosque, and the mandir have aĺl got something, but none of them have got everything.
"In contrast, Serf supports the organizational tool of a Stack, but never forces it on you; a stack is a part which can be put in a window, like a button is. It doesn't have to take up the whole window, and you can nest stacks in each other as deep as you like. And you can make as many separate windows in a project as you want and open more than one copy of each."
emphasis is mine.
"There are so many quirks xTalk picked up over its long evolution. I couldn't keep them all...finally I found the compromise I wanted. Everything from the most trivial arithmetic algorithm to the most complicated indefinite-place factorial finder will run without changes. However, the nature of Parts (such as buttons, cards, and windows), and the way you use them, has been totally reworked and rethought."
Why Dan Gelder "went down the pan" right after releasing Beta 6 is anyone's guess: a pity really.
.