Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 20 10:20
    hasnatbabur starred qooxdoo/qooxdoo
  • Oct 20 06:44
    oetiker commented #9309
  • Oct 19 21:49
    adrelino commented #9309
  • Oct 19 15:41
    cboulanger closed #10030
  • Oct 19 15:41

    cboulanger on cboulanger-create-qx-object-change-owner

    (compare)

  • Oct 19 14:51
    adrelino commented #9309
  • Oct 11 16:24
    ppedrotti starred qooxdoo/qooxdoo
  • Oct 05 07:28
    rommni closed #729
  • Oct 05 07:28
    rommni commented #729
  • Oct 03 18:56
    hkollmann unlabeled #725
  • Oct 03 10:48
    hkollmann commented #729
  • Oct 03 10:20

    hkollmann on master

    Fix misleading documentation (#… (compare)

  • Oct 03 10:20
    hkollmann closed #10053
  • Oct 02 14:21
    rad-pat edited #10053
  • Oct 02 14:19
    rad-pat review_requested #10053
  • Oct 02 14:19
    rad-pat review_requested #10053
  • Oct 02 14:19
    rad-pat review_requested #10053
  • Oct 02 14:19
    rad-pat review_requested #10053
  • Oct 02 14:19
    rad-pat opened #10053
  • Oct 02 14:19
    rad-pat review_requested #10053
Derrell Lipman
@derrell
Has nothing to do with upgrade. I removed node_modules and reinstalled it, and end up with the same ancient version...
@hkollmann Maybe this is related to the dependency work you're actively involved in?
Christian Boulanger
@cboulanger
@derrell We're remodelling the deployment system (see https://github.com/qooxdoo/deployment), which required some time-intensive architectural groundwork. As we speak, @hkollmann is working on re-enabling NPM deployment. We just need @johnspackman to have a final look.
Derrell Lipman
@derrell
That's what I hoped and expected. Thanks, @cboulanger . I'll wait on those changes for now.
Christian Boulanger
@cboulanger
@/all :bell: Thank you for your patience during the redesign of the NPM publication process. We will soon resume releasing new packages of the compiler, the framework and the server component of qooxdoo. Because of its beta status, you should always upgrade to the newest NPM version with caution, but since this will be the first release based on a new workflow and a new "self-hosted" compiler (i.e. the compiler code is compiled using itself), some initial hiccups might occur that we will try to fix immediately. If you find that something is broken, please create an issue. You can always revert to a previous release by executing npm install @qooxdoo/compiler@1.0.0-beta.20200613-2032. We'll post another message once the new packages are out.
Henner Kollmann
@hkollmann
@derrel: After rebuilding api viewer your searched property is there: https://qooxdoo.org/qxl.apiviewer/#qx.ui.form.AbstractField
Derrell Lipman
@derrell
Great!
Christian Boulanger
@cboulanger
That is to say: @qooxdoo/compiler v1.0.0-beta-20200803-1413 is out, containing all the improvements of the current master branch. Try it and let us know if it works for you!
And a big shout-out to @johnspackman and @hkollmann who have made a self-hosted compiler possible!
Tobias Oetiker
@oetiker
cool will test tonight
Christian Boulanger
@cboulanger
my app compiles without problems with the new compiler version!
Tobias Oetiker
@oetiker
I am using the following compile.js with my qooxdoo project
qx.Class.define("callbackery.compile.CompilerApi", {
    extend: qx.tool.cli.api.CompilerApi,
    members: {
        async load() {
            let config = await this.base(arguments);
            if (!config.libraries) {
                config.libraries = ['.'];
            }
            let cbr = process.env.CALLBACKERY_QX;
            if (cbr) {
                ["callbackery"].forEach(dir => {
                    config.libraries.push(cbr+"/"+dir);

                });
            }
            return config;
        }
    }
});


module.exports = {
    CompilerApi: callbackery.compile.CompilerApi
};
after upgrading to the current compiler, it fails horribly
any hint ?
(node:29916) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'libraries' of undefined
    at wrapper.callbackery.compile.CompilerApi.prototype.load() [as load] (/home/oetiker/checkouts/o2h/o2hsrv/frontend/compile.js:6:25)
    at async wrapper.qx.tool.cli.Cli.prototype.__parseArgsImpl() [as __parseArgsImpl] (/home/oetiker/checkouts/o2h/o2hsrv/frontend/node_modules/@qooxdoo/compiler/lib/compiler/index.js:40082:9)
    at async wrapper.qx.tool.cli.Cli.prototype.run() [as run] (/home/oetiker/checkouts/o2h/o2hsrv/frontend/node_modules/@qooxdoo/compiler/lib/compiler/index.js:40032:9)
    at async wrapper.qx.tool.cli.Application.prototype.main() [as main] (/home/oetiker/checkouts/o2h/o2hsrv/frontend/node_modules/@qooxdoo/compiler/lib/compiler/index.js:39517:9)
(node:29916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29916) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
rommni
@rommni
Hi all, thank you for the work on this update ;)
I'm currently on holiday and haven't access to my app however i will test it as soon as I come back ( 17 August).
Pat Buxton
@rad-pat
My App is compiling without error on the latest compiler. It told me that I needed to run qx package migrate, which I did and that updated my Manifest.json, changing the versions of @qooxdoo/compiler and @qooxdoo/framework, which is fine. It also updated compile.json, changing the "extends" member inside the "esLintConfig" from "@qooxdoo/qx/browser" to "@qooxdoo/@qooxdoo/qx/browser" which didn't seem right, so I changed it back.
Christian Boulanger
@cboulanger
This bug should be fixed with qooxdoo/qooxdoo-compiler#752 (once the PR gets merged). Thanks for reporting.
Derrell Lipman
@derrell

@johnspackman @hkollmann This question pertains to compiler dependency analysis and location. I have a project which has a top-level compile.json and Manifest. It uses some git submodules each stored in $TOP/library, so for example there is a $TOP/library/dialog.git directory there. The compile.json for this project lists each of the libraries (git submodules) in its "libraries" array, as something like "./library/dialog.git". It all works perfectly.

Now I have a new project that makes use of that first one, so that whole first project is in the new project's library directory, including its submodules. Should it be necessary for the new project's compile.json to list each of the first project's submodules as libraries? Or shouldn't those just be automatically included when I list the first project in the library key of the new project's compile.json? To rephrase, is it necessary for an application which makes use of qooxdoo libraries, to know about all of the used libraries' dependencies?

Yeshua Rodas
@yybalam_gitlab
I'm still using the python compiler :sweat_smile:
At the University we have 3 app where one is build over other, and all of them relies on two shared library, so the config.json files still is the easiest way to attach other qx apps via Manifest.json, and also other js scrips and css files, and getting a single build js file to deploy. So, I want to ask if already there is support at the new compiler for doing some similiar configuration like the "libraries" declaration at config.json for the python compiler.
Henner Kollmann
@hkollmann
@yybalam_gitlab : we have the package system for this
@derrell : Packages loads there dpendencies recursive. Together with the possibility to define local packages this should to the job.
packages do this by reading there qx-lock.json file.
Derrell Lipman
@derrell
@hkollmann It doesn't seem to do that. It wasn't finding dialog, for example, which was a dependency of the library I included in my new app.
Henner Kollmann
@hkollmann
That was the theory. Needs to be tested and debugged then
Christian Boulanger
@cboulanger
@yybalam_gitlab Have a look at https://qooxdoo.org/documentation/#/development/cli/packages. Packages contain one or more libraries (i.e bundles of code and resources organized with a Manifest.json). Packages need not be published - you can also use them locally.
Derrell Lipman
@derrell
We all know that the reason there is theory is because not all things can be facts :-)
Thanks. It's good to know at least that it's supposed to work as I expected
@hkollmann I had started on something where I encountered that, but then got pulled back to something else. When I return to that I'll see if I can narrow it down, and then create a new issue.
guzmanf
@guzmanf
Hello friends, a question. howto stop an "dragstart" or "drop" from qx.ui.form.List(), when element selected is empty?, thank and regards
Christian Boulanger
@cboulanger
@guzmanf What do you mean by "empty"?
Christian Boulanger
@cboulanger
guzmanf
@guzmanf
@cboulanger thank so much!!!
Nisarg Panchal
@nisarg1184
Which dependency contains novlog.rpc.JsonRpcServlet ?
I mean for maven
We are working on upgrade of libraries
Christian Boulanger
@cboulanger
@nisarg1184 I never heard of this dependency. Is it part of the abandoned qooxdoo Maven integration? We're not supporting this any longer, unfortunately.
1 reply
Dmitry Zolotov
@goldim
Hi, I have a bunch of questions about framework, using it, configuring it (for example what I didn't find in docs by myself) and etc but asking here does not look good because my question could be answered many times. What about resources like stackoverflow, stackexchange, qooxdoo forum? what better choice?
John Spackman
@johnspackman
Stack overflow and here are the best places :+1:
Christian Boulanger
@cboulanger
@goldim I'd say Stackoverflow is best for specific technical questions. If you have questions that involve a lack of documentation (i.e. if there is a specific question that you would like to see more general information), you can also open an issue at https://github.com/qooxdoo/documentation/issues .
Dmitry Zolotov
@goldim
@johnspackman @cboulanger Thank you.
alex5555
@alex5555
Whe are experiencing a problem with the new compiler and Internet Explorer:
SCRIPT450: Número de argumentos erróneo o asignación de propiedad no válida
index.js (1,824644)
this is the code that is causing the problem: getDomParser:function(){return void 0!==window.DOMParser}
it crashes when opening the application, we have a white screen
Pat Buxton
@rad-pat
Hi, can anyone please help me to figure out how to make a table cell editor taller than the row in which it's editing? I've been messing around with various appearance and decorators but still don't seem to manage it. Thanks
Christian Boulanger
@cboulanger
@rad-pat Hi, isn't a modal cell editor what you're looking for: https://qooxdoo.org/qxl.demobrowser/#table~Table_Window_Editor.html ?
Pat Buxton
@rad-pat
@cboulanger, thanks but nope, I want inline, but bigger than the table row so I can have tight table rows but actually see the whole text in the editor