I have commited recipes (except HowTo Use I/O) and core/mixin so far. Code is compilable and _should_ be valid in runtime.
I think new section for articles should be added and HowTo Use I/O moved there. It mentions exact old Qi4j version and is dated. So I think it shouldn't be updated. On Rickard's blog there is a lot of amazing stuff... Create a Constraint recipe should be reviewed, as it's second half is not valid for current version. The same for Create an Entity ( i.e. property subtyping). I can do it myself, but I can only delete invalid parts probably. Should SNIPPET tag be added also into not test/sample classes ( i.e. PropertyMixin.java ) ? If files are not placed in right place, let me know. / Tibor On Tue, May 29, 2012 at 5:09 PM, Niclas Hedhman <[email protected]> wrote: > On Tue, May 29, 2012 at 10:35 PM, Tibor Mlynarik > <[email protected]> wrote: >>> Why not use several snippets? >>> >>> For example, you could define a tag used in several files and then insert >>> multiple [snippet,java] in the asciidoc file. >>> >> >> only objection is that it generates multiple blocks and it doesn't look nice. > > > I object. I think multiple blocks are "better", so that there is > enough space for proper explanation before/after relatively short > chunks of code. Long listings in tutorials are typically skipped. > > Try to keep as much code as possible "runnable", since a fair deal of > Qi4j is resolved in runtime (not compile time), so to avoid > "embarassing" comments from users, saying "Hey, I copied this piece of > code and it throws the following exception in runtime, why?" kind of > questions... > > But I really appreciate your intended effort, so if you insist on > doing it "your way", I will not revert any progress.... ;-) > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/6a2pl4j > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
