I guess that another interesting topic has been raised here. The problem (to my mind) is not to know if we should make an exception for broken themes. For me, the problem is: should we make "our" applications *crash* if the theme is broken. Most applications written for GNOME do not crash when the theme is broken, shouldn't we do the same (then the question would be "how?")?
Making our applications crash if the theme is broken is ensuring that applications will only work with themes that do not have any errors. That is not a bad behaviour but it could be (as we can see) a problem since themes developers are not error proof (and we are not too). What I want to say is sometimes themes developers can miss something making the theme generating warnings. Do we want to make the user pay for that by making the applications crash? Sure it is always a good idea to fix the theme blabla but that's just design to me, making applications crash for design purpose looks like a broken behaviour to me. -- Guillaume Mazoyer - http://respawner.fr/ ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ java-gnome-developer mailing list java-gnome-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/java-gnome-developer
