Adam, On 15/03/06, Adam Fedor <[EMAIL PROTECTED]> wrote: > On 2006-03-15 07:53:12 -0700 Stefan Urbanek <[EMAIL PROTECTED]> > wrote: > > >> From naive point of view the steps necessary would be: > > 1. create API for picking graphics context with prefered destination > > 2. pick ONE graphics library as preffered graphics context library > > and move > > it's > > use (or use of a bundle) into GUI > > 3. update GUI to use graphics context provided by the graphics library > > > > I'm sure you can do that. But then you are requiring more dependancies > (particulaly in the GUI, which is not where we want it). Since both > cairo and art can draw into a bitmap, it would probably be better just > to define an interface between the GUI and back to allow that, then > the particular backend would be responsible for doing the work. >
No, I can't. See below. > > > > Looks like all necessary code is already in GNUstep, it is just a > > matter of > > "rewiring" it. But well ... I do not see much into the internals... > > Oh yes, actually doing the work - well that's the hard part :-) > Excuse me, but I take this from you as a little offence with the meaning:"do not talk, just code". Following text is not going to be only about the issue, but about general attitude on this list. This attitude is repeating on this list again and again... Yes, for some it might seem that I am just talking on the list and contributing nothing for several past months. If you think so, be it. It is common misundestanding, that only value to an opensource project is programming. I did analysis, found the problem, located code and suggested a solution. It seems to me that this is never valued... Moreover, if you, or anyone else thinks, that my "just talking" is worthless on this list, let me know and I will stop. You, as the wise project leader should know better than anyone on the list, who is is "at home" in which parts of GNUstep. Instead of laughing at me (I exaggerate now, so take it with less weight) that I just talk and do not program, you should try to allocate voulenteering resources to the problem according to appropriateness. For me to implement this would mean to dig into the gui and back, as I really do not have a chance how the things are connected. Also note that this would require more discussion of people who developed relevant parts of gui and back to find a solution that would be modular, non-braking and will fit to the libraries. Yes, GNUstep as any other open-source is voulentary project, so the project leader can not force anyone to do anything. Also people have other things to do. But! If I understand the role of project leader correcly, then I think his task is, among others, to allocate resources with redundancy. Or I am wrong? What I was able to do with the time I had, was analysis. I do not code GNUstep anymore and I do not plan to code for GNUstep in the near future... My inputs are not valuable? Again, if yes, then let me know and I will stop "just talking" on the list. It is all about attitude...which drives the project...to somewhere... Regards, Stefan Urbanek p.s.: With "programmers are the only core of the OSS" attidute, I can suggest this to my company to fire all analysts, including me, as they are doing nothing, they just meet, talk and draw pictures. p.p.s.:Moreover, this year I have not seen any relevant answer to project-crucial questions I have posted to the list. The only response was from Alex Perez, who just broght the questions to the light again. Whi this attitude, the project is dead. -- http://stefan.agentfarms.net First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev