I'm also using a WebSession-like base class in all of my Lotusscript agents. One of the problems I ran into to was that in different functions/subs I needed a handle to the same view(s).

Instead of adding variables to the base class for every view I needed, I added a private list variable to the class and added a function to retrieve a view. In the function I check if the specified view was retrieved previously. If it is, the existing handle is returned. If it´s not, the view is retrieved, added to the list and than returned:

retrievedViews_ List As NotesView

Public Function getView( strViewName$ ) As NotesView

If Not Iselement( Me.retrievedViews_( strViewName ) ) Then

Set Me.retrievedViews_( strViewName) = Me.db.GetView( strViewName )

End If

Set getView = Me.retrievedViews_( strViewName )

End Function

(Me.db is a private NotesDatabase variable filled with the current database when instantiating the class)

Besides views you can also use this solution for documents or database handles you need in multiple locations. The getView function can also easily be extended to retrieve views from other databases.

Sorry, didn't mean to be freaky-boy. I just

have really poor memory-retention, as in

I remember only really useless information.

Great for quizzes, not so great for web dev.

FYI, Paul is the MD of the company I work

for. I have expressed my opinions about

getting you on board, should the opportunity

arise. :]

Had an email from a Paul Rameell the other day. Friend of yours?

Thought it might have been a bit too simple. Doh.

Not sure it needs discarding though if it's out of data. Still applies to new versions in this case.

If it does, I guess you could add a "version" attribute to know whether or not to discard it if it's out of date.

Paging is a big one - though working on a solution I will share once done.

Security - both on documents and columns.

Yes Readers fields will block the actual document appearing but what about the ability to delete / edit? Would rather enable / disable in the Flex app before the server returns the not authorised error.

Pass the double click event on the datagrid out to Javascript in the holding HTML page - for a hybrid Flex / Domino App the actual form may stay as a Domino page. This means the Grid becomes a component within a Domino application to replace the view(s) but the rest remains the same initially.

Features which would be nice to have:

Multi row select / select all, Hyperlink column type (e.g. http & mailto), Thumbnail column type, trashcan to delete (if authorised), individual columns editable.

BTW: You might want to read this too:

http://codestore.net/store.nsf/unid/BLOG-20100303-0114

I'm going to take this, throw in some wrapper code for error trapping (using Julian Rubichaux's OpenLog.ntf), and plunk into our Master Design Elements Template, which we deploy to all our other applications.

Thanks for all your hard work!

John

http://www.codestore.net/store.nsf/unid/BLOG-20100210-0329/

Thanks in advance,

JD