by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:50
    oetiker commented #10039
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55
    lucapivato opened #10042
  • Sep 21 20:55
    lucapivato review_requested #10042
  • Sep 21 20:55

    lucapivato on lucapivato-patch-3

    Local variable gaps is in the w… (compare)

  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54
    lucapivato opened #10041
  • Sep 21 20:54
    lucapivato review_requested #10041
  • Sep 21 20:54

    lucapivato on lucapivato-patch-2

    Local variable gaps is in the w… (compare)

  • Sep 21 20:54
    lucapivato synchronize #10039
  • Sep 21 20:51
    lucapivato synchronize #10039
  • Sep 21 20:51
    lucapivato review_requested #10040
Christian Boulanger
@cboulanger
@ofilippov Thank you - looks good to me, let's see what @johnspackman says!
Oleg Philippov
@ofilippov
Thanks a lot!
Aleksandar Josipovic
@nanexo

hi, I'm having a bit of a problem with source maps in combination with the build target source and bundles.
config for the target:

"type": "source",
"outputPath": "compiled/source",
"bundle": {
    "include": "qx.*"
}

The problem I'm running into is that the sources in the source maps are absolute. Are they supposed to be absolute? And can I change that (via path-mappings perhaps)? There is a similar issue qooxdoo/qooxdoo-compiler#669 that got fixed recently, but I think that one only affected deploy builds..

Aleksandar Josipovic
@nanexo
I should add the the sources of the bundles (in this case the qx library) have absolute paths
Henner Kollmann
@hkollmann
Which compiler version do you use? This should be changed with qooxdoo/qooxdoo-compiler#672
Aleksandar Josipovic
@nanexo
I'm on 1.0.0-beta.20200512-2000
Dietrich Streifert
@level420
I'm currently investigating on how translation is handled with the compiler. I have the translation files under myapp/source/translation named de.po and en.poand have defined "locales": ["en","de"] in compile.json. I 've tried qx compile --locale=en or qx compile --locale=de but this doesn't seem to work.
Christian Boulanger
@cboulanger
@level420 It is not automatic. You need to add --update-po-files / -u
Dietrich Streifert
@level420
@cboulanger will try that. thank you.
Christian Boulanger
@cboulanger
There are two bugs open concerning this: qooxdoo/qooxdoo-compiler#618 and qooxdoo/qooxdoo-compiler#158
If I remember our discussions correctly, we haven't come to a conclusion what the default behavior should be because the specs for .po files make a sensible solution difficult - following the specs results in many useless source code changes because of the changing line numbers.
Dietrich Streifert
@level420

How are libraries handled? I've defined in compile.json:

  "libraries": [ 
    "../mylibrary", 
    "." ]

where classes exist which also have this.trentries. should those entries also appear in the *.po files of the app?

Christian Boulanger
@cboulanger
This is another open bug :smile: qooxdoo/qooxdoo-compiler#175
Dietrich Streifert
@level420
:bug:
Christian Boulanger
@cboulanger
Please add your voice there and, if possible, provide a solution :smirk:
Christian Boulanger
@cboulanger
@/all :exclamation: :exclamation: :exclamation: Please do not update the NPM packages for a moment, we have a regression. We'll fix it ASAP and let you know when it is safe to update again.
Christian Boulanger
@cboulanger
We're back! http://qooxdoo.org/status/ It should be safe to upgrade now. If you experience anything out of the ordinary, let us know.
Pat Buxton
@rad-pat
Is there a place to provide feedback about the new website? I had a quick search in here but only found an github issue to provide feedback on the docs.
Tobias Oetiker
@oetiker
you can open an issue here https://github.com/qooxdoo/qooxdoo.github.io/ as this is where the website lives ... or you can discuss here if it is not just a bug ... you can also create a PR if you have something to fix (outside of the documentation)
Pat Buxton
@rad-pat
I'm happy to discuss it here. I just found it a little annoying to have to scroll to the bottom of the home page to get to the links for demo / playground / widget browser. There are drop down menus for the Documentation and the Community an the top of the page so it would seem sense to add some menu/links to get to these other resources without having to scroll to the bottom
John Spackman
@johnspackman
:+1:
please can issues for the website go here: https://github.com/qooxdoo/website
tat’s the source which is compiled into the qooxdoo.github.io repo
Pat Buxton
@rad-pat
I'll add my comment as an issue there
Oleg Philippov
@ofilippov
Hi,
As far as I can see qooxdoo now replace native Array methods with polyfills. It happens cause qx.lang.normalize.Array defer function is executed before qx.bom.client.EcmaScript - and even before environment properties initiation.
It can make a problem cause some methods from qx.lang.normalize.Array have different behavior from native ones (for example "forEach" method skips undefined values from array while native forEach processes it)
We don't have this problem in 5.0.2 qooxdoo
Just open https://qooxdoo.org/qxl.apiviewer/ and type in devtools console something like [].forEach to see that the native method was replaced with polyfill
Derrell Lipman
@derrell
@ofilippov Would you please create an issue on http://github.com/qooxdoo/qooxdoo-compiler ? That sounds like the order of processing is incorrect. Polyfills shouldn't be used if not needed.
Oleg Philippov
@ofilippov
shawnli88
@shawnli88
@cboulanger thanks a lot for you, the qxl.demobrowser can be compiled normally . 👍
Derrell Lipman
@derrell
Thanks @ofilippov
Christian Boulanger
@cboulanger
@shawnli88 credit where credit is due: @hkollmann has been the main force behind porting the demobrowser and other qooxdoo apps to the new compiler infrastructure.... :-)
Dietrich Streifert
@level420
when running the compiler with qx compile --watch --write-all-translations is it supposed to detect changes in the *.po files?
John Spackman
@johnspackman
yes, i would have said so … please can you add an issue for it
Oleg Philippov
@ofilippov
When I run "qx test" it writes at the end "writing coverage information ..." Do you know where I can get this data? Thanks.
As far as I see testtapper sends it to puppeteer-to-istanbul... But what happens after that?
Oleg Philippov
@ofilippov
found :)
npx nyc report --reporter=cobertura
hcarsten
@hcarsten
I am looking to have a button with rounded borders. So I created a decorator, set the borderRadius and background (to "transparent"). After assigning the decorator the button does not have the hover handling anymore ?
Tobias Oetiker
@oetiker
this is because the decorators normally get switched dynamically based on the appearance
if you set a fixed decorator it will not get switched out
hcarsten
@hcarsten
how do I set a "fixed decorator" ?
Tobias Oetiker
@oetiker
widget.setDecorator(...)
Oleg Philippov
@ofilippov
Looks like API viewer doesn't work anymore
I can see multiple errors in console
Christian Boulanger
@cboulanger
@ofilippov Thanks. We are working on fixing it. Please hold off upgrading the framework for the moment.
Oleg Philippov
@ofilippov
It works now, thanks!
Christian Boulanger
@cboulanger
Yes we're back to green: https://qooxdoo.org/status/ (only the package browser update is currently down, but that doesn't affect anything else)
hcarsten
@hcarsten

@oetiker : regarding the decorator problem from yesterday. This basically what I did:

let menuBar = new qx.ui.menubar.MenuBar();
 menuBar.setBackgroundColor("transparent");

 let addButton = new qx.ui.menubar.Button("Add");

 var deco = new qx.ui.decoration.Decorator();
 deco.setRadius(3);
 deco.setBackgroundColor("transparent");
 deco.setColor("silver");
 deco.setWidth(1);

 addButton.setWidth(100);
 addButton.setHeight(25);

 addButton.setDecorator(deco);

and here I get the weired problem that the hover-effect or the button disappeared ...