6 ms·
We use Delphi at work. We've gotten a lot of pressure from customers to move to the web. However the lack of ways to design non-trivial UIs quickly does not ma
by magicalhippo 4y ago
We use Delphi at work. We've gotten a lot of pressure from customers to move to the web.
However the lack of ways to design non-trivial UIs quickly does not make it seen feasible at the moment.
Then there's the fact that Win32 is like bedrock in terms of stability. We've got forms that's been designed and coded over 15 years ago which still works just as fine as they did back then.
We've got input-heavy UIs, the one I'm working on right now is a single window with >150 input fields including multiple child tables up to levels 3 deep with their own grids. Getting the UI layout done and components connected to the DB will take me a day tops, it'll look great and based on history should work for the next 10+ years. The web seems like such a step back whenever I try it.
- yrgulation 4y ago“ >150 input fields including multiple child tables up to levels 3 deep with their own grids” Yeah i’ve built single page apps with more input fields than this and grid tables all in a single view. Are you sure this cant be easily done? Coincidentally that was first 15 years ago with extjs, second time with react 3 years ago - the latter being a slower process but still pretty much doable.
- liveoneggs 4y agoDoes #1 still work?
- yrgulation 4y agoIt did until roughly 5 years ago. From what i found by googling the product was acquired by a larger competitor and then decommissioned in favour of an existing product. The benefit in web based uis is that they work on any platform a supporting browser can be installed. And if you understand js it can work for a very very long time.
- magicalhippo 4y ago> Are you sure this cant be easily done? No, I'm no web expert. We've not found a way so far, and I've not seen something like this on the web, but I'd be happy to be proven wrong. edit: to clarify, I don't doubt one can get 150 fields in a view on the web. But can one dev do it in one day and have it look great?
- auggierose 4y agoIf you pay me £30000 and give me 3 months, and work with me to determine how your current designs look like, and what your current workflow is, I can make a react based environment for you to do your designs in just as quickly. If you pay me £60000, I do it in 2 months.
- jaywalk 4y agoI know nothing about Delphi, but I guarantee that I could take any UI you designed in a day in Delphi and get something equivalent on the web in the same amount of time. Sticking a bunch of inputs on a page (even with some nesting) isn't complex at all. I think you are doing your customers a great disservice by not learning about web development.
- mikewarot 4y agoCan you guarantee it'll run on the same machine, with the same browser, in 5 years, with no changes? Win32 is bedrock, the web is quicksand. Look at "HTTPS everywhere" and "you don't need FTP any more", which did little in terms of actual security, but broke almost everything in some small way. The web doesn't value legacy. It's a petulant 22 year old, that thinks it knows everything, and does stuff deliberately against the advice of those with more experience.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- dimgl 4y ago> However the lack of ways to design non-trivial UIs quickly does not make it seen feasible at the moment. I'm... not sure this is true. There are plenty of ways of designing non-trivial UIs on the web.
- dimitrios1 4y agoThere are indeed plenty of ways of designing non-trivial UIs on the web, but I am not sure any of them are that great, especially when you involve state. And there has been a mountain of pre-work done to make web UIs appear uniform across devices and browsers, and even with that pre-work done you still have issues on various mobile and tablet devices. I'm kind of curious now. Delphi claims you can "Build Native Apps 5x Faster With One Codebase For Windows, Android, iOS, macOS, and Linux" the biggest corollary I can think of there is Election, and we all know how we feel about Electron apps here.
- Joeri 4y agoWe've got input-heavy UIs, the one I'm working on right now is a single window with >150 input fields including multiple child tables up to levels 3 deep with their own grids. I went through this transition in the late 2000’s, moving grid and form heavy delphi windows screens to webpages, using ExtJS, the only framework at the time which kind of sort of could do this. The process made me realise two things: 1. if you try to map information-dense UI’s like that to the web, it will cost more to develop and the UX will be worse. (we saw double the dev cost and a slower and more cumbersome ui) 2. in most cases information-dense UI like that is bad design and should be avoided. I couldn’t see it back then how things could be done differently to make screens less dense, but looking back there were plenty of ways.
- magicalhippo 4y ago> in most cases information-dense UI like that is bad design and should be avoided. We do auto-expand a lot of groups, ie for company name and address fields we might just show name and org. number until you enter the company name field, at which point we show with the full name and address set. Once you leave the group it collapses again. Still, the information-dense UI is what our users like, as far as I can determine. They want to take one look at an order or invoice and get the info they need, not having to flip through several tabs or pages. Part of this is also driven by gov't requirements. That is, users are officially responsible for the data they submit, so they must be able to see all the data they submit.
- shrubble 4y agoWhat no one in the responses is talking about ...is speed of using the UI during day to day operations. Web interfaces are extremely clunky to use when trying to do things via only-keyboard (which is the only way to have muscle-memory help you zip through forms) methods. They are slow to update and in some cases, the Web browser's UI is fighting with you, such as offering to replace your input with the previous data you put in a form field of the same name, etc. In certain cases the tab method of navigation between fields gets broken or something else that interrupts the person's flow happens. Having worked in a case where the ticketing system and related interfaces were half-Web and half-Java-application-on-Windows - even the Java application was better to use via the keyboard. If you are paying people on a regular basis, whether hourly or per-shift, and the UI slows people down by 5% , what is the cost over the (perhaps) 3 years of that application's life? Even 4 users at $50k/year each in the USA (with healthcare and other business expenses etc. that means a $20/hour full time job) means $10K/year (5% * 200K salaries) in extra expense.
- chinabot 4y agoOn my new ThinkPad and the latest Delphi it compiles/links at 50-60K lines/second that performance has been consistent throughout the 25 years using Delphi. What it means in practice is you change a line of code, press F9 and the program is executing with no discernable delay.
- rightbyte 4y ago5% is way to low number. You surely have noticed how employees speed hack away on the keyboard with those old terminal style TUI apps. Modern UX is almost all about looking sleek to the procurer, not usable for the end luser.
- Desti314 4y agoNo clue how much experience you have with normal webuis but they do not match mine at all. You can use tab and hotkeys, add hints for auto fill (or just straight disabling them for a page). Normal UIs are fast enough. I'm not necessarily advocating for only web but I don't think your arguments holding up with reality
- rossmohax 4y agoDid you need to do anything to support HiDPI displays in those 10+ years old forms?
- magicalhippo 4y agoIt's mostly taken care of by the framework, though we have some breathing space due to our customers not jumping on HiDPI. It took some years for most of the kinks to be ironed out in the framework from what I gathered. We've yet to receive a HiDPI bug report, but we do get reports when we forget some customers still run 800x600 screens...