Re: Design questions...
Glen, Just to add to whats already been said... Your app can run at full screen mode or in a window. Your app can resize and reposition the controls as the window is resized. (using very simple commands inside a resizestack handler), so instead of worrying about monitor size, you can make it responsive. Its a bit of extra work, but not that much, and worth doing. Making scrollbars appear if needed is trivial. The key is to plan your interface into groups, and think about what you will need ahead of time. Use "shared" groups that appear on each card. eg a group called "navigation" with all navigation buttons in it. You can create a beautiful, responsive, clean interfaces using livecode. That I know for sure. Easily. All the best on your project. feel free to pm me if u need help. On Thu, Jun 6, 2019 at 2:47 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > I ran into this too concerning the "effective" keyword. The dictionary > says, > > "Adding the effective adjective to either form returns the area of the > screen the application has to itself. In particular, if the keyboard is > activated, it take into account if the keyboard is taking up space on the > screen. (Android and iOS only)" > > I'm not sure if that means that the keyword can only be used with Android > or iOS, or if it means that statement about the keyboard taking up the > screen only applies to Android or iOS (as opposed to say a Windows tablet). > > Looking up the "effective" keyword seems to indicate that it returns the > inherited property of an object. It does not list screenRect(s) as valid. > But it seems (and I'm not complaining, just observing) that getting the > effective screenRect of say a stack or a card would never occur to me. > > > On Jun 6, 2019, at 10:39 , Richmond via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Here's a silly thought that may help a bit . . . > > > > http://forums.livecode.com/viewtopic.php?f=7&t=32683 > > > > Richmond. > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
I ran into this too concerning the "effective" keyword. The dictionary says, "Adding the effective adjective to either form returns the area of the screen the application has to itself. In particular, if the keyboard is activated, it take into account if the keyboard is taking up space on the screen. (Android and iOS only)" I'm not sure if that means that the keyword can only be used with Android or iOS, or if it means that statement about the keyboard taking up the screen only applies to Android or iOS (as opposed to say a Windows tablet). Looking up the "effective" keyword seems to indicate that it returns the inherited property of an object. It does not list screenRect(s) as valid. But it seems (and I'm not complaining, just observing) that getting the effective screenRect of say a stack or a card would never occur to me. > On Jun 6, 2019, at 10:39 , Richmond via use-livecode > wrote: > > Here's a silly thought that may help a bit . . . > > http://forums.livecode.com/viewtopic.php?f=7&t=32683 > > Richmond. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
All good feedback! Fortunately I plan to limit the scope of things to the desktop as previously mentioned. I can't fathom the tablet / phone market given the number of devices and their different specs. Thanks to everyone for their input. Glen On Thu, Jun 6, 2019 at 2:12 PM Phil Davis via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Glen, > > There are some screen resolution stats on the web that may be useful, at > least for 'general public' app window sizes: > > https://en.wikipedia.org/wiki/Display_resolution > > Phil Davis > > > > On 6/6/19 6:47 AM, Glen Bojsza via use-livecode wrote: > > Hello, > > > > I was looking for input on the following design questions...I haven't > done > > anything for years so I am looking for other developers' experiences. > > > > 1. what would be considered the smallest stack size for a desktop app? > > > > 2. Does the above fill most of the screens in use today ...ie what is the > > noraml or considered the standard screen resolution for a desktop laptop? > > > > 3. Are apps considered acceptable if the user needs to scroll down to see > > the full app. > > > > 4. Are menu bars (ie File Open) still necessary or are users familiar > > enough with section buttons? > > > > 5. If the stack is too large for a user (say they use a lower resoultion > > screen notebook then is there a way to detect this and have scroll bars > > appear? > > > > I appreciate any insights the list may have. > > > > regards, > > > > Glen > > ___ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > > > > -- > Phil Davis > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
Hi Glen, There are some screen resolution stats on the web that may be useful, at least for 'general public' app window sizes: https://en.wikipedia.org/wiki/Display_resolution Phil Davis On 6/6/19 6:47 AM, Glen Bojsza via use-livecode wrote: Hello, I was looking for input on the following design questions...I haven't done anything for years so I am looking for other developers' experiences. 1. what would be considered the smallest stack size for a desktop app? 2. Does the above fill most of the screens in use today ...ie what is the noraml or considered the standard screen resolution for a desktop laptop? 3. Are apps considered acceptable if the user needs to scroll down to see the full app. 4. Are menu bars (ie File Open) still necessary or are users familiar enough with section buttons? 5. If the stack is too large for a user (say they use a lower resoultion screen notebook then is there a way to detect this and have scroll bars appear? I appreciate any insights the list may have. regards, Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Phil Davis ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
1. that really depends on the app type and of course on the customers displays. 2. most customers i know have got 17" or higher displays with a ratio of 16:9 or 16:10. The minimum resolution is 1280x1024 or 1280x768. 3. When working with ERP tools or other business software for accounting, shipment or whatever the customers don´t want to scroll. They want to see the complete form. 4. For one of my last projects, a shipping software, i´ve asked the customer what they would prefer. They told me that they do not want to have a menubar or this ugly ribbon bar. They wanted it clear with bigger buttons and the possibility to use the function keys for some tasks. The old shipping software made use of it and they wanted to use the same function keys for the same tasks in the new software. Instead of menus i added big coloured buttons. I´ve also added a scale function, so the user can set the scalefactor of the app to 0.75, 1 and 1.5. Here´s an screenshot of the entry mask for trans-o-flex labels https://dl.qck.nu/samples/screenshot-shipping.png <https://dl.qck.nu/samples/screenshot-shipping.png> Okay it will not win a design contest, but it meets the demand of the customer. ;) Matthias > Am 06.06.2019 um 15:47 schrieb Glen Bojsza via use-livecode > mailto:use-livecode@lists.runrev.com>>: > > Hello, > > I was looking for input on the following design questions...I haven't done > anything for years so I am looking for other developers' experiences. > > 1. what would be considered the smallest stack size for a desktop app? > > 2. Does the above fill most of the screens in use today ...ie what is the > noraml or considered the standard screen resolution for a desktop laptop? > > 3. Are apps considered acceptable if the user needs to scroll down to see > the full app. > > 4. Are menu bars (ie File Open) still necessary or are users familiar > enough with section buttons? > > 5. If the stack is too large for a user (say they use a lower resoultion > screen notebook then is there a way to detect this and have scroll bars > appear? > > I appreciate any insights the list may have. > > regards, > > Glen > ___ > use-livecode mailing list > use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com> > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode Matthias Rebbe free tools for Livecoders: https://instamaker.dermattes.de <https://instamaker.dermattes.de/> https://winsignhelper.dermattes.de <https://winsignhelper.dermattes.de/> ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
I deploy (fancy word saying I have a load of ancient Pentiums . . .) some machines in my school hooked up to flat-screens with a Max Res of 1024 by 780. I mean, at $10 a pop those monitors were impossible to resist! I make my EFL (English as a Fried Language) standalones to a "standard" of 1024 x 720 because of the XFCE panels top-and-bottom on my standard Xubuntu setup . . . Smaller monitors: dunno: even my iMac G3 turquoise manages 1024 x 780. I really wonder if anyone is going to be so cash-strapped they cannot at least manage a monitor that does that. Richmond. On 6.06.19 20:13, Peter Bogdanoff via use-livecode wrote: We use a height of 728—that’s in compensation for a variety of issues—some laptops have very small screens: LC window title bar (can be hidden by LC if necessary) Windows Task bar (can be hidden by LC if necessary) You can get the height of the screen: (item 4 of the working screenRect) - (item 2 of the working screenRect) You can also easily resize the window by using scaleFactor. We do some auto resizing when opening the program to scale it down for very small screens, and have a preference setting for the user to scale it up to maximum available height. Peter Bogdanoff ArtsInteractive On Jun 6, 2019, at 11:09 AM, Glen Bojsza via use-livecode wrote: Bob, thanks for the info...I will start with 1024x768 as a minimal screen resolution for now and see what happens. As for the combo of menus and buttons I will try to find if there is a benefit of both and also usability space within the app. My target platforms are Windows 10 and OS X 10.X Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
Here's a silly thought that may help a bit . . . http://forums.livecode.com/viewtopic.php?f=7&t=32683 Richmond. On 6.06.19 16:47, Glen Bojsza via use-livecode wrote: Hello, I was looking for input on the following design questions...I haven't done anything for years so I am looking for other developers' experiences. 1. what would be considered the smallest stack size for a desktop app? 2. Does the above fill most of the screens in use today ...ie what is the noraml or considered the standard screen resolution for a desktop laptop? 3. Are apps considered acceptable if the user needs to scroll down to see the full app. 4. Are menu bars (ie File Open) still necessary or are users familiar enough with section buttons? 5. If the stack is too large for a user (say they use a lower resoultion screen notebook then is there a way to detect this and have scroll bars appear? I appreciate any insights the list may have. regards, Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
We use a height of 728—that’s in compensation for a variety of issues—some laptops have very small screens: LC window title bar (can be hidden by LC if necessary) Windows Task bar (can be hidden by LC if necessary) You can get the height of the screen: (item 4 of the working screenRect) - (item 2 of the working screenRect) You can also easily resize the window by using scaleFactor. We do some auto resizing when opening the program to scale it down for very small screens, and have a preference setting for the user to scale it up to maximum available height. Peter Bogdanoff ArtsInteractive > On Jun 6, 2019, at 11:09 AM, Glen Bojsza via use-livecode > wrote: > > Bob, thanks for the info...I will start with 1024x768 as a minimal screen > resolution for now and see what happens. As for the combo of menus and > buttons I will try to find if there is a benefit of both and also usability > space within the app. > > My target platforms are Windows 10 and OS X 10.X > > Glen > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
NP. BTW what I do for functionality that exists in both buttons and menus is, barring the handlers being in a library or behavior, I simply send mouseUp from the menu script to the button with the pertinent handlers. It's easier to edit the script of a button than it is to pull up the Menu Builder and get the script of the menu buttons from there. (I develop on OS X so my menus are always hidden.) Bob S > On Jun 6, 2019, at 08:09 , Glen Bojsza via use-livecode > wrote: > > Bob, thanks for the info...I will start with 1024x768 as a minimal screen > resolution for now and see what happens. As for the combo of menus and > buttons I will try to find if there is a benefit of both and also usability > space within the app. > > My target platforms are Windows 10 and OS X 10.X > > Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
Bob, thanks for the info...I will start with 1024x768 as a minimal screen resolution for now and see what happens. As for the combo of menus and buttons I will try to find if there is a benefit of both and also usability space within the app. My target platforms are Windows 10 and OS X 10.X Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Design questions...
The smallerst monitor I know of is 640x480. That is tiny. Many developers require a minimal size monitor to function correctly. Our ERP system specifies a minimum of 1024x768. As far as scrolling, I suppose it depends on the app. Take Facebook for example. It depends on scrolling. You couldn't have that app without it. But an accounting app with preset forms, nada. Some web apps revert to a different form if the screen size becomes too small. Some detect the client is a mobile device and redirect to a different page. If by section buttons you mean Microsoft style ribbons, their review was mixed. I still don't like em. In my apps that have menus, I also like controls on the card which essentially do the same thing. No one will complain about giving them multiple ways to do the same thing. Well... samoe may, but those people are going to complain anyway. Bob S > On Jun 6, 2019, at 06:47 , Glen Bojsza via use-livecode > wrote: > > 1. what would be considered the smallest stack size for a desktop app? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Design questions...
Hello, I was looking for input on the following design questions...I haven't done anything for years so I am looking for other developers' experiences. 1. what would be considered the smallest stack size for a desktop app? 2. Does the above fill most of the screens in use today ...ie what is the noraml or considered the standard screen resolution for a desktop laptop? 3. Are apps considered acceptable if the user needs to scroll down to see the full app. 4. Are menu bars (ie File Open) still necessary or are users familiar enough with section buttons? 5. If the stack is too large for a user (say they use a lower resoultion screen notebook then is there a way to detect this and have scroll bars appear? I appreciate any insights the list may have. regards, Glen ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
