I'm not sure what platform you are on, but I can say that some of these issues aren't universal.
On Windows, I have the following differences in experience. 1. Copy/Paste OS integration works fine. 2. Padre remembers the location of the Padre window, and which tools were open. I agree with you, however, that it doesn't currently remember the precise AUI layout, or "perspective" in AUI terms, but remembering and restoring perspectives turns out to be relatively hard and so I delayed that problem for another time. 3. All Perl installations on Windows have threads. With Task 2.0 it is certainly theoretically possible to write an alternative worker backend that does not use threads. However right now threads work, and are fast, so any replacement is left as an exercise for whoever wants the alternative backend. While it IS possible to turn off threads, all background tasks will run in the foreground and block. So the Padre experience is rather degraded and I recommend against it. 4. Projects are different to sessions. We actually support both concepts, and there is a preference option to load the files you had open when you closed Padre. On that note, the layout of Preferences does still need work. I also agree that things like Syntax checking and the function list are pointless when you don't have a document type open that supports them. I've been meaning for a while to make tools opportunistically close when they aren't applicable, but haven't gotten to it yet. Source control integration is currently primitive and done in plugins. For Padre 1.0 I doubt the situation will improve, and I think that kind of thing is probably more of a target for a Padre 2.0. 5. Plugin support for hooking into the new menu is on my list of things to do. This would allow, for example, a "Modern Perl" plugin to give you those kinds of new moose class options. I remain adamant, for the record, that we shouldn't add a dependency on Moose for the core Padre installation. I also agree that Beginner Mode is currently a bit dodgy. Once we finish refactoring Problems (so we can kill off the separate syntax check window) then maybe we can make this integration better. Some of these things are feasible to fix before Padre 1.0, but some won't be. But I think the idea of a 1.0 is important, because it tells the world that the core of the editor is "done" and the APIs are relatively stable, so people can start to ramp up plugin development without having to be scared everything will break on them. It also marks the point at which we should look at throttling back the level of breakyness that we are willing to allow on a day to day basis, so people can trust Padre to work properly a bit more. A change in project management from breakneck speed to something less crazy. Adam K On 16 August 2011 22:29, Kaare Rasmussen <ka...@jasonic.dk> wrote: > Hi > > I see that people start talking about 1.00. This pushed me to writing > this post, which is long overdue. > > I've been using Padre since the beginning, sometimes with frustration, > but it keeps getting better. But there are a lot of things that still > bite me. > > I've put off writing about it, because, well, I thought I'd find time to > fix them all. But as I realize that it doesn't happen, at least I'll > tell about it. > > Some, or all, of my items may have been taken care of, and I'm just too > stupid to know. But then at least I hope that people will tell me where > the features are. > > Installation > - Padre needs threads. Most standard installed Perls are non-threaded. I > know about perlbrew, but average Joe Perlguy doesn't. > > UI > - The worst is by far the missing c/p integration between Padre and my > OS. I can't just doubleclick on a text in another program and paste it > into Padre by singleclicking, or the opposite way around. > - Padre doesn't remember my ui settings. I have to readjust the windows > every time I start Padre. > - Context sensitivity. If I have a text, sql, or html document, why is > my precious screen estate occupied by outline, syntax check and whatever > I've turned on for Padre to assist me writing good Perl code? > > Features > - Project. It seems there's a concept of project. But it seems that it's > just a way of remembering a bunch of files. If you use your time to save > and reload. It's just cumbersome. At least give a "load last session" > command line option. > Perhaps I just can't find the documentation for projects in Padre. > - Source code control integration. > - Full Screen Debugger > > Documentation > - Some examples: > - Debugging. I put it here, but I realy suspect it should be in "missing > features". How do I debug a program? A plack based server? > - Configuration > What does Perl Beginner Mode mean? > I can see that if I turn on the autocomplete options, Padre lists a > number of suggestions. But what do they mean? How does Padre find them? > > Modern Perl > - I can make a file->new->Perl 5 Module. That starts with 'use 5.006;' > Well, why is there no template for a Moose Role or a Moose Class? > How about some help for making Plack, an app.psgi, > > The list is probably not exhaustive. I started a while ago, and lost it. > So this is a memory refetch. > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
