|
You are assuming there are only 25000 columns, if there are more peaks then there are more columns:
From the author of the thread:
"For 10 peaks Column Count will be 363
For 25 peaks Column Count will be 1608
For 50 peaks Column Count will be 5683
For 100 peaks Column Count will be 21333
For 150 peaks Column Count will be 46983
For 200 peaks Column Count will be 82633 "
So it may be closer to a mile 
Take care,
Tom
-----------------------------------------------
Check out my blog at http://tjoe.wordpress.com
|
|
|
|
|
What the heck is this anyway. The fact that you are trying to view this data it is such an un-normalized fashion completely fascinates me.
Shouldn't you be grouping these things?
General info should be a table
Injection data should be a table
the peaks thing sounds like a function or a set of functions
You should create this databse using meaningful relations. If you need to view dynamics mabye you should apply some differential analysis or maybe use graphs with animation.
Good luck
|
|
|
|
|
Mass Spec?
Anyway - you would need something like a tree to group the data.
You would then only have a constant set of Entries and N Pak-Entries with the Peakinfo underneath.
Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
George Orwell, "Keep the Aspidistra Flying", Opening words
|
|
|
|
|
My current employer hired a contractor who, himself, contracted out some software to India.
It was textbook quality work - in other words, lacking insight. It was, after some debates (read: swallow pride) relegated to the scrap-heap - unused.
This would seem to be an even more extreme (and certainly more amusing) example of meeting design specs as would a thoughtless drone.
Management often seems to have a special skill at managing to muck things up.
First there was a make-or-buy -> make was cheaper
(until they learned that maintainence, custom modifications, upgrades, etc. cost money, too.).
Next, they decided if we have to 'make' our software, let's get it done cheap in some distant land. Turns out that it's not so cheap, after all: once you factor in the extra time in getting the specs understood, and fix after fix on items that should have (would have!) been common sense if it were done home-grown.
Can't wait to see what's next!
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
This is not a management problem. This is a programmer problem. This data is obviously not displayable in the way this programmer is trying to display it. Excel can't even begin to handle that. Anyone that would even consider having a datagrid with 25000 columns, or even 2500 columns, or even 250 columns, is clearly not ready to be doing UI design.
The requirement is NOT to have 25000 columns in a datagrid. The requirement is to give the user access to 25000 peices of heirarchically(sp?) related information. That is more like a treeview or a nested datagrid, or some other type of "drill-down" UI.
Having said all that, if you were to actually try to implement this as a datagrid in a way that was fast enough to use, you would have to virtualize the datagrid so that it loads as the user scrolls, and unloads the portion that has scrolled off-screen.
Standard answer: It can be done in two weeks, provided nothing unexpected happens.
|
|
|
|
|
Actually, we are in agreement on this point. Rereading who I expressed my (two) points, I see how you would have replied as you did. My fault.
The programmer was referred to as a . . . "drone".
The management was being chastised for being concerned with cheap work instead of good work. They really don't understand (why else why would they be managers?) that the body of knowledge gained by experience implimented in a program (or other creative outlet) is a substantial "Value Added".
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
I can't help thinking about a quote from Uncle Bob (Robert C. Martin at ObjectMentor):
When a customer comes up to you with his cell phone and says:
"I need a bigger antenna!"
You should think
"He needs better reception on his cell phone"
and not
"He wants the mother of all cell phone antennas, 'cause it is 15 inches long"
You should always ask yourself, "Why do they want that?", try putting yourself in your customer's shoes.
|
|
|
|
|
I think you really need to review your design.
It's not possible for a human to view that much information all at once, even less to do some sort of analysis on it.
We will need to find better ways to present the results to the users.
|
|
|
|
|
Why don't you try using 25,000 DataGrids with one column each?
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
|
|
|
|
|
|
aloktambi wrote: 25000 columns
 Don't think that is really possible.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Pfft DataGrids cause a localized lowering of the ambient air pressure; I avoid them at all cost. 
|
|
|
|
|
You need to design a custom control, which meets the criteria of you're data you are trying to present. A grid with 25000 columns isn't the way to go, you need a customized grid and when the user scrolls left/right load the columns on demand, it's easy with .net and even easier with WPF. A good software design engineer (cough, cough) such as my self would be able to create such a control (obviously your company would be billed).
WPF - Imagineers Wanted
Follow your nose using DoubleAnimationUsingPath
|
|
|
|
|
The only thing that can possibly handle that amount of columns is Excel 2007 where the column limit has been increased. I think this is your best bet too, in terms of rendering to screen compared to DataGrid.
-- modified at 18:41 Saturday 13th October, 2007
xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."
|
|
|
|
|
May I suggest the following?
1. Have a small fixed number of columns on your screen, say 10.
2. Add two honrizontal arrows on the screen that when clicked would show users the next/previous 10 columns.
|
|
|
|
|
And to get to the middle of the grid, you want the user to click the right arrow button, what, 1,250 times??
|
|
|
|
|
Perhaps a fast forward/backward button would help?
|
|
|
|
|
Even at moving 1,000 columns at a time, that's still 12.5 clicks to see the middle of the table.
No matter how you bandaid this, it's still a horrible "solution".
|
|
|
|
|
Dave Kreskowiak wrote: No matter how you bandaid this, it's still a horrible "solution".
As I recall, the original problem is that the initial poster can't create that many columns in a grid. My "solution" avoids the difficulty of creating that many columns, it is not intended to answer the question of how the hell the users are going to use the application. 
I agree with you that it is a bad design in the first place (that the app needs to create so many columns in a grid).
|
|
|
|
|
Dave Kreskowiak wrote: Even at moving 1,000 columns at a time, that's still 12.5 clicks to see the middle of the table.
No matter how you bandaid this, it's still a horrible "solution".
Not that I advocate continuing on a design path doomed to fail, but you could always have "Jump To" button which would work just fine, maybe even acceptable to a given client assuming it was the same client that came up with 25,000 columns requirement.
|
|
|
|
|
I think you need to re-design your application. Twenty five THOUSAND columns? I'm almost afraid to ask how many rows you anticipate having...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
The obvious solution is to use a virtual table, i.e. only generate the rows and columns that are currently visible on screen.
When the user scrolls this huge table, simply get the values of the visible cells and the visible row/column headers, and display them.
|
|
|
|
|
public static SqlParameter Parameter<t>(string parameterName, DbType parameterType, T value, ParameterDirection direction)
{}
public void SqlParameter Parameter(string parameterName, DbType parameterType, string value, ParameterDirection direction)
{}
Please explain.....
Soniagupta1@yahoo.co.in
Yahoo Messenger Id = soniagupta1
|
|
|
|
|
Sonia - if this is in reply to your other question, please ask this on that thread. It's not good practice to do this. Anyway - to answer your question:
The first Parameter is missing the <T> attribute which marks it out as a generic method. The second Parameter won't actually work because you have void and SqlParameter in the definition. However, if you are talking about the string value portion, the difference is that if you pass in an integer (for instance), you would have to cast this parameter from an integer to a string.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
How To Control Forward and Back Buttons for internet explorer. I wnat when click the back button the appear a message and when click forword button the appear message. in asp.net.
This is possible. then please help me anybody.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
