LightGallery.0.0.1-2007-09-09.zip – doesn't wrap the files in a single folder YUIEditor-2007-11-12.zip – doesn't wrap the files in a single folder and appears to just be a GIF...
1. I think there might be an example/dummy add-on, so everybody can download it and use it as a starting point
should maybe contain: default.php
readme.txt
conf/database.php
conf/definitions.php
conf/settings.php
library/ (Classes and libraries)
translations/ (here should be put LANGUAGE.php files) All the files will contain only includes of the files (including ./conf/definitions.php, ... in default.php) and commented text guiding a developer where it is ok, to put the code and what kind of code.
I can create such dummy add-on also for language add-ons. Depends if we can all agree on some skeleton.
btw, I actually made an extension ExtensionLanguageLoader which tries to read language translations from (not mentioning some others places not important to explain here): languages/LANGUAGE/extensions/*.php and also extensions/*/translations/LANGUAGE.php I would like it to be the standard of placing extension translations since there is none really working system for this yet (using conf/language.php is useless because it doesn't allow use multiple languages - for example with LanguageSelector).
2. There is a lot of add-ons using old way of defining language dictionary definitions:$Context->Dictionary["word"] = 'definition'; should be:$Context->SetDefinition('word', 'definition'); This make extension translations to be always overdefined by default language definitions. I made a bash script and made it an extension FixLanguageDefinitions which goes through all installed default.php files and it fixes these definitions, but it would be really much better if extension developers would fix these definitions themselves so this script would not be needed at all. I can make a list of such addons if requested
@ithcy: any progress with the extension allowing to download? I would like to use that! :-) If there is a problem with wrongly released add-ons, you can just not allow to install the add-on, but I would really like to use it
conf/definitions.php containing language definitions: <?
// use this file for dictionary default definitions
$Context->SetDefinition( 'term', 'definition' );
?>
conf/database.php containing extension database tables settings: <?
// use this file to define your database tables
$Context->DatabaseTables['MyExtensionTable'] = 'MyExtensionTable';
$Context->DatabaseColumns['MyExtensionTable']['MyID'] = 'MyID';
$Context->DatabaseColumns['MyExtensionTable']['Caption'] = 'Caption';
?>
Yeah, there are actually two versions of 1.1. The first one had the whole wgetted directory structure in from my server. I fixed my extension-building script and uploaded a new version 1.1. I didn't think it was worth changing the version number since very few people had downloaded the old one.
RSS feed for http://lussumo.com/addons/ page
This would help members keep up to date with new addons and developments without having to regularly visit the page.
Not sure this is exactly the right place for this comment but I've searched to see if it has been suggested before and I don't think it has.
I'm not sure there's a post about this somewhere. Vanilla Search + Feeds are a very useful combination, you can do that for virtually any content in the forum. You can track any user's posts, all you need to do is typing his name followed by ":"
Comments
SubCategories-2007-08-30.zip – Contains "__MACOSX" folder
MembersOnly-2007-10-14.zip – Contains "__MACOSX" folder and .DS_Store file
JQSmoothJump-2007-09-04.zip – Contains "__MACOSX" folder and .DS_Store file
DiscussionExpiration-2007-10-26.zip – Contains "__MACOSX" folder and multiple .DS_Store files
FeedPublisher-2007-10-31.zip – Contains .svn folders
LightGallery.0.0.1-2007-09-09.zip – doesn't wrap the files in a single folder
YUIEditor-2007-11-12.zip – doesn't wrap the files in a single folder and appears to just be a GIF...
...hmmm, Note to self: must check out my uploaded packages...
should maybe contain:
default.php readme.txt conf/database.php conf/definitions.php conf/settings.php library/ (Classes and libraries) translations/ (here should be put LANGUAGE.php files)All the files will contain only includes of the files (including ./conf/definitions.php, ... in default.php) and commented text guiding a developer where it is ok, to put the code and what kind of code.
I can create such dummy add-on also for language add-ons. Depends if we can all agree on some skeleton.
btw, I actually made an extension ExtensionLanguageLoader which tries to read language translations from (not mentioning some others places not important to explain here):
languages/LANGUAGE/extensions/*.php and also
extensions/*/translations/LANGUAGE.php
I would like it to be the standard of placing extension translations since there is none really working system for this yet (using conf/language.php is useless because it doesn't allow use multiple languages - for example with LanguageSelector).
2. There is a lot of add-ons using old way of defining language dictionary definitions:
$Context->Dictionary["word"] = 'definition';should be:
$Context->SetDefinition('word', 'definition');This make extension translations to be always overdefined by default language definitions.
I made a bash script and made it an extension FixLanguageDefinitions which goes through all installed default.php files and it fixes these definitions, but it would be really much better if extension developers would fix these definitions themselves so this script would not be needed at all.
I can make a list of such addons if requested
@ithcy: any progress with the extension allowing to download? I would like to use that! :-) If there is a problem with wrongly released add-ons, you can just not allow to install the add-on, but I would really like to use it
<? // use this file for dictionary default definitions $Context->SetDefinition( 'term', 'definition' ); ?>conf/database.php containing extension database tables settings:
<? // use this file to define your database tables $Context->DatabaseTables['MyExtensionTable'] = 'MyExtensionTable'; $Context->DatabaseColumns['MyExtensionTable']['MyID'] = 'MyID'; $Context->DatabaseColumns['MyExtensionTable']['Caption'] = 'Caption'; ?>Perhaps a closer perusal of the "1st post in this thread" would yield more enightenment for your good self :-)
...and here is the RSS feed.
Let's say you want to create a feed to follow Mark's interventions. You just have to type Mark: then run a search, then grab the link from the feeds menu in the left panel. And you'll get something like this:
http://lussumo.com/community/search/?PostBackAction=Search&Keywords=Mark%3A&Type=Comments&btnSubmit=Search&Feed=RSS2