<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br>Hi everyone! , <div><br></div><div>I want to pick a project to work on and needed some help. I was wondering what </div><div>would be a perfect beginners project/ or practise assignment. Also, if there is such </div><div>a thing what files should I <span style="font-size: 12pt;">read and what source code should I take a look at. </span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">PS: I have looked at the HACKING file and have had a decent look at the bugs and </span></div><div><span style="font-size: 12pt;">feature requests </span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">Thanks, </span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">Atal Akbari </span></div><div><br></div><div><br><div>> From: devel-request@lists.geany.org<br>> Subject: Devel Digest, Vol 87, Issue 27<br>> To: devel@lists.geany.org<br>> Date: Sun, 28 Jun 2015 09:00:02 +0000<br>> <br>> Send Devel mailing list submissions to<br>> devel@lists.geany.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> https://lists.geany.org/cgi-bin/mailman/listinfo/devel<br>> or, via email, send a message with subject or body 'help' to<br>> devel-request@lists.geany.org<br>> <br>> You can reach the person managing the list at<br>> devel-owner@lists.geany.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Devel digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Spawn module API (Lex Trotman)<br>> 2. Re: Spawn module API (Lex Trotman)<br>> 3. Re: Spawn module API (Matthew Brush)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Sun, 28 Jun 2015 12:54:56 +1000<br>> From: Lex Trotman <elextr@gmail.com><br>> To: Geany development list <devel@lists.geany.org><br>> Subject: Re: [Geany-Devel] Spawn module API<br>> Message-ID:<br>> <CAKhWKDP9E-pcyrUQT0Og7wB-g45BnPT_RBoGM=4-F3LYKcAs3w@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> On 28 June 2015 at 12:40, Matthew Brush <mbrush@codebrainz.ca> wrote:<br>> > On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:<br>> >><br>> >> [...]<br>> >><br>> >> An updated list of the API-s asked to remain public:<br>> >><br>> >> me WIF*<br>> >> lex spawn_get_program_name<br>> >> lex spawn_check_command<br>> >> me/lex spawn_kill_process<br>> >> spawn_async_with_pipes<br>> >> lex spawn_async<br>> >> me/lex spawn_with_callbacks<br>> >> me spawn_write_data<br>> >> lex? spawn_get_exit_status_cb<br>> >> lex spawn_sync<br>> >><br>> ><br>> > We should only export what you have concrete plans to use during the next<br>> > cycle. If Lex wants update plugins during the next cycle to use other parts<br>> > of the API, we can expose them at the time that the PR is made. No point to<br>> > speculatively expose API that nobody has immediate plans to use.<br>> <br>> If no API is available then nobody will have any plans so no API is<br>> needed so nobody will have any plans for the egg so no chicken is<br>> needed so ....<br>> <br>> <br>> ><br>> > Cheers,<br>> > Matthew Brush<br>> > _______________________________________________<br>> > Devel mailing list<br>> > Devel@lists.geany.org<br>> > https://lists.geany.org/cgi-bin/mailman/listinfo/devel<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sun, 28 Jun 2015 13:04:07 +1000<br>> From: Lex Trotman <elextr@gmail.com><br>> To: Geany development list <devel@lists.geany.org><br>> Subject: Re: [Geany-Devel] Spawn module API<br>> Message-ID:<br>> <CAKhWKDPoVZmA--NnLxW83q4UNQxqyXdmYD9YJfAq+NqztewGTg@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> On 28 June 2015 at 12:54, Lex Trotman <elextr@gmail.com> wrote:<br>> > On 28 June 2015 at 12:40, Matthew Brush <mbrush@codebrainz.ca> wrote:<br>> >> On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:<br>> >>><br>> >>> [...]<br>> >>><br>> >>> An updated list of the API-s asked to remain public:<br>> >>><br>> >>> me WIF*<br>> >>> lex spawn_get_program_name<br>> >>> lex spawn_check_command<br>> >>> me/lex spawn_kill_process<br>> >>> spawn_async_with_pipes<br>> >>> lex spawn_async<br>> >>> me/lex spawn_with_callbacks<br>> >>> me spawn_write_data<br>> >>> lex? spawn_get_exit_status_cb<br>> >>> lex spawn_sync<br>> >>><br>> >><br>> >> We should only export what you have concrete plans to use during the next<br>> >> cycle. If Lex wants update plugins during the next cycle to use other parts<br>> >> of the API, we can expose them at the time that the PR is made. No point to<br>> >> speculatively expose API that nobody has immediate plans to use.<br>> ><br>> > If no API is available then nobody will have any plans so no API is<br>> > needed so nobody will have any plans for the egg so no chicken is<br>> > needed so ....<br>> <br>> Or to look at it another way:<br>> <br>> "Welcome to Geany 1.25, so that their command parsing is the same as<br>> Geanys, all plugins are recommended to upgrade to the spawn_* API -<br>> that we havn't released."<br>> <br>> Cheers<br>> Lex<br>> <br>> <br>> ><br>> ><br>> >><br>> >> Cheers,<br>> >> Matthew Brush<br>> >> _______________________________________________<br>> >> Devel mailing list<br>> >> Devel@lists.geany.org<br>> >> https://lists.geany.org/cgi-bin/mailman/listinfo/devel<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Sat, 27 Jun 2015 20:14:06 -0700<br>> From: Matthew Brush <mbrush@codebrainz.ca><br>> To: devel@lists.geany.org<br>> Subject: Re: [Geany-Devel] Spawn module API<br>> Message-ID: <558F667E.90903@codebrainz.ca><br>> Content-Type: text/plain; charset=windows-1252; format=flowed<br>> <br>> On 2015-06-27 07:54 PM, Lex Trotman wrote:<br>> > On 28 June 2015 at 12:40, Matthew Brush <mbrush@codebrainz.ca> wrote:<br>> >> On 2015-06-27 12:46 PM, Dimitar Zhekov wrote:<br>> >>><br>> >>> [...]<br>> >>><br>> >>> An updated list of the API-s asked to remain public:<br>> >>><br>> >>> me WIF*<br>> >>> lex spawn_get_program_name<br>> >>> lex spawn_check_command<br>> >>> me/lex spawn_kill_process<br>> >>> spawn_async_with_pipes<br>> >>> lex spawn_async<br>> >>> me/lex spawn_with_callbacks<br>> >>> me spawn_write_data<br>> >>> lex? spawn_get_exit_status_cb<br>> >>> lex spawn_sync<br>> >>><br>> >><br>> >> We should only export what you have concrete plans to use during the next<br>> >> cycle. If Lex wants update plugins during the next cycle to use other parts<br>> >> of the API, we can expose them at the time that the PR is made. No point to<br>> >> speculatively expose API that nobody has immediate plans to use.<br>> ><br>> > If no API is available then nobody will have any plans so no API is<br>> > needed so nobody will have any plans for the egg so no chicken is<br>> > needed so ....<br>> ><br>> <br>> It can easily be made available on-demand, as normal.<br>> <br>> We should only be concerned about what Scope is requesting as it has <br>> concrete plans to use them during the next development cycle and doesn't <br>> want the plugin to depend on the next development version of Geany <br>> during that time[0]. There's no reason to speculatively rush other APIs <br>> in if no plugins have immediate plans to use them nor have the concern <br>> about depending on the development version of Geany.<br>> <br>> Cheers,<br>> Matthew Brush<br>> <br>> [0]: Which IMO is a kind of tenuous reason since most people will use <br>> the version of Scope that their distro provides or from other releases, <br>> which for the most part means the next released version of Geany/GP <br>> anyway. I guess maybe some bleeding edge distros might package it <br>> in-between releases or something, though.<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Subject: Digest Footer<br>> <br>> _______________________________________________<br>> Devel mailing list<br>> Devel@lists.geany.org<br>> https://lists.geany.org/cgi-bin/mailman/listinfo/devel<br>> <br>> <br>> ------------------------------<br>> <br>> End of Devel Digest, Vol 87, Issue 27<br>> *************************************<br></div></div> </div></body>
</html>