On Tue, Jun 8, 2010 at 12:06 AM, Olemis Lang <[email protected]> wrote: > On Mon, Jun 7, 2010 at 3:49 PM, Roger Oberholtzer > <[email protected]> wrote: >> On Mon, 2010-06-07 at 15:00 -0500, Olemis Lang wrote: >> >>> To be more precise , everything should look similar to this plugin , >>> but for editing wiki pages instead of tickets . >>> >>> http://trac-hacks.org/wiki/VisualBasicTracConnectorIntegration >>> >>> That's pretty close to the kind of integration they demand ;o) >> >> Perhaps something in http://www.alfresco.com/ >> >> Since everything is stored and managed in Trac, I am curious what MS >> Office/Sharepoint add, other than an incompatible gorilla of a WYSIWYG >> editor. > > It's the text editor they prefer . JFTR, I don't even use MS Word ... > >> If it is the WYSIWYG aspect, then I do not think Sharepoint is >> relevant. > > What'd be nice is not to conflict with their habits, especially 'cause > there's this MOSS thing that works the way they want (even if they > probably were not able to even think about what they really wanted ... > ). That's what they do since long time ago, so it's kind of hard-wired > in their brains , hence it's hard for them to change . > >> Since Trac does not use MS Office formatting, even the WYSIWYG >> part is pretty useless. >> > > This group is quite reluctant to change ... nothing I can do > :( > > Customers are always right > ;o)
Of course I don't know anything about the environment you're talking about and those users, but at least from what you describe, it sounds like MOSS gives them what they need, so why change? maybe they really don't need trac? Just to be clear, I'm not saying MOSS is better than Trac (I actually don't think they serve the exact same need), but from my experience with a user-base that have "good enough" toolset, if you try to force on them something else, they will learn to hate it, even if it *is* better... > > -- > Regards, > > Olemis. > > Blog ES: http://simelo-es.blogspot.com/ > Blog EN: http://simelo-en.blogspot.com/ > > Featured article: > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > moving back to the main topic, in my organization, where I'm working on deploying Trac, the wiki editor is a problem (not all users are technical, and even the technical ones are not too happy with text-editor wiki-syntax), and the wysiwyg plugin is not a usable solution for us (as it has no right-to-left support (there's a TH ticket regarding this)). Ideally, some external wiki wysiwyg editor would be a perfect solution, a-la wysiwyg-plugin-on-speed-as-ms-office-extension, but a good in-browser editor (like CKEditor, that has right-to-left support) will also do. But in order to be useful enough, it will have to deal with macro expansion and plugin-manipulation of the wiki content, support advanced formatting (including complex tables), and supply a very convenient user interface (for example - entering Trac links by selecting a target page from a dynamically populated title-index, recognizing inter-trac and inter-map-txt, etc...), which is quite complex. I think this is important enough for us to put in some development effort (after I sell it to management), but as the most Trac-aware user in the organization, I am not enough to lead this effort... Is there any interest in something like this from more proficient users / developers, who will be willing to participate / lead such an effort? Itamar. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
