Radio Liferay

Welcome to Radio Liferay, a peek into what is going on in Liferay from the people doing it themselves.

 

Latest Broadcast

Radio Liferay Episode 60: Performance and Permissions with Preston Crary

  An episode on the "Per" things: Performance and Permissions. I spoke to Preston Crary, who amazingly was not mad at me for losing an earlier recording.

We're talking about these (and more) topics

  • We open with the attention to detail that's required for working on performance tuning and some short conversation about this topic.
  • Sadly, there's not often a single silver bullet, but many areas of dust.
  • Sometimes the fastest code is not the most optimal
  • Continuing with Preston's work on Permissions:
  • ResourceBlock is deprecated, and there's an easy migration path
  • The usecase for Resources, ResourcePermission, and ResourceBlocks (as they're not at all visible on the UI)
  • Preston's way through Liferay from Support to working on the topics that he's now working on
  • The new API for Permissions - and the documentation is also done already (as of me writing this article, not yet published, but available on github - should be a matter of days or hours)
  • Should you implement your own permission system? (and how the answer to this question might change in 7.1)
  • Upgrades are being performance tuned. I smell a future episode coming up. Paging the team that is working on this area
  • The remarkable memory savings that refactoring the UserBag introduced
  • What happend during login
  • Passwords are PBKDF2WithHmacSHA1/160/128000 hashed, a deliberately expensive password hashing algorithm.
  • LPS-75747 and an update to my hardball question: Document Library's default.xml is still in core, can't be updated through a module, just through an ext.

Follow @RadioLiferay, Preston and me (@olafk) on twitter.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory. Make sure to write a review for the podcast directory of your choice - or find everything about Radio Liferay on radioliferay.com.

Or just download the MP3 here:

download audio file

Average (0 Votes)
The average rating is 0.0 stars out of 5.


Threaded Replies Author Date
Clicked the link to radioliferay.com and Chrome... Dante Wang March 28, 2018 8:37 PM
Whoops, sorry - Something went wrong in the... Olaf Kock April 3, 2018 1:05 AM

Clicked the link to radioliferay.com and Chrome warned me about invalid cert...
Posted on 3/28/18 8:37 PM.
Whoops, sorry - Something went wrong in the reconfiguration of that server. Non-https works for now, it's just a forwarder to https://liferay.com/radio anyways...
Thanks for letting me know
Posted on 4/3/18 1:05 AM in reply to Dante Wang.

Tell others

If you enjoy this podcast and are subscribing on itunes or any other aggregator: Please consider telling them how much you like it - just use their rating system. And consider leaving feedback and comments (at the shownotes, linked for each episode)

Older Episodes

« Back

Radio Liferay Episode 47: Chema Balsas and Emil Öberg on Themes and Frontend Development

  Another Devcon conversation - make sure not to miss this event next year! I grabbed Chema Balsas, Software Engineer at Liferay Spain, and Emil Öberg, Consultant at Monator Technologies, a Liferay Partner Company in Sweden. This is a three-way conversation with Chema Balsas and Emil Öberg that we had during Liferay's Devcon 2014. Chema had a Theme-Workshop (sorry, no recording) and Emil a presentation on Rapid Frontend Development, so it made sense to talk to both of them as their experience overlaps. Speaking of experience: Chema is a Software Engineer in Liferay Spain, Emil is a Consultant at Monator Technologies, a Liferay Partner Company in Sweden.

We're trying to bridge the gap and discuss visual topics, e.g. themes, in an audio format:

  • the qualities of Liferay
  • UX (user experience) and UX guidelines
  • Building themes
  • How to start new theme projects
  • Emil's github repository
  • The problem with people like me doing frontend design
  • SASS, LESS
  • New themes coming to marketplace
  • Disabling Bootstrap and the future plans with it
  • Best practices on editing/creating themes, how to update servers and test
  • Sublime, Webstorm, Brackets
  • Developing a Toolchain, ROI
  • Upgrading themes to new versions of Liferay (see also Episode 38)
  • and probably more topics that I forgot to add to these shownotes.

Follow @RadioLiferay, @jbalsas, @emiloberg and @olafk on twitter.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory. If you like this, make sure to write a review for the podcast directory of your choice - or leave your feedback on www.liferay.com/radio.

Or just download the MP3 here:

download audio file

Average (0 Votes)
The average rating is 0.0 stars out of 5.


Threaded Replies Author Date
Hello Olaf, hello Chema, hello Emil, thank you... Dominik Marks January 22, 2015 6:07 AM
Hi! To say that I've a base template for every... Emil Öberg January 22, 2015 1:09 PM

Hello Olaf, hello Chema, hello Emil,

thank you for this interesting episode of Radio Liferay.

In the episode you said that Emil uses a Base Template for each new Theme they develop. Is that Template available somewhere? I did not find it on Emil's github repositories.

Regards,
Posted on 1/22/15 6:07 AM.
Hi!

To say that I've a base template for every new theme is a little bit stretching it.

When we start developing a new theme we always start from a previous project. As we always are learning new things and always get a little bit better, most of the time we start by cloning the last project we worked on. And then we just remove the things which are specific for the previous project. It just takes me a couple of minutes.

The thing which allows us to work this way is that we adhere to the "Atomic design" principle ( http://bradfrost.com/blog/post/atomic-web-design/ ). Take a look at this screenshot of a project of ours https://dl.dropboxusercontent.com/u/3378286/sample-theme.png (This is the source, so this is before the precompiler compile the scss into css, concatenate and minify the js, and make sprites out of images. A few files are censored as this is a client project). Lets say we aren't using maps in project, then I'll just delete the _map.scss file.

Another thing which makes us work this way is that all variables such as colors, fonts etc are set in the _variables.scss file, making it easy to change for a new client.

But no, sorry, I don't have a totally blank theme to show you.
Posted on 1/22/15 1:09 PM in reply to Dominik Marks.