Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-08 Thread Rickard Öberg
On 2010-11-07 12.20, Stanislav Muhametsin wrote: Quoting Rickard Öberg : My plan is to have the basics within Qi4j (e.g. read lines from a text file), and then have Inputs/Outputs where it makes sense (EntityStores especially). Outside of that developers are free to create their own Inputs/Outp

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-07 Thread Stanislav Muhametsin
Quoting Rickard Öberg : My plan is to have the basics within Qi4j (e.g. read lines from a text file), and then have Inputs/Outputs where it makes sense (EntityStores especially). Outside of that developers are free to create their own Inputs/Outputs/Specification/Functions to shuffle dat

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-06 Thread Rickard Öberg
On 2010-11-06 15.04, Niclas Hedhman wrote: I'm not sure that's the best example, since for reading files like that you will end up with one object (a PDF-document) rather than 1-line->1 PDF-object. But for any such transformation, like the String2JSON example, you just create your own Function.

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-06 Thread Niclas Hedhman
On Sat, Nov 6, 2010 at 2:20 PM, Rickard Öberg wrote: > I'm not sure that's the best example, since for reading files like that you > will end up with one object (a PDF-document) rather than 1-line->1 > PDF-object. But for any such transformation, like the String2JSON example, > you just create yo

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-05 Thread Rickard Öberg
On 2010-11-06 14.07, Niclas Hedhman wrote: It looks pretty good. But one thing that 'bothers' me is the static class methods for Inputs and Outputs. They are not very extensible without having access to the library itself. I assume that we don't want that in Qi4j at all and instead have some type

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-05 Thread Niclas Hedhman
It looks pretty good. But one thing that 'bothers' me is the static class methods for Inputs and Outputs. They are not very extensible without having access to the library itself. I assume that we don't want that in Qi4j at all and instead have some type of injection/lookup/resolution... Use-case

Re: [qi4j-dev] A generic Input/Output API in Java

2010-11-05 Thread Rickard Öberg
On 2010-11-06 12.52, Rickard Öberg wrote: The past week I have battled with shuffling of data between sources, such as doing restores of backups and similar. I came to realize that there was a pattern behind how these things work, and created a simple API that allows inputs and outputs to be enca

[qi4j-dev] A generic Input/Output API in Java

2010-11-05 Thread Rickard Öberg
Hi, The past week I have battled with shuffling of data between sources, such as doing restores of backups and similar. I came to realize that there was a pattern behind how these things work, and created a simple API that allows inputs and outputs to be encapsulated and easily used in differ