preferences through html page

[GoogleCodeExporter]

Setting configurations options through the interpreter can be a bit
daunting.  Having an html page (as a plugin? ... like the security
advisor...) to select options (html radio buttons, input fields, etc.)
might be a more user friendly way to proceed.

Original issue reported on code.google.com by andre.ro...@gmail.com on 9 Jul 2008 at 8:17

[GoogleCodeExporter]

As mentioned in my email, I am happy to take this on.

Should this be part of 1.0? I think so.

Original comment by johannes...@gmail.com on 9 Jul 2008 at 8:46

[GoogleCodeExporter]

I had not set it as part of 1.0 as I didn't know if I could handle it - there 
is so
much to be done and I think we should release 1.0 "soon".  However ... from a
usability point of view, yes, it should be part of 1.0.  Setting the label
appropriately.  (Welcome back :-)

Original comment by andre.ro...@gmail.com on 9 Jul 2008 at 8:49

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Good idea!

And to keep the advantage of the new configuration.py, I think this page should 
be
built automatically from settings available in configuration.py. So a new option
could be added without any change in this page.

Original comment by florian....@gmail.com on 9 Jul 2008 at 10:45

[GoogleCodeExporter]

I like Florian's suggestion ... however, the new configuration.py is not 
complete and
it might be a bit tricky to have two people working on it at the same time.  I 
think
that a separate "prototype" could be implemented first, and later integrated 
into
configuration.py.

Original comment by andre.ro...@gmail.com on 9 Jul 2008 at 10:52

[GoogleCodeExporter]

Good thinking Florian.

I will create a framework for dynamically building the page, but initially have 
it
built from some static structure.

Original comment by johannes...@gmail.com on 10 Jul 2008 at 8:51

[GoogleCodeExporter]

State of this issue: as said on the mailing-list, I have work on this issue, 
and a
working configuration page is available in my branch.

There is some points which need some works:
 * Adding the Crunchy menu (André has worked on it with its new menu)
 * Removing dependencies on configuration.py

In r906, I  made some changes that allow to remove the "import 
configuration.py". But
the plugin depends IMHO too much on configuration.defaults (to save settings 
and get
docstrings). This make the writing of tests too complicate.

Original comment by florian....@gmail.com on 9 Aug 2008 at 10:51

[GoogleCodeExporter]

There is a new implementation in my branch based on Florian's work.  I took a
different approach and created a new vlam keyword for insertion of preferences
choosers.  A sample page (/writing/configuration2.html) has been created for 
it.  

I made it much easier to test (in theory) even though I have kept a dependence 
on
configuration.py.  I may make some further changes to make it totally possible 
to
test independently of configuration.py - even though it will still be imported.

I believe it is essentially completed and ready to incorporate in the trunk.  I 
will
wait before I change the status of this Issue.

Original comment by andre.ro...@gmail.com on 12 Aug 2008 at 12:46

[GoogleCodeExporter]

Original comment by andre.ro...@gmail.com on 28 Sep 2008 at 4:57

• Changed state: Fixed