Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 26 22:26
    mahmoudimus starred qooxdoo/qooxdoo
  • Nov 26 20:14
    johnspackman commented #10200
  • Nov 26 16:53
    adrelino commented #10200
  • Nov 26 16:47
    adrelino commented #10200
  • Nov 26 16:22
    adrelino commented #10200
  • Nov 22 15:18

    hkollmann on v7.0.0-beta.4

    (compare)

  • Nov 22 15:18

    hkollmann on master

    "hotfix to support using as pa… (compare)

  • Nov 22 15:11

    hkollmann on master

    Fix require (#10287) * fix req… (compare)

  • Nov 22 15:11
    hkollmann closed #10287
  • Nov 22 13:51
    hkollmann synchronize #10287
  • Nov 22 13:47
    hkollmann synchronize #10287
  • Nov 22 13:45
    hkollmann synchronize #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann review_requested #10287
  • Nov 22 13:35
    hkollmann labeled #10287
  • Nov 22 13:35
    hkollmann opened #10287
Derrell Lipman
@derrell
If you're using qx compile --watch then it has problems when libraries are added or removed. Always a good idea to stop and restart qx compile --watch if you change libraries or the location of classes. (I think it's a known bug)
NW Group
@nwgroup
i finally did this: "libraries": [
"./qxnw.6.0/trunk/",
"."
]
but when i test it i get the next error: Uncaught ReferenceError: qxnw is not defined
i already test with the contrib outside the project but got the same error
Derrell Lipman
@derrell
is the namespace called qxnw or is it called nwadmin3? What namespace does the contrib's Manifest.json "provide"?
NW Group
@nwgroup
the namespace of the contrib is qxnw
the main project is nwadmin
nwadmin3
the Manifest.js of contrib: "provides":
{
"namespace": "qxnw",
Derrell Lipman
@derrell
And is the contrib's Manifest.json at path ./qxnw.6.0/trunk/Manifest.json relative to the app's compile.json?
NW Group
@nwgroup
yes but i test relative and outside like ../../qxnw/trunk/
and got the same error
Derrell Lipman
@derrell
I'm running out of ideas. I think you need @johnspackman or @hkollmann or maybe @cboulanger to help you. They're all in Europe, so it'll be 6-8 hours before they're online.
I feel you're close, though!
gtg. Good luck!
NW Group
@nwgroup
yes! thank you Derrell for your help!
Henner Kollmann
@hkollmann
Good morning! Could you try to ommit the trailing /?
NW Group
@nwgroup
hi, we got the same: Uncaught ReferenceError: qxnw is not defined
but it compile fine
this is our compile.json:
{
"$schema": "https://qooxdoo.org/schema/compile-1-0-0.json",
"targets": [
{
"type": "source",
"outputPath": "compiled/source",
"bundle": {
"include": "qx.*"
}
},
{
"type": "build",
"outputPath": "compiled/build"
}
],
"defaultTarget": "source",
"locales": ["en"],
"environment": {
"qx.icontheme": "Tango"
},
"applications": [
{
"class": "nwadmin3.Application",
"theme": "nwadmin3.theme.Theme",
"name": "nwadmin3",
"bootPath": "source/boot"
}
],
"libraries": [
"../../qxnw/trunk",
"."
]
}
NW Group
@nwgroup
and this is de Manifest.json on qxnw contrib:
{
"info":
{
"name": "qxnw",
"summary": "QXNW Library",
"description": "A estructural schema to high performance process.",
"homepage": "http://www.gruponw.com",
"license": "PRIVATE",
"authors":
[
{
"name": "Andrés Flórez (andresf)",
"email": "direccion@netwoods.net"
}
],
"version": "trunk",
"qooxdoo-versions": ["2.1", "3.0", "3.5", "4.0", "5.0", "6.0"]
},
"provides":
{
"namespace": "qxnw",
"encoding": "utf-8",
"class": "source/class",
"resource": "source/resource",
"translation": "source/translation",
"type": "contribution"
}
}
Derrell Lipman
@derrell
@nwgroup Try qx clean and then qx compile again to see if it makes any difference.
oh, and if you're using qooxdoo from git or a recent npm version, it's probably version 7 but your contrib's Manifest shows "qooxdoo-versions" only up to 6.0. (I would expect a warning, though, if it found the manifest but decided not to use it... likely not the issue.)
NW Group
@nwgroup
Derrell, you are the one! It was "qx clean", thanks a lot!
Derrell Lipman
@derrell
Great!
NW Group
@nwgroup
well, i'm using qooxdoo 6, I'll keep it in mind
Derrell Lipman
@derrell
Changing libraries sometimes requires cleaning and rebuilding. I'm not sure when it's actually required, but when things don't work as expected, I try cleaning.
Glad you're up and running!
paul reed
@paulreed295_twitter
Hi I am looking for help with integrating chartjs with qx. I came across the following but the link seems to be broken: Henner Kollmann @hkollmann Dec 21 2019 09:17
@rixs We are using https://www.chartjs.org/ for charting. Qooxdoo integration is easy.
Here is an example for radar chart https://www.chartjs.org/samples/latest/charts/radar.html
I did talk a look at qxCHART but it seems to be over five years old, not sure if it is still been maintained.
Adrian Haarbach
@adrelino
How can I configure the qooxdoo-compiler / babel to output ES6 modules ?
I want to be able to write at the top of qooxdoo class files
import { extFun } from "util/utils.js"
but the compiler fails with error:
import' and 'export' may appear only with 'sourceType: "module"' (1:0)
Consider renaming the file to '.mjs', or setting sourceType:module or sourceType:unambiguous in your Babel config for this file.
Frank Guzmán
@guzmanf
@paulreed295_twitter reference as idea , best regards (sorry by my bad english) https://www.idscloud.cl/qx/comparativo1.js
Henner Kollmann
@hkollmann
Hi frank, have you changed the Compiler to Support map files? Would be a nice extension
Frank Guzmán
@guzmanf
NW Group
@nwgroup
Hi, we are testing some changes that affect our code, one of them is the next: Uncaught Error: Overwriting member "setValue" of Class "qxnw.widgets.selectTokenField" is not allowed!
and the code that we used was: // overridden
setValue: function setValue(val) {
this.getChildControl('textfield').setValue(val);
return true;
},
and the header of that class is:
qx.Class.define("qxnw.widgets.selectTokenField", {
extend: qx.ui.form.AbstractSelectBox,
implement: [
qx.ui.core.IMultiSelection,
qx.ui.form.IModelSelection
],
include: [
qx.ui.core.MMultiSelectionHandling,
qx.ui.form.MModelSelection
],
so what we can do to avoid that warning?
Frank Guzmán
@guzmanf
hi @hkollmann, the moment.js use and load the map file, i dont modified anything in the compiler, best regards
Henner Kollmann
@hkollmann
Interesting that the map file is loaded in the app - it's not copied into the output directory
John Spackman
@johnspackman
@adrelino that’s a limitation of the compiler at the moment, it does not understand that import syntax
Adrian Haarbach
@adrelino
@johnspackman thanks for your answer, I already though so. I am keen on investing some time into understanding and extending the qooxdoo-compiler, however I need some hints to get me going
  • is the source of the compiler in the qooxdoo repo or the qooxdoo-compiler repo now? There was some merge of known-good qx command, but is that just the binary version of the compiler?
  • where in the compiler source code is babel called so I can modify its options?
Tobi Oetiker
@tobioetiker:matrix.org
[m]
the compiler is fully merged in the master branch
Derrell Lipman
@derrell

@nwgroup You didn't include the entire selectTokenField class, but it looks to me like that class defines a property called value. By doing so, a number of methods are automatically created, one of which is setValue. You can't override that method. You can, however, add an apply field to your property in selectTokenField and a possibly empty method, like so:

properties :
{
  value :
  {
    ...
    apply : "_applyValue"
  }
}

...

members :
{
  _applyValue : function() {}
}

You can then override the _applyValue method in your subclass.

But you do not need to change the compiler - we support setting babel options in compile.json: https://qooxdoo.org/documentation/6.0/#/development/compiler/configuration/compile
Note: using babelOptions in root context is deprecated. Use babel.options section instead.