How do I categorize views properly in xpages.using the standard notes views and embedded views in a page, I can show a view in a nicely formatted categorized view…
ie…
{cat1}
-----(cat2)…
---------(cat3)…
----------------doc1
----------------doc2
----------------etc,etc
But with Xpages, using the view control I cannot get anything to work and reproduce the same result.
what I’m getting is a table and data is evenly spread,by column, across the table.
…CAT1…Cat2…Cat3…
ontop of that, my categories are even word wrapped on me and I can’t find the property to stop that!..
iie…
{Category 1} (what it should be)
{cate
gory 1} (this is what happpens no matter what column sizes I set.).
Can anyone advise me on this please?
I can find nothing on the domino wiki, execept for straight static views (also in the tutorial), and the view control panel seems to ignore the actual view layouts by category…
I’m so confused with this…
Subject: Interesting … I simply select a categorized View…
-
It should take a coon’s age, then pop a list where you can select what columns to show. Make sure you include columns that are actually categorized. I wound up creating special categorized Views just for my XPages, but not because categorization wouldn’t work. I had to limit my columns for XPages vs Notes and that was the simplest route, simpler even than not selecting some of them.
-
This also appears to use the “programmtic name” on the last tab of the view column, not the Notesy name on the first tab, so bunches of them will appear as $number instead of anything useful. To fix that go to your View and make sure the “programmatic name” has a value that makes sense.
-
Otherwise it just works, at least for basic categorization. There are zillions of other things wrong with categorized Views, but plain-jane display with twisties seems fine. Not sure why you don’t see that.
Hope this helps…
Subject: There are formatting issues
The width of the columns are not right. The entries under the categories are usually too far to the right (they take up the entire category column width.) I have reported this as a bug, but, no plans to fix in 8.5.2 to my knowledge.
There is a fix for Firefox for this but it does not work in IE 6 and 7. Just add a style to the style property for the categorized column.
width:10px; white-space:nowrap
Howard
Subject: Fix not available for IE
Yea… your post is exactly what Lotus Support said…
Problem is we are a IE house…so this really screws the pooch… (affects IE8 also!).
Google Chrome and Firefox is absolutely what one would expect…
Subject: I don’t see this particular formatting issue…
-
Exploiter 8 works just like FireFox (for me), except half the column icons appear as broken images, but that could be my code not creating the src= in way that exploiter is happy with. 6 works just like 8 except it puts the content below the navigator instead of beside it, but 7 does the same, so I would call this a render bug in exploiter long before I’d ding Domino on it.
-
Nothing looks out of place on the content in any browser, however (other than icon images). Category headings take up the full width, with a twistie on the left, and data rows under the headings look completely normal in all respects, complete with alternating row colors.
-
This is on R8.5.1FP2 on windoze “server” 2003, 32-bit, two cores, 2GB RAM, cleaned-installed OS & Domino about ten days ago. I don’t recall any difference in this with FP1.
-
I studiously avoided the Lotusy viewPanel prior to that, because the mere idea that I’d want to create a separate XPage (or custom control) for each and every one of the dozens of user-accessible views in this application is unbridled lunacy.
-
Not saying you don’t see something completely different, or that no issue exists. I’m merely reporting my own observations as another data point. Believe you me I’ve been on the other end of that stick more often than not.
Hope this helps…
Subject: Here it is…
In IE 6:
Using Firefox with the fix I noted:
Subject: LOL “Unbridled lunacy”
Made my morning.
Subject: Categorised Views and Column
As far as I understand it, the formatting is logical, in that the view is rendered using a table. That means Cat1 is in the cell in column 1 of row 1. Cat2 is in the cell in column 2 of row 2. There is no inbuilt functionality for the value to span multiple columns, which is effectively what you see in the Notes Client. It should be possible to do it though, whether that’s manipulating the table produced or using a repeat control.
Subject: *I disagree, there is an issue here…
Subject: What’s this, then?
- My Lotusy viewPanel renders a categorized view like this:
- If I didn’t know better I’d say this was doing colspan natively, which would explain why it works for me in all browsers. I’d also say this puts COBOL to shame for verbosity required to present 24 characters to the user.
What does your page source say, Howard?..
Subject: Am I the only one who thinks this?
The XPages concept was all the rage when IBM first announced it. FINALLY, we would be able to do traditional advanced web development with Domino. Now, I feel they really should take a line from the first Spiderman movie and go “back to formula” and just start over with it entirely. There are a lot of things in the concept that I like. The implementation of most of them is basically horrible. Too many things undocumented is a big part of the problem. There is nothing out there at all from IBM beyond the wikis. They should have had a detailed Redbook ready to go when the product launched. One that FOCUSED on new things… like XPages. I recall reading a review of a book two IBM employees put out about 8.51 and it had a very high-level, very brief mention of the concept and that was it. XPages can be powerful, yes, but for the most part, I don’t eve think they’re worth the effort. I’d rather jump through hoops using the traditional hoops in Domino that we’re all familiar with than have to learn new hoops to jump through for an unproven technology. Which, not to make too fine a point on it, sucks at doing a great many things. I can’t believe the hoops you have to go through just to show/hide data using strictly client/side javascript. Whose bright idea was it to write the hide-whens on an XPage based on data returned from the server by default? If they wanted to make an interface that allowed for more modern web development, then that’s what IBM should have done. I will give them kudos for the inclusion of dojo, but then USE it. All the native things in XPages (and I’m going to harp on the visibile/not visible issue here again) should be done in the most efficient manner possible and give the developer the most control possible. MAINLY THERE SHOULD BE AN EXTENSIVE DEVELOPMENT GUIDE OUT BY NOW. Ok, I’m done ranting.
Subject: Lack of documention
IBM created this new beast called Xpages, it will take us months to control and tame with many hrs of frustration and a very steep learning curve.
I just came back from the Eview conference in Boston. I was hoping to get a quick start on Xpages. Not a chance. Speakers kindly reminded us that Xpages is evolving, and that it will take several months to get as good as we are with the existing development techniques.
Now with all the BLOGS around the World, you will only learn new things if you know who is who in Xpages. I wish all the Domino Gurus out there, would centralize their knowledge in one single repository. Yes, add link to their own blog if they wish, but man, post the good stuff in one place for all of us that are trying to learn it!
