We've been using ScrewTurn quite extensively and are looking to deploy it to
several hundred sites and haven't experienced any crashes or exceptions of
note.
Can you give me an example of how to create one?
Thanks
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Ramseur
Sent: Monday, September 17, 2007 8:14 AM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] ScrewTurn Wiki
Im testing out ScrewTurn and it crashes randomly and gives a lot of null and
thread exceptions. It does have an edge being on 2.0 and very professional.
Also has one of the best admin interfaces ive ever seen in an open source
product. However, I think flexWiki can match and beat it with time.
On 9/17/07, Derek Lakin <[EMAIL PROTECTED]> wrote:
> 6. Allow minor edits with section headers and add a table of contents
> based on these headers. ( e.g. Wikimedia, ST)
We started down this road (Derek, wasn't this you?) but it turns out to be a
pretty big deal because it affects the core, which has been in tiny pieces
for a few years now. I think this should be a lower priority than other
things, because I believe we'll get more bang for our buck elsewhere.
I had an implementation for minor edits for the 1.8 core a long time ago,
and don't have it now. Things have moved on a lot since then, and at the
moment, it would be a large piece of work to implement them. The
implementation I had was simply a check box to flag an edit as being minor,
which would enable filtering of some of the noise for topic history. My
original aim was to enable me to make changes to bliki posts to correct
spelling, for example, without causing that post to float to the top.
The feature did not, and was never intended to, enable editing of sections
within a topic. That would be a completely separate feature, that could
probably be achieved much more easily than minor edits, to be honest.
Building a table of contents based on those section headings should also not
be too difficult, and could probably be achieved with WikiTalk (with a few
tweaks).
> 9. Incorporate a developer blog focused on users instead of code.
> I think a lot of the deficiencies of FW are simply perceptions based on
> the current discussions and the poor physical design of FlexWiki.com
> (straight from 1994). If you take a deeper look at FW you will see
> that it is extremely flexible and powerful. Unfortunately, perceptions
> do matter.
Agreed. I blog about FlexWiki occasionally on my personal blog, but it's
hardly a "this week in FlexWiki", and it doesn't include any of the other
developers. How would you suggest we handle this one? We could probably get
a CommunityServer instance or something going on www.flexwiki.com.
This is something that could easily be achieved by using the BlikiLibrary
(something which I'm considering contributing to SVN to make it more easily
available to anyone that wants it) and could perhaps be implemented in a
separate namespace on flexwiki.com.
-------------------------------------------------------------------------
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
<https://lists.sourceforge.net/lists/listinfo/flexwiki-users>
--
Regards,
Eric Ramseur
Rainbow Portal 2.0 Admin
community.rainbowportal.net | rainbowportal.net
http://www.linkedin.com/pub/0/430/214
-------------------------------------------------------------------------
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
