[Nitro] Nitro Status

George Moschovitis george.moschovitis at gmail.com
Thu Oct 13 10:01:21 EDT 2005


I have already both of these fixes ;-)

-g.


On 10/13/05, Chris Farmiloe <chris at motionpath.com> wrote:
>
>
> ooooo:
>
> sorry: didn't expect you to grab it that quick :)
>
> there was a silly mistake in the code. (rob picked it up lalaa)
>
> I have reposted...but dont have a good base to diff against
> at the moment so you'll have to just look at the code
>
> http://www.lego.motionpath.com/view/tags_for_editor
>
> also added an :editor => :none bit to allow property hiding
>
> hope it's of use.
>
>
> chrisfarms.
>
> On 13 Oct 2005, at 11:46, George Moschovitis wrote:
>
> > anw, added the patch, thanks.
> >
> > -g.
> >
> > On 10/13/05, George Moschovitis <george.moschovitis at gmail.com> wrote:
> >
> >>> Could not see how to do this with current ver?.
> >>>
> >>
> >> thats what I meant, you cann annotate with the current version but
> >> you
> >> have to adapt tags_for to make use of it.
> >>
> >> -g.
> >>
> >>
> >>
> >>>
> >>> I made a tiny modification (two lines) to the tags_for method
> >>> this morning to allow me to do what I wanted.
> >>>
> >>> please see the lego wiki if you are interested. I think the concept
> >>> is useful.
> >>>
> >>> chrisfarms
> >>> www.lego.motionpath.com
> >>>
> >>>
> >>>
> >>>
> >>> On 13 Oct 2005, at 09:01, George Moschovitis wrote:
> >>>
> >>> I think you can do this in the current implementation too.
> >>>
> >>> -g.
> >>>
> >>>
> >>> On 10/12/05, Chris Farmiloe <chris.farmiloe at farmiloe.com> wrote:
> >>>
> >>>
> >>> I would also like to see something like this.
> >>>
> >>> I'm waiting to see what has changed in .24 but would very much like
> >>> to be able to assign a code block to the :editor metadata to allow
> >>> for a much more powerful / customizable scaffold controller.
> >>>
> >>> I think this is what I'll work on next.
> >>>
> >>> imagine something like:
> >>>
> >>> property :title, String
> >>> property :body, String, :editor => :textarea
> >>> property :something, Hash, :editor => lambda {|obj, prop, options|
> >>> # ... }
> >>> # or something neater like
> >>> property :something_else, String, :editor => :class_method_in_model
> >>>
> >>> def self.class_method_in_model(prop, options)
> >>>      # html tags producing stuff...
> >>> end
> >>>
> >>> I'll often have specific needs for the editor of a particular
> >>> property in
> >>> a particular class. I also don't think it breaks MVC to expect a
> >>> model
> >>> to understand how to edit / display it's properties.... but am
> >>> certainly
> >>> willing to argue :)
> >>>
> >>> .... I can of course see a time when I have created
> >>> an editing control useful to more than one model, so i guess i'll
> >>> end
> >>> up with a library of :editor control methods to mixin to models.
> >>>
> >>> any thoughts welcomed?
> >>>
> >>>
> >>>
> >>> chrisfarms.
> >>>
> >>> On 12 Oct 2005, at 17:08, Tim Larson wrote:
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Oct 12, 2005 at 10:41:32AM -0400, TRANS wrote:
> >>>
> >>>
> >>>
> >>>
> >>> Nitro Fans,
> >>>
> >>> For all those chomping at the bit for Nitro 0.24, rest assured it's
> >>> "any day now". George and I have been working on a new annotations
> >>> backend, and we're determined to make it "pure mint". So bare
> >>> with us
> >>> while we get that up to spec.
> >>>
> >>>
> >>>
> >>>
> >>> With the changes being made, will it be easy to iterate through
> >>> properties and relations, such as for home-made versions of
> >>> functions like form_for and tags_for, and to pick on a specific
> >>> property or relation for functions like tag_for, label_for?
> >>>
> >>> It would be especially nice if additional not-persisted
> >>> "properties" could also have similar metadata, for uses such as
> >>> being iterated and picked on by the functions listed above,
> >>> without requiring extra code or having to be handled by an
> >>> extra loop that would break the sequencing of properites in
> >>> auto-generated forms.
> >>>
> >>> --Tim Larson
> >>> _______________________________________________
> >>> Nitro-general mailing list
> >>> Nitro-general at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/nitro-general
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Nitro-general mailing list
> >>> Nitro-general at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/nitro-general
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> http://www.gmosx.com
> >>> http://www.navel.gr
> >>> http://www.nitrohq.com
> >>>
> >>> _______________________________________________
> >>> Nitro-general mailing list
> >>> Nitro-general at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/nitro-general
> >>>
> >>>
> >>> _______________________________________________
> >>> Nitro-general mailing list
> >>> Nitro-general at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/nitro-general
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> http://www.gmosx.com
> >> http://www.navel.gr
> >> http://www.nitrohq.com
> >>
> >>
> >
> >
> > --
> > http://www.gmosx.com
> > http://www.navel.gr
> > http://www.nitrohq.com
> >
> > _______________________________________________
> > Nitro-general mailing list
> > Nitro-general at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/nitro-general
> >
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>


--
http://www.gmosx.com
http://www.navel.gr
http://www.nitrohq.com




More information about the Nitro-general mailing list