Thread: [Grecipe-manager-devel] completely dead now?
GNOME Recipe Manager w/ nutrition information and other useful plugins
Status: Beta
Brought to you by:
thomas_hinkle
From: Gene I. <eb...@oz...> - 2008-10-06 20:33:41
|
I hope not. -- Gene Imes |
From: Elizabeth B. <ly...@pr...> - 2008-10-06 23:28:08
|
On Mon, Oct 6, 2008 at 4:17 PM, Gene Imes <eb...@oz...> wrote: > I hope not. Not as far as I'm concerned. I don't know Python, but I joined the team just recently to work on Debian and Ubuntu packaging. -- Elizabeth Bevilacqua // Lyz // pleia2 http://www.princessleia.com |
From: Thomas M. H. <tmh...@gm...> - 2008-10-07 00:44:04
|
The list has never been too active, but I'm still working away on Gourmet... I just got web import working with the plugin architecture, for example. The plugin system was largley a response to a few attempts to create Gourmet spin-offs that I felt really weren't necessary. By moving functionality out of the core of Gourmet, I simplify the interface, which is what the spin-offs were trying to do; meanwhile, we allow people to add the kitchen sink if they want through plug-ins. This means there's some really low-hanging fruit for interested parties -- like adding an "equipment list" plugin -- as well as some tricky tasks that could be taken on (like thinking about whether shopping should become a plugin, or like simplifying and improving ingredient entry). Tom |
From: Gene I. <eb...@oz...> - 2008-10-13 19:51:13
|
Thomas Mills Hinkle wrote: > The list has never been too active, but I'm still working away on > Gourmet... I just got web import working with the plugin architecture, > for example. > > The plugin system was largley a response to a few attempts to create > Gourmet spin-offs that I felt really weren't necessary. By moving > functionality out of the core of Gourmet, I simplify the interface, > which is what the spin-offs were trying to do; meanwhile, we allow > people to add the kitchen sink if they want through plug-ins. This > means there's some really low-hanging fruit for interested parties -- > like adding an "equipment list" plugin -- as well as some tricky tasks > that could be taken on (like thinking about whether shopping should > become a plugin, or like simplifying and improving ingredient entry). > > Tom Great, one of my favorite programs. Just a user though. Tom, have you thought any more about a recipe server (seems like we talked of it before)? Glad GRM is still alive. -- Gene Imes |
From: Daniel T. <da...@pr...> - 2008-10-07 04:04:11
|
On 6 Oct, 2008, at 20:31, Thomas Mills Hinkle wrote: > The plugin system was largley a response to a few attempts to create > Gourmet spin-offs that I felt really weren't necessary. By moving > functionality out of the core of Gourmet, I simplify the interface, > which is what the spin-offs were trying to do; meanwhile, we allow > people to add the kitchen sink if they want through plug-ins. This > means there's some really low-hanging fruit for interested parties > -- like adding an "equipment list" plugin -- as well as some tricky > tasks that could be taken on (like thinking about whether shopping > should become a plugin, or like simplifying and improving ingredient > entry). This sounds neat, any documentation on the plugin architecture? I haven't worked much on RecipeManager since last year because I have been extremely busy with other things but I did throw together a standard for recipe sharing across the network (it's up at recipemanager.org) and the _recipe._tcp protocol is registered to use it in the DNS-SD (aka Zeroconf aka Bonjour) registry. I've been meaning to update my code to follow the spec, but since you now allow plugins this might be a neat idea to try to implement for Gourmet. Take care, -- Daniel G. Taylor http://programmer-art.org |
From: Thomas M. H. <tmh...@gm...> - 2008-10-07 22:28:58
|
> > <snip> > This sounds neat, any documentation on the plugin architecture? > <snip> Documentation is available at the wiki on Sourceforge. I'd post a link but SF seems to be down at the moment. I tried to document the plugin architecture as best as I could while creating it. My guess, though, is that it won't get really well documented until somebody else implements a plugin and helps me improve the documentation (it's hard for me to document well, since I already know how the thing works; I think you always need the perspective of someone else working on a project to really know your documentation is working) Tom |
From: Thomas M. H. <tmh...@gm...> - 2008-10-07 22:35:50
|
> > Documentation is available at the wiki on Sourceforge. I'd post a link but > SF seems to be down at the moment. > Here's the links: Plugin documentation: http://grecipe-manager.wiki.sourceforge.net/Plugins General development stuff: http://grecipe-manager.wiki.sourceforge.net/Development |