pinky-develop

[Pinky-develop] PiNKY 0.1.0 Released

[Peter R. <dr...@us...>]

PiNKY 0.1.0 has been released.  It is available as a sourceforge
download and is also installable within NetKernel using the module installer

Download Install Instructions:

1) download mod-pinky-0.1.0.jar
2) edit NK's etc/deployedModules.xml and add an entry pointing to the jar.
3) boot or cold-restart NetKernel
4) Search for PiNKY to find the documentation

Repeat for test-pinky-0.1.0.jar which contains the unit tests and usage
examples.  To execute tests after install go to
xunit in the developer panel.

NetKernel Module Installer Instructions

1) Go to the module manager:
http://localhost:1066/ep+name@app_install_installer
2) Choose "Install new applications and library modules"
3) Choose "Install new modules from 1060 Mirror."
4) Select your preferred mirror and make sure to check "Display
libraries" (it can take up to 24hrs to be mirrored so use 'Primary
Mirror' today).
5) Select PiNKY and PiNKY Tests from module list.
6) After restart search for 'PiNKY' to find the documentation

Release Notes:

This is the first public build of PiNKY. It implements a large set of
composable feed processing services for high-level feed pipeline
processes.  In addition it contains a resource object model for
constructing and manipulating feeds using either native Java or the
procedural dynamic scripting languages of NetKernel.

Breaking News:

Added a new SetFeedInfo accessor that provides a declarative way to
configure feed metadata.
Added usage examples to the test module in /test/examples/
Wrote a fairly comprehensive guide - search for 'pinky guide'

Enjoy...

The PiNKY Team

Re: [Pinky-develop] PiNKY 0.1.0 Released

[Brian S. <br...@bo...>]

I would like to bring up the point about style. Right now we have  
multiple formatting styles including Randy's own... uhm...  
interesting style that he applied to the CountAccessor when he added  
types to it. :)

We should probably standardize on something idiommatic and apply  
CheckStyle.

Additionally, as this is a dual-purpose module to demonstrate how to  
do these things, I would like to suggest that we don't use the .*  
import notation since that makes it more difficult for people not  
using IDEs to find where things come from.

I plan on being aggressive with Eclipse's Organize Imports feature.  
Just want to throw that out there.

Congrats on the first release.

I'm going to demonstrate Pinky as part of a new Data integration talk  
at the NFJS shows this year.

[Pinky-develop] Package Imports/Style was Re: PiNKY 0.1.0 Released

[Peter R. <dr...@us...>]

> Additionally, as this is a dual-purpose module to demonstrate how to do
> these things, I would like to suggest that we don't use the .* import
> notation since that makes it more difficult for people not using IDEs to
> find where things come from.

Interesting.  I usually find the opposite - developing without code
completion/IDE-support using a variety of languages I find it much more
tolerant and flexible to a do package import (*) of Java classes.  Class
by class is very hard to manage without an IDE.

For the record, it is safe to do * imports in a class in an NK module
since each module's class package space is dynamically managed by the
module classloader. This classloader isolation means its very very rare
to get class collisions.

So for flexibility/malleability we tend to use a * imports of packages
in NK module classes rather than class by class.

I can live with class-by-class if that's the consensus, just thought I'd
raise a general point.

> Congrats on the first release.

Congrats all round.  Incidentally do you think we should have a
contributor page on pinkypipes.org to give all contributors credit?

> I'm going to demonstrate Pinky as part of a new Data integration talk at
> the NFJS shows this year.

That's great!

Pete

PS Butterfield Condensed Bracket Notation eg

method()
{	blah;
	blah;
}

is the in-house 1060 style.  This originates from Mr B. who is an
obsessive normalizer and will not tolerate any waste of space - probably
'cos he learnt his craft developing z80 assembler games using peek/poke.

Re: [Pinky-develop] Package Imports/Style was Re: PiNKY 0.1.0 Released

[Brian S. <br...@bo...>]

On Feb 23, 2007, at 3:35 PM, Peter Rodgers wrote:

> So for flexibility/malleability we tend to use a * imports of packages
> in NK module classes rather than class by class.
>
> I can live with class-by-class if that's the consensus, just  
> thought I'd
> raise a general point.

<shrug>

> PS Butterfield Condensed Bracket Notation eg
>
> method()
> {	blah;
> 	blah;
> }
>
> is the in-house 1060 style.  This originates from Mr B. who is an
> obsessive normalizer and will not tolerate any waste of space -  
> probably
> 'cos he learnt his craft developing z80 assembler games using peek/ 
> poke.

I don't care what the style is, I just want it to be consistent. In- 
house 1060 style works for me.

Do we have any guidelines about language features? 1.4 only? 1.5? 1.3?