Re: [fltk.development] collect all fltk libraries
> HI, > Please FLTK developer try to find a way to collect the small projects (small > extra library that is an extentions for fltk). > As you didn't like my suggestion for the git , and it is up to you to do so > but collecting the widgets beside the core FLTK is very important. Many > questions in the forum is for finding them .. If you have them on the same > home site, you make it easy for beginner and other who are interested in the > toolkit to find answer for their questions. > I hope that you discuss this issue between you .. > Regards, > In fact, using git is a good idea. I used to use svn, but now find git is much more easier to use. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] collect all fltk libraries
On 01/12/12 10:05, Greg Ercolano wrote: > With the current system, 3rd party FLTK widgets are all under > fltk.org -> Links -> Show All Listings, eg: > http://fltk.org/links.php?LA+Q > [..] > We would probably still need a link 'janitor' to annually > purge stale links, or try to figure out what happened to > authors that haven't updated their code in a while. > > No one has stepped up to handle that job in the past, > so I'm not sure the future would be much different. > [..] I just went through about 15 or 20 of the 'Applications' and tested links, changing the title of any that were stale to include "[STALE LINK: Jan 2012]" in the entry's title. Probably 75% were stale. I'd suggest we add a 'janitor' page so that it's easy for someone to quickly test links and change the status of the entries to 'stale' or 'verified', so that stale stuff automatically move into a 'stale links' category. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] collect all fltk libraries
On 01/12/12 09:05, Mariwan wrote: > HI, > Please FLTK developer try to find a way to collect the small projects (small > extra library that is an extentions for fltk). > As you didn't like my suggestion for the git , and it is up to you to do so > but collecting the widgets beside the core FLTK is very important. Many > questions in the forum is for finding them .. If you have them on the same > home site, you make it easy for beginner and other who are interested in the > toolkit to find answer for their questions. > I hope that you discuss this issue between you .. Yes, we should consider a better way for when we make the next change over. With the current system, 3rd party FLTK widgets are all under fltk.org -> Links -> Show All Listings, eg: http://fltk.org/links.php?LA+Q ..which has all kinds of categories: 'widgets', 'tutorials', 'apps', etc. It's a page that indirects to the locations of the actual code. If the problem with the current system is mainly *stale links*, ie. our links point to sites that have since disappeared, I imagine that could be solved if all code projects had to be hosted on either sourceforge or github so that the project remains if the author disappears. We would probably still need a link 'janitor' to annually purge stale links, or try to figure out what happened to authors that haven't updated their code in a while. No one has stepped up to handle that job in the past, so I'm not sure the future would be much different. Someone would have to take on the job of managing the 3rd party stuff to keep the page "in shape". ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
