by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 07 06:09
    johnspackman synchronize #9967
  • Jul 06 22:53
    pazalejandro edited #10012
  • Jul 06 13:01
    hkollmann commented #729
  • Jul 06 12:58
    rommni commented #729
  • Jul 06 12:38
    hkollmann commented #729
  • Jul 06 12:05
    hkollmann commented #731
  • Jul 06 09:11
    rommni commented #729
  • Jul 06 08:54
    rommni commented #729
  • Jul 06 08:54
    rommni commented #729
  • Jul 06 08:50
    rommni commented #729
  • Jul 06 08:49
    rommni commented #729
  • Jul 06 08:48
    rommni commented #729
  • Jul 06 08:38
    hkollmann commented #729
  • Jul 06 08:37
    hkollmann commented #729
  • Jul 06 07:34
    rommni commented #729
  • Jul 06 07:28
    rommni commented #729
  • Jul 06 07:17
    hkollmann commented #729
  • Jul 06 07:13
    rommni commented #729
  • Jul 06 06:45
    hkollmann commented #729
  • Jul 06 06:15
    rommni commented #729
Oleg Philippov
@ofilippov
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 ...

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
kloox.gif
Christian Boulanger
@cboulanger
@ignapas Thanks for reporting, we will look into it. For the time being, you can have a look at the old docs at https://archive.qooxdoo.org/5.0.2/api/#qx which is probably correct for 99% of the code.
Ignacio Pascual
@ignapas
thank you so much!
Tamerlanchiques
@Tamerlanchiques

Got answer from teammate about wrote above issue.

Here it is:

npx qx deploy – now it works but …

Incremental compilation - this is faster but may preserve old artifacts, it is recommended to use --clean command line option ERROR: No deploy dir configured! Use --out parameter or deployPath target property in compile.json.

When using npx qx deploy and
npx qx deploy --clean
I expect to see prepared build in D:\test\compiled\build directory. But size of build folder a little bit less than D:\test\compiled\source folder.

If I execute npx qx debloy --out=D:\test\BUILD I getting build folder in this directory.

compile.json contents:
"targets": [ { "type": "source", "outputPath": "compiled/source", "bundle": { "include": "qx.*" } }, { "type": "build", "outputPath": "compiled/build" }]

As I expect I had to write deployPath somewhere there. But why is it not set automatically during creating of new app process like it set in "outputPath":"compiled/build"?

Extra information that may be useful:
D:\test\compiled\source - size of this dir is around 21MB.
D:\test\compiled\build - around 17 MB.
D:\test\BUILD - around 1 MB.

Should I open bug issue about this?

Tamerlanchiques
@Tamerlanchiques
  • misspelling debloy => deploy of course
John Spackman
@johnspackman
@Tamerlanchiques yes, that would be useful -please file an issue
Martín Alejandro Paz
@pazalejandro_se_twitter
Hello dear community, I would like to ask you to upload the .json files in the Package DemoBrowser (Example: demobrowser/demo/data/demobrowser/demo/data/persons.json, demobrowser/demo/data/demobrowser/demo/data/tree.json , etc)
Excuse my English, I speak Spanish.
Oleg Philippov
@ofilippov
Hi everyone,
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined
It is strange cause I dont't see 'startsWith' in qxl/testtapper/Application.js file
did anyone see that problem before?
Henner Kollmann
@hkollmann
@pazalejandro_se_twitter : What are you missing? They are here https://github.com/qooxdoo/qxl.demobrowser/tree/gh-pages/resource/qxl/demobrowser/demo/data.
Christian Boulanger
@cboulanger
@ignapas The APIViewer (also accessible via http://api.qooxdoo.org) is working again!
Martín Alejandro Paz
@pazalejandro_se_twitter
@hkollmann Thanks! I was trying http://qooxdoo.org/qxl.demobrowser/#data~JsonToList.html and there makes use of the missing file (list.json) I warn you so that the example does not have such an error. For the localhost version I will use the ones you told me. Thank you!
Henner Kollmann
@hkollmann
Could you create an issue in the demobrowser project? Many thanks!
Oleg Philippov
@ofilippov

Hi everyone,
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined

Anyone? This is kinda show stopper for us :(

Pat Buxton
@rad-pat
Since a recent compiler version, some of our legacy code has stopped working as it did. It looks like someone has set up some statics on classes with a prefix of __ and these have then been used by other classes. The compiler seems to mangle these now and they are unavailable to access from the other classes. Although I'm sure I should change all these statics anyway, this represents different behaviour from the python compiler - was this expected?
methods and properties prefixed with __ are private (have always been) and should thus not be accessed from outside the class. The python compiler had enforced this policy for the build version of the code using name mangling. The new compiler only recently started also enforcing this policy. We had some internal discussion as to whether it was actually necessary, since surely nobody would try to access a private variable from outside a class ... :)
Pat Buxton
@rad-pat
surely :)
Oleg Philippov
@ofilippov
New compiler obfuscate even strings like "__blank". Is it possible somehow to prevent that obfuscation?
Oleg Philippov
@ofilippov

Hi everyone,
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined

That happens cause in class qxl.testtapper.Application we have a code like this:
let [testClass, ...testName] = test.split(":");

when compiler process it in qx/tool/compiler/ClassFile.js it falls in method encodePrivate when processing "ArrayPattern" - it assumes that prop has a property "name" (line 1747), but it should check prop.argument.name instead.
see:

{
  "type": "RestElement",
  "start": 6591,
  "end": 6602,
  "loc": {
    "start": {
      "line": 200,
      "column": 34
    },
    "end": {
      "line": 200,
      "column": 45
    }
  },
  "argument": {
    "type": "Identifier",
    "start": 6594,
    "end": 6602,
    "loc": {
      "start": {
        "line": 200,
        "column": 37
      },
      "end": {
        "line": 200,
        "column": 45
      },
      "identifierName": "testName"
    },
    "name": "testName"
  }
}
Christian Boulanger
@cboulanger
@ofilippov Thanks for reporting the bug, please create an issue https://github.com/qooxdoo/qooxdoo-compiler/issues/new
Oleg Philippov
@ofilippov
@cboulanger done: qooxdoo/qooxdoo-compiler#701
hcarsten
@hcarsten
just wondering if this feature here "htmlArea" is still avail. http://archive.qooxdoo.org/1.6.1/pages/gui_toolkit/ui_html_editing.html
Christian Boulanger
@cboulanger
@hcarsten No, but you can use qookery's CKeditor if you don' t mind the additional dependency: http://www.qookery.org/
hcarsten
@hcarsten
@cboulanger thx, might be nicer to bring these to "real" qx extensions.
George Koller
@SwarmShepherd
I'm an OLD fan of Qooxdoo, the first website builder that made any sense to my programmer brain! Super to see you guys still beating head against pretty much the same old wall? What I'd love to understand , right off the top, is where you see your current JS project standing compared to such as the default IONOS website builder? I'm just getting started with it as a 'user' and it seems pretty intuitive and more powerful than I expected.
George Koller
@SwarmShepherd
I'm a retired programmer in middle of USA, and my project has, I believe, is a sweet little puppy with big International Paws. And a new project is coming up in JS to lay a new in-browser Game Face on my Kotlin Server Code. I'm looking at and intending to use http://phaser.io/ - a nice community too. Very briefly my project 'plays like a game' but is really a ILE in disguise.