Re: Death of the Application Browser

Have you tried Navigator? It is a very simple list view, fairly quick, can be made small and collapses down even smaller, and allows for multiple instances so you can see/work with many separate stacks at the same time. I only kinda sorta support it though, so your mileage may vary. The version in

Re: Pi fans, now we have ZERO to look forward to

> On 27 Nov 2015, at 12:07 pm, Mark Rauterkus wrote: > > I love our Thanksgiving Pie but this is different. > > https://www.raspberrypi.org/blog/raspberry-pi-zero/ > > > Okay, what does this mean for LiveCode? > > Will LiveCode run on

Re: Death of the Application Browser

> On 27 Nov 2015, at 11:58 am, Peter W A Wood wrote: > > Given Mark’s earlier explanation, it is difficult to see how the IDE can be > MIT licensed. I posted the link to the license file in the repo. I don’t think I can do much more than that to prove it ;-) > After all, it is just a stack a

Re: Death of the Application Browser

> On 27 Nov 2015, at 11:11 am, [-hh] wrote: > > I would like to have that project browser does at least the same functional > (working) things as the application browser. While it may seem like there are a lot of people saying this stuff there’s actually only a handful. The project browser app

Pi fans, now we have ZERO to look forward to

Hi All, I love our Thanksgiving Pie but this is different. https://www.raspberrypi.org/blog/raspberry-pi-zero/ Okay, what does this mean for LiveCode? Will LiveCode run on the new Pi Zero one day? Man, a $5 computer. Taste good and less filling! Would love to have some of the experts soun

Re: Death of the Application Browser

Monte > On 27 Nov 2015, at 06:29, Monte Goulding wrote: > > >> On 27 Nov 2015, at 9:24 am, Peter W A Wood wrote: >> >> Given Mark Waddingham’s recent view of LiveCode stacks and GPL, if the >> Application Browser is hived off to the community anybody using it would >> only be able to sell

Re: Death of the Application Browser

On 11/26/2015 02:19 PM, Fraser Gordon wrote: I'd be delighted if someone makes an Application Browser++ Awesome Edition plugin. lcStackBrowser Now if it were only dual-licensed... -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: Death of the Application Browser

@Monte: > If all they are hearing is a handful of people saying they don’t like it > and want to use the application browser instead then can you blame them > for coming up with a solution of putting the application browser in > plugins for those users? People in this list are saying repeatedly si

Re: Death of the Application Browser

> On 27 Nov 2015, at 9:24 am, Peter W A Wood wrote: > > Given Mark Waddingham’s recent view of LiveCode stacks and GPL, if the > Application Browser is hived off to the community anybody using it would only > be able to sell it under the GPL. :-) Actually that would appear to only be the case

Re: Death of the Application Browser

> On 27 Nov 2015, at 04:26, Richmond wrote: > For exactly the same reason why the Application Browser is being hived off to > the "community", > because, while Lip-service is being paid to listening to the community . . . Given Mark Waddingham’s recent view of LiveCode stacks and GPL, if the

Re: Death of the Application Browser

On 26/11/15 20:24, Richmond wrote: Aah, so the team isn't going to bother to listen to the Community because it wants to do other things; so it is chucking the Application Browser out to grass. I'm not sure I follow. The application browser isn't going anywhere. If it works for you already, wh

Re: Death of the Application Browser

> On 27 Nov 2015, at 7:07 am, Scott Rossi wrote: > > I doubt anybody is arguing with you. I think most agree that the Project > Browser is a great step toward a modern editor. But the capabilities lacking > in the Project Browser have been pointed out numerous times -- see the mail > archiv

Re: Death of the Application Browser

On 26/11/15 22:07, Scott Rossi wrote: I doubt anybody is arguing with you. I think most agree that the Project Browser is a great step toward a modern editor. But the capabilities lacking in the Project Browser have been pointed out numerous times -- see the mail archives. Perhaps a better

Re: Death of the Application Browser

On 26/11/15 22:02, Mark Wieder wrote: On 11/26/2015 10:36 AM, Richmond wrote: Although I would still like to know why it has been downgraded to a Plug-in. Actually, I don't see that as a downgrade at all. Making it a plugin allows it to be more malleable, fixable, replaceable. Taking it out

Re: Death of the Application Browser

> J. LG wrote: > Something like that would work for me ... If such wonderful things could be realized (will be a feature-exchange), what should then the significantly confused crowd of newcomers do? Use the Application browser plugin? ___ use-livecode m

Re: Death of the Application Browser

I doubt anybody is arguing with you. I think most agree that the Project Browser is a great step toward a modern editor. But the capabilities lacking in the Project Browser have been pointed out numerous times -- see the mail archives. Perhaps a better question to ask is why these have been p

Re: Death of the Application Browser

> On 27 Nov 2015, at 7:02 am, Mark Wieder wrote: > > Actually, I don't see that as a downgrade at all. > Making it a plugin allows it to be more malleable, fixable, replaceable. > Taking it out of the IDE hierarchy should give us more options to work on the > Application Browser. Since the tea

Re: Death of the Application Browser

On 11/26/2015 10:36 AM, Richmond wrote: Althought I would still like to know why it has been downgraded to a Plug-in. Actually, I don't see that as a downgrade at all. Making it a plugin allows it to be more malleable, fixable, replaceable. Taking it out of the IDE hierarchy should give us mo

Re: Death of the Application Browser

AND, defensive as you like . . . The "one" about that the Application Browser had been moved into the Plug-ins was nothing but a . . . I wasn't there! Try harder next time . . . Richmond. ___ use-livecode mailing list use-livecode@lists.runrev.com

Re: Death of the Application Browser

On 26/11/15 21:36, J. Landman Gay wrote: (Finally, I hope I didn't show any claws, though I admit that removing the App Browser would force me to remain in LC 7 indefinitely and I had a moment of despair.) We know that you are really a "pussy cat"; rather like my cats; who are soft and sw

Re: Death of the Application Browser

On 11/26/2015 1:04 PM, Monte Goulding wrote: What I don't really understand is why people aren't offering suggestions on how to improve the project browser so it will work for them. To my mind the simple solution would be to have multiple layout modes (tree, list, column) and the ability to detac

Re: Death of the Application Browser

It's clearly a waste of resources to maintain two things that are intended to provide the same service. Do you do that in your apps? What I don't really understand is why people aren't offering suggestions on how to improve the project browser so it will work for them. To my mind the simple sol

Re: Death of the Application Browser

On 26/11/15 20:31, Mark Waddingham wrote: On 2015-11-26 19:23, Richmond wrote: Application Browser, and that they back-tracked when they realised that people that HAVE to listen to (Ms. Gay) had unsheathed their claws. There was absolutely no back-tracking at all. The PR to move the Applicati

Re: Death of the Application Browser

On 2015-11-26 19:23, Richmond wrote: Application Browser, and that they back-tracked when they realised that people that HAVE to listen to (Ms. Gay) had unsheathed their claws. There was absolutely no back-tracking at all. The PR to move the Application Browser to a plugin was done quite a wh

Re: Death of the Application Browser

On 26/11/15 19:32, Richard Gaskin wrote: Richmond wrote: I've got several buttons, and getting rid of the Application Browser just pushed one of them quite hard. Peter and Ali have already made multiple posts noting that the omission of the App Browser is a bug which will be fixed in the ne

Re: SQLite, keep connection open or close every time?

Thanks Mark, was beginning to doubt myself! Somewhere on the SQLite site they indicate SQLite works well as the data repository for websites with less than around 100k hits per day and has been successfully used on sites with up to 500k hits per day, but they don't indicate whether that's if it is

Re: SQLite, keep connection open or close every time?

On 2015-11-26 18:29, Peter Haworth wrote: I sometimes have multiple processes accessing the same SQLite database on my computer, typically, the application I'm working on and an SQLite admin program. I've also seen discussions on applications with multiple threads accessing the same SQlite da

Re: Death of the Application Browser

Richmond wrote: I've got several buttons, and getting rid of the Application Browser just pushed one of them quite hard. Peter and Ali have already made multiple posts noting that the omission of the App Browser is a bug which will be fixed in the next build. One of the benefits of counting

Re: SQLite, keep connection open or close every time?

I sometimes have multiple processes accessing the same SQLite database on my computer, typically, the application I'm working on and an SQLite admin program. I've also seen discussions on applications with multiple threads accessing the same SQlite database. There don't seem to be any adverse effe

Re: Death of the Application Browser

On 26/11/15 15:33, [-hh] wrote: Peter B. wrote: 1) In general, we have found that the Project Browser is easier to use by newcomers So, all we give a damn about are newcomers . . . to LiveCode, and easier to explain in training materials. Funny that; my group of 9 to 15 year old, non-na

Re: Setting the color of a field's border

On 2015-11-26 01:30, Peter Haworth wrote: I've been trying to set the border around a field to something other than its default by setting its topColor and bottomColor but didn't see the color show up. By chance, I set the borderWidth to 3 instead of the default 2 and the color showed up. Sett

Re: Setting the color of a field's border

Thanks Jacque. Sounds like time for a dictionary note. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Wed, Nov 25, 2015 at 7:08 PM, J. Landman Gay wrote: > It's always been

Re: Death of the Application Browser

On 11/26/2015 01:37 AM, Peter TB Brett wrote: Ali has investigated and has found that the Application Browser was missing from the latest *Development Preview* release of LiveCode 8 due to a bug, which is now fixed. Peter, Ali- thanks for that. I'm sure you'll be delighted to hear that the

Re: Death of the Application Browser

On 26/11/2015 13:33, [-hh] wrote: But do NOT diminish improvements and testing and do NOT cut, as now, one of the most valuable parts from the full version. As I explained, the absence of the Application Browser from the latest Developer Preview release was a bug which will be fixed in the ne

Re: One Rect For All specificaiton

Here are some real numbers: The complete card could be 1400x900. On a 16:9 device you would see all of the 1400 width, and 788 pixels of the height. On a 4:3 device you would see all of the 900 height, and 1200 of the width. So, you would have the important things within the central 1200 of th

Re: Death of the Application Browser

Peter B. wrote: > 1) In general, we have found that the Project Browser is easier to use > by newcomers to LiveCode, and easier to explain in training materials. There is nearly no difference if you have one button and one field. > 2) We also found that there was significant confusion caused by

ios Scroller not passing touches to list field on iPhone6?

I have a native iOS scroller on a list field that works fine on iphone 4 + 5, but it doesn't seem to work properly (at all) on iPhone 6 & 6+. It also doesn't seem to be passing touches (mouseDown or mouseUp) to the list field. I've even tried setting both "canCancelTouches" and "delayTouches" t

Re: Death of the Application Browser

On 26/11/15 04:10, Mark Wieder wrote: On 11/25/2015 01:38 PM, Richmond wrote: On 25/11/15 22:54, Ali Lloyd wrote: It was put into the plugins menu in DP 9. Apologies for the lack of release note to that effect. Then why does it not show up menu/development/plugins ??? Nor in /opt/livecode

Re: Death of the Application Browser

On 25/11/2015 23:13, Mark Schonewille wrote: Does this mean that [the Application Browser] is no longer supported? *Everything* shipped with LiveCode is supported. If we don't intend to support it, we don't ship it. Bearing that in mind: 1) In general, we have found that the Project Browse

Re: Death of the Application Browser

http://quality.livecode.com/show_bug.cgi?id=16497 On Thu, Nov 26, 2015 at 9:13 AM Peter TB Brett wrote: > On 26/11/2015 02:10, Mark Wieder wrote: > > On 11/25/2015 01:38 PM, Richmond wrote: > >> On 25/11/15 22:54, Ali Lloyd wrote: > >>> It was put into the plugins menu in DP 9. Apologies for the

Re: Death of the Application Browser

On 26/11/2015 02:10, Mark Wieder wrote: On 11/25/2015 01:38 PM, Richmond wrote: On 25/11/15 22:54, Ali Lloyd wrote: It was put into the plugins menu in DP 9. Apologies for the lack of release note to that effect. Then why does it not show up menu/development/plugins ??? Nor in /opt/liveco

Re: SQLite, keep connection open or close every time?

On 2015-11-25 22:19, Peter Haworth wrote: Maybe I'm missing something but I don't understand why the issue of concurrent users keeps coming up in threads about SQL dbs. There are perfectly good mechanisms built into every SQL implementation to preserve the integrity of the db, that's ACID is al

Re: Death of the Application Browser

>> J. LG wrote: >> It needs to come back. I can't work without it. Project browser is not an >> acceptable replacement for the kind of stacks I work with. > > I stopped to edit any stack in LC 8. > > The Project Browser is beautiful to look at, also the Property Inspector, > beautiful design, b