And thank you very much for your detailed answers. I am currently
evaluating this framework and trying to figure out if it's easier (less
coding & simpler) to use it to provide a web interface to do database
operations. We may need to provide more complicated user interfaces than
the default ones and I want to know how much work will be involved with
customization and to figure out if it's still much easier than just using
other web based frameworks which does not have crud operation support.
Did you look at the simple blog video tutorial (http://rifers.org/
rife_indepth_simple_blog)? This is how you'd to custom interfaces
with the CRUD extension. RIFE has been built for simplicity and ease
of use, without losing the focus on maintainability and reusability.
This is being recognized by more and more prominent developers (Bruce
Tate, David Heinemeier Hansson, ...)
[Jing] Yes, I did. But it seems to me more like how to create a CRUD web
interface using RIFE only instead of customizing the interface provided by
CRUD extension. I'll look again. But is it fair to say that if I want a lot
of customization of the user interface, it's easier to achieve to use
RIFE/CRUD than RIFE?
About changing the database structure if the model changes. I think it's
kind of hard to do because there are different kind of changes. I am not
sure if it's achievable by adding meta data to the element. When we change
the model, we should specify what kind of change(changes that the
framework supports) we'd like to do to the datastructer. I am just
thinking loud so please ignore it if it doesn't make sense.
I was thinking along the lines of detecting a change and notifying
the user about it at the top of the web interface. It would then
provide a possibility to output all the current data to an external
format (XML), drop the current structure, create the new one and
import the data into the new one. Of course there might be errors
during the import process where user-intervention is needed. I'm not
sure what the best way is to handle that.
[Jing]I'll display my ignorance here. For certain type of changes, you
shouldn't have to do this,right? For example, change that you can achieve by
issue alter command. In my understanding, when you detect the change of the
model, the first thing you will do is to find out what kind of change it is
and then do something about it. If it's a alter table change
(add/drop/rename) a column, you will issue a alter command to the databse to
make the change, and then you will construct your CRUD command to
add/delete/retrieve information from this table. If it's more complex
changes, then you can just declare that this kind of change is not supported
for now before a good solution is figured out:). But at least the framework
should allow certain degree of change to the model because it's usually
unavoidable to change the database structure.
Thanks!
Jing
Thanks again,
Jing or Maggie (the same person)
Is Maggie a translation of Jing?
No:) Jing is my real name and Maggie is just my English name given by my
English teacher when I was at school.
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
