what kind of browser/os do you use for your touch screens?
@daboe01 I do all of the development in Safari on the Mac. Most of our customers are using Chrome in Windows. We have one OEM that builds a custom unit with a touchscreen and PC all in one device. They are using an old version of Firefox in kiosk mode for all of the UI. I was very happy when I tested my Cappuccino app on it and it worked! The only issue I had was that one of the JavaScript math functions that I was using wasn't supported in that version of Firefox. I was able to work around that with a different math function.
We have another OEM that builds a desktop digital press that has a 6 inch touchscreen on the device driven by a Raspberry Pi. I forget what browser they used on that, but I wrote a special version of our Cappuccino app with a custom UI for that screen and it worked great there too. That was a fun project to do.
For the touchscreen mode of the app, I wrote my own keyboard class in Objective-J. It's pretty nice. You can pass in a CPArray that defines what symbol shows on each key of the keyboard and another CPArray that defines what each key press will insert into the targeted CPTextField when pressed. There's also a keypad mode for fields that only take numbers and you can configure it to accept decimals or only integers or allow negative numbers or not.
I very much enjoy developing in Cappuccino!
We have another OEM that builds a desktop digital press that has a 6 inch touchscreen on the device driven by a Raspberry Pi. I forget what browser they used on that, but I wrote a special version of our Cappuccino app with a custom UI for that screen and it worked great there too. That was a fun project to do.
For the touchscreen mode of the app, I wrote my own keyboard class in Objective-J. It's pretty nice. You can pass in a CPArray that defines what symbol shows on each key of the keyboard and another CPArray that defines what each key press will insert into the targeted CPTextField when pressed. There's also a keypad mode for fields that only take numbers and you can configure it to accept decimals or only integers or allow negative numbers or not.
I very much enjoy developing in Cappuccino!
anyidea what this error means?
I have the latest version, commit 8570476cff399bc57840aa745d18b48eb3531069
I run the nib2cib command in a folder that is one level up from the Resource folder
Now, I am getting a different error message
failed to delete /tmp/MainMenu.xib.tmp.nib: Operation not permitted
@vasg77_twitter If you’re using Xcode 13+, Cappuccino needs to be patched with https://github.com/cappuccino/cappuccino/pull/3006.patch
@platkus Do you now specifically which old version of Firefox (from the XUL era, perhaps)? After the node work is released, the next step is to accommodate more modern versions of Javascript than we currently do. Internet Explorer is a non-starter, but it would be good to know what Javascript versions people are depending on - for support of async, let, etc.
1 reply
should I do something more?
@vasg77_twitter Have you tried the Node version? It should work with Xcode 13+. You can easily try it without messing up your narwhal version by running the following in the Terminal:
git checkout node
npm install
jake dist
export PATH="$PWD/dist/cappuccino/bin:$PWD/dist/objective-j/bin:$PATH"Check that it finds the correct nib2cib by running which nib2cib. Make sure you have Node version 14 or later installed. (I currently use version 16).
CPBox setBorderColor: the box must be of type CPBoxCustom AND border of type CPLineBorder in order to use setBorderColor. Ignored.
CPBox setCornerRadius: the box must be of type CPBoxCustom AND border of type CPLineBorder in order to use setCornerRadius. Ignored.
CPBox setBorderWidth: the box must be of type CPBoxCustom AND border of type CPLineBorder in order to use setBorderWidth. Ignored.
CPBox setCornerRadius: the box must be of type CPBoxCustom AND border of type CPLineBorder in order to use setCornerRadius. Ignored.
CPBox setBorderWidth: the box must be of type CPBoxCustom AND border of type CPLineBorder in order to use setBorderWidth. Ignored.
I do not know how important these warnings are, but I need to fix them. I hope I want break anything in the code
About the Node version, is it the same with the narwhal? Does the Node version has more features/functionalities than the narwhal version?
Those warnings are not very important. They were added some time ago when @didierkorthoudt added support more variants of the CPBox
Also, I don't think you should think of moving to the Node version is a very "huge change". There is no change at all to the AppKit or the Foundation. So there are no changes to how your app will run against the frameworks. The only change is the tools how we build things like
jake and nib2cib etc. The way they build things are still exactly the same. It is only narwhal that is replaced with Node. What is for example how we read and write a file etc. So code is replace to use Node api instead of Narwhal api. One major thing is also that Node is asynchronous by default. This means that I had to add async / await to the Objective-j syntax to be able to handle some cases in the tools in an elegant way.
A note for anyone planning to upgrade to Monterey next Monday - Xcode 12 is no longer supported as of today’s macOS 12.0.1 release candidate (it’s Xcode 13 or nothing). This shouldn’t present a problem - both Xcode 13 and Monterey have been remarkably stable and reliable since early July. It does mean manually patching
nib2cib though.
I wasn't able to patch the entire file that I download from git, but I had no problem to patch those 5 patches
Am having a look now at checking version information for xibs and offering to upgrade to modern format - as Xcode does on opening old files in IB. Until we can do this, remember to check target version for xibs if
nib2cib fails. I’m hoping this is the last remaining significant source of silent conversion failures.
Dear all,
Well, yet another time, I have to apologize for my silence… September and October were very busy with the university start of the new academic year and the work in the house. Things are calming down now…
I have a question : as some of you may know, I work on my MBP 16’’ i9 with a Cappuccino environment hosted in a Parallels Desktop VM.
I think to buy a brand new MBP M1 Max machine. Does our beloved environment work on this chip ? I may isolate it in a Parallels 17 VM but I may merge the two environment to get extra speed…
Waiting for your input before signing the order ;-)
I’ll be back ! :-)
Didier
Well, yet another time, I have to apologize for my silence… September and October were very busy with the university start of the new academic year and the work in the house. Things are calming down now…
I have a question : as some of you may know, I work on my MBP 16’’ i9 with a Cappuccino environment hosted in a Parallels Desktop VM.
I think to buy a brand new MBP M1 Max machine. Does our beloved environment work on this chip ? I may isolate it in a Parallels 17 VM but I may merge the two environment to get extra speed…
Waiting for your input before signing the order ;-)
I’ll be back ! :-)
Didier
@mrcarlberg Great news ! So it should also work on this new beast !.. I contact immediatly my accounting team 😉 I’m trying to re-equilibrate my life… So it must have some time for Cappuccino 😍 Work in the house is now done for me, time for specialists… I now only have to coordonate teams. I may need some help to create my new environment on the new baby…
@mrcarlberg I also think to organize a CappCon, don’t worry… 😅
You won’t be able to host non-Apple Silicon macOS versions in a VM though.
Asahi Linux is a Debian variant designed for ARM Macs and apparently running minimally on Apple Silicon. Video drivers are the biggest challenge (as one might expect) - it’s not clear if the new M1 variants add extra challenges in that department.
Somewhat disappointed by the absence of a Mac mini Pro announcement Monday.
@didierkorthoudt The Node version is supporting sandboxed versions of Cappuccino that is not installed globally in the
narwhal directory or /usr/local/bin. This is done by introducing the jake dist command. This means you can have an unlimited number of versions at the same time. You can read more about it on the wiki under the title Install from source without install with npm: https://github.com/cappuccino/cappuccino/wiki/node