11-06-2012, 07:25 PM
Pages: 1 2
11-06-2012, 11:01 PM
None since 5 months, maybe you should ask rsjtdrjgfuzkfg / ilikenwf / freaktechnik about it ?
https://github.com/nightingale-media-pla...therweight
https://github.com/nightingale-media-pla...therweight
11-08-2012, 05:57 AM
Well. The design is pretty much on halt right now, since if we create the page, it should be done together with a redesign of the whole page. Me and Manko already agreed on the frameworks to use. There is a page related to this on the wiki (max. 3 clicks deep from the startpage, but I'm lazy).
Sadly the redesign hasn't even been started. I take it on me, since I still haven't installed a Linux and developing the new page on windows would be a pain (and I don't want to do it). So, basically the database is more or less finished, not final tough. there are some adjustments which need to be made afaik.
Sadly the redesign hasn't even been started. I take it on me, since I still haven't installed a Linux and developing the new page on windows would be a pain (and I don't want to do it). So, basically the database is more or less finished, not final tough. there are some adjustments which need to be made afaik.
11-08-2012, 11:19 PM
I just found out a great plugin for DokuWiki which handle plugins/themes, installation worked but I need to modify it to match categories we have.
11-16-2012, 02:07 AM
So I took a break on my other development (L10n/buildbot/feather) and decided to work on the new (not featherweight) add-ons repository that will replace current wiki page.
In fact this is a temporary solution before featherweight is done.
This solution will still be on the wiki but it's way much better with many features such as search, categories, tags, API, RSS Feed etc.
It will look like this : https://www.dokuwiki.org/plugins
I'm working toward adding features that will both benefits us and the DokuWiki website.
In fact this is a temporary solution before featherweight is done.
This solution will still be on the wiki but it's way much better with many features such as search, categories, tags, API, RSS Feed etc.
It will look like this : https://www.dokuwiki.org/plugins
I'm working toward adding features that will both benefits us and the DokuWiki website.
11-10-2013, 12:36 PM
Ok, it's been one year and I think I would give you my progress here.
Here is a preview on the new add-ons repo (work in progress)
http://wiki.getnightingale.com/doku.php?...playground
Here are features of the new repo :
- Search
- Tags
- Category
- Each Add-on have his own page
- Database storage
- Compatibility information
- Buttons for download/report issues/donation
- Links to other author add-ons (if you put the same email on all your add-ons page)
- Screenshot
- Depends/conflits/similar fields
If you want to post your add-on or modify a add-on page, it's under "add-on:"
Here is the code for a page :
Of course this system will also host feathers, but I haven't imported them yet.
You can read about this add-ons repo project on the wiki :
http://wiki.getnightingale.com/doku.php?...addonsrepo
This work was possible thanks to DokuWiki plugins system
Feel free to test and report me issues/requests (but take a look a the wiki page above to see if it's already in).
Here is a preview on the new add-ons repo (work in progress)
http://wiki.getnightingale.com/doku.php?...playground
Here are features of the new repo :
- Search
- Tags
- Category
- Each Add-on have his own page
- Database storage
- Compatibility information
- Buttons for download/report issues/donation
- Links to other author add-ons (if you put the same email on all your add-ons page)
- Screenshot
- Depends/conflits/similar fields
If you want to post your add-on or modify a add-on page, it's under "add-on:"
Here is the code for a page :
Code:
====== My add-on 1.0 ======
---- add-on ----
description: My add-on makes coffee and cupcakes
author : John Doe
email : john@doe.com
type : Web Browser, Music & Video
lastupdate : 2013-11-01
compatible : 1.12
depends : plugin1
conflicts : plugin2
similar : plugin3
tags : coffee,cupcakes
screenshot_img : http://johndoe.com/coffee.png
downloadurl: http://johndoe.com/extension.xpi
bugtracker : http://github.com/johndoe/myaddon/issues
sourcerepo : http://github.com/johndoe/myaddon
donationurl: https://www.paypal.com/johndoe
----
===== Documentation =====
Regular dokuwiki text here :)
Of course this system will also host feathers, but I haven't imported them yet.
You can read about this add-ons repo project on the wiki :
http://wiki.getnightingale.com/doku.php?...addonsrepo
This work was possible thanks to DokuWiki plugins system

Feel free to test and report me issues/requests (but take a look a the wiki page above to see if it's already in).
05-28-2015, 05:57 PM
Hi everyone,
Is it safe to say that development of the Featherweight addon platform will be stalled for a foreseeable future? I think the work that GeekShadow has done to adapt the DokuWiki plugin for the addon page is awesome and its a major improvement over the current addon page.
If everyone agrees that this is still a good interim solution, I'd be happy to help by creating the remaining addon pages in the new format, collecting screenshots, etc. in order to get this ready to replace the current addon page. Thoughts?
Is it safe to say that development of the Featherweight addon platform will be stalled for a foreseeable future? I think the work that GeekShadow has done to adapt the DokuWiki plugin for the addon page is awesome and its a major improvement over the current addon page.
If everyone agrees that this is still a good interim solution, I'd be happy to help by creating the remaining addon pages in the new format, collecting screenshots, etc. in order to get this ready to replace the current addon page. Thoughts?
05-29-2015, 06:47 AM
(05-28-2015, 05:57 PM)zjays Wrote: [ -> ]Is it safe to say that development of the Featherweight addon platform will be stalled for a foreseeable future? I think the work that GeekShadow has done to adapt the DokuWiki plugin for the addon page is awesome and its a major improvement over the current addon page.
If everyone agrees that this is still a good interim solution, I'd be happy to help by creating the remaining addon pages in the new format, collecting screenshots, etc. in order to get this ready to replace the current addon page. Thoughts?
I don't think Featherweight will be continued; it is perfectly possible that someone will someday create a new add-on page, most likely from scratch. While I wanted to do something like that for a long time, it is almost certain that I won't find time for that within the next ~ 1,5 years.
I cannot speak for other someones, though

Edit: if you want to work on this, we have a backup of the old Songbird add-on pages, which should contain screenshots.
06-03-2015, 06:44 AM
(05-29-2015, 06:47 AM)rsjtdrjgfuzkfg Wrote: [ -> ]imho an add-on platform should have some xpi upload capabilities and allow add-on updates; both things I wouldn't assume the DokuWiki thing has right now.
Hmm, currently there appears to be no version number field in this new DokuWiki addon page, although there is a last update date field. Is it possible or feasible to hack the "Find Updates" portion of the Nightingale extension manager to check for add-on updates by checking either the last update date field, or the version number field (if implemented) on the addon page?
(05-29-2015, 06:47 AM)rsjtdrjgfuzkfg Wrote: [ -> ]Edit: if you want to work on this, we have a backup of the old Songbird add-on pages, which should contain screenshots.
Good idea. How could I access this backup? I have been using the wayback machine/internetarchive site for accessing old Songbird stuff, but it can be slow to browse around using this.
06-03-2015, 11:12 PM
(06-03-2015, 06:44 AM)zjays Wrote: [ -> ]Is it possible or feasible to hack the "Find Updates" portion of the Nightingale extension manager to check for add-on updates by checking either the last update date field, or the version number field (if implemented) on the addon page?No. One could set up a server-side solution doing what you say, but I'd rather not change client update code, as it is standartized between all XULrunner applications (Firefox, Thunderbird, ChatZilla, SeaMonkey, ...). Also, any kind of update mechanism needs HTTPS, else all add-ons must be signed individually iirc. Add-ons can also use the update mechanism with custom endpoints, which may be disturbed if we change this in a quick-and-dirty manner (and I consider a proper implementation to consume more time than completing featherweight or a new add-on platform with update support).
Pages: 1 2