>Now i`m adding new capabilities.
That means you are already working on the next milestone ... >but It does not have sense to raise something incorrect or incomplete If that wouldnt make sense you wouldnt have a pharo image (or any other kind of software) in your hands :) Even when you can prove your software is correct (whatever that means in a context of a UI builder compared to an algorithm) there is always something you can add. So it will never be complete. Even when it is not complete in your own eyes you should declare it "pre-alpha" work and make it accessible. Dont fear that others look at your code! Hey with Smalltalk in your hands your code cant be that ugly ;) You already got positive feedback that you started such a project and people are able to help or tell you what features/directions they would like to see. They may even help you to find and fix bugs. It could also be that nothing happens and you work on it alone as it is now. It may also be that you loose interest and others take it as a base and continue with your work (depending on license). Who knows ... >I prefer not to say when I will conclude my work Release early and show a steady progress by releasing often. Thats the key to success. And listen to feedback. Otherwise you will work towards "the perfect time to release" (remember you already said it will be in a releasable state after 14 days) You already mentioned the next tasks on your list (which will continue to grow the more you work since you will get more ideas and it will become more and more work for a single person). Most of the time projects working towards perfection will never be released or used. There is also the problem that others will start developing a similar one meanwhile since they cant wait or dont know that there is already someone investing his time and knowledge. Even when you think the day has come and anything is perfect you may be disappointed since it is possible that people disagree with the result and come up with something different. Even when it is good others may develop different UI builder frameworks (have a look at Java ;) As I said there is no "complete" or "correct" code - the world is spinning day by day and projects, people, contexts, ... will change. Anything that does not change or adapt to the next day can be declared as dead. >I´m put much effort in that work and i want do it good. However ... it is your decision. I for my part would really like to see a nice UI builder for one of the early releases of Pharo, especially since you already put so much effort into it. Bye Torsten -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
YES!!!
On Aug 30, 2009, at 11:57 PM, Torsten Bergmann wrote: > Release early and show a steady progress by releasing often. Thats the > key to success. And listen to feedback. > Otherwise you will work towards "the perfect time to > release" (remember > you already said it will be in a releasable state after 14 days) > You already mentioned the next tasks on your list (which will continue > to grow the more you work since you will get more ideas and it will > become more and more work for a single person). > > Most of the time projects working towards perfection will never be > released or used. There is also the problem that others will start > developing a similar one meanwhile since they cant wait or dont know > that > there is already someone investing his time and knowledge. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |