Hi,
Is it just me but I get frustrated when I find and example and after making it work how I like I then find the component does not work the same in the format I am using.
This instance I am looking at is the radio button. There was no example in the web app section but I found one in the app developer section. I modified it and was happy it worked how I wanted. I then went to add it to the web app project I am working on and found it is totally different.
It is really frustrating to find things that should (in my opinion) work the same but are totally different.
In the app developer version the radio button has a property to select how many buttons, you can set the button texts etc all in the same component.
In the web app it is one button that you then have to group with others but no example how to do it.
Just why they are not the same is beyond me as they do exactly the same thing and to make them different but with no example is really is frustrating.
Making them different surely actually makes more work, if they were consistent there would not be as much need to make individual examples?
Regards,
Bob
Frustration with Flowcode inconsistency
-
RGV250
- Posts: 434
- http://meble-kuchenne.info.pl
- Joined: Sat Mar 19, 2022 4:53 pm
- Has thanked: 43 times
- Been thanked: 44 times
Re: Frustration with Flowcode inconsistency
Hi,
I think this follows on from my post regarding the 7 segment display that does not have a "show segments" component in web app where app developer does.
Bob
I think this follows on from my post regarding the 7 segment display that does not have a "show segments" component in web app where app developer does.
Bob
-
Steve-Matrix
- Matrix Staff
- Posts: 1828
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 263 times
- Been thanked: 422 times
Re: Frustration with Flowcode inconsistency
Although Embedded and PC Developer share many similarities and often the components used in one are the same as the other.
Web Developer is fundamentally different. It is based on JavaScript rather than C and the simulation is inherently different. Programming concepts for a browser-based environment are also different and so you will need to approach programming in a different, event-driven way.
These differences often mean that components in Web Developer need to behave differently.
Essentially, you will not be able to use Embedded or PC Developer examples as a basis for Web Developer applications.
That said, the common environment of Flowcode should help when creating Web Developer applications.
Web Developer is fundamentally different. It is based on JavaScript rather than C and the simulation is inherently different. Programming concepts for a browser-based environment are also different and so you will need to approach programming in a different, event-driven way.
These differences often mean that components in Web Developer need to behave differently.
Essentially, you will not be able to use Embedded or PC Developer examples as a basis for Web Developer applications.
That said, the common environment of Flowcode should help when creating Web Developer applications.
-
Steve-Matrix
- Matrix Staff
- Posts: 1828
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 263 times
- Been thanked: 422 times
Re: Frustration with Flowcode inconsistency
We have plans to improve Web Developer and having more help and examples on the wiki is part of that.
If you ever can't find info in the wiki (because even when it is there, it is sometimes easy to miss), then please post specific questions on these forums.
We try to be responsive and are happy to help. Plus our other users (and our knowledgeable VCs) are often able to respond with help before we are.
If you ever can't find info in the wiki (because even when it is there, it is sometimes easy to miss), then please post specific questions on these forums.
We try to be responsive and are happy to help. Plus our other users (and our knowledgeable VCs) are often able to respond with help before we are.