<div class="gmail_quote">On Thu, Sep 16, 2010 at 10:41 AM, Bernhard Reiter <span dir="ltr"><<a href="mailto:bernhard@intevation.de">bernhard@intevation.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Moin Igor,<br>
<br>
Am Mittwoch, 15. September 2010 23:58:38 schrieb Igor Novikov:<br>
<div class="im">'<br>
On Mon, Sep 13, 2010 at 12:41 PM, Bernhard Reiter<br>
<<a href="mailto:bernhard@intevation.de">bernhard@intevation.de</a>>wrote:<br>
<br>
</div><div class="im">> > Version: 0.6.17-16 works nicely for me on Debian Lenny.<br>
> ><br>
> > There were a couple of issues and Daniel Baumann, the former Debian<br>
> > packager seems to have fixed some of the in -17:<br>
> > <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=skencil;dist=unstable" target="_blank">http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=skencil;dist=unstable</a><br>
> > He also wrote the package it self would be in a good state,<br>
> > but I haven't tried in Squeeze myself.<br>
><br>
> It's not a problem solution. Patches from packagers are sometime<br>
> unsuccessful.<br>
> I have tested Skencil 0.6.17 under Ubuntu 10.04 and 10.10 It seems the<br>
> fixes are not suitable.<br>
<br>
</div>okay, can you say what the issues were?<br>
(Just curious, if it takes too much times, just skip it. As I cannot currently<br>
test it on those Ubuntu versions.)<br></blockquote><div><br>Major issue is menu rebuild problem. In 2008 there were changes in Tkinter<br>which broke backward compatibility. Package maintainer just surround a problem<br>
code by "try-except" to allow launching Skencil. As a result we have multiplied <br>menu items. I have fixed this issue in snapshot using direct tcl interpreter call.<br>Actually you can see these changes on the same screenshot:<br>
<br><a href="http://saveimg.ru/pictures/16-09-10/b9946b1a266990760a5fe4ab8c85723f.png" target="_blank">http://saveimg.ru/pictures/16-09-10/b9946b1a266990760a5fe4ab8c85723f.png</a><br><br>(problem code lines are commented) <br>
<br>Next issue is a correct canvas refresh while selection rectangle is drew. It's <br>looks like a buggy renderer but this issue also can be easy fixed.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> 2.Source code is separated from other files<br>
<br>
</div>A good goal in principle, do you have a list of specific changes<br>
you are proposing?<br>
<div class="im"><br></div></blockquote><div><br>1. Skencil/, Resources/, Script/ and Plugins/ are moved into src/ folder<br>2. Lib/ folder is eliminated and all native modules are relocated into Skencil/Modules/ folder<br>
3. Pixmaps/ is moved from Skencil/ into Resources/<br>4. Root "skencil" package is introduced<br>5. All native extensions source code is relocated in extensions/ folder<br><br>Also I have moved temporary old description files from root folder into old_files/ <br>
I have left only README file because it's required for distutils. The files should be<br>refactored because some of them are have no sense. For example BUGS is good for<br>small console utilities but not for large application. Known bugs should be in project<br>
bug tracker and there is no sense exposing incomplete bug list in BUGS file. And <br>the same for other files. I think Skencil project should has a more flexible <br>infrastructure on project web site to provide detailed info for users.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
> 3.Proposed source code structure allows launching Skencil using SVN copy<br>
<br>
</div>Directly? Isn't this possible already?<br></blockquote><div><br>Yes, it's possible now. Source code structure is equal to working application. On my computer <br>src/ folder is linked as a 'skencil' in $PYTHON_HOME/dist-packages/ and skencil start script is placed <br>
into /usr/bin That's all needed for running SVN copy. And of course compiled native extensions<br>are copied into src/Sketch/Modules/ By this way we have accelerated sK1 development skipping <br>application build after each code modification. <br>
<br>Also for comfortable development SVN copy has "*.pyc, *.so" ignore patterns. <br></div><br>Concerning ver.1.0 I would prefer maintaining release 0.6.18 and after that final ver.1.0 which will be<br>last in tk branch. Gtk port could be started as ver.1.1 <br>
<br>So, is proposed project structure suitable? If it's OK I will start committing. <br><br></div>-- <br>Regards,<br><br>Igor Novikov<br>sK1 Project<br><a href="http://sk1project.org" target="_blank">http://sk1project.org</a><br>
<br><br>