You raise lots of good points, some of which I'd thought about and some that I'd not.
I'd not addressed either creating pages via the web service nor by hand in the directory. I agree that there is no recourse for mucking about in the directory. I'll look at the web service thingy. (I keep forgetting that it exists) As for the user that creates a bunch of Topics in a page and then clicks on them to create them, he doesn't worry because if the Formatter doesn't recognize it as a TopicName, then it will not be hyperlinked at all... It will just be text on the page. (This is what happened with names with dashes.) I also think that as of this moment, I've got it too restrictive... I think that there are a few (one comes to mind) that you used to be able to create in 1.8 that you cannot edit. I believe this is addressable where we can make the "edit" lots more accepting than the "create". This, I believe, would address the robustness issues. First there were a couple of types of names that I'd run into or saw on the list. Topic names with dashes and slashes broke in different ways. Topics with dashes would get created just fine, but the Formatter didn't know that they were legal, so it would never render them as a link. Even when you surrounded it with '[' and ']'. Slashes, on the other hand, would cause the app to hurl in the engine in various spots and the topic would never even get created. It turns out that both behaviors could be stopped by checking to see if the Formatter thought they were a good topic, so I just added this check in WikiEdit.ShowEditPage(). Right now, it behaves similar to the authorization checks and lets you get to the edit page, but then has a message indicating that the topic name is not valid. I just tried dots in the name and that causes yet another exception, (everything to the left of the first dot is considered a Namespace, and if it is not found it hurls with a null pointer.) At the minimum, I'll make sure that the dots don't hurl and we get a good message to the user besides a null pointer. All this leads me to a few questions that I think that we need to address. 1) What is a valid TopicName? <- the formatter currently has a definition, but other parts of the engine don't know or care about it. 2) Who owns this information? <- this one is tricky because of the Formatter's parsing. It has to have some sort of Regex definition it can use (right now) 3) What do we want the behavior to be when the user tries to create an topic with an invalid name. <-It currently takes the user to the edit page with the topic text forced to "this is a bad name" and no save button displayed. 4) what should happen when the user tries to create a "bad" topic through the web service? 5) Is there a difference between FW behavior in the case of a bad topic vs. a missing NameSpace? Based on the discussion, I'll create some Tracker issues to deal with these items and address them. -nathan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
