Hi Amit, hi rest of the list, thank you very much for taking the time and thinking about and actually creating those new images.
I agree with what Adam wrote before: Generally, the logos are good, but it would be better to keep the original icon. I am fine with the black+white versions, though (as variants, not generally). Regarding the icon, we should stick to it; the web 2.0 style with its logos will not be around forever. I hope that Padre will be around for some time. And if we are the only ones with a *real* picture as icon, why not? Makes us a bit more distinct from the rest ;-) Also, I have the feeling that the people using/developing Padre have become kind of used to it. Please do not take this as criticism of your work (which is great, btw.). Best regards, Zeno On Mon, Feb 14, 2011 at 3:38 PM, amit mojumder <mit....@gmail.com> wrote: > Hello Adam > Thanks for the feedback. I completely understand what you mean. But the fact > is, real image doesnt represent a brand or community. u see all the web 2.0 > logo or social media or any other application's icon over the internet, all > have ICON or Shape/text based logo. Padre is now using an image. i mean that > is solid butterfly image. But i will keep this untouched if u ppl want it in > that way. my intention is to deliver something simple yet elegant and > awesome so ppl understand the gravity of the platform at a first glance. > Still waiting for the other's opinion. > Best Regards > Amit Mojumder > Creative Designer > Portfolio : www.sparklewebbd.com > www.twitter.com/amitmojumder > www.sparklewebbd.com/branding > 0088 01717081623 > NB: This email may contain confidential materials regarding business. > Illegal use of the contents of this mail may occur legal action. > > > On Mon, Feb 14, 2011 at 7:38 PM, <padre-dev-requ...@perlide.org> wrote: >> >> Send Padre-dev mailing list submissions to >> padre-dev@perlide.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mail.perlide.org/mailman/listinfo/padre-dev >> or, via email, send a message with subject or body 'help' to >> padre-dev-requ...@perlide.org >> >> You can reach the person managing the list at >> padre-dev-ow...@perlide.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Padre-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: Padre Logo/Icon/Brand mark (Adam Kennedy) >> 2. Re: [Padre-commit] rev 13689 - change in project support >> (Gabor Szabo) >> 3. Re: Manual test scripts needed for Padre (Gabor Szabo) >> 4. Re: [Padre-commit] rev 13689 - change in project support >> (Adam Kennedy) >> 5. Re: proposal for adding new features (Sebastian Willing) >> 6. Re: proposal for adding new features (Adam Kennedy) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 14 Feb 2011 10:46:51 +1100 >> From: Adam Kennedy <adamkennedybac...@gmail.com> >> Subject: Re: [Padre-dev] Padre Logo/Icon/Brand mark >> To: Padre development discussion list <padre-dev@perlide.org> >> Message-ID: >> <aanlktincd+jgmuqz9tn4gbfcpwdxzgjsms_ce4osc...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> While I'm fine with the cut put variants, I think the butterfly part >> of the logo art shown does not represent an improvement over the >> current usage of the literal photo (although admittedly we have >> squelched it a bit). >> >> I've always liked the photo because it communicates beauty, freedom >> and authenticity. >> >> While the new logo retains the shape, it loses the beauty of the >> original butterfly in my opinion. >> >> Adam K >> >> On 13 February 2011 01:29, amit mojumder <mit....@gmail.com> wrote: >> > Hello All >> > here is the attached first approach for the logo and icon for the Padre >> > User?Interface?which could be used at web, desktop icon, brand mark and >> > fevicon. I designing it in vector format and gave it a glossy look >> > to?visualize?as web 2.0 standard. You can give opinion and use any >> > version >> > included here. If you prefer to use very simple icon then?black?and >> > white >> > version would be idol i think. >> > Hope you all will like it. i will be waiting for your kind feedbacks and >> > opinions. soon i am going to show the home page sample after the logo >> > approval. >> > Regards >> > Amit Mojumder >> > Creative Designer >> > Portfolio?:?www.sparklewebbd.com >> > www.twitter.com/amitmojumder >> > www.sparklewebbd.com/branding >> > 0088 01717081623 >> > NB: This email may contain confidential materials regarding business. >> > Illegal use of the contents of this mail may occur legal action. >> > >> > >> > On Sat, Feb 12, 2011 at 2:00 AM, <padre-dev-requ...@perlide.org> wrote: >> >> >> >> Send Padre-dev mailing list submissions to >> >> ? ? ? ?padre-dev@perlide.org >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> ? ? ? ?http://mail.perlide.org/mailman/listinfo/padre-dev >> >> or, via email, send a message with subject or body 'help' to >> >> ? ? ? ?padre-dev-requ...@perlide.org >> >> >> >> You can reach the person managing the list at >> >> ? ? ? ?padre-dev-ow...@perlide.org >> >> >> >> When replying, please edit your Subject line so it is more specific >> >> than "Re: Contents of Padre-dev digest..." >> >> >> >> >> >> Today's Topics: >> >> >> >> ? 1. Re: Ensuring more eyes on the development process >> >> ? ? ?(Sebastian Willing) >> >> ? 2. Re: proposal for adding new features (Zeno Gantner) >> >> ? 3. Re: proposal for adding new features (Zeno Gantner) >> >> ? 4. Re: Padre UI and Brand design (Zeno Gantner) >> >> >> >> >> >> ---------------------------------------------------------------------- >> >> >> >> Message: 1 >> >> Date: Fri, 11 Feb 2011 14:57:14 +0100 >> >> From: Sebastian Willing <sebastian.will...@web.de> >> >> Subject: Re: [Padre-dev] Ensuring more eyes on the development process >> >> To: Padre development discussion list <padre-dev@perlide.org> >> >> Message-ID: <4d55403a.4090...@web.de> >> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> >> >> Hi, >> >> >> >> this is way too complicated, sorry. :-) >> >> >> >> We really need some trunk/tool/ scripts for creating and merging a >> >> branch for a given ticket-# >> >> >> >> Approval and merging should be a link on the ticket page, if possible. >> >> People should be able to approve a change with one click. >> >> >> >> Alternate idea: Create a ticket for everything, attach the diff and let >> >> someone else commit it after review. >> >> Translation updates and minor fixes like r13678 to r13680 should be >> >> committed without review. >> >> >> >> Sebastian >> >> >> >> Am 11.02.2011 14:27, schrieb Gabor Szabo: >> >> > On Fri, Feb 11, 2011 at 2:08 PM, Gabor Szabo<szab...@gmail.com> >> >> > ?wrote: >> >> >> Here is an example: >> >> >> >> >> >> I'd like to remove the "Perl/Automatic Bracket Completion" >> >> >> menu option as it is also available as >> >> >> "Tools/Preferences/Behaviour/Autocomplete brackets". >> >> >> I just opened a ticket with this >> >> >> http://padre.perlide.org/trac/ticket/1102 >> >> >> >> >> >> I'll now see how easy/difficult this will b with out current >> >> >> technology. >> >> > >> >> > svn cp http://svn.perlide.org/padre/trunk/Padre >> >> > http://svn.perlide.org/padre/branches/Padre-t1102 -m'branch for >> >> > #1102' >> >> > svn switch http://svn.perlide.org/padre/branches/Padre-t1102 . >> >> > >> >> > make the changes >> >> > >> >> > svn ci -m'Remove ?Perl/Automatic Bracket Completion ? ?#1102' >> >> > >> >> > (maybe do some more changes, if it is cleaner that way) >> >> > >> >> > # going back to trunk: >> >> > svn switch http://svn.perlide.org/padre/trunk/Padre >> >> > >> >> > I updated the tricket in trac but I don't see a way to mark it >> >> > "resolved, waiting for approval". >> >> > Now someone need to check the changes and approve them >> >> > >> >> > >> >> > Once that's done someone will need to merge: >> >> > To merge to trunk one needs to be in trunk and run: >> >> > >> >> > # First find out the point of branching: >> >> > svn log http://svn.perlide.org/padre/branches/Padre-t1102 >> >> > --stop-on-copy >> >> > # from the listing get the earlies revision number, where the >> >> > branching >> >> > happaned >> >> > svn merge http://svn.perlide.org/padre/branches/Padre-t1102 >> >> > -r13682:HEAD >> >> > . >> >> > svn ci -m'merge #1102' >> >> > svn rm http://svn.perlide.org/padre/branches/Padre-t1102 -m 'merged' >> >> > >> >> > >> >> > huh >> >> > ? ? Gabor >> >> > _______________________________________________ >> >> > Padre-dev mailing list >> >> > Padre-dev@perlide.org >> >> > http://mail.perlide.org/mailman/listinfo/padre-dev >> >> >> >> >> >> ------------------------------ >> >> >> >> Message: 2 >> >> Date: Fri, 11 Feb 2011 17:43:10 +0100 >> >> From: Zeno Gantner <zeno.gant...@gmail.com> >> >> Subject: Re: [Padre-dev] proposal for adding new features >> >> To: Padre development discussion list <padre-dev@perlide.org> >> >> Message-ID: >> >> ? ? ? ?<aanlktimz6hs38539q2n1x9nzyxcbwpzvbb+oharab...@mail.gmail.com> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> Hi, >> >> >> >> On Fri, Feb 11, 2011 at 12:53 PM, Gabor Szabo <szab...@gmail.com> >> >> wrote: >> >> > I agree that developing things first as a plugin would be a good >> >> > idea. >> >> > It might require some improved API for the plugins so they can >> >> > do thing which the current API does not let them do yet. >> >> > It will also require a clear description of the plugin API and >> >> > making sure we don't break the API without proper notification and >> >> > a period that allows the plugins to move to the new API. >> >> > >> >> > That might mean. >> >> > 1) Add new API feature and mark old API as deprecated. Release Padre >> >> > 2) Wait 2 weeks, then add command line warnings to the deprecated >> >> > methods. Release Padre. >> >> > 3) After another 2 weeks remove old API. Release Padre >> >> > >> >> > The periods can be longer if needed and there can be additional Padre >> >> > releases in the between. >> >> > >> >> > This still does not solve the whole issue though as some of the >> >> > changes >> >> > we want to make are tweaks to existing features. I'll send a separate >> >> > message with that. >> >> >> >> I agree that the solution is incomplete. >> >> I only thought of things that are already easy to implement as plugins >> >> now. >> >> Other than that, if we add complicated rules about API changes etc., >> >> we may be better served with one or several experimental branches >> >> (possibly using git) and that's it. >> >> >> >> Best regards, >> >> ?Z. >> >> >> >> -- >> >> MyMediaLite Recommender System Library: http://ismll.de/mymedialite >> >> >> >> >> >> ------------------------------ >> >> >> >> Message: 3 >> >> Date: Fri, 11 Feb 2011 17:45:02 +0100 >> >> From: Zeno Gantner <zeno.gant...@gmail.com> >> >> Subject: Re: [Padre-dev] proposal for adding new features >> >> To: Padre development discussion list <padre-dev@perlide.org> >> >> Message-ID: >> >> ? ? ? ?<aanlktinrstaavfg7lhscswri0nctmpnl6fdw3o4-g...@mail.gmail.com> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> Hi Sewi and list, >> >> >> >> On Fri, Feb 11, 2011 at 2:47 PM, Sebastian Willing >> >> <sebastian.will...@web.de> wrote: >> >> > The frozen release branch may solve parts of the "stable release" >> >> > request. >> >> >> >> agreed. >> >> >> >> > I don't see people installing Plugins. Things like "svn" and "tidy" >> >> > and >> >> > other mandatory issues are installed, but many others are very >> >> > unknown >> >> > to Padre users. >> >> > >> >> > Option #2 sounds best to me. The >> >> > Padre::Plugin::Experimental(Features) >> >> > should be a core plugin. It could be enabled by default when running >> >> > trunk and disabled by default when running a released version. >> >> >> >> again agreed. >> >> >> >> > Tweaks could be catched by the manual tests and the frozen release >> >> > branch. >> >> >> >> In particular: If we tweak a feature, we should a test for that >> >> feature if it does not exist yet ;-). >> >> >> >> > We need less released bugs, but we shouldn't make development too >> >> > complicated. >> >> >> >> 100% agreement. >> >> >> >> Best regards, >> >> ?Zeno >> >> >> >> -- >> >> MyMediaLite Recommender System Library: http://ismll.de/mymedialite >> >> >> >> >> >> ------------------------------ >> >> >> >> Message: 4 >> >> Date: Fri, 11 Feb 2011 17:47:36 +0100 >> >> From: Zeno Gantner <zeno.gant...@gmail.com> >> >> Subject: Re: [Padre-dev] Padre UI and Brand design >> >> To: Padre development discussion list <padre-dev@perlide.org> >> >> Message-ID: >> >> ? ? ? ?<aanlktikkee8oedu3bjdwawj52z2ujtoryj1vs2lgk...@mail.gmail.com> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> Hi Amit, >> >> >> >> thank you for requisting this kind of input. It would be great to have >> >> some direction here. >> >> >> >> My answers below, inline. >> >> >> >> On Fri, Feb 11, 2011 at 1:12 PM, amit mojumder <mit....@gmail.com> >> >> wrote: >> >> > 01. At present Padre has no color appearing as brand color. so, which >> >> > colors >> >> > should i choice for the designing procedure. If you have any specific >> >> > colors >> >> > to be used you can suggest. >> >> >> >> I really like the Padre logo, so it would be nice to either have the >> >> blue from the icon, the green from the about dialog, or some color >> >> that really harmonizes with those colors. >> >> >> >> > 02. What designing style you are expecting, like web 2.0 or minimal >> >> > or >> >> > general etc. >> >> >> >> I am generally in favor of minimalism, but not at any cost. Make it as >> >> simple as possible, but not simpler. >> >> >> >> > 03. Do you have any specific website, which you like most and would >> >> > like >> >> > to >> >> > see Padre design would be something like that standard? here i can >> >> > mention >> >> > that, twitter has specific web 2.0 style, facebook has a specific >> >> > style. >> >> > so >> >> > something like that, do you have any preference? >> >> >> >> Some examples of software pages I like: >> >> ?- http://perl6.org/ (okay, one can discuss about the colors, but I >> >> guess it is intentional) >> >> ?- http://cream.sourceforge.net/ (quite minimalistic) >> >> ?- http://strawberryperl.com/ (nice logo) >> >> ?- http://monodevelop.com/ (more content, still usable, see the >> >> download section!) >> >> ?- http://redcareditor.com/ >> >> ?- http://fantom.org/ >> >> >> >> > 04. In order to design a proper user experience, do you have any >> >> > suggestions >> >> > or opinions to be implemented specially? >> >> >> >> Do you mean for the website? >> >> >> >> It should enable potential users to >> >> 1. learn what Padre is, >> >> 2. motivate them to try Padre, >> >> 3. make it as simple as possible to find the preferred way of >> >> installation for their platform, and >> >> 4. direct them to solutions in case they have problems. >> >> >> >> Experienced users should find >> >> 1. information about updates and >> >> 2. about advanced functionality, as well as >> >> 3. ways to contribute to Padre's development. >> >> >> >> > 05. What elements you people are expecting to be appeared on the >> >> > Padre >> >> > home >> >> > page? >> >> >> >> screenshots, download instructions, brief and appealing description, >> >> plugin list, how to contribute >> >> >> >> > 06. Gabor told me that, he liked rounded box in case of buttons or >> >> > sections, >> >> > so something like that do you have anything u prefer most? >> >> >> >> -- >> >> >> >> > 07. I am planning on to redesign the padre logo, so that it may >> >> > appear >> >> > as a >> >> > web icons like twitter or facebook, so what do you think about it? I >> >> > would >> >> > like to keep the butterfly shape since, over the times its already >> >> > used >> >> > and >> >> > achieved a?familiarity in the community. >> >> >> >> I like the small icon very much. It is beautiful. >> >> >> >> Best regards, >> >> ?Z. >> >> >> >> -- >> >> MyMediaLite Recommender System Library: http://ismll.de/mymedialite >> >> >> >> >> >> ------------------------------ >> >> >> >> _______________________________________________ >> >> Padre-dev mailing list >> >> Padre-dev@perlide.org >> >> http://mail.perlide.org/mailman/listinfo/padre-dev >> >> >> >> >> >> End of Padre-dev Digest, Vol 31, Issue 14 >> >> ***************************************** >> > >> > >> > _______________________________________________ >> > Padre-dev mailing list >> > Padre-dev@perlide.org >> > http://mail.perlide.org/mailman/listinfo/padre-dev >> > >> > >> >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 14 Feb 2011 08:39:00 +0200 >> From: Gabor Szabo <szab...@gmail.com> >> Subject: Re: [Padre-dev] [Padre-commit] rev 13689 - change in project >> support >> To: padre-dev@perlide.org >> Message-ID: >> <AANLkTimahfLnLs+9qy=hrezm+lvjiaa1-k01_kgca...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Mon, Feb 14, 2011 at 3:46 AM, <s...@perlide.org> wrote: >> > Author: adamk >> > See also: http://padre.perlide.org/changeset/13689 >> > Date: 2011-02-13 17:46:20 -0800 (Sun, 13 Feb 2011) >> > New Revision: 13689 >> > >> > Modified: >> > ? trunk/Padre/Changes >> > ? trunk/Padre/lib/Padre/Document.pm >> > ? trunk/Padre/lib/Padre/Project.pm >> > Log: >> > ? ?- Intuit project root from version control checkout directories and >> > ? ? ?classify them as an ordinary vanilla Padre::Project, before we give >> > up >> > ? ? ?and treat something as a Null projects (ADAMK) >> > >> >> > Modified: trunk/Padre/lib/Padre/Project.pm >> > =================================================================== >> > --- trunk/Padre/lib/Padre/Project.pm ? ?2011-02-13 16:01:40 UTC (rev >> > 13688) >> > +++ trunk/Padre/lib/Padre/Project.pm ? ?2011-02-14 01:46:20 UTC (rev >> > 13689) >> > @@ -37,6 +37,8 @@ >> > ? ? ? ? ? ? ? ?); >> > ? ? ? ? ? ? ? ?return 'Padre::Project::Null'; >> > ? ? ? ?} >> > + >> > + ? ? ? # There are several main indicators this is a Perl project >> > ? ? ? ?if ( -f File::Spec->catfile( $root, 'Makefile.PL' ) ) { >> > ? ? ? ? ? ? ? ?return 'Padre::Project::Perl'; >> > ? ? ? ?} >> > @@ -46,9 +48,24 @@ >> > ? ? ? ?if ( -f File::Spec->catfile( $root, 'dist.ini' ) ) { >> > ? ? ? ? ? ? ? ?return 'Padre::Project::Perl'; >> > ? ? ? ?} >> > + >> > + ? ? ? # Is this a manually configured explicit Padre project >> > ? ? ? ?if ( -f File::Spec->catfile( $root, 'padre.yml' ) ) { >> > ? ? ? ? ? ? ? ?return 'Padre::Project'; >> > ? ? ? ?} >> > + >> > + ? ? ? # If there are no language-specific indicators, check to see if >> > + ? ? ? # this directory is (ideally the root of) a version control >> > checkout. >> > + ? ? ? foreach my $vcs ( '.svn', '.git', '.hg', '.bzr' ) { >> > + ? ? ? ? ? ? ? if ( -d File::Spec->catfile($root, $vcs) ) { >> > + ? ? ? ? ? ? ? ? ? ? ? return 'Padre::Project'; >> > + ? ? ? ? ? ? ? } >> > + ? ? ? } >> > + ? ? ? if ( -f File::Spec->catfile($root, 'CSV', 'Repository') ) { >> > + ? ? ? ? ? ? ? return 'Padre::Project'; >> > + ? ? ? } >> >> I get that you can usually conclude project root by .git or .hg and >> probably .bzr >> as there is only a single such directory in every repository but .svn and >> CVS ? >> They appear in every subdirectory as well. >> >> >> >> Gabor >> >> >> ------------------------------ >> >> Message: 3 >> Date: Mon, 14 Feb 2011 09:31:50 +0200 >> From: Gabor Szabo <szab...@gmail.com> >> Subject: Re: [Padre-dev] Manual test scripts needed for Padre >> To: Padre development discussion list <padre-dev@perlide.org> >> Message-ID: >> <aanlktimvhx2zcdzv6zx6mjcpk0pueysszutr0zpxa...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Thu, Feb 10, 2011 at 6:24 PM, Alexandr Ciornii <alexcho...@gmail.com> >> wrote: >> > Hi >> > >> > 2011/2/10 Shlomi Fish <shlo...@iglu.org.il>: >> > >> >> So something like that for Padre will be very nice. I'm not sure if the >> >> source >> >> code behind "Litmus" is available or if they will agree to host another >> >> project, but I can try to find out. >> > >> > It is free (MPL) and it is written in Perl using Class::DBI . See >> > https://wiki.mozilla.org/Litmus >> >> thanks for the link. >> >> I have started to try to install it. Some links are broken on their wiki >> and I could not find a help mailing list though there was an IRC channel >> mentioned. >> >> If any of you want to play around with the system on the Mozilla web site, >> their live installation and discuss if it can fit us or not. >> >> regards >> Gabor >> >> >> ------------------------------ >> >> Message: 4 >> Date: Mon, 14 Feb 2011 19:00:25 +1100 >> From: Adam Kennedy <adamkennedybac...@gmail.com> >> Subject: Re: [Padre-dev] [Padre-commit] rev 13689 - change in project >> support >> To: Padre development discussion list <padre-dev@perlide.org> >> Message-ID: >> <AANLkTi=Tp7Z4vH2swhczN47cY5=plh4fgfzkgyrbf...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> The implementation in the class method is used when the root directory >> has ALREADY been identified, and we're trying to work out what it is. >> >> The CVS implementation there still does the Repository file check. >> >> The more important version is the one in Padre::Project::from_file, >> which is used to determine the project root from a single file. >> >> In the from_file version is does actually look up the path, and it >> specifically checks for the top-most occurrence of either .svn or >> CVS/Repository. It shouldn't stop half way in the middle of a SVN >> checkout unless it finds a Makefile.PL or something more type-specific >> specific. >> >> Adam K >> >> On 14 February 2011 17:39, Gabor Szabo <szab...@gmail.com> wrote: >> > On Mon, Feb 14, 2011 at 3:46 AM, ?<s...@perlide.org> wrote: >> >> Author: adamk >> >> See also: http://padre.perlide.org/changeset/13689 >> >> Date: 2011-02-13 17:46:20 -0800 (Sun, 13 Feb 2011) >> >> New Revision: 13689 >> >> >> >> Modified: >> >> ? trunk/Padre/Changes >> >> ? trunk/Padre/lib/Padre/Document.pm >> >> ? trunk/Padre/lib/Padre/Project.pm >> >> Log: >> >> ? ?- Intuit project root from version control checkout directories and >> >> ? ? ?classify them as an ordinary vanilla Padre::Project, before we >> >> give up >> >> ? ? ?and treat something as a Null projects (ADAMK) >> >> >> > >> >> Modified: trunk/Padre/lib/Padre/Project.pm >> >> =================================================================== >> >> --- trunk/Padre/lib/Padre/Project.pm ? ?2011-02-13 16:01:40 UTC (rev >> >> 13688) >> >> +++ trunk/Padre/lib/Padre/Project.pm ? ?2011-02-14 01:46:20 UTC (rev >> >> 13689) >> >> @@ -37,6 +37,8 @@ >> >> ? ? ? ? ? ? ? ?); >> >> ? ? ? ? ? ? ? ?return 'Padre::Project::Null'; >> >> ? ? ? ?} >> >> + >> >> + ? ? ? # There are several main indicators this is a Perl project >> >> ? ? ? ?if ( -f File::Spec->catfile( $root, 'Makefile.PL' ) ) { >> >> ? ? ? ? ? ? ? ?return 'Padre::Project::Perl'; >> >> ? ? ? ?} >> >> @@ -46,9 +48,24 @@ >> >> ? ? ? ?if ( -f File::Spec->catfile( $root, 'dist.ini' ) ) { >> >> ? ? ? ? ? ? ? ?return 'Padre::Project::Perl'; >> >> ? ? ? ?} >> >> + >> >> + ? ? ? # Is this a manually configured explicit Padre project >> >> ? ? ? ?if ( -f File::Spec->catfile( $root, 'padre.yml' ) ) { >> >> ? ? ? ? ? ? ? ?return 'Padre::Project'; >> >> ? ? ? ?} >> >> + >> >> + ? ? ? # If there are no language-specific indicators, check to see if >> >> + ? ? ? # this directory is (ideally the root of) a version control >> >> checkout. >> >> + ? ? ? foreach my $vcs ( '.svn', '.git', '.hg', '.bzr' ) { >> >> + ? ? ? ? ? ? ? if ( -d File::Spec->catfile($root, $vcs) ) { >> >> + ? ? ? ? ? ? ? ? ? ? ? return 'Padre::Project'; >> >> + ? ? ? ? ? ? ? } >> >> + ? ? ? } >> >> + ? ? ? if ( -f File::Spec->catfile($root, 'CSV', 'Repository') ) { >> >> + ? ? ? ? ? ? ? return 'Padre::Project'; >> >> + ? ? ? } >> > >> > I get that you can usually conclude project root by .git or .hg and >> > probably .bzr >> > as there is only a single such directory in every repository but .svn >> > and CVS ? >> > They appear in every subdirectory as well. >> > >> > >> > >> > Gabor >> > _______________________________________________ >> > Padre-dev mailing list >> > Padre-dev@perlide.org >> > http://mail.perlide.org/mailman/listinfo/padre-dev >> > >> >> >> ------------------------------ >> >> Message: 5 >> Date: Mon, 14 Feb 2011 14:29:07 +0100 >> From: Sebastian Willing <sebastian.will...@web.de> >> Subject: Re: [Padre-dev] proposal for adding new features >> To: Padre development discussion list <padre-dev@perlide.org> >> Message-ID: <4d592e23.7070...@web.de> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> Hi all, >> >> Am 12.02.2011 07:42, schrieb Adam Kennedy: >> [...] >> > I think the idea of an experimental plugin represents the worst of >> > both worlds. It's shoved in the core, it's all mixed in together (all >> > or nothing, plus way harder to merge just one feature) and it's >> > duplicating an already existing mechanism for experimental features. >> >> I agree, but I don't think many people will enable all experimental >> plugins manually and changes won't be tested. What about >> enable-by-default those experimental-feature-plugin? >> >> Sebastian >> >> >> ------------------------------ >> >> Message: 6 >> Date: Tue, 15 Feb 2011 00:40:04 +1100 >> From: Adam Kennedy <adamkennedybac...@gmail.com> >> Subject: Re: [Padre-dev] proposal for adding new features >> To: Padre development discussion list <padre-dev@perlide.org> >> Message-ID: >> <AANLkTinrDpm__hLK1-X9KUf=qdncuw+tge_ein-xp...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> Then they just become broken features... >> >> >> >> On 15 February 2011 00:29, Sebastian Willing <sebastian.will...@web.de> >> wrote: >> > Hi all, >> > >> > Am 12.02.2011 07:42, schrieb Adam Kennedy: >> > [...] >> >> I think the idea of an experimental plugin represents the worst of >> >> both worlds. It's shoved in the core, it's all mixed in together (all >> >> or nothing, plus way harder to merge just one feature) and it's >> >> duplicating an already existing mechanism for experimental features. >> > >> > I agree, but I don't think many people will enable all experimental >> > plugins manually and changes won't be tested. What about >> > enable-by-default those experimental-feature-plugin? >> > >> > Sebastian >> > _______________________________________________ >> > 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 >> >> >> End of Padre-dev Digest, Vol 31, Issue 19 >> ***************************************** > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > > -- MyMediaLite Recommender System Library: http://ismll.de/mymedialite _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
