it will probably need to be hand made.
The plugin would provide an interface to a web service. There would be a series of screens designed in Designer (see my Designer screencasts), and these screens would attach to the data grid generators provided by the plugin, and set the appropriate text bits on screen.
So, for those of you who want to do the designer work, listen up:
I would see something like the following screens:
* Favourite Recipes (default screen)
* Newest Recipes
* Search for Recipes
* Recipe Detail view
The actual structure of those pages, would depend on what would be used to get the data.
* Find a web service that can be queried for recipes.
* write code in C++ to deal with that service, make it self contained. If needed, convert XML to plain text, etc.
* write a DCE plugin, that provides:
- Data grid generators for the different data grid tables in each screen
- Command(s) to retrieve recipe details
LinuxMCE has commands in orbiter to update designobjs with new image data (i.e. a jpeg or a png). Place designobjs for the recipe images etc, and in the commands to retrieve recipe details, have it set those designobjs.
you should provide pagination buttons to flip pages, if needed. preferrably, the cooking ingredients should be separated from the preparation instructions, so that the ingredients/proportions can stay on screen.
The more you can parse the information, the more that commands can be added for future expansion, i.e. for ordering groceries for a recipe etc.
This is a whole house solution, tied in via a large scale messaging buss. Keep this in mind. LinuxMCE is about integration.