Hi, I am wondering if this project is still being actively maintained?
There seems to be very little activity on it for some time, and the next release branch seems to have ground to a halt.
Im hoping to use this control in a new project, and this will likely result in me fixing a few bugs along the way, but if everyone has abandoned it, Id rather reconsider. If its still active, could I be added as an svn writer please
Thanks
Carpii
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The guy you need to contact to get write permission to the code repository is "adambl" at CP
The trunk was last updated 5 weeks ago - that's pretty recent, last post at CP was just last Wednesday
The version labeled "Next Release" more or less ended up being owned by "stovsey" (CP id), I've no idea where he's at these days. I suspect like me he's taken XPTable so far away from the trunk that he no considers it worth his while maintaining a version on SF in which few seem interested.
I went my own way with XPTable, I wanted to exploit Net 3.5 and use VS2008 features, others were targeting NET 1.1 and 2.0 using VS2003 - it got too hard trying to find a common base especially as there were only 2 other people and a 12 hour time difference between them and me. I used themes, generics and the new event processing models plus laying the foundations for the introduction of a 3rd dimension before turning over the source to my now former client. I threw away a lot more code than I added - mainly because of the extensive use of generics, the new event management techniques in VS2008 and ditching all the WIN32 stuff and the Adobe knock offs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have contacted adam as you suggested. Hopefully he will be able to give me access, even if its just to fix a few minor bugs.
The stock controls in .NET are really rather basic, and so it would be a shame to see this control just fade away. It still has a lot of potential as an open source project I think. Maybe it just needs new blood and a tidy up of the repo.
One of my secondary priorities is to target Mono. I dont know how realistic this is yet, but I imagine of of the first things Ill need to do is to strip out all the WIN32 code, as you did. Any help you can offer with that would be much appreciated.
Thanks
Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How far have you been into making XPTable win32-independent? The applications in our company are supposed to target both .NEt and Mono, and that would be really cool to have XPTable in them!
Any news appreciated,
Regards,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes - I still regard this as an active project, although it has reached a fairly stable state now and the rate of change has slowed. As far as I can see that is because it seems to do the job. If you have any new ideas for development please share them.
As to taking out Win32 stuff, I did have that down as one of my goals, but because it would mean taking out some functionality (i.e. themes support) I left it in. I'm sure you can refactor it so that the themes are suppoirted by some kind of plug-in, but I didn't have a pressing need to do it and other things took my attention. I would be interested to see how you got on with removing it.
(Carpathia - I haven't noticed you trying to contact me, how were you doing it? As mentioned above, I look at the CP page more often than the SF page.)
Adam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you could implement a plugin architecture to replace XPTable's themes,
However the XPTable's themes are very close match to the .NET's theme component, so why not simply replace XPTables methods, definitions etc with the equivalents from System.Windows.Forms.VisualStyles. That's what I did, which meant I was able to scrap the entire contents of the Themes folder - the xxxParts and xxxStates modules each have 1:1 .NET 2.0 equivalent.
To get rid of WIN32 you also need to replace the Drop Down Editor and its Date and Color derivatives with NET 2.0's UIEditor and its derivatives for Date & Color - which means you also get the file and folder editors for free.
XPTable's Drop Down Editor is NOT a clone of 'NET 2.0's UIEditor, whereas XPTable's Themes is a clone of NET 2.0's Visual Styles. Thus the Themes stuff is a doddle once one takes one's blinkers off, whereas the Drop Down replacement requires a bit of thought.
Weeks work for a half decent prog, including test and doco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> How far have you been into making XPTable win32-independent?
> The applications in our company are supposed to target both .NEt and Mono, and that
> would be really cool to have XPTable in them!
Hi Lionel, not very well Im afraid :(
My intention was to port XPtable to MONO, so that I could write software on linux and have it work on both .NET linux and .NET Windows.
However, I hit a series of problems which left me feeling MONO is not really mature enough for my project, and in the end I decided to write my project as web based app. This wasnt really to do with XPTable, but more to do with the MONO development environment, and MONO as a platform
So thanks for the help everyone, Im sorry I wasnt able to contribute like I originally intended
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I am wondering if this project is still being actively maintained?
There seems to be very little activity on it for some time, and the next release branch seems to have ground to a halt.
Im hoping to use this control in a new project, and this will likely result in me fixing a few bugs along the way, but if everyone has abandoned it, Id rather reconsider. If its still active, could I be added as an svn writer please
Thanks
Carpii
XPTable happens here -- http://www.codeproject.com/KB/list/XPTableListViewUpdate.aspx
The guy you need to contact to get write permission to the code repository is "adambl" at CP
The trunk was last updated 5 weeks ago - that's pretty recent, last post at CP was just last Wednesday
The version labeled "Next Release" more or less ended up being owned by "stovsey" (CP id), I've no idea where he's at these days. I suspect like me he's taken XPTable so far away from the trunk that he no considers it worth his while maintaining a version on SF in which few seem interested.
I went my own way with XPTable, I wanted to exploit Net 3.5 and use VS2008 features, others were targeting NET 1.1 and 2.0 using VS2003 - it got too hard trying to find a common base especially as there were only 2 other people and a 12 hour time difference between them and me. I used themes, generics and the new event processing models plus laying the foundations for the introduction of a 3rd dimension before turning over the source to my now former client. I threw away a lot more code than I added - mainly because of the extensive use of generics, the new event management techniques in VS2008 and ditching all the WIN32 stuff and the Adobe knock offs.
Hi Phil, many thanks for the reply.
I have contacted adam as you suggested. Hopefully he will be able to give me access, even if its just to fix a few minor bugs.
The stock controls in .NET are really rather basic, and so it would be a shame to see this control just fade away. It still has a lot of potential as an open source project I think. Maybe it just needs new blood and a tidy up of the repo.
One of my secondary priorities is to target Mono. I dont know how realistic this is yet, but I imagine of of the first things Ill need to do is to strip out all the WIN32 code, as you did. Any help you can offer with that would be much appreciated.
Thanks
Paul
Hello Paul,
How far have you been into making XPTable win32-independent? The applications in our company are supposed to target both .NEt and Mono, and that would be really cool to have XPTable in them!
Any news appreciated,
Regards,
Hi,
Yes - I still regard this as an active project, although it has reached a fairly stable state now and the rate of change has slowed. As far as I can see that is because it seems to do the job. If you have any new ideas for development please share them.
As to taking out Win32 stuff, I did have that down as one of my goals, but because it would mean taking out some functionality (i.e. themes support) I left it in. I'm sure you can refactor it so that the themes are suppoirted by some kind of plug-in, but I didn't have a pressing need to do it and other things took my attention. I would be interested to see how you got on with removing it.
(Carpathia - I haven't noticed you trying to contact me, how were you doing it? As mentioned above, I look at the CP page more often than the SF page.)
Adam
gDay Adam
you could implement a plugin architecture to replace XPTable's themes,
However the XPTable's themes are very close match to the .NET's theme component, so why not simply replace XPTables methods, definitions etc with the equivalents from System.Windows.Forms.VisualStyles. That's what I did, which meant I was able to scrap the entire contents of the Themes folder - the xxxParts and xxxStates modules each have 1:1 .NET 2.0 equivalent.
To get rid of WIN32 you also need to replace the Drop Down Editor and its Date and Color derivatives with NET 2.0's UIEditor and its derivatives for Date & Color - which means you also get the file and folder editors for free.
XPTable's Drop Down Editor is NOT a clone of 'NET 2.0's UIEditor, whereas XPTable's Themes is a clone of NET 2.0's Visual Styles. Thus the Themes stuff is a doddle once one takes one's blinkers off, whereas the Drop Down replacement requires a bit of thought.
Weeks work for a half decent prog, including test and doco
> Hello Paul,
> How far have you been into making XPTable win32-independent?
> The applications in our company are supposed to target both .NEt and Mono, and that
> would be really cool to have XPTable in them!
Hi Lionel, not very well Im afraid :(
My intention was to port XPtable to MONO, so that I could write software on linux and have it work on both .NET linux and .NET Windows.
However, I hit a series of problems which left me feeling MONO is not really mature enough for my project, and in the end I decided to write my project as web based app. This wasnt really to do with XPTable, but more to do with the MONO development environment, and MONO as a platform
So thanks for the help everyone, Im sorry I wasnt able to contribute like I originally intended