Hello,
I've made tarballs of the 0.48.2 release of Inkscape. Please, as per usual don't announce these generally until packages have a chance to make binary packages for users.
I'd really like to thank those that worked on backporting all of the patches, it's tireless and unforgiving work. But I'm sure this will delight a bunch of people.
https://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/
== MD5 Sums ==
f60b98013bd1121b2cc301f3485076ba inkscape-0.48.2.tar.bz2 889dcffb2fc72ea8522ca4bed95427e1 inkscape-0.48.2.tar.gz 7cbac56025f9cbabc3b765b2ce4f1610 inkscape-0.48.2.zip
== SHA1 Sums ==
be30ab2d2714d04ddd69b400bd6ad30b09e83067 inkscape-0.48.2.tar.bz2 422a4bacd4dc42adafa203244bc9816783cba4d3 inkscape-0.48.2.tar.gz 356d770d853bd96299d2c8d5f3f3d4949fac2a58 inkscape-0.48.2.zip
--Ted
Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have)
Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)
Note: A must for 0.48.3 will be functioning tablet support on Windows (which if someone finds a magic version of GTK that works in the near future, we can just repackage 0.48.2 for windows).
Cheers, Josh
On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote:
Hello,
I've made tarballs of the 0.48.2 release of Inkscape. Please, as per usual don't announce these generally until packages have a chance to make binary packages for users.
I'd really like to thank those that worked on backporting all of the patches, it's tireless and unforgiving work. But I'm sure this will delight a bunch of people.
https://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/
== MD5 Sums ==
f60b98013bd1121b2cc301f3485076ba inkscape-0.48.2.tar.bz2 889dcffb2fc72ea8522ca4bed95427e1 inkscape-0.48.2.tar.gz 7cbac56025f9cbabc3b765b2ce4f1610 inkscape-0.48.2.zip
== SHA1 Sums ==
be30ab2d2714d04ddd69b400bd6ad30b09e83067 inkscape-0.48.2.tar.bz2 422a4bacd4dc42adafa203244bc9816783cba4d3 inkscape-0.48.2.tar.gz 356d770d853bd96299d2c8d5f3f3d4949fac2a58 inkscape-0.48.2.zip
--Ted
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Great news! Thanks to everyone for their hard work. I have notified Wolfi, the Debian package maintainer: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633150
I will also see if I can get the Ubuntu package upgraded. However, we are now past Debian import-freeze in the current release cycle, so it may be considered undesirable to upgrade to the latest upstream package version unless Debian does so first.
AV
On 8 July 2011 22:32, Josh Andler <scislac@...400...> wrote:
Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have)
Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)
Note: A must for 0.48.3 will be functioning tablet support on Windows (which if someone finds a magic version of GTK that works in the near future, we can just repackage 0.48.2 for windows).
Cheers, Josh
On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote:
Hello,
I've made tarballs of the 0.48.2 release of Inkscape. Please, as per usual don't announce these generally until packages have a chance to make binary packages for users.
I'd really like to thank those that worked on backporting all of the patches, it's tireless and unforgiving work. But I'm sure this will delight a bunch of people.
https://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/
== MD5 Sums ==
f60b98013bd1121b2cc301f3485076ba inkscape-0.48.2.tar.bz2 889dcffb2fc72ea8522ca4bed95427e1 inkscape-0.48.2.tar.gz 7cbac56025f9cbabc3b765b2ce4f1610 inkscape-0.48.2.zip
== SHA1 Sums ==
be30ab2d2714d04ddd69b400bd6ad30b09e83067 inkscape-0.48.2.tar.bz2 422a4bacd4dc42adafa203244bc9816783cba4d3 inkscape-0.48.2.tar.gz 356d770d853bd96299d2c8d5f3f3d4949fac2a58 inkscape-0.48.2.zip
--Ted
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote:
Hello,
I've made tarballs of the 0.48.2 release of Inkscape. Please, as per usual don't announce these generally until packages have a chance to make binary packages for users.
Great! Thanks Ted! This release seemed to go quickly and painless, am I right? This is good news, and makes it more fun to work on bug fixes for 'point-releases'.
We should mark 0.48.2 as released on Launchpad, and create a 0.48.3 milestone. I can't do it right now, and also don't know how to.
Thanks, Johan
On 11/7/11 09:37, jbc.engelen@...2592... wrote:
On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote:
I've made tarballs of the 0.48.2 release of Inkscape. Please, as per usual don't announce these generally until packages have a chance to make binary packages for users.
This release seemed to go quickly and painless, am I right? This is good news, and makes it more fun to work on bug fixes for 'point-releases'.
We should mark 0.48.2 as released on Launchpad,
Could we please wait with closing reports as 'Fix Released', milestoned to 0.48.2, until the binary packages Inkscape does provide for Windows and Mac OS X are done and available on sourceforge and the release has been officially announced on inkscape.org? Else I fear we'll have to explain repeatedly to puzzled reporters of and subscribers to bugs as well as other users why/what was when 'released' and 'where is the new version?'.
Maybe the release notes for 0.48.2 could be updated during this time? http://wiki.inkscape.org/wiki/index.php/Release_notes/0.48.2
and create a 0.48.3 milestone.
Agreed.
~suv
On 8-7-2011 23:32, Josh Andler wrote:
Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have)
Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)
Is there some issue troubling the packagers that we can perhaps assist with? I am anxiously waiting for the Windows binaries to pop-up on SourceForge, so I can tell all my friends and colleagues!
:-) Johan
On 20/7/11 22:33, Johan Engelen wrote:
On 8-7-2011 23:32, Josh Andler wrote:
Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have)
Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)
Is there some issue troubling the packagers that we can perhaps assist with? I am anxiously waiting for the Windows binaries to pop-up on SourceForge, so I can tell all my friends and colleagues!
:-)
UweSch is on vacation atm (IIRC back at the end of July). Last time I chatted with him before he left, he didn't know whether he'd be able to get online to download the sources, build and upload 0.48.2 while being away, but he'd try to if possible (no promises).
BTW [1] - any news on which devlibs version to use for the stable releases (0.48.x)? What about possibly branching the devlibs for stable releases of the Inkscape 0.48.x branch? [2]
~suv
[1] another UI regression reported earlier today in the German user forum, related to the GTK+ update (not yet in the tracker), apparently affects Windows XP as well as Windows 7: http://uploads.inkscape-forum.de/2011/07/Zwischenablage.jpg http://www.inkscape-forum.de/discussion/2660/bug-schwarzer-schmierfilm-beim-lineal-in-v-048/#Item_8
[2] http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/36656/focus=36677
2011/7/21 ~suv <suv-sf@...58...>:
BTW [1] - any news on which devlibs version to use for the stable releases (0.48.x)? What about possibly branching the devlibs for stable releases of the Inkscape 0.48.x branch? [2]
Revision 23 of devlibs should be OK. Revision 24 contains the experimental Cairo update, so it would be better not to ship that to users.
Regards, Krzysztof
Am 20.07.2011 22:33, schrieb Johan Engelen:
On 8-7-2011 23:32, Josh Andler wrote:
Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have)
Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)
Is there some issue troubling the packagers that we can perhaps assist with? I am anxiously waiting for the Windows binaries to pop-up on SourceForge, so I can tell all my friends and colleagues!
:-) Johan
10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks& Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I've some problems creating 0.48.2 for windows. I get a couple of error messages during building. First of all i can't get back to revision 23 of devlibs. Always bzr revno says R24 instead of R23. I did an "bzr revert -r 23" before. The next problem is building of buildtool.ccp with "g++ buildtool.cpp -O2 -g0 -mtune=prescott -o btool". The message is:
buildtool.cpp: In member function 'virtual buildtool::String buildtool::MakeBase ::getProperty(const buildtool::String&)': buildtool.cpp:3142:20: warning: converting 'false' to pointer type for argument 1 of 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, co nst _Alloc&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std ::allocator<char>]'
Krzysztof meant to use the one from the actual branch, but it didn't work too. #################################################### # BuildTool v0.9.9 #################################################### ######## PARSE : build.xml ============ cmd ============ bzr revno ============================= Make error line 0: error executing 'bzr revno': bzr: ERROR: Not a branch: "D:/_b azaar_svn/inkscape-0.48.2/".
Make error line 0: cannot open file 'c:\devlibs\lib\pkgconfig\gtkmm-2.4.pc' for reading Make error line 0: Cannot find package 'gtkmm-2.4'. Do you have it installed?
Can anyone help?
Sincerely, UweSch
2011/8/14 Uwe Schöler <mail@...2227...>:
I've some problems creating 0.48.2 for windows. I get a couple of error messages during building.
I just checked out 0.48.2 from Bazaar in my Windows XP VM, and I encounter no problems when building from a source checkout with TDM-GCC 4.4.1. It looks like the warning emitted when compiling btool is irrelevant (and I don't even get the warning).
I'm 90% sure the first error is caused by building from a tarball (you just need to create the required inkscape-version.cpp file manually), the second looks like a problem with permissions (maybe UAC is getting in the way?)
Regards, Krzysztof
Everything OKAY! I had problems with my paths... sorry. 0.48.2 is fine now. I'll upload it to SF
Sincerely, UweSch
Am 14.08.2011 23:49, schrieb Krzysztof Kosiński:
2011/8/14 Uwe Schöler<mail@...2227...>:
I've some problems creating 0.48.2 for windows. I get a couple of error messages during building.
I just checked out 0.48.2 from Bazaar in my Windows XP VM, and I encounter no problems when building from a source checkout with TDM-GCC 4.4.1. It looks like the warning emitted when compiling btool is irrelevant (and I don't even get the warning).
I'm 90% sure the first error is caused by building from a tarball (you just need to create the required inkscape-version.cpp file manually), the second looks like a problem with permissions (maybe UAC is getting in the way?)
Regards, Krzysztof
I do confirm the warning when building btool. But this is a warning only. the exe is created. I used the inkscape-0.48.2.zip and the version information file is there included. So the build runs without being a bzr repository.
FYI I use the mingw tdm gcc 4.5.2-tdm-1 from here http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/tdm-gcc-4....
Adib.
2011/8/14 Krzysztof Kosiński <tweenk.pl@...400...>:
2011/8/14 Uwe Schöler <mail@...2227...>:
I've some problems creating 0.48.2 for windows. I get a couple of error messages during building.
I just checked out 0.48.2 from Bazaar in my Windows XP VM, and I encounter no problems when building from a source checkout with TDM-GCC 4.4.1. It looks like the warning emitted when compiling btool is irrelevant (and I don't even get the warning).
I'm 90% sure the first error is caused by building from a tarball (you just need to create the required inkscape-version.cpp file manually), the second looks like a problem with permissions (maybe UAC is getting in the way?)
Regards, Krzysztof
FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage.
Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.
Cheers, Hannes
On 10/7/11 08:44, Hannes Hochreiner wrote:
recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage.
Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.
AFAIU this only affected on some linux distributions (0.48.1 with custom patches on Ubuntu and Debian), and after having been reported on irc and in debian's bug tracker, was addressed in:
Bug #602005 "permissions of script files wrong/missing shebang lines" https://bugs.launchpad.net/inkscape/+bug/602005
(see comment #11 et seq.)
~suv
On 10/07/11 09:10, ~suv wrote:
On 10/7/11 08:44, Hannes Hochreiner wrote:
recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage.
Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.
AFAIU this only affected on some linux distributions (0.48.1 with custom patches on Ubuntu and Debian), and after having been reported on irc and in debian's bug tracker, was addressed in:
Bug #602005 "permissions of script files wrong/missing shebang lines" https://bugs.launchpad.net/inkscape/+bug/602005
(see comment #11 et seq.)
~suv
Thanks for pointing out the bug report to me and especially for taking care of the issue.
Cheers, Hannes
Hi Hannes,
I patched the Ubuntu package (>= 0.48.1-2ubuntu5) to fix this problem. You can try installing this in another DEB based distribution. I don't foresee any problems as long as the distro has all the package dependencies available.
AV
On 10 July 2011 08:52, Hannes Hochreiner <hannes@...1905...> wrote:
On 10/07/11 09:10, ~suv wrote:
On 10/7/11 08:44, Hannes Hochreiner wrote:
recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage.
Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.
AFAIU this only affected on some linux distributions (0.48.1 with custom patches on Ubuntu and Debian), and after having been reported on irc and in debian's bug tracker, was addressed in:
Bug #602005 "permissions of script files wrong/missing shebang lines" https://bugs.launchpad.net/inkscape/+bug/602005
(see comment #11 et seq.)
~suv
Thanks for pointing out the bug report to me and especially for taking care of the issue.
Cheers, Hannes
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Excellent! I'll give it a try. Thanks a lot!
Cheers, Hannes
On 10/07/11 10:46, Alex Valavanis wrote:
Hi Hannes,
I patched the Ubuntu package (>= 0.48.1-2ubuntu5) to fix this problem. You can try installing this in another DEB based distribution. I don't foresee any problems as long as the distro has all the package dependencies available.
AV
On 10 July 2011 08:52, Hannes Hochreiner<hannes@...1905...> wrote:
On 10/07/11 09:10, ~suv wrote:
On 10/7/11 08:44, Hannes Hochreiner wrote:
recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage.
Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.
AFAIU this only affected on some linux distributions (0.48.1 with custom patches on Ubuntu and Debian), and after having been reported on irc and in debian's bug tracker, was addressed in:
Bug #602005 "permissions of script files wrong/missing shebang lines" https://bugs.launchpad.net/inkscape/+bug/602005
(see comment #11 et seq.)
~suv
Thanks for pointing out the bug report to me and especially for taking care of the issue.
Cheers, Hannes
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sun, Jul 10, 2011 at 1:46 AM, Alex Valavanis <valavanisalex@...400...> wrote:
Hi Hannes,
I patched the Ubuntu package (>= 0.48.1-2ubuntu5) to fix this problem. You can try installing this in another DEB based distribution. I don't foresee any problems as long as the distro has all the package dependencies available. ...
Hi Alex, For while the newest version I see available after updating through synaptic is 0.48.1-2ubuntu2. Does this fixed version need to be installed manually or will Ubuntu eventually pick up a newer version?
Thanks! , John
Hi John,
The new version of the inkscape package is available in Ubuntu Oneiric (the latest development version). Unfortunately, it is Ubuntu policy that only *major* issues get fixed in stable versions of Ubuntu (e.g. bugs that make the core functionality of packages completely unusable). The rationale for this is that it is better to support packages with a few well known minor bugs than it is to support poorly-understood/experimental patches. Because JessyInk is just an extension, it is unlikely that the fix will make it into Ubuntu Natty. The best bet is to manually download the latest package version and install it manually. If you need help with that, let me know.
Thanks,
Alex
On 10 July 2011 21:26, John Faith <jfaith7@...400...> wrote:
On Sun, Jul 10, 2011 at 1:46 AM, Alex Valavanis <valavanisalex@...400...> wrote:
Hi Hannes,
I patched the Ubuntu package (>= 0.48.1-2ubuntu5) to fix this problem. You can try installing this in another DEB based distribution. I don't foresee any problems as long as the distro has all the package dependencies available. ...
Hi Alex, For while the newest version I see available after updating through synaptic is 0.48.1-2ubuntu2. Does this fixed version need to be installed manually or will Ubuntu eventually pick up a newer version?
Thanks! , John
On Sun, Jul 10, 2011 at 3:45 PM, Alex Valavanis <valavanisalex@...400...> wrote:
Hi John,
The new version of the inkscape package is available in Ubuntu Oneiric (the latest development version). Unfortunately, it is Ubuntu policy that only *major* issues get fixed in stable versions of Ubuntu (e.g. bugs that make the core functionality of packages completely unusable). The rationale for this is that it is better to support packages with a few well known minor bugs than it is to support poorly-understood/experimental patches. Because JessyInk is just an extension, it is unlikely that the fix will make it into Ubuntu Natty.
...
Hi Alex, Thanks for the explanation. I guess brokenness is a matter of perspective and since I had just started learning JessyInk, it jumped out at me. I'll now stop waiting for natty to catch up! ;-)
Thanks, John
participants (12)
-
unknown＠example.com -
Alex Valavanis -
Hannes Hochreiner -
Johan Engelen -
John Faith -
Josh Andler -
Krzysztof Kosiński -
Nicolas Dufour -
Ted Gould -
the Adib -
Uwe Schöler -
~suv