The need is greater now than ever before... integrating the User perspective with the Developer perspective with the Administrator perspective is, and will continue to be, critical to the success of many human efforts.
Doing so more in the style of millennia old engineering disciplines rather than "old school hacks" is also critical to success (but let's not forget the creative component of the "hack"!)
So, I'm ramping up to get back on this.
I will need a couple of months at least to organize and express the issues I see as currently at hand. In that vein...
1. Define the problem, as completely and unambiguously as possible. Not that this has been neglected (it hasn't), but I need to do it from my own set of perspectives so further discussion may take place (see #2).
2. Discuss (see #1).
3. Iterate (see #1 and #2).
David has said: let this be "the year of Xermes". So be it.
Cheers,
Russell
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Coming up on two years now, man has this been a tough time. The (commercial) project that needed Xermes is long put to bed (Java and XUL), but there is still a need. (Rather, I still have a need.) So, can I tap into this by the end of the year, this year? We'll see. Cheers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm doing a large off-line (read: unpaid) project which is implementing the general idea of remote object delivery on-the-fly and object/view generation based on stored specifications and user context. The system generates views and connections according to general specifications stored in a database, and communicates with other servers via a "message bus" that connects local objects as well as remote objects (it currently works on the subscribe/publish model).
I have given up on Java, too bulky and constraining, in favour of Javascript and various frameworks (e.g., ExtJS) with javascript on the server side as well (currently Jaxer, but may move to JSExt or even V8). Also using JStORM for ORM mapping. The idea is to deliver through the browser and maybe later to the desktop via something like V8.
This is all in the prototype stage at present, will post more as things progress. I would like to see this project (Xermes) take off along the lines described, but there's a lot of experimentation and discovery work to be done yet.
Technology has come a long way since the registration of Xermes (2002)… but the need still exists.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The need is greater now than ever before... integrating the User perspective with the Developer perspective with the Administrator perspective is, and will continue to be, critical to the success of many human efforts.
Doing so more in the style of millennia old engineering disciplines rather than "old school hacks" is also critical to success (but let's not forget the creative component of the "hack"!)
So, I'm ramping up to get back on this.
I will need a couple of months at least to organize and express the issues I see as currently at hand. In that vein...
1. Define the problem, as completely and unambiguously as possible. Not that this has been neglected (it hasn't), but I need to do it from my own set of perspectives so further discussion may take place (see #2).
2. Discuss (see #1).
3. Iterate (see #1 and #2).
David has said: let this be "the year of Xermes". So be it.
Cheers,
Russell
OK, so a year late (almost). Q1 2008 may be it. I have other ideas to bounce about in the context of the spirit of Xermes... we'll get to that.
Not forgotten!
Cheers!
Coming up on two years now, man has this been a tough time. The (commercial) project that needed Xermes is long put to bed (Java and XUL), but there is still a need. (Rather, I still have a need.) So, can I tap into this by the end of the year, this year? We'll see. Cheers.
I'm doing a large off-line (read: unpaid) project which is implementing the general idea of remote object delivery on-the-fly and object/view generation based on stored specifications and user context. The system generates views and connections according to general specifications stored in a database, and communicates with other servers via a "message bus" that connects local objects as well as remote objects (it currently works on the subscribe/publish model).
I have given up on Java, too bulky and constraining, in favour of Javascript and various frameworks (e.g., ExtJS) with javascript on the server side as well (currently Jaxer, but may move to JSExt or even V8). Also using JStORM for ORM mapping. The idea is to deliver through the browser and maybe later to the desktop via something like V8.
This is all in the prototype stage at present, will post more as things progress. I would like to see this project (Xermes) take off along the lines described, but there's a lot of experimentation and discovery work to be done yet.
Technology has come a long way since the registration of Xermes (2002)… but the need still exists.