Fork me on GitHub

Archive for the ‘Releases’ Category

Release 0.6.1.1

Monday, August 4th, 2008

Mack 0.6.1.1 features 38 completed tickets and a whole host of really great features and improvements. Here’s a quick overview of a few of the big features in Mack 0.6.1.1.

Page Caching

There is now a mack-caching gem which gives you easy to use page caching when you require it. To use page caching first you need to add it to your gems.rb file like such:

gem.add "mack-caching", :libs => "mack-caching"

That will require the gem and give your app access to the page caching libraries. Next you to turn on page caching in your application. In the appropriate config/*.yml file add the following:

use_page_caching: true

Now, you just need to tell your controllers which actions they should cache:

class FooController
  include Mack::Controller
  cache_pages :o nly => [:index, :show]
end

If you give the cache_pages no optional parameters then it will cache all the actions for that controller. Alternatively, you could give it an :except parameter to list the actions you don’t want cached. 

Notifiers (aka Mailers)

Mack now has a mack-notifier gem that will be the repository for all ‘notification’ systems, the first of which is email. The Mack::Notifier API is simple and easy to use and will allow developers to plugin in different notification systems under the cover without having to change their application code. 

A notifier can look as simple as:

class WelcomeEmail
  include Mack::Notifier
end

With that you can then write the following bit of code:

we = WelcomeEmail.new
we.to = "foo@example.com"
we.from = "bar@example.com"
we.subject = "Hello World"
we.body(:text) = "My plain text body"
we.body(:html) = "My html body"
we.attach(Mack::Notifier::Attachment.new("/path/to/my/file")) 
we.deliver

Obviously there’s a lot more to the API, including a validations module, but that’s a subject for another post. 

JavaScript (aka RJS)

The mack-javascript gem now gives you Rails-like RJS support for Mack. The default library to use with mack-javascript is jQuery, but there is prototype support available as well. 

Data Factory

Creating faux data for testing can be a real nightmare. Fixtures can be difficult to maintain and trying to create your own faux data can be a chore. That’s where the mack-data_factory gem comes in.

For each model that you want to produce, you will need to define a factory class.  

Let’s say that I have 2 models: Item and User, and Item belongs to user.  So the factories will look like the following:

class ItemFactory
  include Mack::Data::Factory
  field :title, "MyItem"
  field :o wner_id, {:user => 'id'}
end

class UserFactory
  include Mack::Data::Factory
  field :username, "planters", :length => 25, :content => :alpha
  field :password, "roastedPeanuts", :immutable => true
end

So, the 2 classes above defined the factory for item and user.  As you can see, each factory will need to explicitly list all the fields that it will populate, and for each field, you can define rules on how the content is generated.

Supported content types: 

  • :alpha –> alphabets.  rules: [:length, :min_length, :max_length]
  • :alphanumeric –> alphabets and number.  rules: same as :alpha
  • :numeric –> numbers [optional, because if the field's default value is number, its content type will automatically set to numeric)
  • :email --> generate random email address
  • :username --> generate random username
  • :domain --> generate random domain name
  • :firstname --> generate first name
  • :lastname --> generate last name
  • :name --> generate full name
  • :city --> generate city name
  • :streetname --> generate street name
  • :state --> generate state.  rules: [:country --> :us or :uk, :abbr --> true if you want a abbreviated state name (us only)]
  • :zipcode –> generate zipcode. rules: [:country --> :us or :uk]
  • :phone –> generate phone number
  • :company –> generate company name.  rules: [:include_bs --> include sales tag line]
    example:  field, “”, :content => :company, :include_bs => true could generate something like:
    Fadel-Larkin monetize cross-media experiences
There’s a lot more to the mack-data_factory gem, so I highly recommend you check it out.

Changelog:

  • [#60] Fixed Mack executable problem
  • [#59] Fixed gems:* tasks
  • [#57] Moved most files under to lib/mack
  • [#56] mack-more: Added Mack::Utils::RegistryMap
  • [#55] mack-more: mack-facets: Mack::Utils::Registry is now Mack::Utils::RegistryList
  • [#54] Added DataMapper 0.9.3 support
  • [#52] mack-more: mack-[orm] should require mack-[orm].rb using its full path.
  • [#51] Application generator should generate orm support in the right place
  • [#50] Mack will now have 2 environment files: mack_core and mack_app.  Mack.rb will load both files, but it gives other module chance to load just the core files and not the application’s files.
  • [#49] Making sure the orm tasks is available when orm_support is removed from the app_config
  • [#49] mack-active_record:  mack-active_record.rb will require mack-active_record_tasks.rb
  • [#49] mack-data_mapper:  mack-data_mapper.rb will require mack-data_mapper_tasks.rb
  • [#49] Updated warning message if orm is defined in app_config (i.e. user only needs to require mack-[orm_name], instead of both that and mack-[orm_name]_tasks).
  • [#48] rake generator:list now displays the correct names for the generator tasks.
  • [#47] rake gems:* tasks now work, and no longer require mack_ruby_core_extensions
  • [#46] Calling .to_param on nil now raises a NoMethodError exception.
  • [#45] rake stats task now works with Test::Unit::TestCase
  • [#44] Mack::Runner has now been extended to allow for greater extension flexibility.
  • [#43] Added a Mack::Utils::Registry class to allow for easy creation of registries.
  • [#42] Sessions can now be turned off globally using the app_config.mack.use_sessions switch.
  • [#41] Deprecate orm_support.rb
  • [#38] There is now a registry of Controllers that are in the system.
  • [#36] Renamed the initialize method in the Mack::Controller module to configure_controller. This gives
  •   control of the initialize method back to the class.
  • [#34] Mack::l10n now raises exception with a fully qualified name.
  • [#33] mack-active_record now requires ActiveRecord 2.0.2 explicitly, not >=2.0.2
  • [#31] Added support for ruby-debug.
  • [#26] Log Coloring for console output.
  • [#24] Added mack-notifier support.
  • [#18] Added Page caching.
  • [#14] Data Factory
  • [#7] Added support for Extlib::Hook in a few places.
  • [#6] RJS support
  • Added a rake tmp:clear task.
  • gem: application_configuration 1.5.1
  • gem: ruby-debug 0.10.0
  • gem: data_mapper 0.9.3

Release 0.6.0

Wednesday, July 16th, 2008

Well, it’s finally here, Mack 0.6.0! This release has taken a long time, but I feel that it’s definitely worth it. This has to be the best release of Mack to date. During this release the Mack dev team grew by 100%, Darsono Sutedja, previously a contributor to Mack, is now a full time Mack core team developer! Darsono has done an absolutely great job on this release, thanks Darsono. With that out of the way, let’s jump straight to the good stuff, shall we?

DataMapper 0.9.2 Support

At long last Mack supports DataMapper 0.9.2. Because previous versions of Mack used DataMapper 0.3.2, there is some upgrade work that you’ll need to do, but trust me, it’s worth it. DataMapper 0.9.2 is a gigantic leap forward from 0.3.2. If you have problems installing the data_mapper gem, make sure that you don’t have gems.datamapper.org in your source path for rubygems. You can remove it with the following command:

gem source -r http://gems.datamapper.org 

RSpec Testing Support

RSpec is now the default testing framework for new Mack applications. This innovative testing framework makes it fun, and simple, to do behavior driven development. If you haven’t yet played with RSpec, I would highly recommend it. I wasn’t a big fan of ‘spec’ testing prior to meeting Adam French, of DataMapper fame, and he turned me on to the joys of rspec. I think you’ll like it too, if you give it a chance. :)

mack-more

There is now a mack-more package. This will house all the optional gems available to the Mack framework. This include things like HAML and Markaby support, localization, etc… Use what you want, ignore the rest. This will help keep the core code clean, light, and of course, fast.

Localization/l10n Support

Darsono did a great job with the mack-localization gem. There is now optional support for internationalization in Mack applications. Check out the gem, it’s definitely worth it if you need to support multiple languages for your web application.

Much, much more!

Of course, there’s a lot more Mack than the stuff I just mentioned, there’s tons of bug fixes, some code clean up, some API changes, transactional testing support, the ability to catch specific errors in routes and have them diverted to a controller/action for handling.

There is a great wiki entry on upgrading your existing Mack project to 0.6.0 here. I highly recommend reading it whether or not you have an existing Mack application.

With this release the Mack team is also fully embracing Lighthouse. If you find bugs, or have suggestions please visit http://lighthouse.mackframework.com and log them there. You’ll also find the list of features that will eventually be added to Mack.

Changelog:

  • INCOMPATIBILITY NOTICE: Moved Mack::Configuration.root to Mack.root
  • INCOMPATIBILITY NOTICE: Moved Mack::Configuration.env to Mack.env
  • INCOMPATIBILITY NOTICE: Mack::Configuration.* path methods no longer exist. Use mack-paths instead.
  • INCOMPATIBILITY NOTICE: Dropped mack_ruby_core_extensions in favor or mack-facets
  • INCOMPATIBILITY NOTICE: Mack::Controller::Base is now Mack::Controller (and it’s now a module)
  • INCOMPATIBILITY NOTICE: Haml renderer is now part of mack-more.
  • INCOMPATIBILITY NOTICE: Markaby renderer is now part of mack-more.
  • INCOMPATIBILITY NOTICE: Changed request param’s accessor routine, from params(key) to params[key]
  • INCOMPATIBILITY NOTICE: Test::Unit::TestCase is no longer the default testing framework, RSpec is. If you wish to use Test::Unit::TestCase add the following config parameter to your config/app_config/default.yml file:
      mack::testing_framework: test_case
  • INCOMPATIBILITY NOTICE: ENV["_mack_env"] and ENV["_mack_root"] are no longer supported, please use ENV["MACK_ENV"] and ENV["MACK_ROOT"], or just Mack.env and Mack.root
  • INCOMPATIBILITY NOTICE: MACK_DEFAULT_LOGGER constant is no longer available. Please use Mack.logger instead.
  • INCOMPATIBILITY NOTICE: The ApplicationHelper module is now deprecated. Please move view level helpers into Mack::ViewHelpers::* and controller helpers into Mack::ControllerHelpers::<controller_name>
  • thin.ru and thin.yml are no longer needed, you may delete them.
  • RSpec assertions are now automatically added.
  • Added a Mack::Testing::Response class to make testing of responses easier.
  • moved test_extensions to testing and added the module Testing to the files in it.
  • Added a dependency on mack-more
  • Added a set of Rake tasks to update existing Mack applications.
  • [#30] Added Mack::Logging::Filter to filter out unwanted parameters from the logs.
  • In routing you can now define a route that will catch an Exception from another controller.
  • ORM will not be initialized if the app never specify which ORM to use.
  • All Mack unit tests are now written using rspec-1.1.4.
  • mack command now takes an optional -t flag to determine which testing framework to use–value could be test_case or rspec [default]
  • new setting added to app_config: testing_framework
  • gem: cachetastic 1.7.2
  • gem: application_configuration 1.5.0
  • gem: erubis 2.6.2
  • gem: genosaurus 1.2.1
  • gem: thin 0.8.2
  • gem: rspec 1.1.4

Release 0.5.5.4

Tuesday, June 10th, 2008

This is actually a combined post about 0.5.5.3 and 0.5.5.4. They are both small patch releases, but they both address some pretty big problems.

0.5.5.3:

The new version of Passenger (aka mod_rails) now has support for Rack based applications. In their documentation they show how to use a Mack app with Passenger. The documentation is based on the yet to be released Thin adapter. With that said, both of those systems use a piece of Mack that’s no longer there. Because of that I’ve restored the small section of code, to make sure those two systems work with Mack. Which is great news.

On some flavors of Unix when you do a Dir.glob you don’t necessarily get back an ordered list of files. Because of that some people we’re getting uninitialized constant errors. This has also been addressed in 0.5.5.3.

0.5.5.4:

A couple of people have reported issues where they were getting the following error even with the most simple application:

“Rack::Lint::LintError: env missing required key QUERY_STRING”

A Mack supporter by the name of Andre Ludwig stepped up to help me try and figure out the problem. I couldn’t reproduce it on the machines I have access to, I suppose that goes without saying, because I could’ve reproduced it, I would’ve fixed it sooner. Anyway, Andre stepped up with both his time, spending most of his Sunday online with me, but also with his hardware. Andre opened up his server to me so I could go in there directly and play with things until I found the problem.

Sure enough, once I got in there, it didn’t take me too long to figure out what the problem was. It turned out to be a conflict between the latest version of Mongrel (1.1.5) and the latest version of Thin (0.8.1). A simple rewrite of the rake server task and voila! problem solved.

So I would like to say thanks so much to Andre Ludwig for all his time and his hardware. I would also like to thank Saji for originally reporting the problem and for doing some troubleshooting for me as well.

As the community grows I can’t help but be awed by not only how much people are loving what Mack is doing, but also by the communities willingness to get involved and help out. Thanks so much everyone!

Changelog 0.5.5.4:

  • Fixed the damn Lint error some people were facing!

Changelog 0.5.5.3:

  • Restored compatibility with Passenger and the next version of Thin.
  • Fixed ‘requires’ out of order in certain flavors or unix. Hopefully.

 

Release 0.5.5

Wednesday, May 21st, 2008

Finally, Mack 0.5.5 is released! In addition to some great bug fixes, there is now a new rendering engine, support for automatic mime-types, the ability to register new mime-types, Markaby and Haml support, and much much more! It’s a great release.

To find out more about the new rendering engine check out these two posts:

http://www.mackframework.com/2008/05/20/the-new-rendering-engine/

http://www.mackframework.com/2008/05/20/055-adding-pdfwriter-plugin-support-tutorial/

Changelog:

  • INCOMPATIBILITY NOTICE: Ripped apart the ENTIRE rendering engine and rewrote it from the ground up. This means that wherever you are using ‘render’ calls in your views and controllers need to be changed. The new format is render(type, value, options). Examples: render(:action, :show), render(:url, “http://www.mackframework.com”), etc…
  • INCOMPATIBILITY NOTICE: Files named *.xml.erb need to be changed to *.xml.builder to use the Builder::XmlMarkup library. If you leave the .erb extension on there the file will be run through Erubis.
  • INCOMPATIBILITY NOTICE: <%= @content_for_layout %> is now <%= yield_to :view %>
  • Added Markaby support.
  • Added Haml support.
  • Added content_for and yield_to methods in views.
  • Erubis compiled templates are now cached for increased performance.
  • Added render(:inline) and render(:template) support.
  • Refactored, and reorganized some files to clean up the gem.
  • Fixed bug with cookies not merging with configured app_config parameters.
  • Added mime-types. The ‘Content-Type’ header is now being set based on the format that is requested. Default is text/html.
  • Fixed r.defaults in routes so they are always the last routes to be checked, no matter where they are placed in the routes definitions.
  • render(:url) now recognizes ‘local’ urls and tries to run them through the app, mimicking most headers from the original request.
  • Added ‘options’ banners to the mack and mack_ring_server binaries.
  • gem: genosaurus 1.1.8
  • gem: mack_ruby_core_extensions 0.1.28
  • gem: markaby 0.5.0
  • gem: mack-data_mapper 0.5.5

Release 0.5.0

Tuesday, May 6th, 2008

I know I’ve been talking about this release for a while now, and here it finally is. There’s some good bug fixes in here, a few new rake tasks, and some other little things like that.

The biggest thing, however, is what’s been causing a stir online now for the past few days, I’ve split out the ORM support into separate gems. I’m not going to go over it again, you can find all the details here: http://www.mackframework.com/2008/05/04/orms-and-mack/

Needless to say this is a good release to get, if not for the bug fixes alone, but for the great db:create rake tasks that are now in there. Thanks, again, to Darsono Sutedja for his great contributions.

Changelog

  • Added rake db:create and db:create:all rake tasks.
  • Refactored out constants, such as MACK_ROOT and MACK_ENV and made them into Mack::Configuration.env, Mack::Configuration.root, etc…
  • Added test:stats and test:coverage Rake tasks.
  • Removed support for ActiveRecord and DataMapper and moved them into their own gems.
  • Fixed a bug where yields in ERB weren’t giving the desired results.
  • DataMapper database.yml file can now be nested, and is generated as such.
  • Cleaned up some tests, and refactored the HTML generation stuff.
  • Fixed a bug with the scaffold generating ‘bad’ methods instead of ‘post’
  • Made error_messages_for more compatible with DataMapper.
  • Fixed a bug loading url.rb and uploaded_file.rb found by Phil Darnowsky
  • [dsutedja] Render method (in controller_base) now accepts response status code.
  • gem: mack_ruby_core_extensions 0.1.23
  • gem: genosaurus 1.1.4
  • gem: datamapper 0.3.2
  • gem: rcov 0.8.1.2.0
  • gem: mack-data_mapper 0.5.0
  • gem: erubis 2.6.0