From: <hp...@we...> - 2022-06-08 01:44:08
|
Hello René! Am 07.06.2022 um 21:59 schrieb René Jansen: >>>> [...] >> Main obstacles had been: wrong file type, must be .njp instead of >> .nrx, no option (sep !) possible, no /* */ bracketed comment on >> line with addpipe, and many other showstoppers I can't describe >> any more. >> > I don’t know if you are like me, always having a blocnote to jot things down - that might be quite valuable. As these emails are. Hopefully you are not like me, otherwise colleagues might dislike you. No, I am not taking notes, what I can't remember was not worth it. I know this is a problem, getting older I forget too much. For example now in this respect of NetRexx Pipelines I got some hints and can't find them any more. Was it on this list or on ooRexx help forum? Time of others wasted who tried to help. Sorry. >> [...] >> Next steps? No idea. Experts -- please advice. > > If you want to donate the stage, we can put in in 4.04. I’ll have a look at the other pipes. Donate? But it's absolutely not finished yet, it's nothing but a first try how it /could/ look like. In addition, donate... all code snippets, all ideas discussed and published here are public property. My point of view. Just in case (if ever) I claim something to be my ownership I tag it 'licensed under the QPL 1.0" (what is a joke because I can't enforce it). No, this Varload still needs some enhancement. First and foremost a mechanism to actually set variables /at minimum/ in callers variable pool. In addition, did you see all the options of Varload in 'the book'? Then, do "we" have templates like those here: http://vm.marist.edu/%7Epipeline/#Skeleton ? I found them helpful not to forget something. Best, M. |