Re: Separate Widget palette

I think we should be looking at a Palette like Jot Forms: http://www.jotform.com/ They do a great job of organizing the UI elements. It would also be SUPER if there was a way to save grouped objects as templates and just import them and drop them on the card easily. But this could be a script of

Re: Separate Widget palette

The Revolution/LiveCode ‘Tools Palette’ has never been a purely tools palette. The Browse, Selection, Graphic & Paint tools are strictly tools. You select a tool and the pointer becomes that tool. Tools let you build or modify things. All the other things on the Tool Palette are actually objects

Re: Separate Widget palette

On 20.03.2016 18:54, Mark Wieder wrote: On 03/20/2016 05:15 AM, RM wrote: I should at this point out that LC 4.5 does not function on my Xubuntu box, but I use it extensively on my G5 Macintosh . . . That's a bit strange. LC 4.6.4 is my workhorse on Mint 17.2, which has a ubuntu core.

Re: Separate Widget palette

Thanks: I've just tried that. Richmond. On 20.03.2016 18:47, J. Landman Gay wrote: On March 20, 2016 7:17:17 AM RM wrote: I want a way to hide the Widgets in such a way that a kid opening LIveCode won't see them at any point during his/her programming class

Re: Separate Widget palette

On 03/20/2016 05:15 AM, RM wrote: I should at this point out that LC 4.5 does not function on my Xubuntu box, but I use it extensively on my G5 Macintosh . . . That's a bit strange. LC 4.6.4 is my workhorse on Mint 17.2, which has a ubuntu core. -- Mark Wieder ahsoftw...@gmail.com

Re: Separate Widget palette

On March 20, 2016 7:17:17 AM RM wrote: I want a way to hide the Widgets in such a way that a kid opening LIveCode won't see them at any point during his/her programming class with me. You can hide the widget panel using the settings/gear icon. -- Jacqueline

Re: Separate Widget palette

Folks, Some of the software I use has a "views" menu that shows a list of "columns" or items that appear on a specific palette or screen. I wonder if such a menu might be convenient in this case. The user could choose "basic", "extended", "All" or whatever. I can sympathize with Richmond's

Re: Separate Widget palette

Richmond wrote: On 20.03.2016 17:41, Richard Gaskin wrote: Has Adobe's patent on dockable tabbed palettes expired yet? http://www.cnet.com/news/adobe-wins-macromedia-patent-suit/ "a feature that allows users of design software to rearrange the work space on the PC screen." Ha, Ha, Ha: I

Re: Separate Widget palette

"a feature that allows users of design software to rearrange the work space on the PC screen." Ha, Ha, Ha: I really wonder how that can be patented. Every time I open Livecode on a small monitor I rearrange the work space by, for instance, moving revTools palette somewhere other than where it

Re: Separate Widget palette

If LC can’t afford the licence :) then do it like Apples’ interface for Numbers & Pages but in a separate window. All the best Terry > On 20 Mar 2016, at 15:41, Richard Gaskin wrote: > > Has Adobe's patent on dockable tabbed palettes expired yet?

Re: Separate Widget palette

Terence Heaford wrote: ... Then if required each group can be dragged to another part of the main palette or dragged off to create a palette of their own. Has Adobe's patent on dockable tabbed palettes expired yet? http://www.cnet.com/news/adobe-wins-macromedia-patent-suit/ -- - Richard

Re: Separate Widget palette

Why not have a palette where the user can relocate items to suit themselves? In a common palette where all items are grouped according to their function, Core objects, painting, drawing, widgets. Then if required each group can be dragged to another part of the main palette or dragged off to

Re: Separate Widget palette

How about making the sections of the Tools pallette dockable? Allow the users to stack them according to their workflow. I know the dev team wants the shiny new things at the top, but that doesn't compel me to put widgets into all of my projects. ~Roger

Re: Separate Widget palette

On 20.03.2016 16:43, Richard Gaskin wrote: Richmond wrote: Hence my recent suggestion that they could be moved to the bottom of the revTools palette rather than the top. The core team says Widgets should be at the top. You say they should be at the bottom. I wonder why the core team has

Re: Separate Widget palette

Richmond wrote: Hence my recent suggestion that they could be moved to the bottom of the revTools palette rather than the top. The core team says Widgets should be at the top. You say they should be at the bottom. I wonder: Why are controls grouped by implementation method? Why should

Re: Separate Widget palette

in my school: and a wildly different revTools stack may only serve to confuse them. Having an separate Widget palette would allow teachers and so forth, who didn't want the widgets showing up, to hide them away. I suppose were the widgets at the bottom of a unified revTools palette the

Re: Separate Widget palette

e they get home and hook their computers up to the LC download site are going to be offered the "latest thang" which may not be what I have shown them on the machines in my school: and a wildly different revTools stack may only serve to confuse them. Having an separate Widget palette w

Re: Separate Widget palette

On Sun, Mar 20, 2016 at 4:03 AM, RM wrote: > > Well, how about having the widget section at the bottom of the revTools > palette rather than above > the section that is most likely to be used the most often? > Richmond, You may find that you use widgets more than

Re: Separate Widget palette

Aha. Well, how about having the widget section at the bottom of the revTools palette rather than above the section that is most likely to be used the most often? Richmond. On 20.03.2016 01:43, Peter TB Brett wrote: On 2016-03-19 19:50, RM wrote:

Re: Separate Widget palette

On 3/19/2016 11:51 PM, dunb...@aol.com wrote: > Why not go the way of the new properties inspector? Make a widgets > pane and a 'normal" tool pane. Same real estate, same palette. It seems to me to be the logical way. There could be more than just one widget pane, more tabs, grouped by whatever

Re: Separate Widget palette

On 3/19/2016 11:51 PM, dunb...@aol.com wrote: Why not go the way of the new properties inspector? Make a widgets pane and a 'normal" tool pane. Same real estate, same palette. I like that idea. Keeps the clutter at bay. -- Jacqueline Landman Gay | jac...@hyperactivesw.com

Re: Separate Widget palette

Sent: Sat, Mar 19, 2016 9:39 pm Subject: Re: Separate Widget palette If I was voting, I would vote for a pop-out menu, perhaps - so you would have a widget button in the palette with a right-facing triangle which pops out the widgets. Alternatively, you could right-click on a widget button in

Re: Separate Widget palette

If I was voting, I would vote for a pop-out menu, perhaps - so you would have a widget button in the palette with a right-facing triangle which pops out the widgets. Alternatively, you could right-click on a widget button in the tools palette to show the widgets list On Sat, Mar 19, 2016 at 7:43

Re: Separate Widget palette

On 2016-03-19 19:50, RM wrote: http://forums.livecode.com/viewtopic.php?f=6=26785 Please have a look at this, think about it, and if you think it is a good idea say so: loudly, so the LiveCode people take it seriously. As I understand the current design concept for the LiveCode 8 IDE, the

Re: Separate Widget palette

...@gmail.com Subject: Separate Widget palette Date: Sat, 19 Mar 2016 20:50:32 +0200 http://forums.livecode.com/viewtopic.php?f=6=26785 Please have a look at this, think about it, and if you think it is a good idea say so: loudly, so the LiveCode people take it seriously. Richmond

RE: Separate Widget palette

Not a good idea... it means another palette floating about obscuring things.. > To: use-livecode@lists.runrev.com > From: richmondmathew...@gmail.com > Subject: Separate Widget palette > Date: Sat, 19 Mar 2016 20:50:32 +0200 > > http://forums.livecode.com/viewtopic.php?f=6

Separate Widget palette

http://forums.livecode.com/viewtopic.php?f=6=26785 Please have a look at this, think about it, and if you think it is a good idea say so: loudly, so the LiveCode people take it seriously. Richmond. ___ use-livecode mailing list