@guessed & @Ap15e
I gave your posts a quick glance with drowsy eyes last night (looong day at work) and i see similarities, focal points and options.
Starting with the list mcvflorin provided, this could really be a good starting point as for available plugins
Can we publish it in the table form as presented by Ap15e in his wiki? (im not a html guru, so im merely exchangings options here to try and find common ground and some momentum here
I looked at Ap15e's wiki proposal as wel as
http://code.mios.com/ and i must agree with @guessed that it seems to result in duplication of info, thus possibly confusing users. I would suggest we agree on one location.
Following that lead i must say i see pro's and cons to both your approaches. The pro's in the case of
http://code.mios.com/ are heavy though, since this provides a readily available location with not only the code but also screenshots, evoluation and backlink into the forums.
As @guessed proposed in
A Sticky, read-only, FAQ post at the top of this Board can point to that page as the single "source of truth" for the existing Plugins. Over time, that post can be extended to include the other FAQ items that routinely come up... either as direct content, or more likely as pointers to the SoT Posting on the matter.
If we could do the same in moderating the forums (crossreferencing with a hyperlink to the appropriate page on
http://code.mios.com/) that would be an improvement.
To make things more consistent that would mean though that the layout of the forums as well as the code page (categories & sections) would have to be slowly migrated towards a similar layout on both ends (look and feel for users stays the same and feels "like home" .
As @guessed stated, the code page only provides a "degree of consistency" at the moment and in its current layout could be improved using the tables proposed by @Ap15e on his wiki. That could maybe provide a quick overview from where a link can be clicked to the current applicaple subcode page that is available now. Thus preserving whats there, just presenting it slightly different.
I have no idea if this is feasible and if so how labour intensive it would be, but personally i think its worthwile considering it.
Last but not least, i will PM @mcvovidiu to get acces to the code page and see what else in can contribute there in close coordination with you guys.
@ Guessedl;
code.mios.com allowed the community to update the DSC Alarm code when that engineer left. Had that been a ZIP Attachment to a Forum thread, I would not have touched it with a TFP. It allowed folks, like @strangely and others, to contribute a ton to it's overall evolution...
What is TFP? and why would you not touch is as its simply a warpper for the xml files that contain the code.
I take it from this quote you prefer to publish all files seperately? If so, whats the advantage?
In the current state, I'd use the [pre-existing] Luup Projects wiki page as the jumping point. It already points to a number of the original plugins, categorized, and simply needs to be extended to include the newer ones that only exist in the Forums. I believe the documentation for those plugins, their dependancies (etc) should be put within their respective documentation/wiki/forum pages.
Would this mean that the code page and the wiki LUUP projects page would co-exist? or is it possible to bring the two together like you did in sectioning the forum "LUUP & Development" where Plugins & plugin development are under the same section as "scene scripting" and other LUUP projects.
Hope to get feedback and see what we can actually start to DO (in a controlled way)
Henk
