On August 11, 2011 05:17:41 am kfj wrote: > spaghetti code I'm hungry. Let's add some sauce, cheese, and wine!
> To put it very bluntly: It's a techies' show. Scary thought. I prefer to see it as a time-share. It is time for the techies to drive now, and for the rest of us to take a back seat. > > Kay's current proposal, from an end-user point of view, is STATUS QUO. > > Not better not worse. Simply unchanged. It is user friendliness for > > the users of the codebase, i.e. the developers. > > I beg to differ. I hope it will be better, because it should be faster > and crash less. Will you deliver? I rather under-promise and over-deliver than the other way around. > I know nothing of the design concepts and implementation > strategy behind hugin's GUI, but maybe someone from that end can > comment? Like point me to a technical outline? http://ippei.wordpress.com/2007/05/30/the-tasks/ http://ippei.wordpress.com/2007/06/02/categorising-the-header-files/ http://ippei.wordpress.com/2007/06/04/progress-4th-june-run-out-of-creative- titles/ http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/GSoC%202007/Presentation%201/Revising%20Architecture.pdf?revision=2494&pathrev=2494 http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/GSoC%202007/Presentation%202/Beyond%20Hugin.pdf?revision=2494&pathrev=2494 > From the GUI side, when you get a plugin you > see a new menu entry show up which you can click on. Something > happens. What can be more user-friendly? mhhh... that's a little bit spartan. I think there are other definitions of user-friendly, but it is still too early. > I am a competent C/C++ programmer. Yet I know next to nothing of > wxWidgets. If we structure the code well enough, we can make it as GUI-toolkit-agnostic as possible. Do you have a favorite GUI-toolkit? It is even thinkable to have different GUI toolkits for different platform. Many Mac users prefer their app to be Cocoa than wxWidgets, or Qt, or any of the other panoply of available choices: http://wiki.python.org/moin/GuiProgramming > Actually at the moment we have nobody on board. It's a matter of > perspective. Isn't it you the shadow I see in the driver's seat of the bus I am sitting in? Or should I worry and get off at the next stop? > codename munin http://munin-monitoring.org/ > > This is no corporate environment and there is no need for a business > > case. It's a scratch your own itches environment. If Kay has an itch, > > he will scratch it. And if more than one person has an itch and want to > > team up, they will. This is no place to argue for or against: > > everybody is free to do what they want; and without meaning to be > > derogatory, it is no democracy either. It is not 95%. It is not even > > 5%. It is an individual choice for each and every person in the room. > > What can I do and what do I want to do. Kay definitely seems to want > > to go this way and I am with him. For as much as my participation is > > worth. In four weeks I will be reading only legal code and writing > > exams. > > If I'm not mistaken, hugin took of as an individual's project. See > what became of it! The foundations were laid, the concept was good, it > attracted people who put their bit in, and now we have an extremely > powerful tool which demonstrates what can be done and how to do it. > And which we can use as a template, as inspiration, and as code base > for the munin project. The power is not in the tool. The power is in the people. In how we structure ourselves, empower each other, learn from each other, encourage (sometimes prod) each other to progress, try new things, and move forward to where Hugin has never been before. And in how we comfort each other when things crash, as they sometimes do. > > This won't touch the Hugin default branch. It will be a separate branch. > > Or maybe it even makes sense to start a new repository, from scratch, > > and carefully cherry-pick / migrate by copy&paste desirable code while > > leaving the cruft behind. > > I'd do the latter. And start with the basics, preferably with some > sort of application template mechanism that takes care of the standard > basics. Then fill it in with hugin-specific content. As few reinvented > wheels as possible. The time passed since hugin's inception should > have expanded the universe of available tools so much that a lot of > stuff which still was hand-coded in hugin could now be taken from > standardized sources. It ought to be a huge relief. Agree. Do you want to set up a project on Github? I know you don't like SourceForge. It's a historical given. Launchpad is great for tracking tickets (and being able to add attachment up to 100MB and answer by email helps a lot), but I don't like bzr. We could also try tracking on Github as well and see how it goes? > As we progress in software, we must embrace ever more complex and > powerful tools to harness the ever-increasing power, complexity and > sheer volume of our systems. Or stagnate. We can choose. Progress. This is the spirit of Hugin. > > We could (don't jump at me, please) drop *in*the*short*term* the multi- > > platform requirement and initially focus on achieving quick results for > > the one platform that we (team of people that decide to join Kay) choose > > as ours. If what we do is good, others will adopt and adapt it for their > > platforms as the project grows. > > I think this would be wise. If we keep in mind that we want it to run > on all platforms again eventually, we could have a munin policy to use > only such modules (or versions thereof) which are available on all > platforms, and be conservative with very bleeding-edge features Or wait until the other platforms catch up. It's a trade-off and the fine- tuning depends on the point in the life-cycle of the project and of the platform. At an early stage, everything is game. We'll zero-in on it when we get closer to be ready for prime time. What is important is what you say, to keep in mind that we want it to run on all platforms again eventually, and to design smartly for it so that when the platforms catch up, we're ready (or the other way around). > Let me add: There's no threat to the established system. Noone is > going to 'break' that or render it inoperable. If munin fails, the > only loss to hugin will be the development time which people devote to > munin rather than struggling on with hugin. And hugin might even be > able to salvage the odd non-stick pan from it ;-) This can't be reiterated often enough. No threat. If we fail, all we will have wasted is only our time. It is not even a loss to Hugin. Nobody has a claim on your time, not even Hugin. Yuv
signature.asc
Description: This is a digitally signed message part.
