Here's where we're at in the release:
3. Frost. √ Experimental Branch is forked √ Mainline Branch focuses on stabilization √ Only production-ready code committed to Mainline √ Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' √ Start an About Screen contest √ General Bug Hunt: 1500 points √ Post additional inkscape-0.91-pre*.tar.gz releases √ Packagers test creating pkgs of the -pre* releases
Last time I checked make distcheck there were just a handful of warnings. I haven't checked recently but suspect we're at 90% now.
How are we doing on the release notes? When I checked a couple months ago they were looking quite good so assume we're past 90% there too?
For the OSX packaging I have a huge amount of notes about many things that we need to do, but essentially it sounded like we're going to postpone any major work until next release, and just use the existing X11-based scripts. su_v has pointed me at a branch with some osx stuff that needs reviewed/landed, but otherwise is there any other major OSX packaging or porting work I need to be aware of?
For Windows packaging, I don't really have much in the way of notes. Sounds like the current scripts mostly just work, and modulo a few platform-specific bugs we should be good to go. There was work being done on a Win32 Installer using the WIX toolset but this sounds still in progress and not something we need to worry about for this release. Correct me if I'm wrong?
Looking forward... Once the above stuff is settled we'll be entering Freeze. This is both a Feature Freeze and String Freeze. I'll post more details when we get there, but to answer what I think will be a common question - bug fixes can still be landed freely, it's just that feature work and anything that changes user visible (translatable) strings will need release manager approval (i.e. me or Josh). I don't think anyone is planning work of this type so this should be a non-issue.
Probably the next question is how long until Freeze is done? I think we need to keep it going at least 30 days, to give ample time to translators. But most of the tasks for this phase are straightforward and I think we won't need much more than 30 days.
After that comes Hard Freeze, where we tend to whatever release blocking critical bugs remain (hopefully none by now!) and finalizing everything for the official release. Maybe we'll have 0.91 out the door by Thanksgiving.
Bryce
On 2014-10-14 08:45 , Bryce Harrington wrote:
For the OSX packaging I have a huge amount of notes about many things that we need to do, but essentially it sounded like we're going to postpone any major work until next release, and just use the existing X11-based scripts.
"the existing X11-based scripts" have been broken and out-of-date since a couple of years. Without changes there won't be any official OS X packages for 0.91 (neither X11- nor Quartz-based).
su_v has pointed me at a branch with some osx stuff that needs reviewed/landed, but otherwise is there any other major OSX packaging or porting work I need to be aware of?
There are two active branches for OS X packaging at launchpad, but only one is ready for merge:
1) osx-packaging-update https://code.launchpad.net/~inkscape.dev/inkscape/osx-packaging-update https://code.launchpad.net/~inkscape.dev/inkscape/osx-packaging-update/+merg...
- fixes currently broken packaging for OS X (with GTK+/X11 backend) - addresses a couple of known issues with older packages - ready for review (merge proposed)
2) osxmenu https://code.launchpad.net/~suv-lp/inkscape/osxmenu
- enhances current OS X port and packaging to use native GTK+ backend and provides basic OS integration (global menu, keyboard shortcuts, proxy icon) - aims for feature-complete package (includes helper applications & python modules for extensions which are not provided by the OS) - does not address backend-specific issues (delayed canvas redraw, responsiveness, clipboard exchange, SVG font editor, ...) - will need refactoring once 'osx-packaging-update' has landed in trunk - experimental (needs code review & fixing for changes in 'src') - not ready for merge at this point (for 0.91)
See also: http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X
@Liam - anything missing?
You're right Josh,
So once again, but now in the right thread: who's going to decide on the unit-related issues?
Diederik
On Tue, Oct 14, 2014 at 8:45 AM, Bryce Harrington <bryce@...961...
wrote:
Here's where we're at in the release:
- Frost. √ Experimental Branch is forked √ Mainline Branch focuses on stabilization √ Only production-ready code committed to Mainline √ Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' √ Start an About Screen contest √ General Bug Hunt: 1500 points √ Post additional inkscape-0.91-pre*.tar.gz releases √ Packagers test creating pkgs of the -pre* releases
Last time I checked make distcheck there were just a handful of warnings. I haven't checked recently but suspect we're at 90% now.
How are we doing on the release notes? When I checked a couple months ago they were looking quite good so assume we're past 90% there too?
For the OSX packaging I have a huge amount of notes about many things that we need to do, but essentially it sounded like we're going to postpone any major work until next release, and just use the existing X11-based scripts. su_v has pointed me at a branch with some osx stuff that needs reviewed/landed, but otherwise is there any other major OSX packaging or porting work I need to be aware of?
For Windows packaging, I don't really have much in the way of notes. Sounds like the current scripts mostly just work, and modulo a few platform-specific bugs we should be good to go. There was work being done on a Win32 Installer using the WIX toolset but this sounds still in progress and not something we need to worry about for this release. Correct me if I'm wrong?
Looking forward... Once the above stuff is settled we'll be entering Freeze. This is both a Feature Freeze and String Freeze. I'll post more details when we get there, but to answer what I think will be a common question - bug fixes can still be landed freely, it's just that feature work and anything that changes user visible (translatable) strings will need release manager approval (i.e. me or Josh). I don't think anyone is planning work of this type so this should be a non-issue.
Probably the next question is how long until Freeze is done? I think we need to keep it going at least 30 days, to give ample time to translators. But most of the tasks for this phase are straightforward and I think we won't need much more than 30 days.
After that comes Hard Freeze, where we tend to whatever release blocking critical bugs remain (hopefully none by now!) and finalizing everything for the official release. Maybe we'll have 0.91 out the door by Thanksgiving.
Bryce
Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, 2014-10-14 at 11:44 +0200, Diederik van Lierop wrote:
You're right Josh,
So once again, but now in the right thread: who's going to decide on the unit-related issues?
I would like to see 0.91 include the changes to move from 90 px per inch to 96 px per inch. It's been in experimental for some time. If units are used internally (as is now possible in Inkscape with text), there will be rendering discrepancies between Inkscape and Web Browsers.
The one issue I know about is that Guides and Grids are based on pixels values (even if document units are different). Guides and grids in files that use document units other than 'px' will be placed differently. This could be handled by checking inkscape version on input.
Are there any other issues?
If this move is deemed too risky for 0.91, then we should disable the ability to write out text with units other than in user units (px). (I really don't think using units other than user units is really useful.)
Tav
Diederik
On Tue, Oct 14, 2014 at 8:45 AM, Bryce Harrington <bryce@...961...> wrote: Here's where we're at in the release:
3. Frost. √ Experimental Branch is forked √ Mainline Branch focuses on stabilization √ Only production-ready code committed to Mainline √ Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' √ Start an About Screen contest √ General Bug Hunt: 1500 points √ Post additional inkscape-0.91-pre*.tar.gz releases √ Packagers test creating pkgs of the -pre* releases Last time I checked make distcheck there were just a handful of warnings. I haven't checked recently but suspect we're at 90% now. How are we doing on the release notes? When I checked a couple months ago they were looking quite good so assume we're past 90% there too? For the OSX packaging I have a huge amount of notes about many things that we need to do, but essentially it sounded like we're going to postpone any major work until next release, and just use the existing X11-based scripts. su_v has pointed me at a branch with some osx stuff that needs reviewed/landed, but otherwise is there any other major OSX packaging or porting work I need to be aware of? For Windows packaging, I don't really have much in the way of notes. Sounds like the current scripts mostly just work, and modulo a few platform-specific bugs we should be good to go. There was work being done on a Win32 Installer using the WIX toolset but this sounds still in progress and not something we need to worry about for this release. Correct me if I'm wrong? Looking forward... Once the above stuff is settled we'll be entering Freeze. This is both a Feature Freeze and String Freeze. I'll post more details when we get there, but to answer what I think will be a common question - bug fixes can still be landed freely, it's just that feature work and anything that changes user visible (translatable) strings will need release manager approval (i.e. me or Josh). I don't think anyone is planning work of this type so this should be a non-issue. Probably the next question is how long until Freeze is done? I think we need to keep it going at least 30 days, to give ample time to translators. But most of the tasks for this phase are straightforward and I think we won't need much more than 30 days. After that comes Hard Freeze, where we tend to whatever release blocking critical bugs remain (hopefully none by now!) and finalizing everything for the official release. Maybe we'll have 0.91 out the door by Thanksgiving. Bryce ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
Hello again. This happends in document units in mm and in px (from templates). I think is a unit conversion error related to 90->96 not to the units in use.
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:33:13 +0200
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I've just started to translate to Swedish (currently at 38%), one menu at a time. 30 days+ sounds good to me. For sure I must be "finished" before 1st of december (45 days (?)).
Hello again. Im silly!!! Sorry Tav. This behaviour is the espected behaviour because a old svg created using units diferent than pixels become smaller in his printing size at new 96DPI resolution.
For compensation to the noise, i made a simple extension to update the "printing" size of old SVG to match new resolution. Any one is invited to improve it, maybe strings not so good and also maybe could be good a reverse option.
extensions -> Document -> Legacy 90 to 96
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:33:13 +0200
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
Files without some unnecesary alerts
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Wed, 15 Oct 2014 11:31:01 +0200
Hello again. Im silly!!! Sorry Tav. This behaviour is the espected behaviour because a old svg created using units diferent than pixels become smaller in his printing size at new 96DPI resolution.
For compensation to the noise, i made a simple extension to update the "printing" size of old SVG to match new resolution. Any one is invited to improve it, maybe strings not so good and also maybe could be good a reverse option.
extensions -> Document -> Legacy 90 to 96
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:33:13 +0200
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
A update, now container layer become a group in root level, so user can easy ungroup it to make scales permanent and fit structure whith original SVG.
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Legacy 90 to 96 extension Fecha: Wed, 15 Oct 2014 11:43:07 +0200
Files without some unnecesary alerts
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Wed, 15 Oct 2014 11:31:01 +0200
Hello again. Im silly!!! Sorry Tav. This behaviour is the espected behaviour because a old svg created using units diferent than pixels become smaller in his printing size at new 96DPI resolution.
For compensation to the noise, i made a simple extension to update the "printing" size of old SVG to match new resolution. Any one is invited to improve it, maybe strings not so good and also maybe could be good a reverse option.
extensions -> Document -> Legacy 90 to 96
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:33:13 +0200
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Jabier,
Looks interesting. I'll give it a try.
Some quick questions:
Why don't you let the interpreter handle the scale factor (i.e instead of writing 1.066666666666666667, simply write 96.0/90.0)?
What happens if SVG root 'width' is defined with units (e.g. width='10in')?
It might be interesting to also update any guide lines and grids. (Since we are postponing the change from 90 to 96 px/inch to 0.92, I plan on working on a way to automatically update grids and guide lines.)
Tav
On Wed, 2014-10-15 at 11:58 +0200, Jabier Arraiza wrote:
A update, now container layer become a group in root level, so user can easy ungroup it to make scales permanent and fit structure whith original SVG.
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Legacy 90 to 96 extension Fecha: Wed, 15 Oct 2014 11:43:07 +0200
Files without some unnecesary alerts
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Wed, 15 Oct 2014 11:31:01 +0200
Hello again. Im silly!!! Sorry Tav. This behaviour is the espected behaviour because a old svg created using units diferent than pixels become smaller in his printing size at new 96DPI resolution.
For compensation to the noise, i made a simple extension to update the "printing" size of old SVG to match new resolution. Any one is invited to improve it, maybe strings not so good and also maybe could be good a reverse option.
extensions -> Document -> Legacy 90 to 96
Regards, Jabier.
-----Mensaje original----- De: Jabier Arraiza <jabier.arraiza@...2893...> Reply-to: jabier.arraiza@...2893... Para: Tavmjong Bah <tavmjong@...8...> Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:33:13 +0200
Hi, sorry for dont explain well and maybe still wrong but for sure... When we discuss this in the mailing list, in the document propieties there is 2 units combo boxes in document preferences: Document units and units. The first one is removed actualy and only have now the usual units -like in 0,48.5.
But a deeper look the problem are in all places you change from, for example from pixels to MM.
For example a box of 100px changed to "mm" in 0.48 give 28,222mm and in experimental 26,458mm
Regards, Jabier.
-----Mensaje original----- De: Tavmjong Bah <tavmjong@...8...> Para: jabier.arraiza@...2893... Cc: Diederik van Lierop <mail@...1689...>, inkscape-devel@...6... Asunto: Re: [Inkscape-devel] Release Status (Frost) Fecha: Tue, 14 Oct 2014 14:18:24 +0200
On Tue, 2014-10-14 at 13:49 +0200, Jabier Arraiza wrote:
Are there any other issues?
In page propieties a page of 96x96 pixels become at change to "mm": experimental : 25,40000 48.5 : 27,09
I am not sure what you mean by this... but it does remind me that changing "Default units" in the Page tab of the Document Properties page has problems. We should disable changing default units until all the bugs are worked out (probably post 0.91).
This is probably what Diederik was referring too. I was thinking about another issue.
Tav
Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
El mié, 15-10-2014 a las 12:08 +0200, Tavmjong Bah escribió:
Looks interesting. I'll give it a try.
Thanks!
Why don't you let the interpreter handle the scale factor (i.e instead of writing 1.066666666666666667, simply write 96.0/90.0)?
I do it in attached version, a good point
What happens if SVG root 'width' is defined with units (e.g. width='10in')?
Ok i think there is a bug here because now scale all units and this is bad, i update it in the next version to only update SVG root if no units (px)
It might be interesting to also update any guide lines and grids. (Since we are postponing the change from 90 to 96 px/inch to 0.92, I plan on working on a way to automatically update grids and guide lines.)
Done in this version
I have a dude, with, height, viewBox, guides and grid is updated only if no units in whith and height (px), is this correct?
Regards, Jabier.
On Tue, Oct 14, 2014 at 01:26:20PM +0200, Tavmjong Bah wrote:
On Tue, 2014-10-14 at 11:44 +0200, Diederik van Lierop wrote:
You're right Josh,
So once again, but now in the right thread: who's going to decide on the unit-related issues?
I would like to see 0.91 include the changes to move from 90 px per inch to 96 px per inch. It's been in experimental for some time. If units are used internally (as is now possible in Inkscape with text), there will be rendering discrepancies between Inkscape and Web Browsers.
The one issue I know about is that Guides and Grids are based on pixels values (even if document units are different). Guides and grids in files that use document units other than 'px' will be placed differently. This could be handled by checking inkscape version on input.
Are there any other issues?
If this move is deemed too risky for 0.91, then we should disable the ability to write out text with units other than in user units (px). (I really don't think using units other than user units is really useful.)
Let's go with this. Tell you what, let's put this at the top of the list for 0.92, and otherwise keep the todo list for 0.92 short so we can get to doing faster releases again. That way folks won't have to wait *too* long for the web browser discrepancy fix.
Time proves that last minute additions always end up being more issue-prone than expected, and can be a leading cause of release delay. Better safe than sorry.
Bryce
On Tue, 2014-10-14 at 19:44 -0700, Bryce Harrington wrote:
On Tue, Oct 14, 2014 at 01:26:20PM +0200, Tavmjong Bah wrote:
On Tue, 2014-10-14 at 11:44 +0200, Diederik van Lierop wrote:
You're right Josh,
So once again, but now in the right thread: who's going to decide on the unit-related issues?
I would like to see 0.91 include the changes to move from 90 px per inch to 96 px per inch. It's been in experimental for some time. If units are used internally (as is now possible in Inkscape with text), there will be rendering discrepancies between Inkscape and Web Browsers.
The one issue I know about is that Guides and Grids are based on pixels values (even if document units are different). Guides and grids in files that use document units other than 'px' will be placed differently. This could be handled by checking inkscape version on input.
Are there any other issues?
If this move is deemed too risky for 0.91, then we should disable the ability to write out text with units other than in user units (px). (I really don't think using units other than user units is really useful.)
Let's go with this. Tell you what, let's put this at the top of the list for 0.92, and otherwise keep the todo list for 0.92 short so we can get to doing faster releases again. That way folks won't have to wait *too* long for the web browser discrepancy fix.
Time proves that last minute additions always end up being more issue-prone than expected, and can be a leading cause of release delay. Better safe than sorry.
I am OK with this as long as we plan on getting 0.92 out the door quickly. This gives us some time to deal with guides and grids.
Tav
participants (6)
-
Bryce Harrington -
Christoffer Holmstedt -
Diederik van Lierop -
Jabier Arraiza -
su_v -
Tavmjong Bah