Re: [Eledge-developers] Eledge Goals

[<ri...@us...>]

>We need to make eledge more scalable, but find a balance with the=20
flexibility. The proposal is that we >use the struts framework, with=20
velocity templates for the view layer, to make the application more=20
>scalable and maintainable. Some serious thought will need to be put int=
o=20
the design to ensure a high >degree of flexibility in the end product.=20
Any thoughts? ;)

Agree completely with your assert. About Struts + Velocity I've found=20
that stxx (an SF project) is a very valuable piece of the cake, it sits =

at the top of struts and take control, if we want to, for transforming=20
xml data taken from the bussines layer with xsl templates at our choice =

(we can , for example, determine the user agent for selecting xsl=20
templates). =20
The good new is that it adds support for velocity too in the struts=20
framework.

>      2) Somewhere in all our refactoringg, this needs to be done as we=
ll.=20
We need to determine who is >going to work on what aspect.

I'm waiting for Navigo release as you now (they have said april) to take=
=20
it, plug into EJOSA structure and eledgeizing its UI, but i'm a little=20
low of time because a Portal project i'm working for until june.
=20
>eledge, etc.) By creating appropriate interfaces and API's,
>we can make extension much easier; in the future, to add a type
>assignment, for example, would become much easier, and would "fit"
>into the framework that eledge would already be providing.

I suggest that you inspire yourself in OKI interfaces. Maybe they're=20
going to turn to a standard and its good to leverage their thoughts and =

eventually make Eledge OKI compliant in the future. It's not neccesary t=
o=20
=93copy=94 their writed methods cause we can make EledgeOKIAdaptors but =
it=20
could be good to understand and agree if convenient to their view of use=
=20
cases.

>grade/rubric calculation. Other ideas, such as tracking
>student access, fall within IMS/SCORMS compliance, as well as here.

Look at Navigo code, surprisingly (not at all!) they are using stxx to=20
manage native ims/scorm files, they can take that xml and transform it=20
with xsl templates for rendering. It's good to take xml without=20
transforming it (not even to a object model), the thing I don't like is =

the eventual growing complexity of xsl templates but...it's really good =

to have this working examples.