time for an infusion release?

[Justin Obara-3]

Yesterday I had the opportunity to speak with some developers who are using UI Options. They were quite happy with it for the most part, but did mention an issue they were having with line-height. While we do have a fix for this in our repo, we haven't made it available in a release yet.

About a month ago I posed the question of whether or not we should do a 1.4.1 maintenance release which included the line-height fix for UIEnhancer. Colin also thought that it might be good to include Antranig's jQuery related upgrades as well.

see: http://old.nabble.com/line-height-in-UIEnhancer%3A-%27em%27-vs-unitless-to33722373.html

I think we have a few options. We could do a maintenance release that includes both of these. We could do two separate maintenance releases, one for each fix. Another option would be to plan for a 1.5 release. Since the jQuery upgrades would likely trigger a full round of testing, adding this to a full release might save time.

My preference would be to do a quick maintenance release for the line-height fix and move the rest to a full 1.5 release. However, for a 1.5 release we'd need to determine both when it should come out and what exactly should be included.

Any thoughts?

Thanks
Justin


_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Jess Mitchell]

Would we have to do the same amount of testing for a quick maintenance release as a full release?

Jess


On May 25, 2012, at 9:15 AM, Justin Obara wrote:

> Yesterday I had the opportunity to speak with some developers who are using UI Options. They were quite happy with it for the most part, but did mention an issue they were having with line-height. While we do have a fix for this in our repo, we haven't made it available in a release yet.
>
> About a month ago I posed the question of whether or not we should do a 1.4.1 maintenance release which included the line-height fix for UIEnhancer. Colin also thought that it might be good to include Antranig's jQuery related upgrades as well.
>
> see: http://old.nabble.com/line-height-in-UIEnhancer%3A-%27em%27-vs-unitless-to33722373.html
>
> I think we have a few options. We could do a maintenance release that includes both of these. We could do two separate maintenance releases, one for each fix. Another option would be to plan for a 1.5 release. Since the jQuery upgrades would likely trigger a full round of testing, adding this to a full release might save time.
>
> My preference would be to do a quick maintenance release for the line-height fix and move the rest to a full 1.5 release. However, for a 1.5 release we'd need to determine both when it should come out and what exactly should be included.
>
> Any thoughts?
>
> Thanks
> Justin
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work@...
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Ann Arbor, MI USA (GMT - 5:00)
Senior Manager, Research & Development
jess@...
/ c / 919.599.5378
jabber: jessmitchell@...
skype: jesshmitchell
http://idrc.ocad.ca/
http://inclusivedesign.ca/
http://fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Justin Obara-3]

Hi Jess,

That would depend on what goes into it. If we just have the line-height fix or something else that is relatively isolated from the rest of the code base, then the testing can also be equally limited. However, if we were to jQuery or change any of the framework code, these will require a full retest, since they touch everything.

Thanks
Justin

On 2012-05-25, at 9:25 AM, Jess Mitchell wrote:

> Would we have to do the same amount of testing for a quick maintenance release as a full release?
>
> Jess
>
>
> On May 25, 2012, at 9:15 AM, Justin Obara wrote:
>
>> Yesterday I had the opportunity to speak with some developers who are using UI Options. They were quite happy with it for the most part, but did mention an issue they were having with line-height. While we do have a fix for this in our repo, we haven't made it available in a release yet.
>>
>> About a month ago I posed the question of whether or not we should do a 1.4.1 maintenance release which included the line-height fix for UIEnhancer. Colin also thought that it might be good to include Antranig's jQuery related upgrades as well.
>>
>> see: http://old.nabble.com/line-height-in-UIEnhancer%3A-%27em%27-vs-unitless-to33722373.html
>>
>> I think we have a few options. We could do a maintenance release that includes both of these. We could do two separate maintenance releases, one for each fix. Another option would be to plan for a 1.5 release. Since the jQuery upgrades would likely trigger a full round of testing, adding this to a full release might save time.
>>
>> My preference would be to do a quick maintenance release for the line-height fix and move the rest to a full 1.5 release. However, for a 1.5 release we'd need to determine both when it should come out and what exactly should be included.
>>
>> Any thoughts?
>>
>> Thanks
>> Justin
>>
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work@...
>> To unsubscribe, change settings or access archives,
>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
> ~~~~~~~~~~~~~~~~~~~~~~
> Jess Mitchell
> Ann Arbor, MI USA (GMT - 5:00)
> Senior Manager, Research & Development
> jess@...
> / c / 919.599.5378
> jabber: jessmitchell@...
> skype: jesshmitchell
> http://idrc.ocad.ca/
> http://inclusivedesign.ca/
> http://fluidproject.org
> ~~~~~~~~~~~~~~~~~~~~~~
>

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Johnny Taylor]

Justin,

Might you  detail the line-height issue? I'm curious. But only when you can. Thanks.

Johnny

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Justin Obara-3]

Hi Johnny,

In a nutshell we had be setting the line height on the body element with an "em" value when we shouldn't have been using a value at all. This was causing large fonts to have too little line-spacing. An implementer would then need to set the line-height directly, which would in turn break that element from working with UIO.

Full detail can be seen in jira.

http://issues.fluidproject.org/browse/FLUID-4703

Thanks

Justin

On 2012-05-25, at 10:32 AM, Johnny Taylor wrote:

Justin,

Might you  detail the line-height issue? I'm curious. But only when you can. Thanks.

Johnny

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Johnny Taylor]

Justin,

Interesting stuff. Thanks. I couldn't remember how I set my blog up <http://abledaccess> and seeing how I had and issue using rem before <http://abledaccess.com/blog/issue-using-rem/> I was curious how this all played out. And I found some curious behaviour.

 I set all my font settings via the html element. Given my issues using rem I thought I'd better try some stuff (to insure everything still functions properly) just to see what happens. Now by no means am I finished but 2 interesting things so far;

1. You can't exceed or declare any less than a 100% font-size, when setting font-size in your style sheet, on the body element? Which is most likely documented somewhere, but I don't recall reading it anywhere, not that I've read much on UIO before this. Not that this behaviour is necessarily undesirable but you are free to do whatever you want on the html element (up to, and including, 260%, it seemed silly to exceed that). And what is most interesting is everything still works (testing still pending).

2. And I use Georgia as my base font. And I noticed this before, when I switch to "Times New Roman" nothing happens. I figured it might be a result of my using the html element for all the font goodness, but no deal. Is this supposed to happen? Does "Times New Roman" have to match exactly for it to work? Or should any Times font suffice? Before I crack off I should really check if I even have "Times New Roman" installed on my machine. Oops, too late.

That's it, for now.

Johnny

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Justin Obara-3]

Hi Johnny,

I don't know all the details of the implementation of UIO at this point. So someone else may be better to answer, but I'll give the first pass a shot.

First off, which version of Infusion are you using; 1.4 or some pre-release version straight from the git repo? As for the font not changing, that's somewhat expected. UIO will actually pick from a selection of fonts, depending on what's available on your system. The default will be to use Georgia for Times New Roman.

https://github.com/fluid-project/infusion/blob/master/src/webapp/framework/fss/css/fss-text.css#L106

Hope that clears things up a bit. I really appreciate that you continue to experiment with and surface issue for UIO. It's really helpful.

Thanks

Justin

On 2012-05-25, at 3:23 PM, Johnny Taylor wrote:

Justin,

Interesting stuff. Thanks. I couldn't remember how I set my blog up <http://abledaccess> and seeing how I had and issue using rem before <http://abledaccess.com/blog/issue-using-rem/> I was curious how this all played out. And I found some curious behaviour.

 I set all my font settings via the html element. Given my issues using rem I thought I'd better try some stuff (to insure everything still functions properly) just to see what happens. Now by no means am I finished but 2 interesting things so far;

1. You can't exceed or declare any less than a 100% font-size, when setting font-size in your style sheet, on the body element? Which is most likely documented somewhere, but I don't recall reading it anywhere, not that I've read much on UIO before this. Not that this behaviour is necessarily undesirable but you are free to do whatever you want on the html element (up to, and including, 260%, it seemed silly to exceed that). And what is most interesting is everything still works (testing still pending).

2. And I use Georgia as my base font. And I noticed this before, when I switch to "Times New Roman" nothing happens. I figured it might be a result of my using the html element for all the font goodness, but no deal. Is this supposed to happen? Does "Times New Roman" have to match exactly for it to work? Or should any Times font suffice? Before I crack off I should really check if I even have "Times New Roman" installed on my machine. Oops, too late.

That's it, for now.

Johnny

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

[Johnny Taylor]

Justin,

Sorry this has taken so long. My week was pretty full of other sorts a fun. But I'm pretty sure my version of Infusion is 1.4. I was mistaken, that's the instance Colin custom built me, not the Studio's one. Not that it matters. Thanks for the link. It did help get my head around it. 

No problem. It's really quite fun. And figuring this stuff out helps me better understand how things are working and, in turn, insure such solutions are running efficiently.

Johnny

On 2012-05-28, at 12:30 PM, Justin Obara wrote:

Hi Johnny,

I don't know all the details of the implementation of UIO at this point. So someone else may be better to answer, but I'll give the first pass a shot.

First off, which version of Infusion are you using; 1.4 or some pre-release version straight from the git repo? As for the font not changing, that's somewhat expected. UIO will actually pick from a selection of fonts, depending on what's available on your system. The default will be to use Georgia for Times New Roman.

https://github.com/fluid-project/infusion/blob/master/src/webapp/framework/fss/css/fss-text.css#L106

Hope that clears things up a bit. I really appreciate that you continue to experiment with and surface issue for UIO. It's really helpful.

Thanks

Justin

On 2012-05-25, at 3:23 PM, Johnny Taylor wrote:

Justin,

Interesting stuff. Thanks. I couldn't remember how I set my blog up <http://abledaccess> and seeing how I had and issue using rem before <http://abledaccess.com/blog/issue-using-rem/> I was curious how this all played out. And I found some curious behaviour.

 I set all my font settings via the html element. Given my issues using rem I thought I'd better try some stuff (to insure everything still functions properly) just to see what happens. Now by no means am I finished but 2 interesting things so far;

1. You can't exceed or declare any less than a 100% font-size, when setting font-size in your style sheet, on the body element? Which is most likely documented somewhere, but I don't recall reading it anywhere, not that I've read much on UIO before this. Not that this behaviour is necessarily undesirable but you are free to do whatever you want on the html element (up to, and including, 260%, it seemed silly to exceed that). And what is most interesting is everything still works (testing still pending).

2. And I use Georgia as my base font. And I noticed this before, when I switch to "Times New Roman" nothing happens. I figured it might be a result of my using the html element for all the font goodness, but no deal. Is this supposed to happen? Does "Times New Roman" have to match exactly for it to work? Or should any Times font suffice? Before I crack off I should really check if I even have "Times New Roman" installed on my machine. Oops, too late.

That's it, for now.

Johnny

_______________________________________________________
fluid-work mailing list - fluid-work@...
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work