Re:
- Posted by "Patrick Barnes" <mistertrik at hotmail.com> Jun 04, 2004
- 1749 views
>From: Robert Craig <guest at RapidEuphoria.com> > > That is fine, I know you're close to releasing 2.5 now. > > Could we have a page on rapideuphoria somewhere that shows the features >you > > plan to implement in the next version of the language (So currently for > > 2.5), and a list of features that are being considered for unspecified > > versions beyond that? It would make it easier for us to see what you are > > planning with the language, and make appropriate suggestions. > >That's been requested before, >and I think I promised to do something or other. >I'll think about it. Maybe we need an official >system for posting suggestions and bug reports >and getting a quick one-line response from me: > "Yes, it's a bug", > "I love that suggestion!", > "I hate that. I'll never, ever implement it" > etc. > >It comes as a shock to some people, but >I don't have any master plan. >Once I latch onto something useful, I implement it, >then I go back to my pile of half-baked ideas >and suggestions, and pick out something new to >work on. There's no plan. If post my long list >of cryptic half-baked ideas, I'll be flooded with proposals >and questions about all sorts of odd things that I >really don't want to implement. Heheh... Well, perhaps split it up into sections. Have a section called "Cloud 9", or even just "Half-baked ideas" for that, and state at the top that they're not being seriously considered now, or possible ever. If someone submits something that is so obviously a bad idea ("Rob, why can't I write inline COBOL in euphoria????!?!?") it can be moved to a "Bad idea section". Given your experience with ListFilter, a good idea might be to parse any top-level submissions (proposals, not replies), and show a list of "this idea may have been submitted already in one of these previous submissions, check before posting" to reduce duplicates. Allow users to edit the top-level submission (the proposal) as new ideas are incorporated into the proposal, with a changelog. Mark agains replies to the proposal what version the replies were made. Hmmm, I think this would be nice. MrTrick