by

## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• 21:21

github-actions[bot] on gh-pages

deploy: c06a33c7e52f11236962001… (compare)

• 21:20
cboulanger commented #743
• 21:19

cboulanger on master

add deploy action (#743) Co-au… (compare)

• 21:19
cboulanger closed #743
• 20:46
hkollmann synchronize #743
• 12:08
oetiker commented #748
• 12:07
oetiker commented #748
• 12:05
oetiker commented #748
• 12:04
oetiker commented #748
• 12:03
hkollmann closed #736
• 12:03
hkollmann commented #736
• 12:02
hkollmann synchronize #736
• 12:00
hkollmann closed #724
• 12:00
hkollmann commented #724
• 11:58

github-actions[bot] on gh-pages

deploy: 0d53765718c0886091289b4… (compare)

• 11:56

hkollmann on master

fix for https://github.com/qoox… (compare)

• 11:56
hkollmann closed #745
• 11:20
hkollmann synchronize #745
• 11:19

github-actions[bot] on gh-pages

deploy: eb7d48411b63ca884fb146e… (compare)

• 11:17

hkollmann on fix-746

Christian Boulanger
@cboulanger
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
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
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
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
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();

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

addButton.setDecorator(deco);

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

Tobias Oetiker
@oetiker
yes as I said ... if you want dynamic behavior you have to use appearance
Christian Boulanger
@cboulanger
Tamerlanchiques
@Tamerlanchiques

Hello everyone!
Teammate got next problem:

npx qx compile – works if build command is performed before.

Listed below commands are getting error messages when performed.
Main question is "How to do build in these circumstances"?
1st command:
D:\test\MYAP>npx qx deploy Source maps are not being deployed, see --source-maps command line option Incremental compilation - this is faster but may preserve old artifacts, it is recommended to use --clean command line option Error: Error: Error in property libraryPoPolicy of class qx.tool.compiler.targets.BuildTarget in method $$setLibraryPoPolicyImpl with incoming value 'undefined': Undefined value is not allowed! 2nd command: D:\test\MYAP>npx qx deploy --clean Source maps are not being deployed, see --source-maps command line option Error: Error: Error in property libraryPoPolicy of class qx.tool.compiler.targets.BuildTarget in method$$setLibraryPoPolicyImpl with incoming value 'undefined': Undefined value is not allowed!

In addition my teammate faces the following trace:
at Object.error (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13176:15) at wrapper.set (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:110) at wrapper.eval [as setLibraryPoPolicyImpl] (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:540) at wrapper.eval [as setLibraryPoPolicy] (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:31) at wrapper.eval (eval at __attachPropertyMethods (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13065:28), <anonymous>:3:114) at targetConfigs.forEach.targetConfig (D:\test\node_modules\@qooxdoo\compiler\source\class\qx\tool\cli\commands\Compile.js:675:16) at Array.forEach (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:10169:22) at wrapper.createMakersFromConfig (D:\test\node_modules\@qooxdoo\compiler\source\class\qx\tool\cli\commands\Compile.js:633:21)

What advice can I give him?

Christian Boulanger
@cboulanger
@Tamerlanchiques Can you open a bug issue here: https://github.com/qooxdoo/qooxdoo-compiler/issues/new and copy the error messages - above it looks a bit mangled.
We've done some refactoring with qx deploy which might result in some temporary instability - thanks for reporting any buggy behavior.
Aleksandar Josipovic
@nanexo
I've had the same issue, but with the newest version it works again.
It got fixed with this qooxdoo/qooxdoo-compiler#694 .
Christian Boulanger
@cboulanger
@nanexo Ah, even better, thanks! @Tamerlanchiques Can you confirm upgradint to the newest compiler solves your issue?
Tamerlanchiques
@Tamerlanchiques
@cboulanger I will contact with my teammate for extra discussion about this and will tell him to check his compiler version out.
And we can open bug issue a little bit later with more thorough narration if the problem doesn't fix on the latest version of compiler.
If it's will be fine I will write about it here …
Ignacio Pascual
@ignapas
Hi everyone. Do you know where I can access the API documentation? https://qooxdoo.org/qxl.apiviewer/# is broken