Project screenshots - share yours

You can achieve same exact quality in vision because it’s vector base. Just remember to not scale your window (like perspective that doesn’t have any scaling)
For your test as I told you try to divided your processing in several pages so you lower the number of embedded view. And try to use direct object for pipes and other decoration as much as possible. Any constant object like hand value can be object Not embedded view.
I know it’s not ideal for our developer but it is what it is.
This is the problem of using Java even when you don’t use embedded view the cpu and memory usage of perspective is high compare to others. Even in vision the performance of ignition is always lower than other SCADA packages.
If you try webFactory, myscada or factory studio from tatsoft you get what I mean.
In the technical point of view I dont understand why it is difficult to have some wizard option to import html5/javascript component which is made already before import into the perspective and access to their properties in perspective. All other SCADA software do that.

When I spoke to Travis about perspective performance, he said one of the things that they'll most likely be looking at is to flatten the views at the server before sending them across to the client. In this way, all of your embedded views will essentially come to the client as if the components were all just placed on the page itself, thus making load time essentially the same as you see in the flat example in my test (and your screens). The biggest benefit obviously being that then you can structure your project nicely for a developer and have the performance that you would expect.

Yes, but the Java renderer seems to do a slightly poorer job than a browser does. If I compare the same symbol rendered in Vision and Perspective, Perspective wins at least to me

1 Like

Great news, but what happens to component that use dynamic embedded view? Like flex repeater. you may need to change the view path of embedded view component dynamicly at runtime.

Hey guys, I’m wondering if you pick a fixed resolution for your projects, or if you care about responsiveness at all.

I’ve noticed that it takes such a long time to develop an application to be responsive, and the performance is greatly impacted by using flex containers and breakpoints. That makes me wonder if it’s even worth it. I’m curious to hear some thoughs from you all, could you shed some light on the subject?


I actually target FHD for the max resolution of my target devices. If the target device is 2,4,8K there is no problem because the browser does the scaling for us and you see the same size graphic.(unlike vision)
The only problem is if the target device is a little larger than FHD. At this point, I try to center all objects in root to the target screen which looks nice.

Sure designing a responsive page is worth it, but the actual technique you use is really important.
For example for P&ID pages, you should think about using optimal resolution and make your objects always center on different screen sizes.
But for pages like forms, data entry, tabular data, you always had to use flex. As I told before don’t use flex in the repeated embedded view but in the main root page itself is a different story. Even if you use them in Flex in embedded view, there is no problem because the number of embedded views is very low.
There is another responsive design that is important in the embedded view itself. For example, imagine you want to create a valve object for your P&ID, it is nice if the design responds to the actual width and height of the embedded view.


My responsive dashboard style design for pump stations.


Amazing… That responsive design is super impressive as well, something I will need to do for an upcoming project. Keep em coming Nader, very inspirational. Although, as with most things inspirational, the rest of us can only hope to get 10% of the way there :grinning_face_with_smiling_eyes:


Amazing Nadir … your way of using perspective value is different … thanks a lot of sharing this


Automatic detection system for trucks by RFID technology. With the capture of weight from the scale through serial 485 converters. It is a ticket station where the user prints his own ticket. a car service


Interesting. It reminds me of this project in Colombia (Cáqueza, Department of Cundinamarca) 2014 for fixed and mobile toll stations. And all these beautiful trucks richly illuminated!

1 Like

hi nader, are these arrows a gif?

No there are just SVG. With vision timer you can animate them easily.
In each iteration you move the svg shape a head until reach the limit and send back svg to original position.


thanks you

Interested yo know if you using a standard for the devices (valves, pumps, flow switches) or are these a specific customer specification?

No standard per se, and no customer spec. These are our own with influence from ASM and HPHMI guidelines, but not quite

Nice work :+1:

1 Like

Impressive design

1 Like

96x96 LED screen control for sending data from vehicle plates with connection with ignition



Energy Consumption Dashboard
Thanks to forum, I got great support from Ignition community whenever I stuck on some challenges


Hi I’d like to share with you some screens of my first project in Maker Edition ! your feedback is welcomed.