If it is a stable as 1.0, then let me be the first in line!
You have done a wonderful job so far, and if you need any help with ASP coding or interfacing, just let me know!
Is it somewhere near the end of this month or are we talking about december?
I'm especially interested in fixing the position of multiple colums when you scroll to right/left.
We need a grid which works exactly like this one only with few fixed colums. We are defining the functional design a this moment.
tnx in advance!
its more likely for the alpha to be in December and then 2-3 months before the final release. So far I can confirm that multiple fixed columns (on the left) and grid footer will be available in 2.0.
Does anybody need also fixed columns on the right :-) ?
I'm currently working on a very large project (Requirements Gathering and some Prototyping) where this grid may be used. There are a couple of situations where fixed columns on the right would be useful. Also, do you plan to have ToolTipâs available within the grid? Some of the fields we would be working with are quite large and a ToolTips would come in handy.
I haven't had a lot of time to do investigating, but does version 1.0 have automatic paging capabilities when row counts exceed a certain limit?
Now if there was a navigator control that could be linked to the grid that had the ability to use custom code for the PageUp and PageDown buttons, this might be cool. I have one written for a grid that I wrote, I'll see what I can do to create it using the toolkit and post it for everyone.
but I hesitate to use it and therefore to buy because of the lack of maintenance (no new version since more then one year).
CAn we obtain some information? how many developers? forcast date of new release? ...
Please don't forget that this is 'work in progress' and not even alpha yet. The timescales are available on the '2.0 status page':
That is one thing I think many people could use.
Wider browser support is one of the things that makes 2.0. It is a new generation tool that is requiring a lot of changes. Developers don't like to move backward, when you introduce new features (IE new browser support) you release them in new versions. Supporting Opera and the other esoteric browsers is NOT easy. I am surprised Alex is even going to be able to support them. As a developer myself, I know how strange Opera is and how hard it is going to be for Alex to support it. My vote is for the new features first, Opera support later. It is better, in my opinion, to have a great application (I don't do web pages, I do web applications) that can do more and simply tell the clients that not all browsers are supported. Believe me, they understand. Currently, my application only works on IE (not a limitation due to AW, but a limitation in some code I am using) and I have only had one person even want to use it on anything else and that was FireFox.
The more I read this thread, and others, I see that everyone wants everything and they want it yesterday. Alex is not a huge corporation but is doing quality work in spite of it. He puts out the features that people request as soon as humanly possible. So let him do his work, get the next version out. And then we can all sit back, evaluate that version, and make suggestions on how that version can be improved.
If you want to see features included in future releases, I suggest making a monetary donation to the cause. Nothing speaks louder then money.
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.