cappuccino/cappuccino

Web Application Framework in JavaScript and Objective-J

Vasilis Gkanis

@vasg77_twitter

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…

Vasilis Gkanis

@vasg77_twitter

Is something wrong with the CPButton class? I can not longer add an image to a button.

I examine the html code, and the img tag is missing

Vasilis Gkanis

@vasg77_twitter

I found the problem with the image

The following code does not work

[button setImage:image];
[button setBordered:NO];

but, if I reverse the order, it works!!

Now, can I also set the title of button when I am using an image as background?

I tried to setTitle after I have set the image, but in vain

Martin Carlberg

@mrcarlberg

@didierkorthoudt you should have more lines from that error? The result of this line should be somewhere later in the console?

Didier Korthoudt

@didierkorthoudt

@vasg77_twitter I’ll have a look ASAP

Didier Korthoudt

@didierkorthoudt

@mrcarlberg Here is the complete trace :

sgi-mac20:~ u029386$ capp gen HelloWorld
/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3946
                        throw new Error("Could not load file at " + aURL + (compilingFileUrl ? " when compiling " + compilingFileUrl : "") + "\nwith includeURLs: " + StaticResource.includeURLs());
                        ^

Error: Could not load file at file:/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/dist/cappuccino/lib/capp/main.j
with includeURLs: /Users/u029386/Frameworks/,/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/dist/cappuccino/Frameworks/
    at completed (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3946:31)
    at resolveResourceComponents (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3490:24)
    at Array.<anonymous> (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3487:21)
    at EventDispatcher.dispatchEvent (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:730:50)
    at resolveStaticResource (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3151:36)
    at onfailure (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:3199:17)
    at EventDispatcher.dispatchEvent (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:733:13)
    at determineAndDispatchHTTPRequestEvents (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:973:29)
    at XMLHttpRequest.CFHTTPRequest._stateChangeHandler [as onreadystatechange] (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/@objj/runtime/lib/objective-j.js:800:13)
    at Immediate.<anonymous> (/Users/u029386/.npm/lib/node_modules/@objj/cappuccino/node_modules/xmlhttprequest-ssl/lib/XMLHttpRequest.js:628:53)

David Richardson

@enquora

Safari 15 has broken disclosure indicators, at least in CPOutlineView. They are stuck closed. This is using macOS 12, second release candidate.

Anyone using the Safari 15 preview under Big Sur who can test?

David Richardson

@enquora

The mainMenuBar object is not available in the AppController’s awakeFromCib method. Is this expected behaviour or a bug in our application setup and loading cycle? If expected, can anyone explain why it isn’t availbe even though the cib is finished loading at this point?

Martin Carlberg

@mrcarlberg

@enquora I don't see any reason why the main menu bar should not be available at awakeFromCib:

@didierkorthoudt I will take a look why this is happening with your Node version.

enquora

@enquora:matrix.org

[m]

I don’t either. Nevertheless, it is nil. When hiding it, it’s necessary to do so in applicationDidFinishLaunching. I haven’t checked behaviour in an Objective-C app, but this smells like a bug. Which may be causing other problems too. It also looks confusing to newcomers to set the window to full browser size in awakeFromCib, but to hide the app menu in applicationDidFinishLaunching!

Martin Carlberg

@mrcarlberg

@enquora A quick check in CPMenu.j:

- (void)awakeFromCib
{
    if (_name === @"_CPMainMenu")
    {
        [self _setMenuName:@"CPMainMenu"];
        [CPMenu setMenuBarVisible:YES];
    }
}

This means that the mainMenu is set in awakeFromCib:. I think this is a bug as I should already be set when awakeFromCib: methods are called. Your awakeFromCib: is called before this one is but it could have been called after. There is not order on when they are called.

Where communities thrive

People

Repo info

Activity