Ext.nd Beta 3r1 available for download

[jratcliff]

We're still working on a few other bugs (like the combobox on the name picker and the issue with the demo app and the response form). However, we have a few fixes that we thought those of you using Beta 3 could use right away. To apply these fixes just replace the extnd-all.js and extnd-all-debug.js in your Ext.nd Beta 3 database with the ones includes in the attached zip file.

Ext.nd Beta 3 can be downloaded from here:
http://extjs.com/downloads/extnd_b3.zip

Jack & Rich

[breckster]

Hi Jack

I've tried two different zip tools to extract the .js files with no luck.

Thanks

Breck

[jratcliff]

Hi Jack

I've tried two different zip tools to extract the .js files with no luck.

Thanks

Breck
Are you using IE? There is a known issue with downloading zip files from IE. Use some other browser instead.

[breckster]

Thanks Jack

[msobczak]

I still can't open any of the documents. I can double-click on them, and I don't get an error as with B3, but I still can't view the documents.

[breckster]

Hi Jack

Wondering if you got a chance to upload the correct files (extnd-all.js,extnd-all-debug.js) per this thread

http://www.extjs.com/forum/showthread.php?t=81583


thanks

breck

[giuliocc]

Guys. I know you're all putting in alot of effort producing the EXT.nd/Ext frameworks. But I have been stuffing about for an hour trying to make the demo database work with great difficulty. From first appearances no one seems to actually be testing a clean install of the demo database. Or the instructions on installation are poorly placed or missing.

The demo database is your chance to enlist the keen and un-initiated to the process. If it doesn't work out of the box easily, you're just losing an easily reachable audience.

Every time I try and open main. I get an "Ext is not defined" on line 41 of main.html
The line in question is below.

Ext.onReady(ExtndApp.init, ExtndApp, true)

Perhaps it's quite easy, and I am the uber-jerk who doesn't get it. I would have thought the installation would simply be case of running the "signing" the agent, edit/save the configuration document, and opening the "main.html" on the browser. But all I get is an error, quoted above.

Thanks in advance if you can point me in the right direction.

[msobczak]

Hi giuliocc,

You need to open the Ext.nd.Profile form in your web browser, enter the path to your Ext.nd database, select version 3.x and save. For some reason, the profile form isn't set up to be edited in the Notes client. You have to edit the profile and save via a browser.


Hope that helps,

- Mike.

[msobczak]

I uploaded the new JavaScript files and the multi-category expansion view still doesn't open documents when I double-click on one in the view.

[giuliocc]

What you're recommended worked. I opened the form on the browser and saved the document and it seems to load up.

What's EXTREMELY misleading is the agent under the actions menu "Extnd\Edit Extnd Profile doc" which saves the document as a database profile document but doesn't seem to have any affect at all.

Because there is NO doco about configuring the demo, (not even something in the About/Using database), I have to take guesses as to what to configure.

Now that it's going, it looks great. The difficulty in starting up the demo has taken some of the gloss off what is otherwise an impressive development effort.

Guys, please, you need to check your deployments or get someone to do it for you to make the demo as smooth as silk..

[marceloprietos]

Hi Jack, this is an excelent functionality of Lotus Notes let to all the designers hide or show content or action buttons in a form or view when the formula is true, ExndB3 does not support this in action buttons on forms and views, but it works in forms and pages content. Please take in count this functionality for the next release.

Best regards.

[hirecules]

I compared the files with a previous Extnd version I downloaded a year ago (maybe r1) and noted that the Extnd/source files were entirely missing in the r3 download.

[ragdam]

Multi Expand Categorized View doesnt work correctly:
1 - When i expand a category, the icon "+" still stay "+" et doesnt transform into "-"
2 - When i expand all, the icon "-" appears but at this moment i can't collapse one only category.

[jratcliff]

Hi Everyone,

Just wanted to let you know that we're listening and trying to catch up on things. Working on API docs now so they'll be in beta 4.

Jack

[talekaramit]

Hi Everyone,

Just wanted to let you know that we're listening and trying to catch up on things. Working on API docs now so they'll be in beta 4.

Jack

Jack - Nice to hear about API Docs, needed the most =D>. Any targeted date for beta 4 ?

Amit

[Laurent Bruere]

Hi Everyone,

Just wanted to let you know that we're listening and trying to catch up on things. Working on API docs now so they'll be in beta 4.

Jack

When using ExtNd with IE8 and enabling "show errors" in IE8
there is a few error popups

and in the bottom left, there is a message "errors in page"

Thanks

[jratcliff]

Jack - Nice to hear about API Docs, needed the most =D>. Any targeted date for beta 4 ?

Amit

I'm shooting for December 1st for beta 4 which will include some more fixes AND the api docs. :)

[jratcliff]

When using ExtNd with IE8 and enabling "show errors" in IE8
there is a few error popups

and in the bottom left, there is a message "errors in page"

Thanks

What does the error say? And where does it happen? Is it happening in a custom app of yours? Or the demo app? I can't reproduce anything using IE 8 with error notifications turned on in some custom apps of mine and the demo app.

[Laurent Bruere]

Dear Jack,

I have described the problem in the PDF file (Hmm File limit is low...)

I have also created a login for you to our application to see by yourself if you get the same problem with your version of IE8

Best regards,

[jratcliff]

Dear Jack,

I have described the problem in the PDF file (Hmm File limit is low...)

I have also created a login for you to our application to see by yourself if you get the same problem with your version of IE8

Best regards,

Laurent, I removed your pdf file since it had the url and login info of what you wanted me to look at. I didn't think you also wanted everyone else to see this too. :)

Also, to help trouble shoot this, can you change your code to load the -debug.js versions of the js files?

Thanks!
Jack

[Laurent Bruere]

debug

[bond8]

I can't unzip it,why?

[Zakaroonikov]

I think it has something to do with using IE to download:

http://www.extjs.com/forum/showthread.php?p=391987#post391987

[TY@GP]

I have been testing release 2 in the past and just recently installed version 3. Although there will propable be a lot of changes I do not see a lot of differences from the outside. Can you tell me where I can find information about the release changes, api documentation, etc for release 3.x

[TY@GP]

I have tested the UIView function of release 3.x. Below the list of findings for the UIVIEW.


Multiline view headers are not supported
View header colors are still not supported
View body colors are still not supported
Domino style view sorting (asc, desc, none) is still not supported
Response documents are not shown and the twisty is missing for response documents
Indenting is not correct for response documents
Partial view loading is not supported.
Background view images are not supported


For release 2 I have developed a extension on the uiview. I am currenlty redesigning this extersion to support release 3 and as a plugin.

Below the screenshot to explain the differences

The original R3 look and feed

17879

The Real Domino representation (display via UIVIEW extension)

17880

[TY@GP]

Ik tried to evaluate the multi category function of Release 3.1 but it does not seems to work. An other problem is that it does not remember the multi expand setting so when a view is opened via an outline it used to base gridview which let me only expand a single column.

[jratcliff]

I have observed a bug on right click of UIView. i.e when we right click on documents in UIView Open and Edit options are displayed multiple times. Please find the screenshot of the bug.
:-?

Does this happen in all of your views or just certain views? I've tried to reproduce this without success.

Jack

[R.J]

Dear Jack,

Unfortunately yes it does happen in all my views... :( .... what is the solution to it.. ?

[jratcliff]

I have tested the UIView function of release 3.x. Below the list of findings for the UIVIEW.


Multiline view headers are not supported
View header colors are still not supported
View body colors are still not supported
Domino style view sorting (asc, desc, none) is still not supported
Response documents are not shown and the twisty is missing for response documents
Indenting is not correct for response documents
Partial view loading is not supported.
Background view images are not supported


For release 2 I have developed a extension on the uiview. I am currenlty redesigning this extersion to support release 3 and as a plugin.

Below the screenshot to explain the differences

The original R3 look and feed

17879

The Real Domino representation (display via UIVIEW extension)

17880

Hi TY@GP,

Great job as always! Yes, we still do have this planned as well but it hasn't made it to the top of the priority list yet. However, I do have a question about these items:


Domino style view sorting (asc, desc, none) is still not supported
Response documents are not shown and the twisty is missing for response documents
Indenting is not correct for response documents


We support all three and with my test views they work. Can you give me some more info on what doesn't work in your environment? Maybe if you can even send me a database with views that are setup for these features with a few sample documents that will help me more quickly see what you are seeing and what my test views are not perhaps covering for my test cases.

Thanks!
Jack jackratcliff at gmail dot com

[jratcliff]

Ik tried to evaluate the multi category function of Release 3.1 but it does not seems to work. An other problem is that it does not remember the multi expand setting so when a view is opened via an outline it used to base gridview which let me only expand a single column.

Yes, you are right. We are working on this issue now.

[jratcliff]

Dear Jack,

Unfortunately yes it does happen in all my views... :( .... what is the solution to it.. ?

Hmm, what version of Ext.nd and Domino are you using so I can test against and is there any chance you can send me a stripped down database with just a few views where this happens with a few docs in the db so I can see it and troubleshoot it in my environment.

[R.J]

Dear Jack,

Surely I will create an ntf and will forward you the same on this forum itself.... I am using Ext.nd Beta 3r1 version of Ext.nd which is currently available for download. Between any success on the below Thread ?
http://www.extjs.com/forum/showthread.php?p=422314#post422314

[jratcliff]

Dear Jack,

Surely I will create an ntf and will forward you the same on this forum itself.... I am using Ext.nd Beta 3r1 version of Ext.nd which is currently available for download. Between any success on the below Thread ?
http://www.extjs.com/forum/showthread.php?p=422314#post422314

Thanks! as for the other thread, I think the issue is with the fact that I forgot that 'dbPath' needs to be an absolute path (including the db filename) and therefore you need a beginning and ending forward slash.

Jack

[TY@GP]

Yes, you are right. We are working on this issue now.

I already found the issue. It is working as designed. To open a uiview in categorized mode you need to add the line

Ext.nd.DominoUI({uiOutline : '<outlineName>', viewDefaults: { multiExpand: true}}, uiView: {viewName: '<viewName>', showSearch: true, multiExpand: true}}

to the start page.

[TY@GP]

I checked tried to find the bug why the menuitem are shown twices (the dom tree for the menu tag is not cleared before the context menu is build again). This is not a fix but a workaround.

Solution.

I added the buildMenu function that verifies it a menu item already exists before adding. Below the code.

Just replace the current gridHandleRowContextMenu code with:



buildMenu: function(menu_prop, menu_items) {

var menu = Ext.menu.MenuMgr.get(menu_prop.id);
var b = menu===undefined;
if (b) {
menu = new Ext.menu.Menu(menu_prop);
}

for (var i=0; i<menu_items.length; i++) {
menuitem = menu_items[i];

if (b || menu.find('text', menuitem.text)===undefined) {
menu.add(menuitem);
}
}

return menu;
},

// private
gridHandleRowContextMenu: function(grid, rowIndex, e){
e.stopEvent();

debugger;
var menu=this.buildMenu(
{ id: 'xnd-context-menu'},
[{
editMode: false,
text: 'Open',
handler: this.gridContextMenuOpenDocument,
scope: this
},{
editMode: true,
text: 'Edit',
handler: this.gridContextMenuOpenDocument,
scope: this
}]
);

// tell menu which row is selected and show menu
menu.grid = grid;
menu.rowIndex = rowIndex;
var coords = e.getXY();
menu.showAt([coords[0], coords[1]]);
},

[TY@GP]

I had a look at the categorized view code. This code is currently always using the expand option to build the view. The expand option is very resource consuming for large views because a lot of viewentries that are already in memory are read and translated. By adding the following code it wil only load the childeren form the category you have selected.

Below the code

Just replace

Ext.nd.data.CategorizedStore => loadCategory: function(position, options)

with


loadCategory: function(position, options){

var rec = this.findRecordByPosition(position);
if (!rec.isCategory || rec.childrenRendered) {
return;
}

if (rec==undefined) {
debugger;
//also need to load parent rec, using expand
// TODO: need to add multiExpandCount
this.proxy.doRequest(
'read', // action
null, // record
{
start: position,
expand: position,
//TY@GP Changed, orgininal: count: 60
count: this.defaultExpandCount ? this.defaultExpandCount : 60
}, // params
this.reader, // reader
this.loadCategoryRecords, // callback
this, // scope
Ext.apply({
rec: rec
}, options) // options
);
}
else {
//TY@GP Added only load the required category using navigate/skip navigate (faster and using less resources for large view)
// TODO: need to add multiExpandCount
this.proxy.doRequest(
'read', // action
null, // record
{
start: position+".1",
navigate: 5,
skipnavigate: 6,
count: this.defaultExpandCount ? this.defaultExpandCount : 60
}, // params
this.reader, // reader
this.loadCategoryRecords, // callback
this, // scope
Ext.apply({
rec: rec
}, options) // options
);
}

[jratcliff]

I already found the issue. It is working as designed. To open a uiview in categorized mode you need to add the line

Ext.nd.DominoUI({uiOutline : '<outlineName>', viewDefaults: { multiExpand: true}}, uiView: {viewName: '<viewName>', showSearch: true, multiExpand: true}}

to the start page.

Ahh, yes, setting the multiExpand property to true in the viewDefaults config will set things up so that all views opened from the outline to open using the multi expand view option. However, what I meant what we were working on was the fact that there are several bugs with the multi expand views (such as plus/minus icons not change and documents not opening when you double click on a row). We are working on those issues now (basically rewriting the multi-expand view code).

Jack

[jratcliff]

...(the dom tree for the menu tag is not cleared before the context menu is build again)....

Thank you thank you thank you! I just wasn't paying enough attention to what was going on here. We're building a new menu each and every time when we should first check to see if one already exists and use it instead. This should be an easy fix. Thanks again for troubleshooting this and reporting what you found.

Jack

[jratcliff]

Added only load the required category using navigate/skip navigate (faster and using less resources for large view)


this.proxy.doRequest(
'read', // action
null, // record
{
start: position+".1",
navigate: 5,
skipnavigate: 6,
count: this.defaultExpandCount ? this.defaultExpandCount : 60
}, // params
this.reader, // reader
this.loadCategoryRecords, // callback
this, // scope
Ext.apply({
rec: rec
}, options) // options
);


Do you have any more info on 'navigate' and 'skipnavigate'. What version of Domino were these introduced?

[TY@GP]

Do you have any more info on 'navigate' and 'skipnavigate'. What version of Domino were these introduced?

It was already introduced in domino 6.x. I do not know if there is any formal documentation about this function but I it used by the domino view applet when you click on an expand item. I did tried to test the different skip and skip navigate options but only the skip=5 and navigatie=6 is very usefull.

I did not verify this function using a 8.x server. But works on 6.x, 7.x

[TY@GP]

Ahh, yes, setting the multiExpand property to true in the viewDefaults config will set things up so that all views opened from the outline to open using the multi expand view option. However, what I meant what we were working on was the fact that there are several bugs with the multi expand views (such as plus/minus icons not change and documents not opening when you double click on a row). We are working on those issues now (basically rewriting the multi-expand view code).

Jack

I looked at the openDocument problem, here my analysis.

The on open document is getting the selected document using the ...getStore.itemAt(rowIndex). This is referring to the wrong index when you have expanded a category.

Below the solution to solve this, the only remark I want to make is that this function is building a array to only select one element. This is very resource intensive. So should be refactored to a function that does not build the array first.

getSelectedDocument: function(rowIndex){

var doc;

if (rowIndex) {
//TY§GP replace => doc = this.getStore().getAt(rowIndex);
doc = this.getStore().findRecordByIndex(rowIndex);
} else {

var sm = this.getSelectionModel();
var selections = sm.selections;

// use itemAt(selections.length-1) to get the last row/doc selected
doc = sm.selections.itemAt(selections.length-1);
}

if (doc && doc.unid) {
return doc;
} else {
return undefined;
}
},

[TY@GP]

Ahh, yes, setting the multiExpand property to true in the viewDefaults config will set things up so that all views opened from the outline to open using the multi expand view option. However, what I meant what we were working on was the fact that there are several bugs with the multi expand views (such as plus/minus icons not change and documents not opening when you double click on a row). We are working on those issues now (basically rewriting the multi-expand view code).

Jack

Hi, Jack, I have tried to analyse the problems you descibed in your chat. I have refactored the dominorenderer so it fully support multi categorized views.

This code fixes the following issues
1) DblClick issue
2) Twisty issue
3) Domino color/style support
4) Indenting of response columns
5) Double context edit menuitems

Its set the default view mode also to categorizedView because is it must user friendly.

Below the code, I added the tag //TY@GP ... to every change I have made. Maybe you can use the code for the next release

18285

[anba2404]

Hy TY@GP, I tried to compile and compress your files, but there seem to be syntax errors.
Can you help or even publish the file 'extnd-all.js'?
Thank you. Andrea

[TY@GP]

I have been offline for a few months, do you still need this update. Because I wil check what typo's are in the code.

[deedllit]

Hi, I am trying to use a datawriter with ExtJs 3.3.1 on a Lotus Domino 8.5.2 server.
When I get the data they are encoded, if decoded them I got some strange sometimes.

It is possible to use Datawriter with lotus notes agent ?

Someone can share a sample ?

Thank you

[ferg]

Hi
could someone please write up a simple step by step guide to installing this?

For someone with zero experience here that would be of great help!


what I did so far is,
download and extract Ext.nd Beta 3r1 to my notes\data folder.
ran "Ext.nd.Profile" in a web browser;
location of = "C:\Program Files (x86)\IBM\Lotus\Notes\Data"
Ext version set to 3.x

I am getting the line 41 error discussed on the first page