Re: [Pyatcron-devel-list] Brainstorming

[Julien Olivier]

> 1) Your're right for the Task::getEditorWidget, it should only returns
> the Widget itself, and the Widget construction should go into
> __init__().
> Now, I see two options here.
> 1. The __init__() method should call a buildWidget() method which goal
> is to build the Widget. That way, Task child class will have to
> reimplement this function, not the __init__() one.
> 2. Make Task class inherited from gtk.Widget class. That way, no need to
> have a getEditorWiget() function. This is certainly the smarter way, but
> might be more difficult to do.
> PS: I like the  second way, as we might be able to send signals when
> internal fields changes. Think about how easy it could be to connect the
> MainWin GUI to Task, Scheduler and SchedulerList "changed" event.
> 

Before I answer, I see that you've already been experimenting with the
2nd solution in CVS. I see no inconvenient using the second solution,
except that it doesn't seem right from a logical point of view: a task
isn't a widget... a task can be described by a widget. However, as long
as it works, doesn't break in the future, and doesn't add unnecessary
limitations, I'm all for it.

> I think that there is some brainstorming to have there. The best way
> would be writting the class API before writing any code. Hmmm, this
> project is getting more and more interesting ;-)
> 

I don't like talking too much about implementation details. My point of
view is to try and implement things. If they work and seem done the
right way, we keep them. If someone finds another solution to the same
problem, we can start talking by comparing the different solutions.

I'll look at your solution (the one in CVS) and report any problem.

> 
> 2) Sure, the SchedulerEditor with it's Notebook is not perfect, but hey,
> an hour to implement everything, this is where the real performance is
> ;-) Seriously, this is a quick draft, and I'm waiting for your
> improvements...
> 

Of course, that's the way I understood it. I'll hack on it when I've
time. I'll also add the task's widget into the new task assistant.

> 3) I should be able to apply your big patch this afternoon. Source code
> I've changed a bit between your patch creation and now, so I can not
> apply it straight forward. Give me a few hours from now and I'll do the
> job.
> 

As I said, take your time :)

> 4) I've bought the domain name for a year (12$, not so much). I've no
> problem at paying for that, thanks anyway for the help.
> 

OK, I'll pay you some drinks one day ;)

-- 
Julien Olivier <address@hidden>