I haven't found a way to use pixel size fonts. It is rather difficult to match guidelines that use pixels sizes by using point sizes...
If not currently possible, would it be possible to add it to next release?
Everything in Prototyper works in pixels, the fonts too. It's really hard to implement the point-pixel transformation in Prototyper and it's not currently planned to do. I'm afraid you'll have to wait for later updates than the next one. So sorry.
>Everything in Prototyper works in pixels
But a widgets font size property is specified in points according to the guide. They certainly aren't pixel units. If I use the HTML widget, I can enter text and use inline css to create the correct size but this is a headache.
Do you think there might be a workaround/is it possible to edit a templates CSS (not just default styles) for example?
Sorry Petteri, I was wrong, the font in Prototyper is in points, not in pixels. The only workaround I can think of is to translate your pixel sizes in points by multiplying it to 1.33 . They won't be exact though. We are planning the update for June (we'll launch one the last days of the current month) and we will make efforts to make the text as pixel-perfect as we can.
That's great to know - thanks for your reply Victor
Hello, is there any news from this update ?
I am currently reviewing your software for Orange.fr and it's an issue for us. The designers work with pixels and i can't see telling them to do calculation :-)
I understand, but is something related with the framework which Prototyper is made. To be honest we can do little about it.
Victor, that sucks ;)
It does indeed. We are monitoring the changes on the framework and as soon as they fix it we will try to add it.
"soon as they fix it we will try to add it"
That doesn't suck.... THAT'S GREAT!
can you explain why it is great ?
That JIM can ́t do anything about this problem. And if they could thery would implement this ar once. JIM's service is great.
But they had to do more research before they began using this framework;)
Ah okay ! I misunderstood, i thought "point are great" :-)
haha no POINTS SUCK ;)
We should have done more research before using Eclipse but we believed the people at IBM when they said that you can make rich client apps with their framework...
:) haha great answer Victor :) I would have done the samething!
Any update about this issue? It's one of the problems that stops me from totally dumping Photoshop.
Unfortunately this is not supported by Eclipse (the technology we are using to develop the tool). But we are investigating how to work it out so Justinmind can use pixels.
Unfortunately this won't be implemented any time soon but we will let you know when we know in which version this will be implemented.
Maybe you could find a way to support pt sizes with commas, like 11,5 etc? That would at least let create the consistent sizes with px from real websites.
This is a deal breaker for us, unfortunately. I'd even be willing to do the 1.33 calculation but, since I can only enter whole number point values, the calculation is meaningless. It's such a shame to have invested so much effort in other areas of the application and have it fall on its face over something so small. But, if I can't specify a desired font size to my dev team, the rest goes to waste.
But, everything else about the application is head and shoulders above what's available. Keep up the great work and I hope to be able to use JIM in the future!!
+1 for this feature!
+1 for this feature. Very confusing that a prototyping tool for the web is using points to determine font sizes, especially when rulers and other dimensions in JIM are pixels. I can't recommend this tool over Axure with such a fundamental flaw.
"Unfortunately this won't be implemented any time soon"
Then I can't make a recommendation to buy JIM licenses for my group. Very, very bummed. Back to Axure.
We are happy to inform that this feature has been implemented in Justinmind v6.4.1.
Now you could easiy add a way to change pt size to px size in preferences.
Most designers would prefer px sizes.
Pt are easily calculated to px, so you could do this directly, instead of users looking to PT-PX conversions table.
I have version 6.9.1 but I cannot change to px in the preferences.
Could you please let me know how to do it?
Also, I have problem with "opensans" font, which I uploaded. The problem is when I want to use "semibold", it decrease the font size automatically, and I can't change anything. What should I do?
There isn't any possibility to change px. The feature that was implemented into v6.4.1 was the possibility to introduce a calculation with points (ex. 1.33).
thanks, is there any plan to add this feature to the future versions?
I will transfer your request to our development team.
Why would a web development prototyper put fonts in pts at all???
I can't find any options to set the fonts to a calculation of any kind.
There is a specific and technical reason why they were implemented in pts instead of pixels. Sorry for any inconvenience,
there isn't any calculation setting at the properties tab (fonts).
Any update on this? To get 16px in my browser I set my font size to 12pt, would be great to have 1:1 relationship between those to, less brain power and guessing to get it right. Thanks!
Still remains the deal killer for us. Such an easy temporary fit to put a calculation on your end rather than asking users to do it. I was shocked to see this still open.
Unfortunately it won't be possible to see the font size in pixels at the properties tab yet, however on our next update the conversion from pts to pxls will be available at the CSS tab.
Actually it's not only a headache it's a deal-breaker for me... :/ As I see there is also a lack of many other css txt properties, commonly used in web design, eg. font size - choice between px, percent, rem value, spacing (tracking / kerning) - you might add some basic properties to the project (in case of rem, em initial size, so other sizes could be calculated from that size and for RWD design (which should be a standard) it would be a killer ( no more need for few versions of "the same" prototype ;) );
But....as this subject was started like 6 years ago I kind of doubt you will really take care of that... maybe from a technical point of view it's not a deal and is a kind of a problem (however doesn't seem to be), but from a design point of view it's really important thing which can cost you loosing users...
Pts and pixels are apple and oranges...and since Justinmind is for prototyping for devices, why did you guys go with pts in the first place? Don't make sense at all...
This is something our development team is investigating and trying to solve since a long time ago. Working with pixels instead of points it's a quite complicated development because the fonts are used differently between devices and OS. Meanwhile, since our last update, you will be able to visualize the equivalence in pixels through the CSS palette. See the screenshot attached.
I hope this helps.
Comments have been locked on this page!