Author |
Topic: GUILIB (Read 617 times) |
|
Andy Parkes
Developer
member is offline
Gender: 
Posts: 25
|
 |
Re: GUILIB
« Reply #45 on: Jan 31st, 2014, 10:15pm » |
|
Hi Folks,
Over the past couple of days, I have made a stab at section 1 of Richard's GUILIB specification, specifically:
1.1, 1.2, 1.3, 1.4, 1.7
http://wiggio.com/yui/folder/stream_file.php?doc_key=qzoGwHPMw5YPmQHvlem1YJwv2VPYvWN4fAwoh5i5FIE=
The start of the file contains some code to demonstrate its use. I have made no attempt to include code to handle events, so if you run it, its best not to click on anything until its done. I think it succeeds in setting 'a' foundation for a simple unified interface for all window types and controls, but I've achieved this using brute force and ignorance. You'll see what I mean.
Theoretically, I could continue in this fashion and meet most of the specifications for GUILIB, but I think it would turn into the 'John Logie Baird' rather than the 'Marconi-EMI' of GUILIBs.
http://www.bbc.co.uk/programmes/p019d7fl
Thanks
Andy
|
|
 Logged
|
|
|
|
admin
Administrator
member is offline
Posts: 1145
|
|
Re: GUILIB
« Reply #46 on: Feb 1st, 2014, 09:56am » |
|
on Jan 31st, 2014, 10:15pm, Andy Parkes wrote:| Over the past couple of days, I have made a stab at section 1 of Richard's GUILIB specification |
|
Not content with three people (seemingly) independently working on GUILIB, we now appear to have a fourth!
Whilst the last thing I want to do is to curb enthusiasm, which is sorely lacking (not least on my behalf!), this is no way to run a software project! The idea was that GUILIB would be a collaborative effort; quite how the work might be farmed out I don't know - presumably there would be somebody (not me!) in overall control.
A prerequisite for a 'team' development is for the specification to be sufficiently detailed and complete that everybody knows what is being aimed for, and I don't think the existing spec achieves that.
So can I ask that Matt, Svein, David and yourself get your heads together, decide who is going to be in charge, update the spec (I would want to take a role in that) and then work out how to proceed from there?
If you, collectively, don't feel that a collaboration is possible I'm not sure how we should proceed. I don't want to be presented with several independent offerings from which I am expected to cobble together some kind of Frankenstein's monster of a library. 
Richard.
|
|
Logged
|
|
|
|
|
