LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: SambaDancer

My personal wish list for future versions. Pleas add your own/(down)vote.

1. Replace floating point arithmetic with fixed point arithmetic. Make rounding (forgive me) more 'Excel-like'.

2. Thousand separator in BRD Viewer.

3. In BRD Viewer, right-align numeric fields.

4. BRE for Linux (not just server: BRE !).

5. Make the help file more readable for non-techies (I'm not stupid, but I have to read some instructions 5 times before I get it).

6. Create a 'Scripthub': a centralised library of examples.

7. Share documentation + examples on commonly used authentication methods for API's (e.g. http node).

8. Make it possible to work together on a single graph.

9. De-installation => key is unlocked again for installation on another machine.

10. Installation on a VM should be possible by default, not on request.

11. Override emit should place the overwriting field on the same horizontal position as the overwritten field (instead of all the way at the end).

12. Include basic Python (etc) courses on the Lavastorm Academy).

best regards from The Netherlands,
Bart.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Back to #11.. are you aware of this?

The code above will place the new field value as the FIRST column (far left), rather than as the last column (far right)

Are you also aware that you can set the order of the fields in the BRD viewer and they will be remembered from session to session? (but doesn't affect writing to excel, etc)

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Here are some of my own personal observations.. these are NOT official company policy...

4) Stay tuned for LAE version 7.. it will be browser based, therefore much more platform independent.
5) Technical documentation always tells you WHAT a function will do, but it can never tell you WHY you would want to use it. Your request #6 answers that question better.
6) There are a fair number of examples here in the forum. There obviously could be more, but so much of what you can do with LAE is dependent upon your unique mix of data and business rules.
7) Same general problem.. each API is so different that there may not be a lot of reusable material.
9) This is possible if you simply contact license@lavastorm.com
10) What issues are you having with VM?
11) It is a common request to be able to specify column order, but.. for extremely large datasets, that option can significantly affect performance. In the past, the decision was generally to favor performance over maintaining column order. Specifying column order is a recognized need when publishing data (Excel, Csv, Email, etc)
12) There are two documents (Java/Python) for writing custom nodes. have you seen those?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

A bit more on #5 - Documentation. When I am teaching class, I always advise students to deal with technical documentation this way:

Read the ENTIRE documentation start to finish THREE times.

#1 - Read the document from cover to cover just to see the words without attempting to understand the context. If there are any words/terms you don't understand.. make a note and look them up. If it's printed documentation, I advise doing this step _away_ from the computer.
#2 - Re-read the whole document, again without trying to act upon what it is telling you, this time to trying to understand the concepts. But don't allow yourself to get bogged down in making any of them work.. you're just trying to comprehend the concepts.
#3 - Finally, re-read each section and try to _use_ what it is telling you, but keep it to small pieces of sample data, rather than some advanced analysis request from your boss.<grin>

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: tiendat

tks you )))

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: SambaDancer

Thanks so much, Stony!
Can't wait for LAE 7.
Tip on 'default emit' is a great one!
I still think the help file could use a 'for dummies' upgrade; For example, the documentation on the html node is very good and understandable, but on 'older' node it's very technical.
I don't have isues with VM, other than the fact that you need another license for it than for a physical machine.
I know every API is different, but there are only so much authentication methods, like OAUTH, SOAP, etc. Some general pointers / examples would be great, as are some common causes of failure.
Gonna study the Java/Python docs!
Best regards from The Netherlands!
Bart.