I think they are making good-faith efforts in that direction. The test
repo's main Halo extension has patches no longer! to core /anything/.
Further, a project to eliminate patches to HaloACL has started, so
there's much room for optimism, albeit at a pace less than optimal.
/jmc
On 11/8/2013 11:43 AM, trueskew wrote:
Yes I know, and WikiEditor is probably a more reasonable first step
for getting things running again with later versions of MW than 1.17.
But I'm more enthused about the team taking the more useful SMW+
extensions and making them compatible with "normal" MW/SMW.
The big problem with SMW+ was that they branched away from working
with the standard extensions, patching them instead. It would be
great if DIQA decided to stop that practice.
*From:*John McClure [mailto:jmccl...@hypergrove.com]
*Sent:* Friday, November 08, 2013 11:34 AM
*To:* semediawiki-devel@lists.sourceforge.net
*Subject:* [SMW-devel] smw+
SMW+ lives on as DataWiki, from DIQA-PM.
They have graciously made the MW19/SMW8 *_test_ *repository available
at http://repository.data-wiki.com/release180/.
You will note that WYSWYG is no longer there -- WikiEditor is being
distributed. I'm working now to get this new suite running, and will
report how much the Annotation toolbar and other items in the previous
editing interface, have been preserved.
Thanks!
/jmc
On 11/6/2013 4:18 PM, trueskew wrote:
Short history:
With Mediawiki 1.16 / Semantic Mediawiki 1.5.2 / Semantic Forms
0.4.1, you could open a form, and in the free text area you could
enable a rich text editor, FCKeditor 1.0.1 (a.k.a. CKEditor).
Then there was SMW+, which went to Mediawiki 1.17 / SMW (not sure)
/ and WYSIWYG, which I believe is an update to FCKeditor. It had
the same functionality with Semantic Forms, and they improved it
quite a bit over FCKeditor.
The SMW+ is no longer what it used to be (I'll leave it at that,
there are plenty of discussions about it's status changes online),
a group has been updating the WYSIWYG extension to work with later
versions of Mediawiki:
http://www.mediawiki.org/wiki/Extension:WYSIWYG
I've tried it, it's the best so far and very robust compared to
FCKeditor. It has a feature set that appears to greatly exceed
that of the roadmap of the VisualEditor effort:
http://www.mediawiki.org/wiki/Extension:VisualEditor
particularly for those of us in a work environment where things
like Word import is valuable. You can see a discussion about this
here:
http://comments.gmane.org/gmane.comp.web.wiki.semediawiki.user/14775
Project Idea:
I suggest a project to get the WYSIWYG extension working with the
latest Semantic Forms, in a way that can be supported with little
if any effort in later versions of Semantic Forms. I believe it
would be a greatly appreciated effort for more organizations than
just mine.
Thanks, and good luck.
Sal
*From:*Chenoweth, Stephen V [mailto:cheno...@rose-hulman.edu]
*Sent:* Wednesday, November 06, 2013 7:22 AM
*To:* semediawiki-devel@lists.sourceforge.net
<mailto:semediawiki-devel@lists.sourceforge.net>
*Subject:* [SMW-devel] A list of suggested developments for
undergrads to try?
Everyone,
Any ideas for a serious class project, like in PHP, perhaps, that
also would be useful to SMW?
I have 23 talented junior CS majors who built a SMW-based Wiki
this fall. When populated with data, it will show the flow of
concepts related to our courses, etc. at Rose-Hulman Institute of
Technology.
This same class is next heading into a course in software design.
I would love to give them a design and programming project to do,
which could benefit this particular Wiki they built, but which
also would be of interest to you, the SMW community. I suggested
PHP, above, because a key goal of the design course is for the
students to become adept at software patterns and other OO skills.
As a student project, this should not be something critical in
your development path, but, ideally, if they produced a high
quality result, it is something that might end up rolled into the
general product or might become an extension. In previous
classes, we have ended up submitting results back into SourceForge.
So, do you have specific ideas that come to mind? Or, do you have
a "wish list" already, that they could go look at, and choose for
themselves?
We would love to have this class be the test case for an ongoing
relationship.
Your recommendations are greatly appreciated!
Steve Chenoweth
Assoc Prof, CSSE
RHIT
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and
register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
<mailto:Semediawiki-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
