Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 27 18:59
    ivucica commented #2967
  • Jan 27 18:44
    ivucica commented #2967
  • Jan 27 18:43
    ivucica commented #2967
  • Jan 27 18:16
    ivucica commented #2967
  • Jan 27 15:37
    mrcarlberg commented #2967
  • Jan 27 15:12
    ivucica commented #2967
  • Jan 27 08:03
    didierkorthoudt commented #2970
  • Jan 27 08:03
    didierkorthoudt commented #2969
  • Jan 26 17:05
    cappbot commented #2969
  • Jan 26 17:05
    cappbot commented #2970
  • Jan 26 16:42
    cappbot labeled #2969
  • Jan 26 16:42
    cappbot milestoned #2969
  • Jan 26 16:42
    cappbot milestoned #2970
  • Jan 26 16:42
    cappbot labeled #2970
  • Jan 26 16:36
    cacaodev opened #2970
  • Jan 26 16:31
    cacaodev opened #2969
  • Jan 23 02:03
    yaymakeup starred cappuccino/cappuccino
  • Jan 21 07:26
    felipemeamaral starred cappuccino/cappuccino
  • Jan 21 04:00
    fanyufan starred cappuccino/cappuccino
  • Jan 19 08:03
    mrcarlberg commented #2968
Didier Korthoudt
@didierkorthoudt
@michaelbach #2948 fixes the stepper problem.
Didier Korthoudt
@didierkorthoudt
@enquora I can indeed reproduce your table in a box problem. That’s the positive side of a negative situation… 😉 Will dig on this one.
Shawn Platkus
@platkus
@enquora I’ve come across the need for having client requested string labels in our Mac app. I don’t think localization techniques is the right call here as those strings would need localizations themselves. In our Mac app, there was a specific bike for this OEM and check aged the strings just for that OEM build.
For a Cappuccino app, the approach I would take for just a couple strings would be to special case them in the code. Our Cappuccino app has a JSON file of tags and values that we read in when the application starts up. I have OEM specific values in this JSON file that can be set to tell my application what installation specific options are desired. You could do something similar with a JSON Boolean or string for this client that tells your application to use the alternate strings. You could even embed the alternate strings in this JSON config file and read them from there and set them in code dynamically.
1 reply
cacaodev
@cacaodev
There are also issues with radio buttons. In Tests/Manual/CPRadioBindings you can now select multiple radio buttons and you coud not before the recent merges. An "out of bounds" error is also thrown when you select index 0 in the first popup of second section.
Didier Korthoudt
@didierkorthoudt
@cacaodev I’ve not checked this manual test indeed. This should be a side effect of the modern Cocoa radio buttons management. I’ll have a look ASAP. Thank you for pointing this.
Michael Bach
@michaelbach
@didierkorthoudt: I fixed the steppers according to your PR and they are fine now, great!
I was just going to report the radio button issue, I have it too. There's more: the rotary slider is drawn as a tiny linear slider, not a round disk with indicator. Furthermore, on some buttons (especially when I use some unicode for label) there is an exception as shown in the attached screenshot. Finally, I get an error with array manipulation, also shown in a screenshot.
And I nearly forgot: Sometimes checkboxes stay visually checked, although they transmit their status change correctly to their action functions.
Still, thanks for your immense efforts!
Screenshot 2020-10-29 at 18.25.11.png
Screenshot 2020-10-29 at 18.38.23.png
David Richardson
@enquora
@didierkorthoudt This looks likely to be where the tableview error occurs: https://github.com/cappuccino/cappuccino/blob/e6fe9396f8956447616b0140270249a74ecd6bf2/AppKit/CPTableView.j#L1746
Why your CPBox revisions should trigger it is unclear though.
Didier Korthoudt
@didierkorthoudt
@mrcarlberg Hi Martin ! I’m trying to debug @enquora problem with table in box… It’s a nib2cib problem so difficult to debug. Is there something I could call to trace the call stack ? I’m currently inserting CPLog.info here and there but it would be easier to obtain the full call stack.
Martin Carlberg
@mrcarlberg
@didierkorthoudt You could remove the msgSend inline option by removing the -O2 compiler option in the Jakefile for nib2cib
That will allow you to turn on backtrace decorators by adding the following line somewhere in the nib2cib tool:objj_msgSend_decorate(objj_backtrace_decorator);
Finally you could use objj_backtrace_print(CPLog.warn); to print out the call stack.
Didier Korthoudt
@didierkorthoudt
@mrcarlberg Thank you !
Didier Korthoudt
@didierkorthoudt
@enquora @mrcarlberg This table in a box problem seems (yet another time) related to a non-ready view (the table view). It doesn’t seem to be fully decoded when the box tries to set its own frame, thus setting the table frame also… I continue to dig into this…
I’ll try this with #2917 to see if it’s fixing this problem also…
Didier Korthoudt
@didierkorthoudt
Nope. Would have been too easy…
Didier Korthoudt
@didierkorthoudt
@enquora @mrcarlberg OK, found a fix. Have to test further and clean things…
Martin Carlberg
@mrcarlberg
:thumbsup:
Didier Korthoudt
@didierkorthoudt
@enquora @mrcarlberg #2949 fixes the “table in a box” problem.
@enquora Could you please check that it also works for you ?
David Richardson
@enquora
@didierkorthoudt First test indicates it works. I’ll have a definitive answer Monday morning after full testing
Looking at the fix, one wonders how this worked at all previously
Didier Korthoudt
@didierkorthoudt
@enquora Well, this could be due to many things like, for example, a change in CPBox subviews decoding order… And, yes, I’ve never tested putting a CPTableView inside a CPBox… 😉
Didier Korthoudt
@didierkorthoudt
@mrcarlberg Sorry for #2950 but each time I compile Cappuccino, I say to myself “I’ll fix this warning ASAP”… for about a year !.. So this is now fixed. 😉
daboe01
@daboe01
@didierkorthoudt we really appreciate your endurance with finishing this mammoth task
Didier Korthoudt
@didierkorthoudt
@daboe01 Thank you but it’s only because each time I push a PR, my wife gives me a beer… 😉 Currently working on your buttons title alignment problem...
daboe01
@daboe01
excellent stuff!!
Didier Korthoudt
@didierkorthoudt
@daboe01 It works with Aristo2 but you’ll have to wait for Aristo3 to obtain those windows-like window buttons icons… 😉
David Richardson
@enquora
I presume Travis’ pricing changes affect us. Can anyone comment on the specifics?
Martin Carlberg
@mrcarlberg
@enquora Do you have any info about what "pricing changes" Travis has done?
David Richardson
@enquora
@mrcarlberg As I read it, Travis CI FOSS accounts must now use their new Trial plan, are credited 1,000 minutes, and can ask for more credits when those are exhausted.
David Richardson
@enquora
Also, do we test-build XcodeCapp? I assume so, and Mac costing appears to be more expensive. Although it appears possible to perform only the XcodeCapp portion on Mac infrastructure
David Richardson
@enquora

How many weeks/months would 1,000 minutes last based on historical usage?

The language used in this blog post, combined with the acquisition structure two years ago doesn’t seem promising for unfounded open source projects like this one.

Martin Carlberg
@mrcarlberg
We only test on Linux
Michael Bach
@michaelbach
Linux is good, that's still free. I'm ready to pick up a 15$ tab if it helps.
daboe01
@daboe01
so am i
David Richardson
@enquora

@michaelbach I’m having trouble parsing their statement on pricing. The blog post says 'The pricing change does not affect most Travis CI users who run their builds on public and private repositories using Linux and Windows OS’ but later says pricing changes will apply to those building on public repositiories only, with no qualifiers.

Further, it states pricing changes apply specifically to https://travis-ci.com. What else would they apply to - travis-ci.org ceases to exist in under 60 days?

Some of the other language used is the smarmy sort used when large organizations want to obfuscate and, combined with the buy-out by private equity firms 18 months ago raises red flags.

We can certainly run on donations, but that increases the administrative burden
Didier Korthoudt
@didierkorthoudt
I could donate also…
David Richardson
@enquora
We’ve moved from travis-ci.org to travis-ci.com, correct?
If we were a new project starting out just now, would we pick Travis over Github Actions, or GitLab CI? If so, why?
David Richardson
@enquora
This also raises the question of our execution environment for tests - I presume we’re using Rhino since WebKit isn’t available on Linux? Presumably we’ll see much reduced build times once we move to Node. Are there significant aspects to that transition beyond the ones for normal dev usage?
Martin Carlberg
@mrcarlberg
@enquora We are currently running the tests with Rhino. As you say, WebKit is not available on Linux. I think there are some test cases that must run on Rhino but we could turn those off to make it run on Node.
David Richardson
@enquora
@didierkorthoudt @mrcarlberg Confirming that PR2949, while already merged and closed, has been more extensively tested here and does fully solve the problem of tables in boxes. I’m still left wondering how that code worked at all previously! And how many other places we have improperly or incompletely initialization. For recall when weird behaviour appears in the future.
I’m not displeased with default buttons’ increased corner radii - it is a welcome visual distinction from popup buttons.
David Richardson
@enquora
@mrcarlberg Is it reasonable then, to write XcodeCapp tests in Xcode, include them in repo, and assume anyone reviewing prior to commit will run them manually on their own machine? There is flaky behaviour in XcodeCapp’s listener interactions with the filesystem that seems worse in Catalina and Big Sur. I have a few more general cleanup items but need to look at that problem soon.
Martin Carlberg
@mrcarlberg
@enquora Great that you find #2949 to be working. Regarding test cases for XcodeCapp, please do test cases and include them into the Xcode project. As you say they have to be run manually but it is always good to have test cases. And things might change so we can run them automatically in the future.