Re: [Modus-devs] 0.2

[Brad P. <br...@ro...>]

I only have one small comment right now. I have been messing around a
little creating simple content objects, like a "link", thinking in terms
of the BACFUG site. Anyway, I was using renderBasicForm so ran into the
field ordering issue. It is really quite simple to handle it on your
own, and I would tend to agree that the core architecture shouldn't
worry about that. My $0.01 for the evening.

Brad

On Thu, 2002-09-19 at 19:22, Nathan Dintenfass wrote:
> [I've been out of town, but the discussion of frameworks is a great one to
> have]
> 
> FYI: I released the head as 0.2 today because I posted a message to the
> CFGURU list that talked about Modus persistence, and didn't want people
> downloading 0.1.
> 
> Basic differences since 0.1:
> 
> Sorting of contentObjects
> New field validation rules
> New form field rendering component
> New default persister using the file system
> Basic caching of object instances
> makeClone() method in the baseContentObject() [used in caching]
> makeID() in the baseContentObject() -- to allow implementations to have
> their own default ID generation
> 
> Also, cleaned up the code, so all tag attributes for CFFUNCTION and
> CFARGUMENT should now be in place.
> 
> Still to do (from the original list I wanted for 0.2, now for 0.3):
> 
> -- Building SELECT form fields and multiple radio fields
> 
> -- Working on fields with multiple values and the MULTI-SELECT/Checkbox form
> fields for that
> 
> -- Filtering of results.  For instance, "get all press releases created
> since one month ago".
> 
> (following is repost from an old thread, but just to keep these items fresh
> in the mind . . . )
> 
> Then, after that things like:
> 
> -- Joins: how will we have many-to-many and one-to-many relationships
> between object types?
> 
> -- Searching: how will we do searching of field values
> 
> -- Field ordering.  Unfortunately, the metaData of a CFC does not return
> properties in the order in which they appear in the CFML, so fields come out
> in random order.  This is kind of a bummer for things like
> renderSimpleForm(), though I also could see an argument that order of
> display is a front-end issue, not something the core architecture should
> worry about, so I may skip this one for now, as I can't think of a really
> clean way to make it happen.
> 
> -- contentObjects as field values -- would it ever make sense?
> 
> -- clustered caching: this is not a high priority for me because Modus does
> not have huge scalability as a primary design consideration, but it should
> 
> -- sample applications: something a bit more robust than what we have now
> 
> -- documentation
> 
> I also think there could be higher level kinds of things like:
> 
> -- workflow and something like Spectra PLP's
> 
> -- pluggable security mechanisms
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Modus-devs mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modus-devs
> 
>