Just got back from a nice trip to the beach. I'm feeling refreshed and energized. Before I had left on vacation I had been working on refactoring all of my code for Domino Web Views/Outlines into custom JavaScript Objects. I plan on finishing this by the weekend but I need some ideas of what to work on next. I thought about fixing the code so that you can have "portal views". I would use Ajax techniques to allow the developers to layout a web page to include more than one view. Another thought would be to add support for calendar views. What's your vote?
I vote for Flash Action Scripting that will allow the data to be pulled into a Beautiful Flash Front End GUI!!!! :)
(Though I don't really know what you are talking about!)
Hey Jack,
Don't work too hard on the portal thing -- my code already allows multiple instances of views on one page. When we talk (soon, I'm hoping) I can show you how all of that works in my solution and show you everything else it does.
The biggest challenge I see is paging with categorized views, particularly when taking readers fields into account. Bob's navigator is awesome for flat views, but obviously doesn't work for categorized views at all.
The trick is *determining* how many viewentries (and therefore pages) are available to the user. Here's some hidden tricks I've discovered by sniffing the packets from the Java applet:
1. "rangeentries" - *this* tells you how many entries are actually visible to the user. Unfortunately the only way to get this attribute returned in the XML is to make a call with both &StartKey AND &UntilKey. You can fairly reliably get an 'all encompasing' range with "&StartKey=&UntilKey=~", but this only works with first-column-is-text views. If there are any "(Not Categorized)" entries, though, they will NOT be returned in the count.
2. "&EndView=1" - apparently this jumps you to the last entry in the view. You could use this to at least get the viewentry number of the entry, and make some half-guess about how many pages of data are in the view.
I'd love to see you focus a bit of time on this problem... I've done a bit of experimenting using LS to help, too, with the NotesViewNavigator class. Getting a count via NotesViewNavigator.AllEntries.Count() is accurate, but unfortunately is *very* slow on a large view. Perhaps limiting the navigator depth would help...
Anyway, if you can solve this problem, then we'll have driven the last nail in the coffin of Domino view navigation.
What i really need is to modify all views in a database.
So the colors, font, actionbuttons etc..
I was trying this with XML export and import but was getting some strange behaviour.
This is absolotaly a must need for all developers
@Erik, I'm pretty close on the portal views but if you'll share your code I'll be glad to work on paging with Categorized views. :)
@Nadeem, can you be more specific? Not sure I understand what you are wanting to do.
Jack
Hi Jack,
I just have read what you want to do next and I am absolutely enthusiastic. Since exactly what you are planing to do (portal views) my boss wants me to do.
My project is that You have one view in one Frame with customers i.e. ,you select one and in the other frames you see views with only the documents of this customer(Single Category). Everything went fine since I had to open the view in an other frame. In the same frame I got single category to run. But now there are problems about the addressing of the HTML Elements since they are no longer document but parent.forms.formname.document.... Can you give me a hint how to start and what I have to do ? Will you do this in the near future.
Thanx a lot and greetings from Germany
Martin
P.S. If Erik can help me pls write to krauss@adv-boeblingen.de