Well, one thing that should probably be done with documentation at
least is noting what version it was designed against.
* The Rapid tag library
* Rich types
* Users and authentication
These are the ones that I think will be of the most use for new people
but would agree with Tiago that if any of those are due for a rewrite/
upgrade before 1.0, the docs should be held off until the changes are
made.
On Dec 14, 10:30 pm, roland oth <[email protected]> wrote:
> I totally agree with Tiago.
>
> A very vital piece of documentation is how to modify controllers
> Newcomers with rails experience will have spent a lot of time between
> models, controllers
> and, wll the erb views. The views are replaced by dryml a very neat
> and advanced concept
> the models get all the fatness that they should . The very bareness of
> the controller seems
> nice at first, but one soon realizes that tweaking controllers and
> interweaving sime fine
> tuned things will either happen through dryml or the controllers. But
> where exactly is the
> question.
>
> I am just at this moment trying to figure out how the front controller
> works together with
> the new permissions (8.5) and the index actions.
>
> Here are my top 3 items from Owens list:
>
> * Controllers and routing
> (Bringinghttp://hobocentral.net/docs/controllers/
> up to the latest)
> * Users and authentication (mostly covered by the permission
> walkthrough, except for the view_permitted? aspect)
> * Multi-model forms
>
> Ffound this real gem of functionality: viewhints.
>
> Saw that on the releasenotes - This is great stuff, especially if
> trying to internationalize a site in one non english language.
> But I found no instructions on usage of this. Figured it out partially
> by trial and error.
> Some hints in the code on how to use that feature that would produce
> rdoc would have been very beneficial.
>
> Thanks Roland
>
> Am 14.12.2008 um 23:47 schrieb GamaFranco:
>
>
>
> > Owen,
>
> > I will be forced to ask for documentation about topics that I didn't
> > already understood yet (Mltu-model forms and Misc model extensions).
> > This will probably not benefit new-comers.
>
> > Hobo is facing some breaking changes in almost every release. I'm sure
> > this will be the rule of thumb unitl 1.0. In order to avoid reworking,
> > I suggest that the topics that will not suffer additional changes
> > should be documented first.
>
> > I've noticed that there is still some documentation in hobo-central
> > that was not moved to the cookbook (i.e. hobo controllers). Probably
> > because it is outdated and needs a strong review before making the
> > move? New-comers will find it easy if all the existing documentation
> > is located only in one place.
>
> > Thanks,
> > Tiago Franco
>
> > On Dec 14, 4:39 pm, Owen <[email protected]> wrote:
> >> TF,
>
> >> Couldn't agree with you more! How has the new doc (hosted at
> >> cookbook.hobobcentral.net) been for you so far (DRYML, LIfeCycles,
> >> Permissions? In addition to filling out the complete "Taglibs",
> >> what
> >> suggestions or other doc to model would you suggest?
>
> >> Here is the remaining list:
>
> >> * Multi-model forms
> >> * Automatic named scopes
> >> * Miscellaneous model extensions
> >> * Controllers and routing
> >> * The Rapid tag library
> >> * Rich types
> >> * Users and authentication
> >> * Subsites
> >> * Migration generator
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en
-~----------~----~----~----~------~----~------~--~---
