Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:26
    didierkorthoudt commented #2877
  • 16:24
    didierkorthoudt synchronize #2877
  • 16:18
    didierkorthoudt commented #2877
  • 16:04
    didierkorthoudt synchronize #2877
  • 13:16
    daboe01 synchronize #2877
  • 13:13
    daboe01 synchronize #2877
  • Dec 13 13:46
    kerusan commented #2877
  • Dec 13 13:22
    kerusan commented #2877
  • Dec 13 06:59
    daboe01 closed #1646
  • Dec 13 06:59
    daboe01 commented #1646
  • Dec 13 02:27
    AAChartModel starred cappuccino/cappuccino
  • Dec 12 19:51
    daboe01 reopened #1646
  • Dec 12 19:51
    daboe01 commented #1646
  • Dec 12 19:17
    jasperdeb commented #2872
  • Dec 12 18:33
    daboe01 synchronize #2877
  • Dec 12 13:25
    kerusan commented #2877
  • Dec 12 10:08
    mrcarlberg commented #2877
  • Dec 12 09:23
    kerusan commented #2877
  • Dec 12 08:26
    daboe01 commented #2872
  • Dec 11 21:38
    jasperdeb commented #2872
Martin Carlberg
@mrcarlberg
On CPView the setFrame: method will call the setFrameSize:method. The later will call setFrame: on all it's subviews. It will travel down the view hierarchy on all the subviews. Each setFrame: method will update the tracking areas. Each update on the tracking areas will travel down the view hierarchy on all the subviews. So the tracking areas will be updated many many times.
I just do it once. :smile:
I will prepare a pull request that you can review.
Didier Korthoudt
@didierkorthoudt
😃👍🏻 Waiting to see this !.. 😊
Martin Carlberg
@mrcarlberg
And I also have a nice speedup on tracking areas when the visibleRect calculations are done when traveling down the view hierarchy.
David Richardson
@enquora
I’m adding missing methods to CPView and want (initially) to edit/test in an existing app without recompiling Cappuccino with every change. In the past I’ve simply imported an app-local version of the Cappuccino file. Is it possible to use an app-local version which contains only the additions/changes (CPView is quite large)?
aksuska
@aksuska
@enquora Use a category?
David Richardson
@enquora
I was about to mention ‘without using a category’ ;-) I want to keep the source and addition files’ contexts the same. It isn’t a huge problem keeping a full app-local version though — it’s just that the source is rather long.
Martin Carlberg
@mrcarlberg
@enquora I usually use a category just like @aksuska says.
David Richardson
@enquora
As a related question, what editors are people using? And tools for code formatting. Navigation in long Cappuccino files is the problem. Xcode is the only editor I know of which makes use of the pragma marks
Didier Korthoudt
@didierkorthoudt
@enquora I use Xcode... 😊
David Richardson
@enquora
@didierkorthoudt We can’t reformat using it though ;-) At least until I complete that syntax definition :-( I, too, use Xcode sometimes just for code review. When Xcode 11 isn’t sulking and refusing to go to work (which is still all too often, even with 11.3). Perhaps I’m the target market for the new Mac Pro
I’m tempted to build an AMD Ryzen Hackintosh just for Xcode 11
aksuska
@aksuska
I use BBEdit with a home-grown language module. This gives me function popup and syntax coloring perks, but it doesn't do pragma marks for custom languages "out of the box", however, but you can mimic it in a couple ways.
How do you get Xcode to work? I tried it a while ago and it couldn't grok the syntax...
David Richardson
@enquora
Work? As in syntax highlighting and code folding? Select Objective-C — it’s what @didierkorthoudt does :-)
Martin Carlberg
@mrcarlberg
@enquora I use Xcode and Sublime Text
Both handle pragmamarks
And I use Sublime Merge as a git client
David Richardson
@enquora
@aksuska It’s still possible to write one’s own syntax definition without running afoul of code signing. I’ve had a work-in-progress for more than a year :-(
Haven’t tried Sublime Text for several years. I couldn’t get over the non-native look (as with VS Code)
Martin Carlberg
@mrcarlberg
I have tried all editors out there and Sublime Text was the one that I liked the most.
David Richardson
@enquora
I love the Xcode 10+ editor. Xcode 11 has been nothing but grief though - SwiftUI Preview regularly kills performance of my entire OS until a reboot and cleanup of ~/Library/Developer
Martin Carlberg
@mrcarlberg
Yes, Xcode 10+ editor is very nice. I use that a lot too.
Have not yet made the switch to Xcode 11
David Richardson
@enquora
I’ve come to believe one of the reasons Catalina is so rough is development is dependent on Xcode 11, which is a year away from being ready for prime time
Martin Carlberg
@mrcarlberg
Could be! I'm staying away from Catalina too
:smile:
David Richardson
@enquora
@mrcarlberg If one doesn’t need SwiftUI, I’d stay away from both until at least the next point release
aksuska
@aksuska
@enquora IIRC, "work" as in function/method popup. I think it would simply fail to recognize the existence of methods if it came across some not-so-objective-c-looking code.
David Richardson
@enquora
@mrcarlberg While you’re still around, can you provide a quick refressher on NSView vs Cappuccino? There was a discussion some time ago but I don’t remember the details. The SourceList framework I’m porting uses NSCell and associated compositing methods/constants which don’t seem to be available in Cappuccino. I had hoped to avoid grokking the code completely from entry point onwards but that is what I’m faced with doing now
@aksuska Yes, that requires a language-specific definition. Can be done although it’s nowhere documented. And needs to be added to Xcode itself each time it’s updated. The extension mechanisms which once existed are no longer supported. It is possible though.
Xcode is working towards Language Server Protocol definitions (for everything, I presume, rather than just Swift and Objective-C). Not much public progress since this announced last year though
Martin Carlberg
@mrcarlberg
@enquora Some views in Cocoa uses a cell below the actual view. I guess you can call a cell a light weight view. It was needed 30 years ago when the CPUs where slower and it was expensive to handle a view. Cappuccino does not implement cells. All the functionality is in the view itself.
David Richardson
@enquora
Thanks. That helps understand things conceptually. It is likely a matter of porting drawing methods one-by-one. I’m currently running jake debug in the test app and dealing with missing method errors as they appear.
It’s tedious but I don’t know of a better approach. I had thought the work would be in porting the datasource this framework provides rather than drawing the outline.
Didier Korthoudt
@didierkorthoudt
Well, I also have problems with Xcode 11, so I use Xcode 10.1 under High Sierra (in a Parallel VM, which is almost OK but the GitHub Desktop client. Was under VMWare Fusion but Parallel is better and speedier for what I can see). I also use the “exported UTIs” trick to have automatically Objective-C syntax treatment for Objective-J file… Works like a charm… I won’t consider upgrade to Catalina and Xcode 11 before finishing Aristo3 (my guest OS is Catalina)
Didier Korthoudt
@didierkorthoudt
@mrcarlberg I’ve just downloaded Sublime Merge and it seems very cool !.. (no problem being in a VM !)
David Richardson
@enquora
@didierkorthoudt High Sierra is my backup configuration, on a separate machine. My gut GUI is Fork
daboe01
@daboe01
i am on catalina and have no issues with Xcode so far. using only the text editor though.
David Richardson
@enquora
@daboe01 xcrun has serious problems with the new filesystem layout. It’s capable of introducing orders of magnitude increases in I/O latency. It is the mechanism which dynamically resolves the tools instance being used (as specified by Xcode-select). I you don’t do anything which invokes the toolchain you won’t see it. You also have a much faster machine!
David Richardson
@enquora
The Swift compiler has always been lethargic, but SwiftUI Previews seems to have been designed with the assumption of zero latency. It uses a simulator, which has always taken forever to launch. There seems to be no supervisory co-ordinating process worth the name and the simulator or preview task is forever crashing.
And, Xcode 11 seems to have forgotten how to perform incremental builds, expecially for Objective-C. Those are starting to look more like the coffee breaks Swift builds can be.
David Richardson
@enquora
Xcode’s editor is shaping up to be a very nice tool. The toolchain is a mess at the moment.
Kjell Nilsson
@kerusan
@daboe01 I'm sorry to have suggested bezel-color on the textView. When I look at NSTextView they have not a bezel style as NSTextField have. So after a short discussion with @mrcarlberg we have agreed that the attribute should be named "background-color" instead. This should also been better for the CPTextField, who uses bezel-color. But we leave that for now.
@daboe01 We also need a "content-inset" since now the Text starts exactly where the bezel ends on the left side.
Kjell Nilsson
@kerusan
image.png
daboe01
@daboe01
@kerusan we are lucky to have the support of expert @didierkorthoudt :-)
Didier Korthoudt
@didierkorthoudt
@kerusan Hi Kjell ! Funny as I made the same remark about bezel/background attribute name. I’m working on this right now with @daboe01 :-)
Didier Korthoudt
@didierkorthoudt
@daboe01 Just saw you did modifications I’ve also done here… 😄