Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 15 15:08
    deiviuds starred cappuccino/cappuccino
  • Jan 14 18:55
    cappbot commented #2877
  • Jan 14 18:55
    cappbot labeled #2877
  • Jan 14 18:55
    cappbot labeled #2877
  • Jan 14 18:55
    cappbot unlabeled #2877
  • Jan 14 18:27
    daboe01 commented #2877
  • Jan 13 13:05
    kuanyui starred cappuccino/cappuccino
  • Jan 13 06:16
    cappbot commented #2883
  • Jan 13 06:16
    cappbot labeled #2883
  • Jan 13 06:16
    cappbot labeled #2883
  • Jan 13 06:16
    cappbot unlabeled #2883
  • Jan 13 06:16
    cappbot commented #2884
  • Jan 13 06:16
    cappbot unlabeled #2884
  • Jan 13 06:16
    cappbot labeled #2884
  • Jan 13 05:50
    daboe01 commented #2884
  • Jan 13 05:49
    daboe01 commented #2883
  • Jan 12 16:08
    daboe01 synchronize #2884
  • Jan 12 08:24
    Letterus starred cappuccino/cappuccino
  • Jan 11 15:04
    daboe01 closed #2869
  • Jan 11 15:04
    daboe01 commented #2869
Martin Carlberg
@mrcarlberg
Do I understand you correctly that the module initialization will load the around 12 cibs and it takes more than 12 seconds? It sound like a very long time.
David Richardson
@enquora
@mrcarlberg That’s correct. I need to take another look at the code - what profiling methods are available for Objective-J?
Martin Carlberg
@mrcarlberg
The best profiling method is the browser. I usually use Chrome when debugging but Safari will also work. Have not used Firefox for debugging for a while but I guess it is ok too. Start from your index-debug.html to get good method names. Open the Developer tools and choose the Performance tab. Press start when you want to start recording and stop when done to look at the result. Very convenient tool.
jasperdeb
@jasperdeb
@daboe01 Concerning the attachment support in CPTextView. I mentioned before that I would like to have support for the CALayer in the PR we worked on together. I managed to make some view based on CALayer to resize and crop an image (see working work as is in movie above). I would love to incorporate this into CPTextView. Any idea to add this support for CALayer?
Didier Korthoudt
@didierkorthoudt
😄 Found another Cocoa rift in the space-time continuum : if you display a calendar with a clock, there’s no AM-PM indicator. If you only display the clock, the AM-PM indicator appears… I suggest that I stay away from this “who could explain this ?” behavior… 😉 (and, of course, always display the AM-PM indicator)
Didier Korthoudt
@didierkorthoudt
BTW, this is corrected in Catalina
Didier Korthoudt
@didierkorthoudt
Well, in fact, I should always check in Catalina as they have adapted many things… For example, there’s now a disabled state for the calendar (slightly different from what I’ve done, but I can easily adapt) and for textfield date picker.
daboe01
@daboe01

@daboe01 Concerning the attachment support in CPTextView. I mentioned before that I would like to have support for the CALayer in the PR we worked on together. I managed to make some view based on CALayer to resize and crop an image (see working work as is in movie above). I would love to incorporate this into CPTextView. Any idea to add this support for CALayer?

can you provide a demo app with your CALayer view embedded into a CPTextView?

jasperdeb
@jasperdeb
@daboe01 I will provide the app somewhere this week. First some cleaning up needed of the code ...
Martin Carlberg
@mrcarlberg
@didierkorthoudt Looking forward to test your improved date picker component. Will we be able to merged in this as a separate pull request?
Also I have merged in the speed improvements on changing the size of a view. This will make resizing the browser window or resizing a split view much faster. It will also improve the speed on view setup so our apps will feel a little bit snappier now :wink:
Martin Carlberg
@mrcarlberg
Please test it and let us know if you find any odd behaviors.
daboe01
@daboe01
@mrcarlberg cool! thank you! i will put this into production asap.
Didier Korthoudt
@didierkorthoudt
@mrcarlberg OK, I’ll isolate the new date picker in a specific PR. I’m fighting with the clock right now (last part of the date picker).
daboe01
@daboe01
just did jake install on my new MBP16". 38 secs :-)
Martin Carlberg
@mrcarlberg
@daboe01 That is fast... :smiley:
Didier Korthoudt
@didierkorthoudt
@daboe01 Still waiting mine !.. 😢
Martin Carlberg
@mrcarlberg
I'm still on my 2018 MacBook Pro. Takes about 60 seconds to do a jake install on Cappuccino. :smiley:
@didierkorthoudt Can you check if my suggestion on #2876 is something we could do or if we should merge it as it is.
Didier Korthoudt
@didierkorthoudt
@mrcarlberg Ooops ! Sorry, didn’t see it. OK, I’ll check this ASAP.
David Richardson
@enquora
@mrcarlberg Turns out including a local copy of CPView.j to test modifications before commiting to Cappuccino doesn’t work - @imports break. Testing as a category is the most practical workflow
Martin Carlberg
@mrcarlberg
@enquora Yes, testing as a category is usually the best way. This is what I try to do. But CPView can be tricky as some preprocessor directives like #if PLATFORM(DOM) might not work as some macros are not defined when compiling in the browser. Try to remove them from the category if they are not working.
daboe01
@daboe01
@mrcarlberg your tracking area improvements are a big win! interestinly, also seem to fix #2869
thx!!
Martin Carlberg
@mrcarlberg
Awesome that it fixes other problems too. Our application feels a lot snappier now with these speed ups :smile:
Didier Korthoudt
@didierkorthoudt
@mrcarlberg @daboe01 Can’t wait to test this ! But right now, I’m transferring my MBP to my brand new MBP 16’´ 😉😊
Martin Carlberg
@mrcarlberg
Wow! New toys are always fun :smile:
daboe01
@daboe01

Awesome that it fixes other problems too. Our application feels a lot snappier now with these speed ups :smile:

it seems also to boost startup-time substantially in my main application. super awesome :-)

Martin Carlberg
@mrcarlberg
Yes, everything that has to do with initialization or change of the size of views has got a substantial speed up. 😀
David Richardson
@enquora
@didierkorthoudt Do you notice Catalina's performance problems on your 16” MBP? Xcode 11’s?
Didier Korthoudt
@didierkorthoudt
@enquora Well, no but my dev OS is virtualized with Parallels... This machine rocks but loves to spin fans !
David Richardson
@enquora
Do you mean you wiped the machine clean when you received it and installed an earlier version of macOS?
I’m wondering if the root problem with Catalina and Xcode 11 is an unwillingness on Apple’s part to make it run acceptably on the lowest spec machines they sell.
Someone from the Xcode team has already said as much.
Even though it’s a fool’s errand for developers to isolate themselves from familiarity with entry-level machines.
Didier Korthoudt
@didierkorthoudt
@enquora Nope, my primary OS is Catalina but as I wanted to stabilize my Capp dev environment, I’ve virtualized it (High Sierra) to run under my work environment. I’ve tried VMWare Fusion but Parallels Desktop is better at running OSX under OSX...
David Richardson
@enquora
I’m debating what to do about Catalina/Xcode 11 and curious if the most recently spec’ed machines are fast enough to gloss over the underlying architectural problems. Unfortunately the Mac Mini team seems to have gone into hibernation again, the economics of the Mac Pro don’t work, there are no visually matching monitors for the iMac range (and a single display is a non-starter) and a laptop is both poor economics and ergonomics. I’m leaning heavily to a Ryzen Hackintosh (while it’s still possible)
Didier Korthoudt
@didierkorthoudt
@enquora Well, I’m not your guy as I find the MBP 16´´ à killer machine... The only thing I have to regret is that fans are waking up early...
David Richardson
@enquora
It’s mostly the performance of Catalina/Xcode 11 I’m curious about, whether the very latest hardware is fast enough to make the underlying software’s egriously erratic performance just a nuissance rather than a serious problem. I’m skeptical though because my iPhone experiences the same problems -— we’re likely stuck with them until one or two more years have passed and Apple has cleaned up its development act.
daboe01
@daboe01
@enquora i am mostly using the xcode 11 editor an do not see any performance issues, neither on MBP16 nor on mac pro 2013
David Richardson
@enquora
The editor is fine. It’s the compilers and entire build process which are shaky. SwiftUI previews are dreadful.
@daboe01 Written on iPhone as I wait for my machine to reboot after another kernel panic. Well over three dozen now under Catalina
The Xcode editor is mostly a joy to use
daboe01
@daboe01
@enquora i can feel you pain. lucky that most apps perform autosaving these days
leeharveyosmond
@leeharveyosmond

Hi folks
pardon me if this is known issue, I have Googled and not found anything.
I'm working on a colleague's project, it has OJTest-based tests.

I'm picking over the OJUnit source, because I am finding is that a test method may contain multiple assert... messages, if an assertion fails (a test fails) then this is reported via throwing an exception. This means that after the assertion has failed, flow of control doesn't return to the test method.

This isn't what I expect from unit test frameworks in other environments. This behaviour doesn't appear to be documented either. Have I missed something?

leeharveyosmond
@leeharveyosmond
Also: a general observation, I'm using Xcode 10.2 on OSX 10.14.6 . I tried to reorganize the Cappuccino-based project on which I am working to have more than one target, to build a framework, and then to build and run the corresponding unit tests. This project was created with a much older version of Xcode. Current Xcode seems to have very poor support for editing and managing targets of type "external build system" compared to older versions
Martin Carlberg
@mrcarlberg
@leeharveyosmond Yes, the assertion in OJTest will throw an exception if it fails and stop. This is different from for example XCTest in Apples environment that will throw an exception, log it and continue.
Using the build system in Xcode is an interesting approach but something that I have never tried. We have a separate bash script that builds our application with all the frameworks and cib files when we install.
When developing I let the browser compile all our frameworks when loading the application.