|
Let's make an effort to take those wonderful ideas and tutorials posted on CodeProject and make Universal Gui LibrarY (UGLY)  . Take those owner-drawn buttons and transparent labels and custom scroll-bars and sliders and make a whole suite of tools for windows programming.
We would want to provide:
Consistent interface across controls (function calls, data types, iterators)
Maximum flexibility (skinning, derivable classes)
Maximum efficiency (speedy, powerful, easy to use)
Cross platform availability (.NET, MFC, Win32)
please add more.
|
|
|
|
|
WE need to do this simply in order to use the acronym. I love it 
cheers,
Chris Maunder
|
|
|
|
|
Good idea! My second favorite besides a book. But I wouldn't be the one do the MFC controls.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
|
Important idea. But you might want to help out with that.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Much better acronym.
-Sean
----
Shag a Lizard
|
|
|
|
|
Ok, so I tried far too hard for that! And don't ask what Brian has to do with it... 
I'm sorry. 
David Wulff
"Without hopes and dreams we're directionless" - Anna
|
|
|
|
|
Don't have to ask what Brian has to do with it. It is obvious he is the BUTT of the joke.
:;
|
|
|
|
|
UGL (Universal Gui Library)
[EDIT: Oops! I just saw that there already are one Graphics Library named UGL http://www.gaeinc.com/ugl.pdf [^] ]
/EDIT]
Better name I think. UGLY is a little too suggestive. Just imagine working in that project and thinking UGLY, UGLY the whole day and dreaming the whole night...
And, impossible to search on Google with all those other "ugly" things ..
For example 269.000 hits on "UGLY graphics"
jhaga
CodeProject House, Paul Watson wrote:
...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner.
...Good heavens!
|
|
|
|
|
Well, to be honest, with the number of people getting involved here things could get UGLY really fast. I don't know if that is a good thing. 
|
|
|
|
|
I was just thinking the same thing. Maybe we can break it up into a group of subprojects? Also, we may see the sourceforge effect where there is a flurry of activity with new projects and it seems to taper off fairly quickly.
Hey don't worry, I can handle it. I took something. I can see things no one else can see. Why are you dressed like that?
- Jack Burton
|
|
|
|
|
This is almost guaranteed. Plenty of members never post an article or on a message board. But they participate in the community in their own way. Most of them won't respond to this idea, but some will.
Once things get started people will drop off before it really begins. Then as time goes on they will thin out for one reason or another. The key is to get a good project leader that can own the project and keep it on track.
Keep the core group of people that have physical control over code to a minimum. One person that updates it. Many that contribute via comments, submitting code etc.
|
|
|
|
|
Perhaps we'll let the team leader decide how to handle team members.
I also see us splitting the volunteers between maybe 3 projects. Obviously not everyone can work on the best.
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
Splitting up the volunteers would mean that we lose some of the momentum that we now have. I would rather finish off one project and first then start a new project?
If we split up, nowbody will then be interested in what we do, compared to now when everybody wants to know what is happening.
If we have only one project we can also discuss it in the lounge and it might be fun, but with many projects going on, the discussion would be more boring, I think, because you dont know what the others are talking about.
jhaga
CodeProject House, Paul Watson wrote:
...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner.
...Good heavens!
|
|
|
|
|
That's a good consideration. We'll probably end up starting with the GUI Library, as it's hands down the most popular.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Not to mention the other projects can benefit from using UGLY for their user interface.
|
|
|
|
|
jhaga wrote:
If we split up, nowbody will then be interested in what we do
I disagree. I think having focused teams will be better. If we all work on a single project it makes things more difficult to manage. Also, are you going to work on a project you really have no passion for if you not being paid to do it?
Splitting us up will actually help because you will work on the project that you really like. We all use the same technologies, but as a whole, we have a very broad range of what we apply those too. Yet somehow we have all come here to share our ideas. So with different ideas I don't see us losing interest.
|
|
|
|
|
I just worry that we will end up with projects were only 1 or 2 people are really doing something.
If we have 40 people on one project then maybe 20 does something and 10 works intensively.(Taking in count that most of us have a work or study) With more people there will always be something happening, and we can daily follow the progress in the lounge. Anybody who has ever been in a SourceForge project, knows that it is not fun when nothing happens in months.
jhaga
CodeProject House, Paul Watson wrote:
...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner.
...Good heavens!
|
|
|
|
|
How about we just split into coding units, so different teams focus on different sectors of the project??
Would this work?
*¨¨`)
¸¸.·´ ¸.·*¨¨`)
(¸¸.·* ¸ .·*
¸¸.·*
(¸¸.~~> Joel Holdsworth.
|
|
|
|
|
Good Idea!
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Sounds ok to me.
jhaga
CodeProject House, Paul Watson wrote:
...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner.
...Good heavens!
|
|
|
|
|
Here's how I envision it, but I assume the project leader will decide on team structure and function.
Project A has 20 developers that want to work on it. They assign a project leader who will assign roles. Like any software project, Project A is split into sections (say GUI, app preferences, and main functionality). The project leader will asses his resources (developers) and assign them to teams for these different sections.
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
How about this:
1) We start with the most popular project, for example UGLY and call it Project A, assign it a project leader, and let people sign up.
Probably 15-25 will sign up and we will have a stong group that can start working right away.
2) People who have not signed up at Project A can then vote on which shall be the next project, Project B, assign project leader, and let people sign up, and start working.
3) Then Project C etc. until everybody have found a project were they want to work in.
This could be an ongoing process were new volunteers sign up and new projects are found for them.
jhaga
CodeProject House, Paul Watson wrote:
...and the roar of John Simmons own personal Nascar in the garage. Meg flitting about taking photos.Chris having an heated arguement with Colin Davies and .S.Rod. over egian values. Nish manically typing *censur*. Duncan racing around after his pet *c.* Michael Martin and Bryce loudly yelling *c.* C.G. having a fit as Roger Wright loads up *c.* . Anna waving her *c.* and Deb scoffing chocolates in the corner.
...Good heavens!
|
|
|
|
|
Here's the way Chris M. explained how it would probably work:
A project will be alot like articles and anyone can create one. Once its created, the leader/creator can accept requests to join the team. Then the leader will assign jobs.
So we could have any number of projects going at once.
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
So I guess we start tomorrow? I have tons of ideas for the top 2 projects.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
