Hey,
> What can we learn from Drupal development, where multiple modules are
integrated via extensive use of APIs?
Some problems we are facing here:
* Our (PHP) APIs are generally badly defined and poorly thought out. This
applies to both MediaWiki core, SMW and other extensions. That makes it
very hard not to end up breaking compatibility.
* Code is not split into seperate components and tight coupling with
unrelated things is made for not good reason. For instance, most of the SMW
code could have been written in such a way that it would work without MW.
Currently pretty much everything depends on it. This makes the code more
complex and prone to breaking when changes in MW are made.
* A lot of developers either do not have the experience on how to avoid
creating the above problems or simply do not care.
/rant ;)
> can we start a 'developer documentation' page on smw.org?
https://semantic-mediawiki.org/wiki/Programmer%27s_guide_to_SMW
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
