20 Jan
2010
20 Jan
'10
3:16 p.m.
Hi Doru
How hard would it to implement this enhancement?
I see two paths, the dirty one and the clean one:
Dirty: make two panes stacked, one for the evaluator, the other a table widget with the
history. The history is stored in the moose entity.
Clean: make a custom widget. Problem: where to store the history (if I browse to a parent
entity and lose the finder pane of the entity, then I want my query history when coming
back in the browser)
What do you think.
--
Simon
20 Jan
20 Jan
4:16 p.m.
Hi Simon,
I implemented this in VW a long time ago. My solution was to actually
have an external class that would store this information as methods
and relate them to the types of entities that they make sense on.
Afterwards, the Evaluator, instead of just displaying self it displays
the result of querying this database.
I might take a shot at it this evening.
Cheers,
Doru
On 20 Jan 2010, at 15:16, Simon Denier wrote:
Hi Doru
How hard would it to implement this enhancement?
I see two paths, the dirty one and the clean one:
Dirty: make two panes stacked, one for the evaluator, the other a
table widget with the history. The history is stored in the moose
entity.
Clean: make a custom widget. Problem: where to store the history (if
I browse to a parent entity and lose the finder pane of the entity,
then I want my query history when coming back in the browser)
What do you think.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
5450
days inactive
5450
days old
1 comments
2 participants
participants (2)
-
Simon Denier -
Tudor Girba