pybliographer-devel — Development of pybliographer

[pyblio-devel] pybliographer 1.4.0 released

[Germán Poo-C. <gp...@gn...>]

Pybliographer 1.4.0 is out. Changes include:

    Remove dependency on python-gnome2, python-gnome2-vfs,
     and python-glade2.
    Pybliographer now requires pygtk 2.24.0 and gettext 0.19.8
    Improve and simplify the build system
    Known regressions to be fixed later:
        Format entries cannot be saved 
    Known regressions that will not be fixed:
        Remove support for old confirmation dialog option
        Drop history on combo boxes 

UI translations

    Alan Mortensen (da)
    Anders Jonsson (sv)
    Ask Hjorth Larsen (da)
    Balázs Úr (hu)
    Daniel Mustieles (es)
    Jiri Grönroos (fi)
    Marek Cernocky (cs)
    Mario Blättermann (de)
    Piotr Drąg (pl)
    Rafael Fontenelle (pt_BR)
    Мирослав Николић (sr) (sr@latin) 

Doc translations

    Marek Cernocky (cs)
    Mario Blättermann (de) 

https://download.gnome.org/sources/pybliographer/1.4/

-- 
Germán Poo-Caamaño
http://calcifer.org/

[pyblio-devel] Pyblio-core-devel and the bibtex parser

[Germán Poo-C. <gp...@gn...>]

Hi Frédéric,

May you expand/explain a bit of your plans with pyblio-code-devel,
besides that you were separating the UI from the data (as far as could
you remember :-)

How did you plan to integrate it to an user interface? How did you plan
to deal with non-standard fields in bibtex files? (for the specific
case of the bibtex parser)

Additionally, it seems to me, you rewrote the BibTeX parser in Python
(I have just skimmed the logs and the code). Am I right? How far did
you go?

I read the manual, and I like the idea.  I tried it a little bit, and
it looks like a clean approach. It might be cumbersome to integrate
with the 1.2 version.

FWIW, I am working on the Gtk+3 branch, and I think it is time to
address the bibtex parser (the only issue remaining). Gtk+3 likes
everything in utf-8 whereas the code is all about latin-1.

The branch is at:
https://git.gnome.org/browse/pybliographer/log/?h=wip/gtk3

It should work with something like:

$ ./autogen.sh
$ make
$ scripts/pybliographic

Assuming _bibtex and _recode are somewhere in PYTHONPATH.

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] icons and more

[Germán Poo-C. <gp...@gn...>]

On Tue, 2017-10-03 at 18:15 +0200, Zoltan Kota wrote:
> Oh, nice to hear from you. :)
> 
> Well, last year or so my gnome git access was disabled due to
> inactivity. By now I got it back, and my commits are pushed also into
> the gnome repo. (And my main repo at github.)
> 
> Recently I updated my linux on my macbook and tried pybliographer. It
> still works :), and I decided to update some staff related to new
> gnome standards. And the icons I created two years ago(?) have been
> in a pending folder on my desktop. :))
> 
> If you agree I push a new bugfix release with these updates.

Yes, please go ahead.

> Finishing Gtk3 porting, and porting both pyblio and python-bibtex to
> python3 would be nice, but I'm a bit sceptic.

:-)

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] icons and more

[Zoltan K. <zo...@gm...>]

Oh, nice to hear from you. :)

Well, last year or so my gnome git access was disabled due to inactivity.
By now I got it back, and my commits are pushed also into the gnome repo.
(And my main repo at github.)

Recently I updated my linux on my macbook and tried pybliographer. It still
works :), and I decided to update some staff related to new gnome
standards. And the icons I created two years ago(?) have been in a pending
folder on my desktop. :))

If you agree I push a new bugfix release with these updates.

Finishing Gtk3 porting, and porting both pyblio and python-bibtex to
python3 would be nice, but I'm a bit sceptic.

 Zoltan



On Tue, Oct 3, 2017 at 4:38 PM, Frédéric Gobry <go...@pu...> wrote:

> Hey Zoltán, I was also curious about the commits :)
>
> Germán, what exactly is the issue? As we all have diacritics in our names,
> let's make this work :)
>
> On Tue, Oct 3, 2017 at 7:00 AM Germán Poo-Caamaño <gp...@gn...> wrote:
>
>> On Tue, 2017-10-03 at 15:51 +0200, Zoltan Kota wrote:
>> > Hi,
>> >
>> > Is there anybody here alive?
>>
>> Hi Zoltan, I noticed your recent commits. I was wondering why Sf? I had
>> the idea that you have access to gnome repository.
>>
>> I have not touched the master pybliographic in a while, I had this idea
>> of porting it to gtk3, but I have one important regression that I have
>> not been able to address properly (utf-8 nightmare :-)
>>
>> --
>> Germán Poo-Caamaño
>> http://calcifer.org/
>
>

[pyblio-devel] icons and more

[Zoltan K. <zo...@gm...>]

Hi,

Is there anybody here alive?

Zoltan

[pyblio-devel] pybliographer 1.2.17 released

[Zoltan K. <zo...@gm...>]

Dear All,

Pybliographer 1.2.17 is out.
http://www.pybliographer.org/News/2014-11-30

Zoltan

Re: [pyblio-devel] pyblio 1.2.17 and beyond

[Frédéric G. <go...@pu...>]

Pretty good already :)

On Wed Nov 26 2014 at 12:04:07 AM Zoltan Kota <zo...@gm...> wrote:

> Hi,
>
> After a short course on Inkscape I have a "let's try quickly" version of
> the icon. :-))
>
> http://www.pybliographer.org/ZoltanKota/icons
>
> With some refinement, I have the chance maybe to get close to the original
> version. :-))
>
> Zoltan
>
>
> On Thu, Nov 20, 2014 at 10:08 PM, Germán Poo-Caamaño <gp...@gn...>
> wrote:
>
>> On Thu, 2014-11-20 at 09:29 +0100, Zoltan Kota wrote:
>> > Hi All,
>> >
>> > I plan to release pybliographer 1.2.17 soon to include and publish the
>> > latest bugfixes and appdata staff.
>> >
>> > In the next step, we should update a bit the installation system and
>> > include icons in the format of gnome recommendations.
>> > According to my latest knowledge, we don't have the original vector
>> file of
>> > pybliographer's logo, so we should redraw it!? Could anybody help with
>> > this? I'm not an expert in Inkscape, although I had to use it recently
>> to
>> > create a conference logo.
>> > (I've already played a bit with Inkscape, but I could not reproduce some
>> > lighting effects yet.)
>>
>> I remember that a while ago, one could ask to the art team for icons and
>> related stuffs.  I am unsure if still #art or #gnome-art in GimpNet is
>> active, but it might worth to give it a try.
>>
>> Probably you would need to give an explanation of the tool, and maybe
>> give the free way to design a new one if they feel inclined to do so.
>>
>> --
>> Germán Poo-Caamaño
>> http://calcifer.org/
>>
>>
> ------------------------------------------------------------
> ------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&
> iu=/4140/ostg.clktrk_______________________________________________
> Pybliographer-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pybliographer-devel
>

Re: [pyblio-devel] pyblio 1.2.17 and beyond

[Zoltan K. <zo...@gm...>]

Hi,

After a short course on Inkscape I have a "let's try quickly" version of
the icon. :-))

http://www.pybliographer.org/ZoltanKota/icons

With some refinement, I have the chance maybe to get close to the original
version. :-))

Zoltan


On Thu, Nov 20, 2014 at 10:08 PM, Germán Poo-Caamaño <gp...@gn...> wrote:

> On Thu, 2014-11-20 at 09:29 +0100, Zoltan Kota wrote:
> > Hi All,
> >
> > I plan to release pybliographer 1.2.17 soon to include and publish the
> > latest bugfixes and appdata staff.
> >
> > In the next step, we should update a bit the installation system and
> > include icons in the format of gnome recommendations.
> > According to my latest knowledge, we don't have the original vector file
> of
> > pybliographer's logo, so we should redraw it!? Could anybody help with
> > this? I'm not an expert in Inkscape, although I had to use it recently to
> > create a conference logo.
> > (I've already played a bit with Inkscape, but I could not reproduce some
> > lighting effects yet.)
>
> I remember that a while ago, one could ask to the art team for icons and
> related stuffs.  I am unsure if still #art or #gnome-art in GimpNet is
> active, but it might worth to give it a try.
>
> Probably you would need to give an explanation of the tool, and maybe
> give the free way to design a new one if they feel inclined to do so.
>
> --
> Germán Poo-Caamaño
> http://calcifer.org/
>
>

Re: [pyblio-devel] pyblio 1.2.17 and beyond

[Germán Poo-C. <gp...@gn...>]

On Thu, 2014-11-20 at 09:29 +0100, Zoltan Kota wrote:
> Hi All,
> 
> I plan to release pybliographer 1.2.17 soon to include and publish the
> latest bugfixes and appdata staff.
> 
> In the next step, we should update a bit the installation system and
> include icons in the format of gnome recommendations.
> According to my latest knowledge, we don't have the original vector file of
> pybliographer's logo, so we should redraw it!? Could anybody help with
> this? I'm not an expert in Inkscape, although I had to use it recently to
> create a conference logo.
> (I've already played a bit with Inkscape, but I could not reproduce some
> lighting effects yet.)

I remember that a while ago, one could ask to the art team for icons and
related stuffs.  I am unsure if still #art or #gnome-art in GimpNet is
active, but it might worth to give it a try.

Probably you would need to give an explanation of the tool, and maybe
give the free way to design a new one if they feel inclined to do so.

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] Simplification(?) of python-bibtex and moving to Unicode

[Germán Poo-C. <gp...@gn...>]

On Thu, 2014-11-20 at 09:50 +0100, Zoltan Kota wrote:
> Hi,
> 
> I don't remember exactly for what python-bibtex uses 'recode'. But could we
> not get rid of the recode package dependency somehow? 'Recode' is not
> really maintained anymore. From a point of view of a packager, it is also
> harder and harder to rebuild recode in newer distributions.

I would aim to remove it.  I had the perception that it was used to
convert from/to LaTeX to latin-1.  But in other parts of the code,
encode/decode was also in use.

FWIW, when I started porting pybliographer to Gtk+3, I got one encoding
issue for showing the "native" window editor.  When I started to track
it down, finally I decide to start from bottom to top, and use Unicode
everywhere.  During that process, I took the chance to write a more
generic (hopefully friendlier) API to parse LaTeX.

On a side note, in the original design of Pybliographer, the core is the
Iterator class, which I would aim to simplify it too (if that would make
sense to do).

So, the next steps would be:
     1. Adapt pybliographer to the new python-bibtex API.
     2. Decorate the classes that implement __str__ with
        python_2_unicode_compatible, and using the package six to help
        with some conversions.
     3. Check every part that encodes or decodes strings.
     4. Try to fix the config settings (the strings would be different:
        str != unicode in Python 2), that is, to read the old config
        settings and write them in a new format (all unicode)

I think in (3) we can know for sure if we can remove or replace recode.

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] Simplification(?) of python-bibtex and moving to Unicode

[Zoltan K. <zo...@gm...>]

Hi,

I don't remember exactly for what python-bibtex uses 'recode'. But could we
not get rid of the recode package dependency somehow? 'Recode' is not
really maintained anymore. From a point of view of a packager, it is also
harder and harder to rebuild recode in newer distributions.

Zoltan


On Thu, Nov 20, 2014 at 9:26 AM, Germán Poo-Caamaño <gp...@gn...> wrote:

> On Thu, 2014-11-20 at 04:22 +0000, Frédéric Gobry wrote:
> > >
> > > I think it is simpler than the old way.  Besides this, instead of using
> > > PyString_FromString I would use PyUnicode_FromString, and provide
> > > unicode support from closer to the actual data.  That would remove the
> > > need for encode/decode inside pybliographer in most of the code.
> >
> > Nice. This sounds fairly reasonable :) (bear in mind that I wrote that a
> > long time ago, with little experience in i18n)
>
> I just pushed a work-in-progress branch.  It contains PyDoc, but I have
> not added any example nor checked test cases.  However, I put a basic
> example in https://gist.github.com/gpoo/f615b856029d74ad3bfc
>
> I have not tested set_native and reverse (renamed to field_set_native
> and field_reverse), and I think they might need some tweak and
> validations.
>
> The main struct has some noise (3 dummy members) that I used them to
> play while learning about C Python.
>
> help(bibtex) / help(bibtex.BibtexParser) should give some clues of
> the API.
>
> > > In addition, there are some functions that are public in the current
> > > _bibtex, but I think those are too low level for what could be use. For
> > > example, get_offset and set_offset.
> >
> > Hmm,  this is too far away for me to remember why I exposed them.
>
> I remove them from the branch, if they were required we can put them
> back. But I don't see them in pybliographer.
>
> --
> Germán Poo-Caamaño
> http://calcifer.org/
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Pybliographer-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pybliographer-devel
>

[pyblio-devel] pyblio 1.2.17 and beyond

[Zoltan K. <zo...@gm...>]

Hi All,

I plan to release pybliographer 1.2.17 soon to include and publish the
latest bugfixes and appdata staff.

In the next step, we should update a bit the installation system and
include icons in the format of gnome recommendations.
According to my latest knowledge, we don't have the original vector file of
pybliographer's logo, so we should redraw it!? Could anybody help with
this? I'm not an expert in Inkscape, although I had to use it recently to
create a conference logo.
(I've already played a bit with Inkscape, but I could not reproduce some
lighting effects yet.)

Cheers,
Zoltan

Re: [pyblio-devel] Simplification(?) of python-bibtex and moving to Unicode

[Germán Poo-C. <gp...@gn...>]

On Thu, 2014-11-20 at 04:22 +0000, Frédéric Gobry wrote:
> >
> > I think it is simpler than the old way.  Besides this, instead of using
> > PyString_FromString I would use PyUnicode_FromString, and provide
> > unicode support from closer to the actual data.  That would remove the
> > need for encode/decode inside pybliographer in most of the code.
> 
> Nice. This sounds fairly reasonable :) (bear in mind that I wrote that a
> long time ago, with little experience in i18n)

I just pushed a work-in-progress branch.  It contains PyDoc, but I have
not added any example nor checked test cases.  However, I put a basic
example in https://gist.github.com/gpoo/f615b856029d74ad3bfc

I have not tested set_native and reverse (renamed to field_set_native
and field_reverse), and I think they might need some tweak and
validations.

The main struct has some noise (3 dummy members) that I used them to
play while learning about C Python.

help(bibtex) / help(bibtex.BibtexParser) should give some clues of
the API.

> > In addition, there are some functions that are public in the current
> > _bibtex, but I think those are too low level for what could be use. For
> > example, get_offset and set_offset.
> 
> Hmm,  this is too far away for me to remember why I exposed them.

I remove them from the branch, if they were required we can put them
back. But I don't see them in pybliographer.

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] Simplification(?) of python-bibtex and moving to Unicode

[Frédéric G. <go...@pu...>]

>
> I think it is simpler than the old way.  Besides this, instead of using
> PyString_FromString I would use PyUnicode_FromString, and provide
> unicode support from closer to the actual data.  That would remove the
> need for encode/decode inside pybliographer in most of the code.
>

Nice. This sounds fairly reasonable :) (bear in mind that I wrote that a
long time ago, with little experience in i18n)


> In addition, there are some functions that are public in the current
> _bibtex, but I think those are too low level for what could be use. For
> example, get_offset and set_offset.
>

Hmm,  this is too far away for me to remember why I exposed them.


> I would like to expose BibtexEntry in a similar way, if that would make
> sense.
>
> My idea is to make use of bibtex (or any other module name), instead of
> _bibtex, which usually is for internal modules (AFAIU).  That would
> benefit other developers, I would expect.
>
> Thoughts?
>
> --
> Germán Poo-Caamaño
> http://calcifer.org/
>
>
> ------------------------------------------------------------
> ------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&
> iu=/4140/ostg.clktrk
> _______________________________________________
> Pybliographer-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pybliographer-devel
>

[pyblio-devel] Simplification(?) of python-bibtex and moving to Unicode

[Germán Poo-C. <gp...@gn...>]

Hi,

As part of moving everything to UTF-8 (and prepare the support for both
Python 2.7 and Python >= 3.4 at some point) I started to work on a "new"
API for python-bibtex.

So, far I have implemented an object that can be instantiated like:

        import bibtex
        
        db = bibtex.new_from_file('my-file.bib', strictness=False)
        
        for entry in db:
        	do_something_with_every_entry()

It is basically a wrapper on the functions that already exists.

I think it is simpler than the old way.  Besides this, instead of using
PyString_FromString I would use PyUnicode_FromString, and provide
unicode support from closer to the actual data.  That would remove the
need for encode/decode inside pybliographer in most of the code.

In addition, there are some functions that are public in the current
_bibtex, but I think those are too low level for what could be use. For
example, get_offset and set_offset.

I would like to expose BibtexEntry in a similar way, if that would make
sense.

My idea is to make use of bibtex (or any other module name), instead of
_bibtex, which usually is for internal modules (AFAIU).  That would
benefit other developers, I would expect.

Thoughts?

-- 
Germán Poo-Caamaño
http://calcifer.org/

[pyblio-devel] Fwd: [pybliographer:feature-requests] #33 Please create an AppData file

[Zoltan K. <zo...@gm...>]

Hi All,

I think we should create an Appdata file. :-) See below.
Zoltan

---------- Forwarded message ----------
From: Richard Hughes <hu...@us...>
Date: Tue, May 27, 2014 at 5:02 PM
Subject: [pybliographer:feature-requests] #33 Please create an AppData file
To: Ticket 33 <33...@fe...>


------------------------------

* [feature-requests:#33]
<http://sourceforge.net/p/pybliographer/feature-requests/33/> Please create
an AppData file*

*Status:* open
*Group:*
*Created:* Tue May 27, 2014 03:02 PM UTC by Richard Hughes
*Last Updated:* Tue May 27, 2014 03:02 PM UTC
*Owner:* nobody

Please consider writing and installing an AppData file with the application
description and some screenshots, else Pybliographic Bibliography Manager
looks really bad in the GNOME and KDE Software Centers. We'd love to
showcase more applications, but without the extra data file we can't. See
http://people.freedesktop.org/~hughsient/appdata/ for details; thanks!

Richard
------------------------------

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/pybliographer/feature-requests/33/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[pyblio-devel] python-bibtex-1.2.7 is out

[Zoltan K. <zo...@gm...>]

Dear All,

python-bibtex-1.2.7 is released. It contains bugfixes and code cleanup.
Please, install, test it and report if you meet any problem. :-) Thanks!

Zoltan

Re: [pyblio-devel] python-bibtex 1.2.7

[Germán Póo-C. <gp...@gn...>]

On Fri, 2014-03-21 at 13:35 +0100, Zoltan Kota wrote:
> Hi All,
> 
> I am about to release python-bibtex 1.2.7, which contains only fixes and
> cleanups thanks to Frederic.

Sounds good.

In the meantime, I cleaned up the build system in the gtk3 branch. With
minor changes, they could be also applied to master.

Basically, I fixed 'make distcheck' to make it work, and fixes some
issues I found when installing pybliographer in non-standard
directories, and running from the source code without installing it any
place beforehand.

I noticed that some locales settings are hard coded, but for developing
that is not a big deal (not for me at least :-)

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] Reg. GSoC 2014

[Digvijay S. <ssr...@gm...>]

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/
>

[pyblio-devel] python-bibtex 1.2.7

[Zoltan K. <zo...@gm...>]

Hi All,

I am about to release python-bibtex 1.2.7, which contains only fixes and
cleanups thanks to Frederic.

Zoltan

Re: [pyblio-devel] Reg. GSoC 2014

[Germán Póo-C. <gp...@gn...>]

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/

Re: [pyblio-devel] Reg. GSoC 2014

[Digvijay S. <ssr...@gm...>]

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/
>

[pyblio-devel] GSoC and OPW

[Germán Póo-C. <gp...@gn...>]

Hi,

I am sorry this is a kind of late notice for the mailing list.

Close to the deadline to submit ideas for GSoC project, I added one for
Pybliographer, as you may already noticed.

The description is short [1]:

-----------------------------
Pybliographer Finish the port of to GTK+3 and other improvements
(mentor: Germán Poo-Caamaño) 

Requirements: Knowledge of Python, familiarity with Gtk. (knowledge of
unit tests is a plus)

Notes: The UI porting is mostly done, but it is necessary to add unit
tests to check regressions before making them final. Once the porting is
done, it will require to make the application follow the UI guidelines
for GNOME 3 applications. Other improvements involve making the UI
simpler, integration via dbus with other editors or word processors like
Gedit or LibreOffice (to add references in documents). See related
bugs. 
-----------------------------

However, this is just a starting point.

FWIW, I could also become a mentor for Evince. So, having a co-mentor
here would be great considering the usual restrictions.

[1] https://wiki.gnome.org/Outreach/SummerOfCode/2014/Ideas

-- 
Germán Poo-Caamaño
http://calcifer.org/

Re: [pyblio-devel] Reg. GSoC 2014

[Germán Póo-C. <gp...@gn...>]

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/

Re: [pyblio-devel] Reg. GSoC 2014

[Germán Póo-C. <gp...@gn...>]

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/