Summary

So, FlexWiki has bugs. And lots of feature requests. That's OK, because it's been a beta-quality release for a while. It's time to change that.

And we want your help.

Along with getting a SolidRelease out of this process, you'll get the chance to learn the FlexWiki code base. I (DavidOrnstein) will be actively working on this project and if you're helping out, I'll be much more willing and able to take the extra time needed to help you learn about (the insides of) FlexWiki

Process

Here's the stages in this project:

What You Can Do Now

Here's how you can be helpful right now:

• Update this page and related pages with your ideas about the SolidRelease project
• Especially -- help us with the stages that are listed above as underway
• Join the FlexWikiUsersList and FlexWikiDevelopersList where we'll be talking about this project
• Become a FlexWiki developer (read how to become a contributor)
• Start fixing bugs or adding features!

So, is there still a drive to do this? I haven't seen many changes on this page recently.

I believe there is but after reading the e-mail list, it appears Craig is the only person working on the code at this time and he said he can't put a lot of time into it. Despite the problems with the code, I'm still using it but I can't help because I'm not familiar with .NET. I think .NET, however powerful, has slowed down a lot of development on the internet because it's very complex. FlexWiki may be a victim of this complexity. I hope not. There are lots of Microsoft people involved with this but none of them have committed to working on it. Perhaps we can convince them to help. See: MicrosoftTeam for members of FlexWiki who also work at Microsoft.

2005-10-25

I was wondering the same things. Microsoft makes a splash in the open source pond and then appears to walk away from it. It appears I'm on a more current version (1.8.0.1677) than the FW site itself (1.8.0.1673). I get the feeling they have other more important moneymaking things to work on. As a developer, it's a little difficult for me to get motivated to contribute if the champion of a product is off somewhere in his manager's "real world" working on some driver code or something. My workgroup uses FlexWiki for collaboration and it suffices but could be better. Ah well. It was (and is) a usable hunk of software. I guess we'll use it until it quits working or something else grabs our attention. As for the "drive to version two", just like these guys, I have revenue-generating projects to work on, mouths to feed, and bills to pay. I'll check back in a couple months and see if anyone's picked up the ball. I get the bad feeling that FW has just about run it's trial course, scratched someone's itch, and already served it's purpose. I'm guessing that only the guy with the original idea had the interest of the product itself at heart. Everyone else had to be sold on it for other reasons like getting open source toes wet or proving .net's worth both to themselves and to the rest of the world. So now one guy's left holding the application and everyone else appears to have moved on. Jeez. How many times have I seen this happen... Does the heart of FW still beat or is it a corpse??

Wes Williamson

2005-11-01

"FlexWiki - words in action"... where's the action?

//Aha... I see Craig is busy doing a full rewrite for .NET 2.0 as one of his low-priority projects, due sometime in 2006.//

2005-11-08

I think this project has some wind in its sails still. Word needs to get out; mediawiki just doesn't cut it for larger implementations (see load time on the wikipedia home page). I am a new user, and developer-in-waiting, and I had to search long and hard to find a reference to this project.

2006-03-08

Any plans to port this project to the 2.0 CLR? Any reasons why not to?

Patrick Altman

-- good work

2006-01-08

I think this project is good.

I'm a VisualCSharp Developer and I'm new in ASP.NET.

I may add for example Tab Pages to the Project or other features on the next, but I prefer to work with JavaScript for doing several tasks.

I'm developing a two application and i'll try to merge them together: the first one is a DataBase application, the second one

is a Web application.

My prevalent interests are in standalone applications for security reasons and so i haven't got time to try ASP.NET.

I think that ASP.NET is complex expecially because the Web component aren't modular like black boxes.

I've seen several progress in VS2005 but at the moment I'll not to buy it for bugs, it's a Statistical evidency.

FlexWiki is good for me, because with simple editing work, I build ASP.NET pages.

At the moment I may test the application, but I have to do a lot of work for my own and so I prefer

to build a JavaScript application that's called from Your ASPNET pages.

In the future I would like to merge several technologies for make a very complex and stable interface in one place.

I would like to learn more about FlexWiki integration with SQL Server 2000 or later.

I see that FlexWiki work on files ... mmm ... I think it's a good idea for having a Portable Platform.

I'll work to integrate XML files with SQL Server 2000.

I'd made a centralized application for managing XML, FW Files encapsulated in a SQL Server repository.

I'm searching documentation about FW (FlexWiki) and about Flexwikipedians people around the world. It's so funny!

Good work

P.C. DevItaly

I think we should make it more useable,FlexWiki make many people crazy ,A good software must have a good user interface. ---wsoangel