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 > > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
