Lars Kneschke wrote:
“Ralf Becker” RalfBecker@outdoor-training.de schrieb:
I want to show with a view technical points, how ZendFW and extjs could
be used in eGroupWare and Tine, and at the same time allowing Tine as a
user interface draft to run in parallel to the existing web GUI.
A motivation for this approach would be:
- joint development with the current trunk
- ability to include it as an optional interface in the next release
I’m not aiming to be complete, just emphasizing a view key points:
As you can see it would be very easy to add layers of backward compatibility
to our proof of concept code any time very easily. We just need to know,
which kind of backward compatibility we need.
But the main problem for the future of eGroupWare are not point a,b or c.
They could all be solved easily by us. But we can’t solve the problems of
eTemplate.
Ralf, Lars,
There are a lot of good creative/innovative ideas floating across the
list associated with the current discussion. One of the difficulties I
see in trying to navigate the current waters is that there is no compass
to be found. We all agree that faster is better, but running faster in
the wrong direction does nothing more than get us lost/off track quicker.
I don't know if this can be done, but what I haven't seen, that I would
like to see, is a set of goals for where egw wants to go that we can
evaluate the competing ideas against. This doesn’t need to be anything
elaborate, formal or detailed, but just something that will help clarify
and define the competing visions for egw. A list of priorities so to speak.
If the competing camps can agree to take 24 hours to step back and list
the goals of what they want to do with egw we would then at least have a
reference point for carrying the discussion forward. None of the ideas I
have seen from either side are mutually exclusive. The difficulty I have
seen is from an inability to evaluate a list of stated goals and
evaluate each item to determine the direction for egw. I think it would
help.
I think a simple list would include goals for:
o backwards compatibility/migration path for exceptions
o exclusive use of in house code/reliance of 3rd party packages
o desire for package responsiveness/client side rendering
o server load/client load
o core packages/supported packages/unsupported packages
This is just 40 seconds of typing, but if everyone would agree to take
24 to hammer this out, I think discussions could move forward.
Each of the resulting issues will have to be discussed. An example is
the in house code v. reliance on 3rd party packages. There is a lot to
be said for the total control that comes from custom code. There is a
lot to be said for using good off-the-shelf code. However, many people
have been screwed when they have relied on off-the-shelf code only to
have the external coding project tank. The project is screwed at that
point unless the project picks up the left-overs.
Much tension abounds, but keep the focus on "what's good for egw" From
the swirl of competing ideas, each of the developers can and must answer
that question. Not everything has to be done tomorrow. Fighter pilots
and astronauts have a very simple way of staying alive (I know, I
trained the crews of STS-44, 54 and 68 on OBS) It applies here:
-
Keep the vehicle under control;
-
Analyze the situation;
-
Take corrective action.
We are two-engine TAL at this point. See:
http://science.ksc.nasa.gov/shuttle/technology/sts-newsref/mission_profile.html
–
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers