Re: memo

Dennis Tomas <[email protected]> Thu, 22 Mar 2018 21:04:45 +0100
Newsgroups gmane.comp.desktop.rox.user
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============6389500214796861465==
Content-Type: multipart/alternative;
 boundary="------------B912FC40DF0FEA28E4BF818B"
Content-Language: de-DE

This is a multi-part message in MIME format.
--------------B912FC40DF0FEA28E4BF818B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Am 22.03.2018 um 00:00 schrieb Will Godfrey:
> On Tue, 20 Mar 2018 11:36:51 +0100
> Liam Proven<[email protected]>  wrote:
>
>> On 19 March 2018 at 22:01, Will Godfrey<[email protected]>  wrote:
>>> Nobody? :(
>> No Eye Deer here, I'm afraid.
>>
>> On my to-do list here is to attempt to package ROX Desktop for
>> openSUSE and get a ROX-only version up and running. Aside from that,
>> though, I've barely looked at ROX in years, I'm afraid.
>>
>> I fear it may be nearing the end of the line. AIUI ROX is written in
>> Python, I'm guessing Python 2 -- and Python 2 has less than 2 years to
>> live now.
>>
>> https://pythonclock.org/
>>
>> After that, its only hope might be Tauthon, and that does not seem to
>> be achieving a lot of traction... :-( Most people I've spoken to have
>> not even heard of it.
>>
>> https://github.com/naftaliharris/tauthon
>>
> Well moving to Python 3 should be a major impediment. I've done that myself
> with some stuff. It's tedious rather than difficult.
Since porting to Python 3 would mean porting to the new PyGObject 
bindings (and thus GTK3) as well, there may be some issues to run into, 
depending on how much old/deprecated/missing API the application uses 
(haven't looked into Memo's code yet).
I made an effort of porting ROX-Lib2 and my panel applets some time ago, 
but there had been issues related to missing functionality, don't recall 
which exactly. I remember getting the bulk of the applet-related code to 
work, though.
Sadly, atm I don't have much time on my hands either, but I could dig 
out my incomplete ROX-Lib2 port and put it on GitHub as a starting point.

--------------B912FC40DF0FEA28E4BF818B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Am 22.03.2018 um 00:00 schrieb Will
      Godfrey:<br>
    </div>
    <blockquote type="cite" cite="mid:20180321230011.688b8978@debian">
      <pre wrap="">On Tue, 20 Mar 2018 11:36:51 +0100
Liam Proven <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">&lt;[email protected]&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">On 19 March 2018 at 22:01, Will Godfrey <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">&lt;[email protected]&gt;</a> wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">Nobody? :(  
</pre>
        </blockquote>
        <pre wrap="">No Eye Deer here, I'm afraid.

On my to-do list here is to attempt to package ROX Desktop for
openSUSE and get a ROX-only version up and running. Aside from that,
though, I've barely looked at ROX in years, I'm afraid.

I fear it may be nearing the end of the line. AIUI ROX is written in
Python, I'm guessing Python 2 -- and Python 2 has less than 2 years to
live now.

<a class="moz-txt-link-freetext" href="https://pythonclock.org/">https://pythonclock.org/</a>

After that, its only hope might be Tauthon, and that does not seem to
be achieving a lot of traction... :-( Most people I've spoken to have
not even heard of it.

<a class="moz-txt-link-freetext" href="https://github.com/naftaliharris/tauthon">https://github.com/naftaliharris/tauthon</a>

</pre>
      </blockquote>
      <pre wrap="">Well moving to Python 3 should be a major impediment. I've done that myself
with some stuff. It's tedious rather than difficult.
</pre>
    </blockquote>
    Since porting to Python 3 would mean porting to the new PyGObject
    bindings (and thus GTK3) as well, there may be some issues to run
    into, depending on how much old/deprecated/missing API the
    application uses (haven't looked into Memo's code yet).<br>
    I made an effort of porting ROX-Lib2 and my panel applets some time
    ago, but there had been issues related to missing functionality,
    don't recall which exactly. I remember getting the bulk of the
    applet-related code to work, though.<br>
    Sadly, atm I don't have much time on my hands either, but I could
    dig out my incomplete ROX-Lib2 port and put it on GitHub as a
    starting point.<br>
  </body>
</html>

--------------B912FC40DF0FEA28E4BF818B--


--===============6389500214796861465==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============6389500214796861465==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rox-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rox-users

--===============6389500214796861465==--