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
Christian Boulanger
@cboulanger
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.
My silly site is now some 12 hours old, but excited like kid to get a brain dump started without all the distractions of HTML/CSS and so. DE is a big target country for this project btw.
Drop me a note at: http://FUNuage.org ? (it'll be my first!)
(or maybe you guys know a JS programmer typ that might enjoy doing this game with me?)
John Spackman
@johnspackman
@SwarmShepherd I’ve not used Ionos but at first glance it looks like a different type of product - ionos is a CMS for creating and styling content, where Qooxdoo is for building single page applications. So what you would do is to create a Qooxdoo application (ie your game) and add it to one of the pages that you create with ionos. i don’t know how phaser.io would fit in though, it sounds like that it might be its own framework?
slachtar
@slachtar
@oetiker I see you're working on a new theme (with dark and light colors), IMHO it's one of the greatest additions to qooxdoo, especially for new users, where app look is an important criteria when selecting a framework. I'm still using qx V5, does it work with this version, if not, could you please share some screenshots of the new theme. Thank you
Aleksandar Josipovic
@nanexo

Hello everyone, I have a question regarding resourceloading: I need to add a suffix for every resource request. The suffix is dynamically generated and is inserted into index.html from where I can retrieve it. Looking at the source, I tried setting

qx.util.LibraryManager.getInstance().set("qx", "resourceUri", "resource/" + suffix);
qx.util.LibraryManager.getInstance().set("myapp", "resourceUri", "resource/" + suffix);

first thing in Application.main which seems to do the trick.

Is this the right approach?

George Koller
@SwarmShepherd
@johnspackman Avoiding HTML & CSS is rather a life goal for me, so there is a major alignment here :). As programmer I want to BUILD - love the Qooxdoo-ding approach . As biz-guy (of sorts) I want to think about content (at least for chunks of time), and I don't really want to get tied up with Servers/Hosting and just all of that (I'm an old Applications guy - desktop). Did some Wagtail, even go back to Sinatra (Ruby days). Well, I'm looking around the docs.
George Koller
@SwarmShepherd
Where and how does content like paragraphs get into the website? Qooxdoo Tuts are giving me a 404. I'll be taking a spin around github to find something like I want to do.
Oh, Anything / anybody doing a Kotlin-ding on Qooxdoo?
John Spackman
@johnspackman
the website is generated using nunjucks as a static site, from this repo: https://github.com/qooxdoo/website
please can you file an issue there if the tutorials (or other links) are not working?
George Koller
@SwarmShepherd
THIS IS WAAY MORE interesting than my first impression...
Tobias Oetiker
@oetiker
@slachtar will share, :) as soon as it is in a presentable state
1 reply
Tobias Oetiker
@oetiker
Screenshot 2020-05-26 at 22.17.36.png
3 replies
another 2h later
Benayed-Mohamed
@Benayed-Mohamed
Hello , i want to know why the qx.ui.form.Spinner() allows max value as 100 and min value as 0 , those values shouldn't be unlimited when no parameters are given ? Here is the playground link to see how it behaves : https://tinyurl.com/y8357wfq
Christian Boulanger
@cboulanger
@Benayed-Mohamed Hi, you need to explicitly set minimum and maximum values, see https://tinyurl.com/yavqj9cl - see also the API: https://qooxdoo.org/qxl.apiviewer/#qx.ui.form.Spinner