Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 26 21:34
    cboulanger commented #10102
  • Jan 26 20:04
    hkollmann review_requested #800
  • Jan 26 20:04
    hkollmann review_requested #800
  • Jan 26 20:04
    hkollmann opened #800
  • Jan 26 19:15
    johnspackman commented #10102
  • Jan 26 18:37
    hkollmann synchronize #10102
  • Jan 26 18:37
    hkollmann commented #10102
  • Jan 26 18:36
    hkollmann labeled #10102
  • Jan 26 18:36
    hkollmann labeled #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann review_requested #10102
  • Jan 26 18:36
    hkollmann opened #10102
  • Jan 26 09:13

    github-actions[bot] on gh-pages

    deploy: 4b43c6b6cd6511cc7096112… (compare)

  • Jan 26 09:09

    hkollmann on master

    this.argv.showStartpage could b… (compare)

  • Jan 26 09:09
    hkollmann closed #799
  • Jan 26 07:16
    johnspackman synchronize #799
Christian Boulanger
@cboulanger
Oh I see - @sqville you have to npx qx pkg publish it first.
Otherwise, it is recorded as a package, but with no releases.
Derrell Lipman
@derrell

How do you guys do enums? I am trying setting an object to my class statics but I have a problem referring to it in my check of the properties. Here is an example
of what I mean https://tinyurl.com/y5udhbj5
Generally, is there any preferred pattern to do enums with qooxdoo?

@voger There are a number of ways to write a check. One is to provide an array of values, as you're trying to do there, but it's not run as a function. I think it's hard-coded at compile time, or something equivalent that prevents use of class names and this. The best alternative is to have check be a function that takes in the value being set, and returns true of false based on whether the value is allowed. That function has access to class names and this.

That said, keep in mind that check is only used in the debug version of your app, not in the typical full build/deploy for production. What you want to use instead is validate. here's an example: https://tinyurl.com/yxs8dowr

(I have no idea what the "unrecoverable internal error" is that appears when first loaded. The application is running properly and can be rerun thereafter without any error.)

Christian Boulanger
@cboulanger
@derrell I didn't know that check is only active when qx.debug is on. Is that documented?
"Due to performance optimization, we strip these checks for the build version. If you want a property validation, take a look at the validation section defining_properties.md#validation_incoming_values."
I'm actually not sure that it's qx.debug-related, but somehow those checks get stripped.
Christian Boulanger
@cboulanger
@derrell Thanks, after all these years of qooxdoo development I wasn't aware about this basic thing, good to know! So the check key is really not suitable to check runtime values (I always wondered about the additional validatekey), but only for type checking during development.
Althought I wonder whether the performance hit of the check is really still relevant in modern browsers. This type of optimization was put into place in the late 2000s when the browsers were really slow.
Derrell Lipman
@derrell
Agree. We may want to rethink it, and having an environment key that dictates whether check is enabled at runtime. (nodejs qooxdoo apps can run on low-end Raspberry Pi-type devices, so we can still encounter low-performance computers.)
SQville
@sqville
@cboulanger @vinidiktov Thanks! i'll publish today
voger
@voger
@derrell thanks. I know that check is used only in development. I wanted to do it that way mostly as a means to document in code my intentions. Also I am very curious if there is a preferred way in qooxdoo community to do enums.
Derrell Lipman
@derrell
@voger I do enums as a map in statics, like you did.
voger
@voger
Thanks. I will keep it that way then.
SQville
@sqville
@cboulanger Okay, I think I did it right. Tags are all on and I have a release out.
... more libraries to come :-)
Christian Boulanger
@cboulanger
@sqville It has been picked up by the package browser, but unfortunately there were compilation problems: https://qooxdoo.org/qxl.packagebrowser/qxl.packagebrowser/#sqville~ville.Clean~problems
Alexei Vinidiktov
@vinidiktov

@sqville It has been picked up by the package browser, but unfortunately there were compilation problems: https://qooxdoo.org/qxl.packagebrowser/qxl.packagebrowser/#sqville~ville.Clean~problems

I had similar error messages when compiling my app recently after cloning my repo to another location.

It turned out that some folders had incorrect casing.

I'm not sure it's the same issue but I thought it might be,

Alexei Vinidiktov
@vinidiktov
Well, I've installed the Clean theme package, and the source/class/widgetbrowser folder is empty.
Alexei Vinidiktov
@vinidiktov
vocabilis_clean_1.png
I've installed the Clean theme in my unfinished app, and it looks really nice.
vocabilis_clean_2.png
vocabilis_clean_4.png
vocabilis_clean_5.png
vocabilis_clean_3.png
Fritz Zaucker
@zaucker
👍🏻
SQville
@sqville
@vinidiktov Alexi, your awesome man. Thank you for testing and sharing. Sorry, everyone for the miss. I corrected and my fingers are back to crossed.
@cboulanger Do i need to do a second release in order for the widgetbrowser to show?
Christian Boulanger
@cboulanger
@sqville Yes, you have to make a realease for any code change. Unfortunately, because of the approval process and the fact that the package browser is rebuilt in a nightly cron job, a release might take a day or more to make it to the package browser. I am thinking about ways to make this process faster.
SQville
@sqville
@cboulanger done. Thanks!
Christian Boulanger
@cboulanger
@/all We now have a status page for qooxdoo packages in addition to the Package Browser. The status page shows which versions are available for npx qx update and is more up-to-date than the Package Browser which is usually only rebuilt once every 24 hours.
Fritz Zaucker
@zaucker
👍🏻
adax
@adax
Hi, http://qooxdoo.org/qxl.demobrowser/# does not show any demo
Christian Boulanger
@cboulanger
@adax You are right- thanks for reporting
SQville
@sqville
@cboulanger Excellent!
Dmitry Zolotov
@goldim
Hello and good day, just updated qooxdoo package. The problem with es6 which i mentioned here was solved. Don't know what you did but thank you so much. Also got problem with a scroller widget, noticed it in my app. In doc getWidth( init value is null) and in older version I checked null too. But new current build gives me value 0. May support example from playground if wanna see. I used before this year the next build - 20200515-0957.
John Spackman
@johnspackman
@goldim re: scroller - that’s a recent commit which was reversing a regression; the idea is that the scroller width is 0, meaning that is it’s minimum size. Normally, your scroller would be stretched to the container (eg either because the container has a qx.ui.layout.Grow, or it’s a HBox/VBox and the scroller is added with { flex: 1}). Please do a playground example and ill take a look
Dmitry Zolotov
@goldim
@johnspackman yes it is stretched now. I used a scroller for difficult button menu. I didn't setup options for the scroller I mean I didn't care what layout it includes. Example: https://tinyurl.com/yxmq4u99
John Spackman
@johnspackman
what’s happening is that the outer container (eg getRoot()) will try and distribute space to it’s children (eg p and p2) according to the rules you give it, and also taking into account what the widget says that it needs. When a widget has width of null, then the widget will assume the width of all of it’s children; this causes it’s parent (getRoot()) to think that is what the widget needs and therefore will try to allocate that space, at the expense of other widgets which do not have a width. But the issue is that, as a scroller, it is supposed to have scroll bars and specifically not try to force it’s width beyond what the container would normally give it - this is how it worked in v5, and the regression was that the width was set to null which caused the scroller to demand more space
Dmitry Zolotov
@goldim
@johnspackman I got it, thank you. Imho how it worked in v5 was more obvious for users. A scroller like a candy wrapper it doesn't change size of candy. But anyway if new approach is right I have to make changes. I thought it was a bug.
John Spackman
@johnspackman
i think what the current 6.0.0 release does is the same as v5? I hope so anyway, that was why we thought it was a regression
Dmitry Zolotov
@goldim
@johnspackman I moved to v6.0.0 a long ago and can't say tbh how it was in v5.
Dmitry Zolotov
@goldim
I would like add Russian language (locale file .po) for qooxdoo making PR. Not difficult for me. what u think about it? don't u mind? I know I can add translation for text of framework widgets in my project defining specific id.
John Spackman
@johnspackman
That would be great, yes please :+1:
Dmitry Zolotov
@goldim
@johnspackman one problem maybe I've seen somewhere in the widget browser or demos where flags of countries supported languages were and demonstration of changing lang. Then I have to change this thing too.
John Spackman
@johnspackman
i can’t think where that is - i’ve just had a quick look in the demo browser and widget browser, and they just use the language for the browser. But I would imagine that if there is something that lets you change language on the fly, that I just auto-detects the list of languages? So from your point of view, you would translate one of the .po files into ru.po, and if you recompile the widgetbrowser/demobrowser locally it should just start using it.
Dmitry Zolotov
@goldim
@johnspackman maybe it was just removed. I certainly remember it was. I'll go through what on qooxdoo site and let u know. And probably create separate PR for widgetbrowser/demobrowser projects.
John Spackman
@johnspackman
:+1: