Here's my list in no particular order:

* Custom NET Authentication Provider Support

* Improved DNN integration (some custom DNN controls)

* DB class converted to an interface for third-party support of other databases (MSSQL is going to be our only officially support DB -- but it won't be hard to add support for other DBs if someone desires)

* Full conversion to NET v2.0. This means:

* Using Themes System

* Code being moving into partial classes

* More .NET v2.0 specific niceties maybe

* Much improved theme system.

* Redo page HTML and convert it to XHTML using CSS instead of tables – allow for much improved cross-platform support (just change CSS)

* URL re-writing system for improved search engine visibility

* “Archive” catalog system for search engines (all posts/topics in simple formatting)

* Improved User admin

* Help System

* Quick Reply thing

* Collapsible everything

* Documentation!

Just a few notes:

My resources are limited and I don’t even have an install of VS 2003 anymore to work on NET v1.1. So development on my end is already moving to a YAF for v2.0 only. But, I have no problem with someone coming on board and keeping the NET v1.1 of YAF in sync – it’s just that I’m not going to do it.

Thanks for any help anyone can provide. Even if it’s just modifying ONE page of HTML and converting it to XHTML – it’s appreciated.

Nevertheless, the applications are independent, although they can share users, roles, etc.

YAF is an application that works very well alone, but integration with other applications (DNN for example) is limited and is necessary to prepare it (to create integration modules).

A change of architecture, that could not be very expensive, could obtain the use of YAF in any application.

This change would be simply to divide the present application in two projects:

:!: One would be a library of controls, with the forum core and all its functionality.

:!: The second would be a project Web, a simple layer of presentation, that uses the controls and library of the YAF core.

This way, YAF working alone, would be as present and the motor of YAF could be used in any application very easily.

I was giving it much thouht recenty, when I was trying to convert a phpBB theme with little success.

I believe that we could overcome both issues if the crucial content-displaying pages would produce XML output formated with XSL.

Basicaly, XML contains data, and XSL fotmating.

XSL pages should be a part of theme.

That way, the designer gets all the data he needs, formats it any way he finds appropriate without modifiying core ASPX.

For example: now, if you want for some reason to disable private messages, or quotes, or you just dont want to see other ppl's signatures or avatars, you would nead to modify your files and create de facto your own private version of YAF.

If we use XML/XSL model, you'd just create a new theme file striped of the things you don't need.

XML + Aural CSS could also make reading the forum easier for the (visually impaired) people who use screen readers.

XML/XSL model would facilitate reading forum on other devices - primarily the mobile ones with smaller displays.

I believe most of you know what are XML and XSL. In a nutshell - XML acts like a database table in a file. It is interpreted on user's machine using the instructions from XLS file. The XSL file reads the data from XML an places XHTML tags around it.

My two cents: (also in random order; in adittion to those already mentioned)

* Fixing the known JavaScript code insertion issues

* to cleanse the code from hard-coded text, so the forum could be fully localised (just 3-4 places)

* export/import of dirty words filter. Also extend the filter to signatures and all the user input fields.

* minor tuning of the default forum installation settings (The avatars, smilies, No Acess Acess mask, version name...)

* Advanced search

* Turn "Host settings" to "Board settings" - now this one is big. If you need to run more (and more) separate independent boards, centralized managemend turns into a nightmare. The brute force solution of installing yet another instance of YAF could be avoided if what the settings currently located in "Host settings" could apply to single board.

* E-mail templates need to be linked to a custom board too! I was quite embarrased when a user subscribed to a topci in Board B got the email notification apparently from the Board A.

* "Ignore list" for pm molesters.

* differentiate Sticky and Announcement

* introduction of separate "display name". Appart from the fact that the username makes 50% of someones identity in the 'eyes' of the server, the separate display name would facilitate automatic generation of usernames and passwords for large amounts of users.

* Bulk import of users

* moving posts to other topics.

* fixing the minor "move topic" issues (moderators can move topics to forums they have no moderator rights; the Moved topic pointer remains even if the topic is returned to the original forum; the Moved topic pointer remains after "Show Moved Topics" is unchecked)

Regardless of the development ideas, I think we need some kind of goal - what we want YAF to be, and why are we making it. A mision statement.

If we want the fastest and the most robust board system on the net, or, if we want to have more instalations than any other board system on the net, or if we want the most disabled-friendly BS, or if we want the BS with the most supported languages on the net, will strongly influence which development ideas are more important than others.

Thank you for your time reading this.

I don't think XSLT is right for this forum, unfortunately. XSLT doesn't allow a real way to create ASP.NET controls. It can be done, of course, but it would look pretty strange. I like XML, but that's not what the system produces right now. That could change but you'd be giving up functionality as well as addition flexability.

ASP.NET controls don't work seamlessly with XSLT transformed data -- not even sure how'd you do databinding -- but I can imagine it would be rather complex.

Anyway, I can't say I'm going to go in this direction.

More direction on these suggestions would be appreciated. For the first two -- where are the issues?

I actually started working on this a while ago -- sort of board settings override for host settings. Will put it on the list.

Thanks for these.

I’m not exactly sure at this point. I cannot shoot for it to be the ultimate BB -- I really don't have that kind of time. The problem is there are lots of holes. Frankly, I don't want to fill them all. I am hopeful that a few people (who are very helpful) can help make this thing work good and fill some of these voids. But I am also a very busy man – I just don’t want to see YAF die and I am willing to assist when I can, but not at the expense of my life.

1. JavaScript execution through [IMG] tag as described here 

2.