ACS is now licensed through ADPL
(Arsdigita Public License). It's open source, and I don't see how it fits into definition of "soon to be proprietary product". As always, the code which is now open-source under ADPL will always remain available under same licensing terms.
You're asking about "enterprise class open source applications" built on top of Tomcat (or some other servlet engine)? You should take a look at the Arsdigita Community System which is open-source and provides most of the things you're asking for (Content Management System, for example). It's being actively developed and yes, I'm working for Arsdigita.
Don't worry about InterBase developer pool: newly formed InterBase Software Company has one of the original IB architects, Ann Harrison, as its president (the other is her husband), and many highest talented people from former InterBase division at Inprise.
And don't worry about InterBase developer community either: take a look at the www.interbase2000.com to see how it's organized and how you can contribute.
You may find what you're looking for in ArsDigita Community System (ACS), a GPL-ed toolkit for building RDBMS-backed Web sites with "collaborative dimension".
It needs AOLserver (free, open-source) and Oracle 8 (not free, not open-source). You may also be interested in InterBase or Postgres port.
Ticket Tracker, ACS module, may come very handy for managing tasks/issues/resolutions.
--but the problem is, the Linux version is only 5.1, where the NT, Solaris and HP/UX versions are all at 5.5, so there's been some question about Inprise's commitment to Linux.
If this rumours happen to be true, this release would be any DBA's dream -- imagine a product with feature set freezed, and bug set seriously restricted.
All in all, one can hardly question Inprise/Borland commitment to Linux after all this.
Borland deserves some credits from us Linux folks. I've always had good times with Borland tools - from Turbo C coding in old DOS days till these days.
Now I wonder what their current relationship with InterBase (Inprise?) is. As far as I know, InterBase grew out of an independent team of programmers long ago before Borland came to scene. Or am I wrong?
This way or that way, Linux developers should really take a look into InterBase DBMS. BTW, they still offer (oldish) 4.0 for Linux free of charge. Combined with the open-sourced AOLserver (see previous Slashdot story) with AOLserver driver for InterBase, it can be helluva web/db application tool.
As the name implies, it is a networked machine which doesn't have to have its own hard disk (but may have one). All files it needs it gets via NFS (Network FileSystem). If it hasn't local hard disk, how does it boot? One solution is booting by ROM plugged in the network adapter card, but you must have enough knowledge and access to EPROM burner to do it. The solution I describe is booting by floppy disk which contains Linux kernel image. Once loaded, kernel takes over the control of the diskless client and floppy is not needed anymore.
This describes one real-world setup and also sheds some light on motivation. In my experience, deploying diskless (Linux) clients led to significant decrease in hardware and software cost, and (most important!) greatly reduced admin time.
Simple question: What�s new since 2.0.36?
on
Linux 2.2 Released
·
· Score: 1
Or better, is there some site where you can see change log (not the source diff) between two arbitrary revisions (e.g. between 2.0.30 and 2.2.0)?
Most of the time we work on correcting existing polygon data, both spatial and attributes. We collect data from various sources, so there is a big amount of data editing.
This is the problem #1. And the problem #2 are sophisticated printouts of that data which are royal PITA to compose in ArcView.
Next, we have plain old RDBMS keeping some statistical data we wish to throw in. At the moment we use 'linked tables' in ArcView to link ArcView polygons to records in RDBMS tables using something like parcell ID as a key. However, very often polygon gets splitted (or joined or deleted) and RDBMS must be informed manually of these changes.
BTW, can GRASS handle attribute table attached to some vector dataset?
I'm working in County Planning Office and having a lot of work with GIS related stuff. I use ArcView on Winbloze, primarily for printing maps. I find GRASS of no use to me, beacuse it is raster oriented, while I'm dealing with lines/polygons all of the time.
With time our datasets grew big, and it is pain to handle them with ArcView. We are thinking about migrating to ArcInfo+SDE connecting to Oracle.
We will be happy to use any tool that works, but after fiddling with GRASS 4.2 I am definitely sure that it does NOT fill our needs.
Slashdot Mirror
ACS is now licensed through ADPL (Arsdigita Public License). It's open source, and I don't see how it fits into definition of "soon to be proprietary product". As always, the code which is now open-source under ADPL will always remain available under same licensing terms.
You're asking about "enterprise class open source applications" built on top of Tomcat (or some other servlet engine)? You should take a look at the Arsdigita Community System which is open-source and provides most of the things you're asking for (Content Management System, for example). It's being actively developed and yes, I'm working for Arsdigita.
can be found at InterBase Developer Initiative web site: www.interbase2000.org.
And don't worry about InterBase developer community either: take a look at the www.interbase2000.com to see how it's organized and how you can contribute.
It needs AOLserver (free, open-source) and Oracle 8 (not free, not open-source). You may also be interested in InterBase or Postgres port.
Ticket Tracker, ACS module, may come very handy for managing tasks/issues/resolutions.
IIRC from discussions at news://forums.inprise.com/interbas e.public.linux and news://forums.inprise.com/interb ase.public.general, InterBase 5.6 -- and that would be final release of 5.x codebase -- should be released for NT and Linux at the same time.
If this rumours happen to be true, this release would be any DBA's dream -- imagine a product with feature set freezed, and bug set seriously restricted.
All in all, one can hardly question Inprise/Borland commitment to Linux after all this.
Borland deserves some credits from us Linux folks. I've always had good times with Borland tools - from Turbo C coding in old DOS days till these days.
Now I wonder what their current relationship with InterBase (Inprise?) is. As far as I know, InterBase grew out of an independent team of programmers long ago before Borland came to scene. Or am I wrong?
This way or that way, Linux developers should really take a look into InterBase DBMS. BTW, they still offer (oldish) 4.0 for Linux free of charge. Combined with the open-sourced AOLserver (see previous Slashdot story) with AOLserver driver for InterBase, it can be helluva web/db application tool.
Because I'm tired of writing it all over again, I put it on http://acs.lavsa.com/sskracic/diskless/.
This describes one real-world setup and also sheds some light on motivation. In my experience, deploying diskless (Linux) clients led to significant decrease in hardware and software cost, and (most important!) greatly reduced admin time.
Or better, is there some site where you can see change log (not the source diff) between two arbitrary revisions (e.g. between 2.0.30 and 2.2.0)?
This is the problem #1. And the problem #2 are sophisticated printouts of that data which are royal PITA to compose in ArcView.
Next, we have plain old RDBMS keeping some statistical data we wish to throw in. At the moment we use 'linked tables' in ArcView to link ArcView polygons to records in RDBMS tables using something like parcell ID as a key. However, very often polygon gets splitted (or joined or deleted) and RDBMS must be informed manually of these changes.
BTW, can GRASS handle attribute table attached to some vector dataset?
With time our datasets grew big, and it is pain to handle them with ArcView. We are thinking about migrating to ArcInfo+SDE connecting to Oracle.
We will be happy to use any tool that works, but after fiddling with GRASS 4.2 I am definitely sure that it does NOT fill our needs.
Any comments?