| Age | Commit message (Collapse) | Author |
|---|
|
Restarting from scratch seems to be the fastest approach to switch to
sqlite and get rid of some other structural mistakes from the past.
|
|
This is actually possible when using <textarea> instead of <pre>. With
this change the recipe server has full support for browsers without
JavaScript.
|
|
This reduces the number of clicks to delete a recipe.
|
|
|
|
Using a database is way more complex (see the commit statistics of this
commit) than using files to store recipe data. Also administration and
usage is simpler.
|
|
|
|
|
|
|
|
The upstream URL can be encoded easily by the user in the Markdown-based
description. The title can be parsed by the first found top-level
heading in the Markdown text.
Thus these two columns are no longer used. To avoid an additional
migration they will be kept in the database.
|
|
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
|
|
Since there are no good solutions to upload the file and markdown
description text via HTML forms the edit page will upload the changes
using embedded javascript.
The page is now complete apart from the necessary javascript code and
the backend handlers.
|
|
|
|
|
|
This reduces copies of the same HTML code.
|
|
Recipes should be completely editable and removable. Thus this edit page
was added.
|
