peakpg
- In other BrowserCMS news, this week we also released a module to integrate with a Central Authentication Server. See 2:29 PM Nov 6th from TweetDeck
- BrowserCMS 3.0.3 is done! Adds a lot of patches from the developer community. See for complete release notes.2:27 PM Nov 6th from TweetDeck
- @ Ok. I will add that as a lighthouse ticket and see if we can't track down what the issue is.6:33 AM Nov 3rd from TweetDeck in reply to iain_nl
- @ Was this for a rails project that included browsercms as a gem? Or a browsercms project including an additional noncms gem?6:23 AM Nov 3rd from TweetDeck in reply to iain_nl
- @ Hm... I will have to look at the rake gems issue. I wasn't aware there was a problem with it.6:13 AM Nov 3rd from TweetDeck in reply to iain_nl
- @ Out of curiosity, what specifically do you feel like is out of date with Rails styles on?6:01 AM Nov 3rd from TweetDeck in reply to iain_nl
- @ No but if you knew the data structure of Drupal you wanted to migrate from, you could probably use Rails migrations to do it.7:30 AM Oct 29th from TweetDeck in reply to hedron
- @ For @, you can choose to not store template data in the database as well. Add an erb file to /app/views/layouts/templates.7:20 AM Oct 19th from TweetDeck in reply to s0lnic
- @ I would start from the Reference docs at , and then install it and create a demo project.9:52 AM Oct 8th from TweetDeck in reply to asyraf9
- @ RoR, though both really work the same when it comes to templates.10:22 AM Oct 7th from TweetDeck in reply to thebestsophist
- @ I vote for BrowserCMS. And I am in no possible way biased. At all.8:23 AM Oct 7th from TweetDeck in reply to asyraf9
- @ Templates are very flexible. An html file can become a template by renaming it .html to .html.erb, and adding some helpers.7:40 AM Oct 7th from TweetDeck in reply to thebestsophist
- BrowserCMS 3.0.2 has been released to rubyforge. Contains some small bug fixes, details can be found here: 7:14 AM Oct 7th from TweetDeck
- @ We use BrowserCMS all the time, what sort of support do you need for preparing your client proposal?7:08 AM Oct 7th from TweetDeck in reply to thebestsophist
- @ Only if you plan on distributing that code. Building a client site != distribution. Building a product on top of it = distribution.7:32 AM Sep 22nd from TweetDeck in reply to cglee
- @ And we specifically picked LGPL so that people can build and even sell modules, themes, etc without having to open source their code.10:50 AM Sep 21st from TweetDeck in reply to cglee
- @ Even under GPL, building a site for a single client isn't 'distribution'. Otherwise, Drupal (a GPL CMS) wouldn't be so popular.10:47 AM Sep 21st from TweetDeck in reply to cglee
- @ On BrowserCMS, what do you feel like the LGPL license is preventing you from doing?5:54 AM Sep 21st from TweetDeck in reply to cglee
- @ Twitter seems to require you to be following me in order to send you a direct message.7:48 AM May 29th from TweetDeck in reply to headius
- @ We haven't really spent time making @ compatible with JRuby yet, but its certainly of interest for us. v2.0 was in java.7:08 AM May 29th from TweetDeck in reply to headius
|
|