4 votes
Make Xavante WSAPI all the way down
Refactor Xavante so it uses WSAPI internally, instead of the current API. This would alleviate the need for a WSAPI handler and would make it easier to reuse some WSAPI filters.
Refactor Xavante so it uses WSAPI internally, instead of the current API. This would alleviate the need for a WSAPI handler and would make it easier to reuse some WSAPI filters.
1st ranked
petsagouris
please please ignore my last post. I was being a troll... :o)
I did do some more reading. and yes, 3 votes for implementing Xavante wsAPI all the way down.
3 months ago
petsagouris
@carregal: ... to WSAPI (it is not a catchy name btw :) I'd go for wsAPI).
I am afraid that there is no simple and straight forward way for someone to understand (read tutorial-documentation isn't enough) how wsapi, orbit, cosmo work together to produce web applications.
3 months ago
Javier
petsagouris, IMHO the Lua-est interface possible could have even more modules! i'd like to refactor Xavente to make it thinner, with most of the functionality as optional modules. In fact, most of my objections to WSAPI stem from making too much non-optional. But after some insights from Fabio, i now think it's (part of) the way to go
3 months ago
carregal
Petsagouris, may I ask if you are referring to Kepler as a stack or just WSAPI? I agree that Kepler seems over modularized, but WSAPI is quite simple per se, no?
3 months ago
petsagouris
Javier I think you stood right when you talked about a purer Lua implementation. I still haven't realised why they have made this so complex with all these interlinking modules, dependencies etc. I think that Xavante (or Kepler as a whole for that matter) is very confusing to work with, at the moment due to its high complexity. IMHO the dev team overstepped between module management and complexity
3 months ago
Javier
i still think WSAPI is needlessly based on some other 'standard' (python's one? i don't remember). one designed for Lua would be different. of course, when we discussed it on the wiki i noticed i was the only one thinking that, so i just turned back from the discussion (and from xavante development)
3 months ago