[Kalzium] Kalzium atom labels

[Marcus D. Hanwell]

On Monday 21 May 2007 19:04:53 Benoît Jacob wrote:
> On Monday 21 May 2007 18:12:15 Marcus D. Hanwell wrote:
> > I have updated the avogadro label engine to be configurable using the
> > avogadro system. I chatted with Donald briefly on IRC and he was saying
> > we could add that widget to the kalzium display. I got halfway through
> > doing that before I realised it would break the gridlayout and stopped
> > myself.
>
> In kalzium we had the "no labels" entry in the combobox. Would that be
> possible to have in libavogadro? Honest question, I understand that it may
> feel redundant in libavogadro as avogadro uses a separate checkbox to
> enable/disable the labelengine.
>
It would certainly be possible to have that as an option but it would be quite 
redundant in the avogadro application. May be that is a customisation that we 
should make in the kalzium label engine? 

> Maybe that sort of issue underlines that it'd be good if libavogadro
> offered some freedom to the app developer, i.e. libavogadro provides slots
> to which the app developer can connect the signals of whatever gui elements
> he likes.

Yes but part of the problem is the level of flexibility we would like in the 
configuration options available to engines. In the current configuration 
pretty much anything can be offered as a configuration option for an engine. 
If we had to declare the slots in the engine API that would require narrowing 
what was available. I am not sure what the ideal solution is in this case.
>
> I just understood that this connecting could be done by the glwidget.
> Indeed, the glwidget knows about both the engine (which it loaded) and the
> dialog (its parent widget). So it should be able to connect each other.
> This could be done by subclassing Avogadro::GLWidget, as is currently done
> by Kalzium.
>
This is the solution I had considered but could not decide on the proper 
solution. The way avogadro works it makes very few assumptions about the 
configuration options an engine might offer whereas we have pretty much 
decided everything in our UI design for kalzium and just want to connect our 
widgets to the correct slots. They are two quite different approaches.

I have been working on some of the compiler warnings we have been getting too 
in avogadro trunk. May be we should import an updated snapshot at the end of 
next week before the feature freeze? As far as I can see we have addressed 
all the elements we wanted to for the port to libavogadro. We should list any 
remaining concerns to ensure they are addressed.

Thanks,

Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kalzium/attachments/20070522/2eb6dd90/attachment.pgp