summaryrefslogtreecommitdiffstats
path: root/TODO
blob: 480b9cf3df0f9c1f49b85f97cfd9bcaef2410326 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112

Frei0r TODO
~~~~~~~~~~~

Table of Contents
=================
Welcome hackers! 
Port existing code 
Bugfixes 
    Test suite 
    Null parameters 
Spec Update 
Documentation 
    Screenshots 
    Trac spam 


Welcome hackers! 
~~~~~~~~~~~~~~~~~

The Frei0r mailinglist is the first step to get in touch with us: the
one we use is [frei0r-devel] and it has [public archives] that are also
[searchable and indexed] online.

The bugtracker we are currently using  is [the Piksel trac], have a look
there and, if  you know how to  report a bug, please open  a new issue
and give it as many details as you can.

Here below are outlined some open issues in the development flow, they
range   from  /bugfixing/   tasks  to   /specification   updates/  and
/documentation/.


[frei0r-devel]: https://piksel.no/mailman/listinfo/frei0r-devel
[public archives]: http://piksel.no/pipermail/frei0r-devel/
[searchable and indexed]: http://blog.gmane.org/gmane.comp.video.frei0r.devel
[the Piksel trac]: http://www.piksel.no/projects/frei0r/report

Port existing code 
~~~~~~~~~~~~~~~~~~~

Porting  new Effects  from existing  collections should  be  easy, for
instance there  is a lot of code  to be ported from  [EffecTV], the [Demo Effects Collection],  [Pete's plugins] and  the XScreensavers… let  us if
you engage  the task, it can  be fun and  not so difficult if  you are
just learning how to program in C or C++.


[EffecTV]: http://effectv.sf.net/
[Demo Effects Collection]: http://demo-effects.sourceforge.net/
[Pete's plugins]: ftp://ftp.dyne.org/freej/plugins/petespluginslinux_070114.tar.gz

Bugfixes 
~~~~~~~~~

We should remove from installation any plugins which casuse a crash or
data loss - and if we want them back we'd better fix them, in any case
we can't allow distribution of  plugins that can potentially crash the
host.

This is an  old issue with dynamically loaded  objects: if they crash,
they'll crash the  host application loading them!  one  reason why JWZ
made XScreensavers share an X11 /back-display/...

TODO Test suite 
================

Develop  a test  suite  for frei0r  plugins (/scaffolding/  technique)
which  can  be run  to  generate reports  on  reliability.

TODO Null parameters 
=====================

Fix  plugins which do  not set  parameters to  a default  value inside
*f0r_init()*  - this crashes  some applications  as often  reported in
bugreports.

Spec Update 
~~~~~~~~~~~~

We sometimes need  to review the Frei0r specification  and confront it
with new issues coming up. It might be also useful to confront it with
the  specification  drafted  in   [LiViDO],  which  provides  a  broader
case-study, and other standards adopted in [GStreamer].


[LiViDO]: http://livido.dyne.org/codedoc/
[GStreamer]: http://gstreamer.freedesktop.org/documentation/

Documentation 
~~~~~~~~~~~~~~

Screenshots 
============

A Gallery of filters is  already being generated, but not yet complete
with screenshots. Right now [FreeJ]  is being used with scripts to parse
plugin contents and render them into a webpage, still what are missing
are screenshots or maybe short video renderings of plugins in action.


[FreeJ]: http://freej.dyne.org

TODO Trac spam 
===============

We should fix the trac on piksel.org, install a new bugtracker like
[flyspray] or use the mantis already up at [bugs.dyne.org].


[flyspray]: http://flyspray.org
[bugs.dyne.org]: http://bugs.dyne.org