I think this debate could go on for some time ;-) Being pragmatic, we have to look at the impact on the lift code base and its users. Would a change to Box[MyClass] really improve user understanding and lower the learning curve to a point where making such a fundamental change in the lift API would be justified?
This is really the question we should now be asking now. <personal_opinion> Being english, the semantic of Box seems more logical, however, right now im sitting on the fence on weather or not the change is justified. Lets look at the dictionary: == Can 1 be able to 2 be permitted to 3 used to indicate that something is typically the case == Box noun 1 a container with a flat base and sides, typically square or rectangular and having a lid : a cereal box | a hat box. 3 a small structure or building for a specific purpose, in particular • a separate section or enclosed area within a larger building, esp. one reserved for a group of people in a theater or sports ground or for witnesses or the jury in a law court : a box at the opera | the jury was now in the box. 4 a protective casing for a piece of a mechanism. The fact that Box only really has a single meaning, is very attractive from a cognitive point of view IMO </personal_opinion> Realistically, what would the damage be API wise if we moved to box? Have we any way of understanding the impact in real terms? Cheers, Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
