Re: [Anygui-devel] Please voice your opinion... :)
Brought to you by:
mlh
From: Hellen C. <he...@cl...> - 2003-03-02 19:50:41
|
On Sat, 2003-03-01 at 05:44, Magnus Lie Hetland wrote: > In case it wasn't clear from the previous email, I would be very > grateful if anyone with (semi-)strong feelings in the backend-shipout > issue would speak up, even with a simple +1 or -1 :) Why not keep the backends in the commonn CVS repository by default and have specific backends adopted by other projects as an exception to the rule? They can always be marked as unsupported when a new release of the anygui API is made. For me (as a potential applications programmer using anygui), the exciting part about a backend separation is the ability to release and revise the anygui API independently of all the various backends that may support it. For example, if I want to use the latest release of anygui with one or two specific backends, I only need to wait for (or even help with *gasp* ;-) those backends to support the latest release and not also wait for a raft of backends that I will never need for my specific situation. That said, I still think that the anygui API should always release with at least one working backend to prevent an 'Ivory Tower' effect. Basically, the advantage boils down to faster iteration on the API. BTW, I appreciate the work that has been put in to all the backends and realize that having multiple backends is what will give the anygui API its value. I just want to start using the API with some of the more popular backends this sometime this year. Thanks again for a potentially awesome GUI programming environment, Jonathan |