Jump to content

Manfred62

Members
  • Posts

    326
  • Joined

  • Last visited

Everything posted by Manfred62

  1. I agree. Why not simply stay with Arial, Helvetica? Maybe we should do a poll? What's more important? good performance and cross browser/OS compatibility nice (visual) typography
  2. I'm always building a static site at first, means only html and css etc. For example creating a start-page, a profile page and so on (depends on what the project needs). After that I'm stripping down the html and bake them all into PW. BTW: there are 2 simple grids..? http://simplegrid.info/ http://thisisdallas.github.io/Simple-Grid/
  3. I tried something in a test-site to get better (sharper) google-web-fonts in Chrome on Windows: -webkit-text-stroke: 0.3px; here you can play with the value. I only placed this for my headings (where web-fonts are used). Got nice results. Not sure about the performance when used for all. Screenshots (with Montserrat font), second is without text-stroke:
  4. Hi Pete, on the english version the slideshow has 3 slides (1 image missing/blank). The german and danish only have 2.
  5. The forum here uses IP.Board (look at the right bottom of the page). A simple module for PW is Discussions.
  6. maybe you can use the Blog Profile as a starting point?
  7. hi Ryan tested the 2.3.7 version. In my eyes it looks nice on Win 7 in FX and Chrome. With FX it looks a little bit sharper. Also the font-size is good (not too small). The dropdown translation is fixed too. Translation questions: what about making the ProcessLanguageTranslator module translatable (the text on top and the save button)? under access/user the column titles? under access/user/username the Roles section is not translated?
  8. hi Radek looks nice, but the dropdowns are 'hanging', when leaving with the mouse? See screenshot.
  9. Nice written. Like it!! BTW: check the link in the article (one s missing). http://neuwaerts.de/emerge/articles/2013/proceswire-module/
  10. Hi obiuno, welcome to PW. Take a look at this thread. At the end you find a empty language pack to start with. Maybe it's not complete. In the dev version of PW I have 94? language files. Ask, if you need more assistance.
  11. @Soma: where is this string? EDIT: found and done (prepared locally) I have some more translations prepared for the 2.4 version (on my local 2.3.6 installation), but will wait with pull-request until Ryan is ready.
  12. yes, a lot of time spent to try other fonts... Wouldn't it be easier to stay with 'Arial, Helvetica, sans-serif'? Another point (already mentioned earlier). In the setup menu dropdowns the translation isn't available. Only 'languages' is translated.
  13. I agree. But maybe Ryan could give Fira a try? Looks nice on all browsers and was already mentioned in this thread. If Fira is no option, we should stay with 'Arial, Helvetica, sans-serif' as a safe solution.
  14. the difference is minimal on Win 7, 64bit. First is Firefox, second is Chrome (both actual versions). Safari 5.1.7 on Win 7 looks the same like Chrome.
  15. same experience in TinyMCE. When I change the skin (to e.g. bootstrap), it's misaligned. After deactivating box-sizing: border-box; it's ok again. See screenshots maybe we have to exclude some parts with border-box: content-box; ? EDIT: if you want to use a skin like bootstrap for TinyMCE in PW dev version, add following code to the reset part in the ui.css (begins at line 5) \wire\modules\Inputfield\InputfieldTinyMCE\tinymce-3.5.8\themes\advanced\skins\bootstrap\ui.css /*------- for buttons in toolbar -------*/ -webkit-box-sizing: content-box; -moz-box-sizing: content-box; box-sizing: content-box;
  16. Last week I had time and worked with PocketGrid. As example I took the same demo-page on which I tested Kube. At first I worked from desktop to mobile (like I did with Kube). Rebuilding the site with PocketGrid was fun and no problem. Next challenge: building it mobile-first with PocketGrid. Puuh, was hard at the beginning. You had to think completely different (css). Was my first real 'mobile-first' doing. But at the end I got it. Result: less clean html, removing one unnecessary breakpoint, clean css. On the other side: IE8 needs a extra css or some js (because mobile-first). In short words: PocketGrid is supercool... Also I like the clean logical html. All the responsive magic is done in the css. No need for cryptic classnames. <div class="navigation block-group">...</div> <!-- PocketGrid --> <div class="footer block">...</div> <div class="small-2 large-4 columns">...</div> <!-- Foundation --> <div class="col-xs-6 col-md-4">...</div> <!-- Bootstrap --> Using percent, em, px... whatever you like. PocketGrid is absolutely flexible.
  17. Sorry, no. Didn't tried it. I'm also waiting for update.
  18. there are some skins for TinyMCE: http://pixabay.com/de/blog/posts/a-modern-custom-theme-for-tinymce-4-40/ http://thebigreason.com/blog/2008/09/29/thebigreason-tinymce-skin https://github.com/gtraxx/tinymce-skin-bootstrap the new TinyMCE version 4.x already looks very nice: http://skin.tinymce.com/
  19. @Pete: maybe you can make this topic sticky in the modules section of the forum?
  20. not sure, but do you have a translation file for e.g. Google Analytics? If not, you should create one in the admin language translation section. Path is relative. Example: '/site/modules/ProcessGoogleAnalytics/ProcessGoogleAnalytics.module' Maybe then you see it in the menu.
  21. Already checked the new version. The message bars on top and the 'add new' in dropdowns are nice! The font-size in general is now smaller again (than in the previous version)? Not sure. The font size in the hover pop-ups is a little big? And this popup is still misaligned? See screenshot: The translation in the dropdown is not taken from the /site/templates-admin/default.php. Also the module title (getModuleInfo title, if available) will not be checked for translation strings in the dropdown. See 'Fields' and 'ModulesManager'. Strangely the 'Language' --> 'Sprachen' is translated?? The hover effect on the login fields still exists. The download size of PW-dev is now bigger (8,9 MB instead of 6,3 MB). Correct?
  22. back from vacations and tested the new version (it says 2.3.5). Looks very good. Still found some things... In the login screen hover over the arrow shows the field-name In the setup/templates view hover over the page number symbol: the popup is misaligned In the top navigation under setup the 'Fields' is not translatable Color schemes: warm and modern are nice. Futura looks very good, but the red buttons look wrong. Martijn already mentioned this. Classic is also nice, but the gradients .... hmm better not. Translations: how far is the work with translatable strings gone? Seems, there are still some missing strings. regards Manfred
  23. This, or upgrade to the new TinyMCE v4? a second thought on this RTE topic: what about including both RTE's (TinyMCE + CKEditor) in the default PW install? Both as separate modules available but not preinstalled. Then the developer could decide, which of them to install (same procedure as with other modules like repeater etc.). Maybe also in this case the RTE's as modules are easier to maintain and update? contra: the size of PW gets bigger.
  24. just an idea: make CKEditor to the new default RTE?
  25. Here is another thread where we talked about frameworks. If size and flexibility matters, PocketGrid could be a good choice? It's only a grid, nothing more. Very minimal and seems to be very flexible. Looks like you can do anything with it (like doing with PW). But haven't tested it.
×
×
  • Create New...