Hi, > This is all very abstract. New features should be use case driver, and > not "abstract idea driven". > I can't see what wrong with abstract ideas as material of design, but Sergi is suggesting the same thing. He only resume all that has been said about extensions to end this theoretical thread and go from abstract to start with some prototype or proof of concept implementation. > What about providing some example (client) source code, including some > documentation what it does? That makes it _much_ easier to decide We open the discussion to see all possible points of view for scatter the best ideas and your opinions and guidance before start anything. We express common interests with the intention of collaborate, but before this mail we don't even know if you wish or will decide to drop or drive this initiative personally. Anyway your response is clear about your expectations.
Regards Dario -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
