Feature Requests

[Christopher Coté]

Just getting started with releasing the Humongolus framework into the
open.

If you see anything missing please let me know. Currently in the
pipeline is base

Form Widgets
BSON field
GridFS field
Binary field
Search mechanism

[Paul-Olivier Dehaye]

Different keys, as in
https://groups.google.com/d/msg/mongodb-user/su2e52_oQeo/o5ZfJTev5vIJ
(would also be useful to me)

[Paul-Olivier Dehaye]

What exactly do you mean with the "search mechanism" bit? It would be very nice if humongolus could translate back requests through the schema into valid mongo queries.

[Paul-Olivier Dehaye]

Link on git to this group (that one should be easy :)

[Christopher S Coté]

dbkey is available for all fields, lists and embedded-documents.

[Christopher S Coté]

when creating a field, list or embedded document you can use the "dbkey"
attribute to indicate a different attribute in mongo.

On 02/20/2012 10:35 AM, Paul-Olivier Dehaye wrote:

[Voltron]

Hi!

I do not think anything is missing in that list, at least for a first
version. I am ditching all my old code for Humongolus as soon as it
gets the Form widget and GridFS support. Wow! A mean piece of kit it
would be, those features and the speed. The speed factor comapred to
the bare-bones PyMongo driver is what really bothers many with the use
of the many ORMs/ODMs out there.

Thanks and keep up with the good work!

[Christopher S Coté]

I'm glad you like it!

What kind of projects do you currently work on?

On 02/20/2012 11:37 AM, Voltron wrote:
> Hi!
>
> I do not think anything is missing in that list, at least for a first
> version. I am ditching all my old code for Humongolus as soon as it
> gets the Form widget and GridFS support. Wow! A mean piece of kit it
> would be, those features and the speed. The speed factor comapred to
> the bare-bones PyMongo driver is what really bothers many with the use
> of the many ORMs/ODMs out there.
>
> Thanks and keep up with the good work!
>

[Voltron]

At the moment? Web applications that work on desktop and mobile
devices. I use Tornado in my stack.

[Christopher Coté]

Not quite sure what you mean "translate requests through"

What type of requests are you talking about? Something like RESTful
interface?

Also the search would be pretty basic, ideally settings certain fields
in a model to be searchable, on save it would update the values, in a
key store.

Not quite sure, just an idea I've been playing around with.

On Feb 20, 10:40 am, Paul-Olivier Dehaye <pauloliv...@gmail.com>
wrote:

[Voltron]

Hey Christopher! ETA for the "last killer feature"? Files. Shouldnt
these 3 items be abstracted into one field type?

BSON field
GridFS field
Binary field

Thanks!

[Christopher Coté]

Definitely. See what i can do.

[Christopher Coté]

Added the File field type, it's a light wrapper around the GridFS
class.

Check out tests/test_field.py Field.test_file() for usage and
implementation.

[Voltron]

Nice! I will check it out ASAP, Thanks!

[Christopher Coté]

Documentation is coming along.

Although Sphinx seems to have some issues with virtualenv, I'll be
looking into it a bit more.

[Voltron]

OK, Another thing :) Why the mandatory Settings object? Would it not
be comfortable if we couls also do something like :

car = Car(collection="my-coll", conn=conn, logger=mylogger) <-- This
would be great
car.owner = chris
car.make = "Isuzu"
car.model = "Rodeo"
car.year = datetime.datetime(1998, 1, 1)
print car
c_id = car.save()

This helps in sorting out large projects where there are separate
folder forfForms, models, templates and so on.

Thanks

[Christopher Coté]

I've never had any issues with needing to set the settings object multiple times, you should only need to do it once per process, in your startup script.

Also, passing in the collection at run-time seems iffy. Would you really be changing the collection per "Car" object?

Perhaps if i could see an example of your project layout and start-up script I could get a better idea of what your trying to accomplish.