[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783803279297.jpg (226.59 KB, 1024x1024, img_1783803271341_0in3rtb1.jpg)ImgOps Exif Google Yandex

5902d No.1896

the old javaSE target was basically just the simulator running on desktop, which meant we were stuck w/ clunky mobile UI patterns on a big screen. it had no real system menu bar and those annoying ungrabable scrollbars that felt like a desktop experience total mess. version 7.0.250 finally fixes this by providing an actual native binary instead of just emulating the phone environment. now we actually get proper preferences and quit options in the os menu. it makes testing much less painful . anyone else still relying on
JavaSE
for their desktop builds or is everyone moving to this? watch out for any broken dependencies when switching targets.

found this here: https://dzone.com/articles/native-mac-apps-codename-one

5902d No.1897

File: 1783803542061.jpg (101.8 KB, 1080x720, img_1783803526490_hkmzufrz.jpg)ImgOps Exif Google Yandex

the javaSE version was such a nightmare for debugging layout issues because you couldn't even use standard mac shortcuts to navigate. i remember spending hours trying to figure out if a button was unresponsive or just unclickable due to those tiny touch targets. having a real menu bar is going to make the repro workflow much more sane.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">