Naked Objects?
Wolfgang Keller
was an (the?) inspiration for SQLkit.
Sincerely,
Wolfgang
--
HOMO HOMINI HOSTIS IN FELIBUS FELICITAS
Alessandro Dentella
> Having come across the "Naked Objects" concept, I wonder whether this
> was an (the?) inspiration for SQLkit.
honestly: I know nothing about "Naked Objects", so that I can state that that
was not the inspiration. I quickly read right now what wikipedia sayed
about them but I know too litle theory of programming to be able to say to
what degree sqlkit embodies part of those ideas even thought I loosly map
sqlkits' layout to the view, the hook to the controller and the in an MVC
pattern.
sandro
*:-)
--
Sandro Dentella *:-)
http://www.reteisi.org Soluzioni libere per le scuole
http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy
Wolfgang Keller
The point of this concept is that the developer writes only the model
(including behaviour as required), the rest of the application is
"reflected" (you could also "generate" it) by the framework.
There's a PhD thesis available as PDF which cites an example of a
commercial application where this approach did not only reduce the
amount of code drastically, but also provided an application that was
considered much more functional by the users.
Since Sqlkit seems to require little hand-coding (the least of all
database application frameworks that I've looked at) and since Sqledit
uses even more excessive "reflection"/"generation", I had thought
there's some kind of relationship.
> so that I can state that that was not the inspiration. I quickly read
> right now what wikipedia sayed about them but I know too litle theory
> of programming
You're not a computer scientist? Just out of curiosity: What's your
primary profession then?
> http://www.reteisi.org Soluzioni libere per le scuole
Teacher?
Alessandro Dentella
> > honestly: I know nothing about "Naked Objects",
>
> The point of this concept is that the developer writes only the model
> (including behaviour as required), the rest of the application is
> "reflected" (you could also "generate" it) by the framework.
> There's a PhD thesis available as PDF which cites an example of a
> commercial application where this approach did not only reduce the
> amount of code drastically, but also provided an application that was
> considered much more functional by the users.
> Since Sqlkit seems to require little hand-coding (the least of all
> database application frameworks that I've looked at) and since Sqledit
> uses even more excessive "reflection"/"generation", I had thought
> there's some kind of relationship.
the former idea is that the least number of code I need to write the least
possibility I have to introduce an error. I know it doesn't *really* work
like that and sometime if you spend some more words you gain readability. My
feeling is that code for sqlkit keeps a good level of readability anyhow.
When I started to develop sqlkit (2005) I didn't find other database
application framework for python, later camelot and dabo started. I never
had time to really compare them with sqlkit even thought it's something I
really would like to do. Do you or someone else know other frameworks and
wants to share some camparison?
> > so that I can state that that was not the inspiration. I quickly read
> > right now what wikipedia sayed about them but I know too litle theory
> > of programming
>
> You're not a computer scientist? Just out of curiosity: What's your
> primary profession then?
Now I do make a living as computer professional since 15/20 years, but I
graduated in physics. I did teach physics for a little time and I love
teaching programming and networking whenever it's possible. I didn't study
computer science at the university thought.
sandro
*:-)
http://it.linkedin.com/pub/alessandro-dentella/15/a95/b14
--
Sandro Dentella *:-)
http://www.reteisi.org Soluzioni libere per le scuole
Wolfgang Keller
> least possibility I have to introduce an error.
Not only that, but less code might also use less ressources, execute
faster and...
...take less time to write. >;->
> When I started to develop sqlkit (2005) I didn't find other database
> application framework for python,
Yes, this field unfortunately was a desert for a long time. Although I
would consider Python as THE language for such purposes. It's just been
missing frameworks so far.
> later camelot and dabo started.
I think Kiwi was even earlier than those two.
> I never had time to really compare them with sqlkit even thought it's
> something I really would like to do. Do you or someone else know
> other frameworks and wants to share some camparison?
So far I haven't actually tried out anything myself, just collected URLs
and read the documentation, where available. A "feature list" of what
you can do with which framework would be a "nice to have", such as, e.g.
- does the framework support just "active record" or more complex
mappings (the latter requires SQLalchemy, I supppose)
- does it support composite primary keys
- does it care/provide for concurrency conflict resolution or does it
follow a "philosophy" like "the last client that commits wins"
- how about internationalisation
- on which OSes does it get actually use/testing by the developers
- etc.
There are also some applications out there that might be possibly
abused as frameworks by "ripping out" all the domain-specific logic.
Qtalchemy and OpenObject effectively seem to result from this approach.
> I didn't study computer science at the university thought.
Neither did I - otherwise I would be writing my own framework. I happen
to be a mechanical engineer. And I'm thoroughly fed up with getting
such "adequate tools" as MS Excel, Access and VBA imposed onto me for
information logistics.
Alessandro Dentella
> > When I started to develop sqlkit (2005) I didn't find other database
> > application framework for python,
>
> Yes, this field unfortunately was a desert for a long time. Although I
> would consider Python as THE language for such purposes. It's just been
> missing frameworks so far.
>
> > later camelot and dabo started.
>
> I think Kiwi was even earlier than those two.
that's true, the reason I didn't use it is that the mailing lis was not at
all reactive to my questions (very novice ones indeed!)
> > I never had time to really compare them with sqlkit even thought it's
> > something I really would like to do. Do you or someone else know
> > other frameworks and wants to share some camparison?
>
> So far I haven't actually tried out anything myself, just collected URLs
> and read the documentation, where available. A "feature list" of what
> you can do with which framework would be a "nice to have", such as, e.g.
>
Just to be clear
> - does the framework support just "active record" or more complex
> mappings (the latter requires SQLalchemy, I supppose)
yes
> - does it support composite primary keys
yes but not for completion
> - does it care/provide for concurrency conflict resolution or does it
> follow a "philosophy" like "the last client that commits wins"
the last client wins...
> - how about internationalisation
the interface is localized in italian, english, german, polish, spanish
and uses Babel so that numbers and date should be sensitive to LANG* endv
variables.
> - on which OSes does it get actually use/testing by the developers
> - etc.
Developed on Linux, used on Windows and Mac as well by my direct customers.
sandro
*:-)