After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 138714 - Py-Slice should use file chooser for "Path to export HTML to"
Py-Slice should use file chooser for "Path to export HTML to"
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Gimp-Python
git master
Other All
: Normal enhancement
: 2.4
Assigned To: Manish Singh
GIMP Bugs
: 138827 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-01 04:38 UTC by Joao S. O. Bueno
Modified: 2006-07-20 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch fixing all three bugs (2.11 KB, patch)
2004-04-01 04:41 UTC, Joao S. O. Bueno
committed Details | Review

Description Joao S. O. Bueno 2004-04-01 04:38:17 UTC
Py-slice...the motive why a web developer doesn  need gimp-perl and 
could go with gimp-python instead. 
 
Can not,as of gimp 2.0.0:  
   - Work if there are only horizontal or only vertical guides, but just 
with both. This is just becasue of a misplaced "and" in the beggining of 
the plug-in 
 
   - Correctly save images to a different directory of the one of the 
base HTML file: 
	 Images relative paths doesn't apear in src attributes of 
img tags in generated html/ 
 
   - (enhancement) - "Path to export HTML to" should be a PF-FILE entry, not a  
PF-String. I've Addressed this, taking care to pick the directory only part of 
choosen path. 
 
I will atach a patch addressing all 3 bugs. I think they can go straight into 
2.0.1
Comment 1 Joao S. O. Bueno 2004-04-01 04:41:37 UTC
Created attachment 26189 [details] [review]
Patch fixing all three bugs
Comment 2 Manish Singh 2004-04-02 07:07:35 UTC
I'll commit a somewhat tweaked version of this after some testing.
Comment 3 Manish Singh 2004-04-02 07:10:47 UTC
*** Bug 138827 has been marked as a duplicate of this bug. ***
Comment 4 Sven Neumann 2004-04-10 10:22:23 UTC
Yosh, will you commit your changes or would you like to wait till 2.0.1 is out?
Comment 5 Manish Singh 2004-04-10 18:53:13 UTC
I'd like to get it in for 2.0.1, but I won't get a chance till 4-5 hours from now.
Comment 6 Sven Neumann 2004-04-10 19:05:03 UTC
I will wait as long as it takes then.
Comment 7 Manish Singh 2004-04-11 17:00:54 UTC
2004-04-11  Manish Singh  <yosh@gimp.org>
                                                                                
        * plug-ins/pygimp/plug-ins/py-slice.py: When using a separate dir for
        images, actually prepend the dir to the img srcs in the html. Allow
        only horizontal or vertical guides in an image, do not require both.
        A bit smarter path handling. Addresses most of bug #138714.
Comment 8 Manish Singh 2004-04-11 17:01:39 UTC
I didn't do the PF_FILE change because pygimp's filesel stuff is a little wonky
right now. Will address after 2.0.1.
Comment 9 Sven Neumann 2004-05-24 13:16:46 UTC
Yosh, did you get around to look at this in the meantime?
Comment 10 Manish Singh 2004-05-24 17:25:14 UTC
I think this should be part of the larger pygimp changes that will go in 2.2.
Comment 11 Sven Neumann 2004-10-04 09:14:03 UTC
Will the larger pygimp changes be ready in time for 2.2?
Comment 12 Joao S. O. Bueno 2004-10-04 12:50:58 UTC
Yosh, I've browsed through the code, and now I can imagine what are these 
"larger pygimp changes". Widget diversification and layout, and 
internationalization come to mind. I am willing to help. That means, I can 
implement something as of now - I just would like to know what you have 
thought about these issues. Maybe we should open a tracker bug for pygimp and 
work there? 
 
Sven - looking at the code, I'd say it can be done in time for 2.2, but not in 
time for the proposed string-freeze. Once i18n is not in place in pygimp as of 
now, even if Pygimp is not coming into a separate tree, I think this should no 
t block the string freeze. Anyway, it should go into a separate translation 
module. 
Comment 13 Sven Neumann 2004-10-04 13:05:21 UTC
The best thing to do here is to move pygimp into a separate module. It can be
released independently then and we don't need to wait for pygimp with the 2.2
release.
Comment 14 Sven Neumann 2004-10-24 20:40:56 UTC
Yosh, are you still planning to do any major changes to pygimp before 2.2?
Otherwise I'd suggest to just ship 2.2 with the current state of pygimp and move
this bug report to the Future milestone.
Comment 15 Manish Singh 2004-10-24 20:46:07 UTC
Bumping it. No time for pre-2.2 for this.
Comment 16 Michael Schumacher 2005-07-07 16:23:07 UTC
Does the version attached to bug 159564 address this as well?
Comment 17 Joao S. O. Bueno 2005-07-09 21:12:00 UTC
I incorrectly listed 3 issues when reporting this bug.  
Two of then are corrected, and the only thing remaining is that the "Path to 
export HTML to" is a string when it would be correct if it were 
a file widget. 
 
Yosh preferred to let it this way because the PF_FILE widget is not a nice 
file selector (see comment #8), and I am using it just how it was left over. 
 
However, I consider that displaying a string widget when the input should be a 
filesystem object is a bug - it just depends on another bug: fixing the 
Python-fu file selector widget, as in #8. 
Comment 18 Michael Schumacher 2005-07-10 00:38:08 UTC
Could you please update the summary to something useful then? :) 
Maybe it could be a good idea to close this bug and open a new one for just the
PF_FILE issue (with a dependency on the PF_FILE enhancement request) pyslice
has, this one is rather confusing and mostly obsolete already.
Comment 19 Michael Schumacher 2005-07-11 17:27:25 UTC
This is an enhancement request now that the bug parts are fixed, and I've
updated the summary to something useful :)
Comment 20 Manish Singh 2006-07-20 07:56:03 UTC
2006-07-20  Manish Singh  <yosh@gimp.org>

        * plug-ins/pygimp/plug-ins/py-slice.py: use PF_DIRNAME for save_path.
        Fixes bug #138714.