Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 30 15:48
    aparajita closed #1853
  • Jan 30 15:48
    aparajita closed #1843
  • Jan 30 15:48
    aparajita closed #1490
  • Jan 30 15:47
    aparajita closed #1730
  • Jan 28 03:11
    taoeffect starred cappuccino/cappuccino
  • Jan 22 10:16
    deuchainn starred cappuccino/cappuccino
  • Jan 18 13:07
    mrcarlberg updated the wiki
  • Jan 17 14:50
    mrcarlberg updated the wiki
  • Jan 17 14:48
    mrcarlberg updated the wiki
  • Jan 17 14:40
    mrcarlberg updated the wiki
  • Jan 09 12:17
    zetasq starred cappuccino/cappuccino
  • Dec 27 2022 09:05
    yadex205 starred cappuccino/cappuccino
  • Dec 18 2022 12:22
    ulysses-ck starred cappuccino/cappuccino
  • Dec 12 2022 21:32
    cappbot commented #3049
  • Dec 12 2022 21:07
    enquora edited #3049
  • Dec 12 2022 21:05
    cappbot milestoned #3049
  • Dec 12 2022 21:05
    cappbot labeled #3049
  • Dec 12 2022 21:04
    enquora opened #3049
  • Dec 12 2022 09:57

    mrcarlberg on aristo3

    Revert "Fixed: Before this PR, … Fixed: Allow space in path to .… Fixed: å and Å did not work wel… and 21 more (compare)

  • Dec 12 2022 09:56

    mrcarlberg on node

    Revert "Fixed: Before this PR, … Fixed: å and Å did not work wel… FIXED: CPLikePredicateOperatorT… and 1 more (compare)

Shawn Platkus
@platkus
@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!
Vasilis Gkanis
@vasg77_twitter
hi
Vasilis Gkanis
@vasg77_twitter
I am trying to run nib2cib on a xib file, and I am getting an error message about not being able to find the bundle
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
Vasilis Gkanis
@vasg77_twitter
and Could not convert to xml plist for file:....
David Richardson
@enquora
@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
Vasilis Gkanis
@vasg77_twitter
@enquora I am using Xcode 13+, I will try to apply this patch. Thank you
Vasilis Gkanis
@vasg77_twitter
@enquora same error. After I applied the patch, I run the bootstrap.sh and then jake install
should I do something more?
Vasilis Gkanis
@vasg77_twitter
it is working!!! I need to set the build for to "macOS 10.11 and later"
Martin Carlberg
@mrcarlberg

@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).

Vasilis Gkanis
@vasg77_twitter
@mrcarlberg no I have not. Frankly, I hesitate to make such a huge change. I run the new jake on my code, and I got the following warnings:
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.
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?
Martin Carlberg
@mrcarlberg
It is the same version.
The Node version has support for async / await syntax but is otherwise the same as latest master. We have move over to running 100% Node now in our project.
Those warnings are not very important. They were added some time ago when @didierkorthoudt added support more variants of the CPBox
Martin Carlberg
@mrcarlberg
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.
Vasilis Gkanis
@vasg77_twitter
I read that the node code is an alpha version. Is it stable?
Martin Carlberg
@mrcarlberg
Yes, it is an alpha version as not all tools are converted yet. As soon as all needed tools are working under Node it will go to a beta version. I don’t know if we should call it stable or not but it is working for us. We will never go back to the narwhal version.
David Richardson
@enquora
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.
Vasilis Gkanis
@vasg77_twitter
A note to those who will manually partch the nib2cib file, once you download the patch file, create 5 ( if i remember correctly) patches from that one. Each patch starts with "From.... "
I wasn't able to patch the entire file that I download from git, but I had no problem to patch those 5 patches
daboe01
@daboe01
@enquora shouldn't we merge your patch into the official HEAD?
Martin Carlberg
@mrcarlberg
@daboe01 The pull request #3006 is now merged into the master branch :smile:
Michael Bach
@michaelbach
@mrcarlberg + All: that's GREAT! It would be a pity if the master were in a non-working condition for current MacOS environments for any prolonged time.
David Richardson
@enquora
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.
Didier Korthoudt
@didierkorthoudt
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
Martin Carlberg
@mrcarlberg
Nice to hear from you Didier! I have ordered a new 16” M1 Max. I will get it next week I hope. 😃 I will make sure that our environment will work on it. I have already tested it on a 13” M1 and MacMini M1 and it works great.
Didier Korthoudt
@didierkorthoudt
@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… 😅
Martin Carlberg
@mrcarlberg
Woohoo 😀
David Richardson
@enquora
@didierkorthoudt Someone here was part of the hardware transition kit/program last year - apparently successfully (no written complaints, at least). And no reason why anything should not work.
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.
David Richardson
@enquora
I’ve just updated my main macOS instance to Monterey. Means no access to Xcode 12 unless I set up a Big Sur VM
Somewhat disappointed by the absence of a Mac mini Pro announcement Monday.
daboe01
@daboe01
@didierkorthoudt welcome back!
Didier Korthoudt
@didierkorthoudt
@daboe01 Thank you ! I hope this is the last (too long) break ! I still remember I have some little things to finish… ;-)
Michael Bach
@michaelbach
;-)
Martin Carlberg
@mrcarlberg
@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
Didier Korthoudt
@didierkorthoudt
@mrcarlberg Thank you ! This should help me merging day-to-day working environment and Cappuccino dev environment. My future M1 MBP is now ordered and I’m now waiting for it… 😉
Didier Korthoudt
@didierkorthoudt
@mrcarlberg How this copes with capp_env ? Which method should I use ?
Didier Korthoudt
@didierkorthoudt

@mrcarlberg Trying the pointed info on the wiki, I’ve followed the installation instructions and, when trying capp gen HelloWorld, I get the following error :

                        throw new Error("Could not load file at " + aURL + (compilingFileUrl ? " when compiling " + compilingFileUrl : "") + "\nwith includeURLs: " + StaticResource.includeURLs());

Any idea why ?
This is tried on my current system, just to be sure it could work on the future M1Max MBP…