Date 1 - 1 of 1
[controller-dev] Learning curve for new users of the ODL platform
|1 - 1 of 1|
Chris Wright <chrisw@...>
* Srini Seetharaman (srini.seetharaman@...) wrote:
I started out as a beginner user of the ODL platform and put together theThank you for the feedback, it's very useful (and mirrors some of the
feedback I've heard too).
I wanted to kick off a discussion about howWhat do you consider the audience? This, to me, sounds like a
developer, not a user. I'd expect a user to get a prebuilt controller
and use that. IOW, OSGi, Eclipse and Maven seem out of scope for an
And, put another way, are you interested in helping with this kind of
documentation? It's a big gap right now, ready to be filled with
awesome volunteers ;)
- Why not leave out the tests for the modules from the basic edition?I think this is the right mindset (app dev != platform dev). This should
be possible already if you build your app separately from the controller.
As one extreme, imagine an app written in python using REST API only.
A Java app can build and load into the controller w/out building the
- It will help to have several primitives that make it easier to performAre you thinking of helper application libraries?
- Coding style is too anal about the trailing space. This is the mostWe have a little bit of this in the wiki and can certainly use more/better
doco, but debugging and compilation, again, are more developer oriented.
Having clear command line (I dunno, maybe example for run.sh -debug) and
details on log files, etc. make great sense for users.
- Using eclipse + running consumes quite a bit of memory and computingthanks,
|1 - 1 of 1|