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.
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.
Last edited by giuliocc; 5 Oct 2009 at 10:04 PM.
Reason: Typographical error
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.
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..