- Joined
- Jul 16, 2009
- Messages
- 9,262
- Reaction score
- 15,533
I am fine with the general layout -- but there are numerous places that really need some love.
TIMERS:
@Matthias @Gaël -- I understand that the interface hosted on the device may be limited by resources, but the lack of friendly names throughout the interface is extremely problematic in systems with numerous timers, logic, switches, pumps, etc. One should not have to have a manual reference chart of names to ordinals for switches, logic, pumps. timers, etc. It is cumbersome and invites errors.
GCC is long in the tooth, and Windows Only -- You have stated that you have zero plans to port it to MacOS.
However, other than firmware, GCC can run via TCP/IP -- so why not build a modern cross platform application using any of the modern stacks? That way the interface can be a but more polished for LOCAL TCP/IP programming, replacing the clunky GCC tabbed and windows only monstrosity.
Electron and Webview2 are two modern frameworks that allow desktop applications to be easily created using HTML. CSS and JS. If GCC can program the P4 via TCP, I can't fathom why a Webiew or Electron app couldn't take its place for programming in a more robust UI than the device can host.
As you both know, I love my Porfilux -- but the software interface grows older and more bothersome every day.
TIMERS:
- Why are timers called "processes" they are timers not processes??
- Timers can be given a descriptive name:
But why can't that name be seen when referencing a timer in switches or logic?
PROGRAMMABLE LOGIC:- Why can't programmable logic be given a descriptive name?
- See images above, drop downs for selecting control or triggers are all numbered lists - there should be descriptions there.
@Matthias @Gaël -- I understand that the interface hosted on the device may be limited by resources, but the lack of friendly names throughout the interface is extremely problematic in systems with numerous timers, logic, switches, pumps, etc. One should not have to have a manual reference chart of names to ordinals for switches, logic, pumps. timers, etc. It is cumbersome and invites errors.
GCC is long in the tooth, and Windows Only -- You have stated that you have zero plans to port it to MacOS.
However, other than firmware, GCC can run via TCP/IP -- so why not build a modern cross platform application using any of the modern stacks? That way the interface can be a but more polished for LOCAL TCP/IP programming, replacing the clunky GCC tabbed and windows only monstrosity.
Electron and Webview2 are two modern frameworks that allow desktop applications to be easily created using HTML. CSS and JS. If GCC can program the P4 via TCP, I can't fathom why a Webiew or Electron app couldn't take its place for programming in a more robust UI than the device can host.
As you both know, I love my Porfilux -- but the software interface grows older and more bothersome every day.
Last edited:


