On Montag, 18. August 2008, Denny Vrandečić wrote: > Oh, sorry, I was unclear: yes, you are fully right, every extension > should have its own folder. The question is just, should they be > > 1) Grouped in one SemanticMediaWikiExt directory
I think this is only good if all the extensions are best thought of as *one* extension with a common base directory and a common way for admins to select which of the "features" of the extension should be enabled. Hence, I suggest 1') Create two extensions SMWExtraDatatypes SMWExtraQueryFormats that basically are a list of single files (one per datatype, one per query format) shipped with a simple setup file that reads the wikis config settings to figure out which of those are to be enabled. Datatypes are things like Daniel's SMW-YGO type, formats are things like Denny's Google Charts printers. I think these two kinds of mini extensions are most common. As a rule, one could require that no Special pages or other complex features are added, and that every datatype/format that wishes more than a single source file puts it into a subdirectory that is named like the datatype/format. One would also establish a common naming scheme for datatype IDs used by extension datatypes (to prevent clashes with SMW types or other extensions). I think this would be much better than having every datatype/format in a single extension and do their own private stuff there, given that those extensions are so closely related. Such a common setup would also simplify internationalisation, since you do not have to make a new project at BetaWiki to get your datatype/format names international for single file extensions. > 2) Be first level on the MediaWiki/extensions directory Would be doable, and is my preferred solution for larger extensions like SF and Halo. But these directories should use a common naming scheme like the current Semantic* For datatype and format extensions, I prefer (1'). > 3) Be grouped in a SemanticMediaWiki/extensions/ directory No, I would definitely object to that. SMW core should be as slim as possible (some features might even move to the (1') extensions), and the way you check out stuff from SVN would make people pull ./extensions in any case. Markus > 4) somewhere else (explain) > 5) whatever > > Having all the files fly around in a single directory is definitively a > very bad idea :) > > denny > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- Markus Krötzsch Semantic MediaWiki http://semantic-mediawiki.org http://korrekt.org [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
