Menu
▾
▴
pybliographer-devel
|
From: Digvijay S. <ssr...@gm...> - 2014-03-18 19:33:01
|
Hi,
I am computer science undergraduate student from IIIT Hyderabad. I am
planning to apply for GSoC 2014 in GNOME for the project Pybliographer. I
have started looking at the source-code and the bug tracker.
I am quite proficient in Python and C++. Besides this, I have hands on
experience with GTK3.
I checked out your current gtk3 branch and was going through the porting
work. I just wanted to enquire about a few things :
1. Is there any TODO list which can provide me the set of tasks that are
left in the porting job?
2. Besides this, can you provide me a starting point where I can work in
particular to strengthen my proposal, since only a few days are left before
the deadline.
3. I need some help knowing how to run the gtk3 branch in develop mode.
Thanks.
Regards,
Digvijay Singh
|
|
From: Zoltan K. <zo...@gm...> - 2014-03-19 15:11:56
|
Hi Digvijay, Yes, German is who started to port pyblio-1.2 to GTK3. I don't know the current state. German could you help in this? I couldn't test the gtk3 branch yet, but I still plan. :-) Anyway, this should be checked, tested, fixed, etc. If you are familiar in gnome stuff and specifications, you could also help in updating/fixing the icon and mime related issues. These are still in my todo. Later, maybe we could think of checking the compatibility and porting the code to python3. What do you think, guys? Zoltan On Tue, Mar 18, 2014 at 10:36 PM, Frédéric Gobry <fre...@gm...>wrote: > Hi Digivijay, > > I believe that the gtk3 branch was mostly worked on by Germán, he probably > has a clearer picture of the current state of things. Zoltan, did you run > some tests with it as well? > > This would indeed be an exciting opportunity to get the port in shape ;) > > > On Tue Mar 18 2014 at 12:33:08 PM, Digvijay Singh < > ssr...@gm...> wrote: > >> Hi, >> I am computer science undergraduate student from IIIT Hyderabad. I am >> planning to apply for GSoC 2014 in GNOME for the project Pybliographer. I >> have started looking at the source-code and the bug tracker. >> I am quite proficient in Python and C++. Besides this, I have hands on >> experience with GTK3. >> >> I checked out your current gtk3 branch and was going through the porting >> work. I just wanted to enquire about a few things : >> >> 1. Is there any TODO list which can provide me the set of tasks that are >> left in the porting job? >> 2. Besides this, can you provide me a starting point where I can work in >> particular to strengthen my proposal, since only a few days are left before >> the deadline. >> 3. I need some help knowing how to run the gtk3 branch in develop mode. >> >> >> >> Thanks. >> >> Regards, >> Digvijay Singh >> ------------------------------------------------------------ >> ------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today! >> http://p.sf.net/sfu/13534_NeoTech______________________________ >> _________________ >> Pybliographer-devel mailing list >> Pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pybliographer-devel >> > |
|
From: Germán Póo-C. <gp...@gn...> - 2014-03-19 18:27:15
Attachments:
signature.asc
|
On Wed, 2014-03-19 at 01:02 +0530, Digvijay Singh wrote: > Hi, > > I am computer science undergraduate student from IIIT Hyderabad. I > am planning to apply for GSoC 2014 in GNOME for the project > Pybliographer. I have started looking at the source-code and the bug > tracker. > I am quite proficient in Python and C++. Besides this, I have hands on > experience with GTK3. > > I checked out your current gtk3 branch and was going through the > porting work. I just wanted to enquire about a few things : > > 1. Is there any TODO list which can provide me the set of tasks that > are left in the porting job? No, there is not. There are not many things left in order to get it with the same functionality already provided with gtk2. Regardless, there are some things that can be improved and to take advantage of the new things in gtk3. However, I am of the idea of adding unit tests before doing major changes. You can find a list of bugs in https://bugzilla.gnome.org/browse.cgi?product=pybliographer which are mostly ported from sourceforge. > 2. Besides this, can you provide me a starting point where I can work > in particular to strengthen my proposal, since only a few days are > left before the deadline. In GSoC projects under the umbrella of GNOME, it is a must that applicants had submitted *at least* one non-trivial patch. That helps to guarantee that the students got familiar with the project, have a minimal understanding of the code base, can run it, and have the potential. > > 3. I need some help knowing how to run the gtk3 branch in develop > mode. The way I do it, $ git checkout gtk3 $ scripts/pybliographic > Besides email, I will hanging around #pibliographer at irc.gnome.org. Happy hacking! -- Germán Poo-Caamaño http://calcifer.org/ |
|
From: Germán Póo-C. <gp...@gn...> - 2014-03-19 18:28:40
Attachments:
signature.asc
|
On Wed, 2014-03-19 at 16:11 +0100, Zoltan Kota wrote: > Hi Digvijay, > > > Yes, German is who started to port pyblio-1.2 to GTK3. I don't know > the current state. German could you help in this? I couldn't test the > gtk3 branch yet, but I still plan. :-) Anyway, this should be checked, > tested, fixed, etc. If you are familiar in gnome stuff and > specifications, you could also help in updating/fixing the icon and > mime related issues. These are still in my todo. > > Later, maybe we could think of checking the compatibility and porting > the code to python3. What do you think, guys? We can use the package six to get it working in both 2.x and 3x initially. -- Germán Poo-Caamaño http://calcifer.org/ |
|
From: Digvijay S. <ssr...@gm...> - 2014-03-20 10:41:50
|
Hi,
Thanks for the response. I've started looking at the bug tracker.
In the meantime, please look at this patch for the file setup-check.py: "
https://github.com/ice-pice/pybliographer/commit/bc60dc149e2ec9460f73042a863090027e04ac71".
I've ported this to gtk3. Please have a look at it and let me know if any
changes are required.
Regards,
Digvijay
On Wed, Mar 19, 2014 at 11:33 PM, Germán Póo-Caamaño <gp...@gn...> wrote:
> On Wed, 2014-03-19 at 16:11 +0100, Zoltan Kota wrote:
> > Hi Digvijay,
> >
> >
> > Yes, German is who started to port pyblio-1.2 to GTK3. I don't know
> > the current state. German could you help in this? I couldn't test the
> > gtk3 branch yet, but I still plan. :-) Anyway, this should be checked,
> > tested, fixed, etc. If you are familiar in gnome stuff and
> > specifications, you could also help in updating/fixing the icon and
> > mime related issues. These are still in my todo.
> >
> > Later, maybe we could think of checking the compatibility and porting
> > the code to python3. What do you think, guys?
>
> We can use the package six to get it working in both 2.x and 3x
> initially.
>
> --
> Germán Poo-Caamaño
> http://calcifer.org/
>
|
|
From: Germán Póo-C. <gp...@gn...> - 2014-03-20 16:32:43
Attachments:
signature.asc
|
On Thu, 2014-03-20 at 16:11 +0530, Digvijay Singh wrote: > Hi, > Thanks for the response. I've started looking at the bug tracker. > > In the meantime, please look at this patch for the file > setup-check.py: > "https://github.com/ice-pice/pybliographer/commit/bc60dc149e2ec9460f73042a863090027e04ac71". I've ported this to gtk3. Please have a look at it and let me know if any changes are required. > Thanks for trying this. I think that for the gtk3 branch we should go for something in the configure.ac: AM_PATH_PYTHON PKG_CHECK_MODULES(PYBLIOBRAPHER, pygobject-3.0) Or even: AM_PATH_PYTHON(2.6) PKG_CHECK_MODULES(PYBLIOBRAPHER, pygobject-3.0) Or 2.7, depending if we use start using features available in PyGobject 3.10. 2.6 is the minimum Python version required for 3.4. So, setup-check.py would be less needed. However, it is necessary to changes in other places as well. However, I would prefer if you could take a look at other places than the build system (at this moment). For example, with the current status, non-ascii bibtex entries can not be edited using "Native Editing". -- Germán Poo-Caamaño http://calcifer.org/ |
|
From: Digvijay S. <ssr...@gm...> - 2014-03-21 18:21:42
|
Hi, Since I was short of time I have submitted my proposal " https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014/diggy/5846034605408256 ". Can you please review it and give some feedback? Also now that I got time, I will be working on the bug and be submitting patches in this week. Regards, Digvijay Singh On Thu, Mar 20, 2014 at 10:02 PM, Germán Póo-Caamaño <gp...@gn...> wrote: > On Thu, 2014-03-20 at 16:11 +0530, Digvijay Singh wrote: > > Hi, > > Thanks for the response. I've started looking at the bug tracker. > > > > In the meantime, please look at this patch for the file > > setup-check.py: > > " > https://github.com/ice-pice/pybliographer/commit/bc60dc149e2ec9460f73042a863090027e04ac71". > I've ported this to gtk3. Please have a look at it and let me know if any > changes are required. > > > Thanks for trying this. > > I think that for the gtk3 branch we should go for something in the > configure.ac: > > AM_PATH_PYTHON > PKG_CHECK_MODULES(PYBLIOBRAPHER, pygobject-3.0) > > Or even: > AM_PATH_PYTHON(2.6) > PKG_CHECK_MODULES(PYBLIOBRAPHER, pygobject-3.0) > > Or 2.7, depending if we use start using features available in PyGobject > 3.10. 2.6 is the minimum Python version required for 3.4. > > So, setup-check.py would be less needed. However, it is necessary to > changes in other places as well. > > However, I would prefer if you could take a look at other places than > the build system (at this moment). For example, with the current status, > non-ascii bibtex entries can not be edited using "Native Editing". > > -- > Germán Poo-Caamaño > http://calcifer.org/ > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X