Yes and no. You can reuse any of the Wisej classes easily (use F12 to see the class names) but changes of state and changes of class names are dynamic in Wisej and you’d have to write javascript code to change the class name from say “qx-button” to “qx-button-hovered”. Wisej (qooxdoo) generates css classes on the fly from the theme definition as the application runs. If your app never uses a a certain control, the css classes for that control are never created in the browser.
See attached sample app and screenshot below. It shoes an html panel using an html file and a stylesheet file to style its content and it show a label control with HTML text set to look like a wisej button.

Hi Henry,
Thank you!
To answer your questions:
HTH
Best,
Luca
Hi Danny,
The default project template creates a child window by default. It doesn’t create the main page or main desktop. We are adding more templates.
In Wisej there are 3 top level controls and a main canvas HTML page:
In your sample app, add a Wisej.Web.Page control, open it in design mode, add controls, then in Program.Main() add new Page1().Show() – or Application.MainPage = new Page1(), the two are equivalent.
HTH
Best,
Luca
Hello Luca,
yes we used a lot of Application.Update() and Thread.Sleep(), because when we added 50 User Controls or more to the FlowLayOutPanel the whole UI got frozen until everything was loaded. To avoid this we used Application.Update() to simulate dynamic loading.
Anyway, the demo-app you published works exactly as we wished, what are your changes and can you give us the improved code.
Greets,
Marcel
Hi Andrew,
you can find a sample using jstz and the different options to integrate it into Wisej here:
http://wisej.s3.amazonaws.com/support/attachments/Wisej.JavaScriptCallbacks.zip
Few notes:
Best regards
Frank
Hi Wilfred,
this issue is fixed in the latest development build (1.3.17).
Best regards
Frank
Hi Michael,
it´s logged as WJ-7876 and fixed in the latest development build (1.3.17).
Best regards
Frank
Hi Wilfred,
it´s fixed in the latest development build (1.3.17).
Best regards
Frank
Hi Andrew, James,
please find migration guides here:
https://wisej.com/support/question/migration-guides
Hope that helps,
Frank
Danny, Ewan
please find migration guides here:
https://wisej.com/support/question/migration-guides
Hope that helps,
Frank
Hi Mark,
please find migration guides here:
https://wisej.com/support/question/migration-guides
Hope that helps,
Frank
Please try this: http://demo.wisej.com/apps/flowlayouttest
This is what I get now: https://www.screencast.com/t/Pu6peTdWT
Not yet, setting up the samples on a test server that can be reached with a real tablet and not an emulator.
Question: I noticed a lot of Application.Update() and Thread.Sleep() in there. Is it to emulate load or why do you need those?
I also noticed an issue with the scrolling jumping to top when adding the controls and other issues that I will address in your sample and send the code back to you.
Best,
Luca
It simply means that the rendering of the link, image, button cells has changed and instead of styling the cell’s main div, they are now rendered inside and the main div of the cell is used as a container.
The main difference between the datagrid and all the other widgets is that the content of the grid is rendered as html, in other words, the cells are not widgets. Each cell is a div in a row div, etc. They are removed when scrolled out and appended when scrolled in. The content is rendered (html is re-created) each time a row scrolls in from the data source. That’s how the grid is able to handle unlimited rows.
Getting back to your question. The feature that was added and you can use is the Role property added to all grid cell events. If you add a custom html to a cell like <span role=’my-element’>Hello</span> when you click in the cell on that element, the Role property if the event will have “my-element”.
For us, this was a necessary change for the PropertyGrid, expandable rows with panels, collapsible rows which child rows since it’s a lot easier now to detect pointer events on elements inside a cell.
HTH
Best,
Luca
Thanks Ser,
this issue is logged as WJ-7886, fixed and will be included in the next build.
Best regards
Frank
Hi again,
i just wanted to ask if you could experience the same scrolling behavior on tablet and mobile devices with our test case project and maybe have any further advice for us.
Best,
Marcel
Hi Guenter,
this is currently not supported. I have added enhancement request WJ-7885 for it.
Best regards
Frank
Thanks, Wilfred.
Logged as WJ-7884.
Best regards
Frank
Thanks Wilfred,
for sample and description.
I could reproduce the problem and have logged it as WJ-7883.
Best regards
Frank
Tx, that’s fast again..
At least it is worth to send in problems and/or bugs!
In the current case I need to have it to the top of the taskbar.
