Hi !!
I need an expandable grid where it is possible to navigate through multiple levels.
The one provided in the example test_subgrid seems to be able to show just a level of subgrid and it seems to be very hard to extend this example so that to be able to handle multiple levels of subgrids (I mean that a subgrid can have other subgrids and these ones other subgrids as children).

Can anyone help me?

Thanks,

Davide

THIS IS A PROJECT - NOT A JOB OPPORTUNITY; HOWEVER...

GridApp Systems does database management automation better than anyone else...but we need you to provide the front-end reporting expertise using dojoX;, AJAX, Java, and/or Flash (obviously dojo is preferred because AJAX flakes out in the thousands-of-rows area we need).

You have a great sense of the GUI as well as BI experience. Given that the front-end is OO PHP, Perl, JavaScript, and HTML, knowing these couldn't hurt.

Hello !

I'm in a simple problem : dojo is working, dijit is working, but impossible to load dojox widgets !
I obtain this error on Firebug : "GET http://**myurl**/undefined../dojox/etc..." 404

The problem is about this "undefined"... Could somebody help me ??? Where can I "define" this ???

thanks

The solution is simple, you want to have a button on a cell.
Just think about editor !
By extending the class dojox.grid.editors.AlwaysOn, the button will allways appear during the viewing of the grid.

Source code

dojo.provide("foo.Button");

dojo.require("dojox.grid._data.dijitEditors");
dojo.require("dijit.form.Button");

dojo.declare("foo.Button", dojox.grid.editors.AlwaysOn, {
_valueProp: 'cellValue',
constructor: function(inCell) {
this.text = this.text || this.cell.text;
this.deleteAfter = this.deleteAfter || this.cell.deleteAfter;

I have been running through the dojox/wire/demos/markup demonstrations in the 1.1 toolkit and am seeing some issues (Firefox v2.0.0.14 & also on IE v6-sometihng on xp pro sp2, behind an apache v2 server) that I wanted to ask about. Are these "real" errors, or perhaps I've setup my file structure incorrectly? I've tried accessing both locally and behind Apache. My typical access looks like:
http://mysystem:2345/dojox/wire/demos/markup/demo_ConditionalAccess.html

----
demo_actionChaining.html
displays 3 input boxes, no buttons, I can type in the first box but nothing happens.

Hello everybody,

Im trying to find some examples for a gantt chart using dojox.charting, but it looks as there is not one single example available...

is there anyone out there who has a complete example, actually the js and html part of it and can post it for me right below this?

thanks in advance

rolarga

Hi!

I want to access some functions in _base.js in dojox.math. I used the following function but I get an error. Can anyone of you please put me in the correct track??

function getStatistics() {
dojo.require("dojox.math._base");
alert(factorial(5));
}

Hi,

I'm trying to change the width of the Gallery so that it will play nicely with my css/div columns.

I have the Gallery in the left div column, and text content in the right column.

The thumnail picker is floating over onto the right column by several hundred pixel.

I looked around with firebug, and it looks like:
dojo.byId('dojox_image_ThumbnailPicker_0').style.width === "500px"

Changing it to 300px doesn't completly fix the problem though, because the "next" button is still floating far to the right. (and it doesn't have an id so I can't attach to it with dojo.byId).

I have a grid using an ItemFileReadStore (actually same thing happens with a QueryReadStore and doClientPaging=true) with a moderately large (600 record x 9 field) dataset.

Performance stinks with Firefox, and is decent with Microsoft Internet Explorer, but that's not the issue.

When I click on a column header to reverse sort, the grid seems to be quite "confused". Scrolling causes even more confusion.

(See next response - I've editing this after adding sequential numbers to the dataset to get a better picture of what's happening.)

Lots of things have been happening in DojoX lately, both big and small. I'll leave it to Pete and Adam to talk about some of the widget-based improvements that have been making their way into the codebase, but I'll talk real quick about some of the other things that have landed recently, and some upcoming things to look for.