If at every point you encounter a surprise or frustration, your response is to add it to the blacklist. Furthermore it is common to feel intimidate to journey down that bumpy "road less travel" and easily get burned by incomplete understanding.
Mango is awesome. It's easy to learn partially, and much harder to learn completely. Inspiring a strong appreciation for all that Mango is and can do will help in shorten the learning curve and eventually more projects are built on the Mango platform.
Certainly possible, I don't have time to get right into this right now but you could use the maDataSource service to check for the existence of the DS and create it if one matching the name attribute doesn't exist.
If this is remotely similar to making a new point using the maPoint service perhaps I can be of assistance here
I don’t ask you to give me an example , but I would like to know where I can learn myself ?
What is the best way to do myself a complete flex page with side bar and one or two windows ?
If I can pick up pieces of code an put it into the edit markup , it’s OK.
Just my five cent thought,
1.There is no best way to do a web page
2.Copy and paste pieces of code without understanding will make your learning disable.
3.The web technologies is a prerequisite, at least know the fundamentals,
3.1. HTML to define the content of web pages
3.2. CSS to specify the layout of web pages
4.The learning speed is your choice.Everything is up to you.If you are struggling, take a break, or search google for the material
5.Explore the example page provided by Mango. Examples are often easier to understand than explanations. Try it out yourself. In my opinion, this is one of the best playground for anyone who want to learn and understand Mango.
Update on a really old thread. There was just no option for me to change anything on the PLC side as mentioned before but figured out a workaround.
The problem was that the pump could not be started if the stop bit held the 1 (or stopped if the start bit held the 1) You can visibly see a stuck button if the bit held the 1. The same button could be pressed again to attempt to write a 0 at release.
But instead of explaining that process, I am having the momentary of the start write a 0 to the stop and the stop will write a 0 to the start. This ensures the end user uses the buttons as intended without having to worry about stuck button or held bits. Seems to work fine.
Thanks for the suggestions, I ultimately went a different route with this, and bound a slider to the variable that was previously at the top of the page (which was 30 in the first instance) and allowed the user to select how many days worth of data they wanted to see:
The text box is also editable, so they can manually type a number in, if they wish (the '500' example at the end). I did use some of the styles suggested to modify the axes to a different grey to lessen it's impact upon the page, but it also meant that the X-axes date was relevant again, so the requirement to remove it changed (let's just call it 'agile development :). The slider modifies about 10 graphs across the page and works quite fast.