From: Chris W. <ch...@cw...> - 2003-06-04 19:01:34
|
I'm hoping to get an early beta of OpenInteract 2 out shortly (Monday June 9). Most features should work but there will need quite a bit of polish -- I haven't done much CSS work at all yet, there isn't any data migration or automation for all aspects of porting packages, Apache2 isn't yet supported, and probably a bunch of other things aren't yet done. But it seems to be working well so far and I'd like to get something out, if only to let people know the project is still kicking :-) I'm sure a document discussing what changed would be useful (it'll be here), but is anyone interested? Later, Chris |
From: Andrew H. <hu...@ll...> - 2003-06-04 20:04:02
|
I'm interested, and we might use it for an internal application here, but it remains to be seen if we can use it or not. "I'm not totally convinced to use OI yet" -- my boss. We might use Oracle Forms instead :( http://otn.oracle.com/products/forms/htdocs/9iforms_fov.htm So I vote a qualified "yes, I'm interested hopefully." -Andrew At 03:00 PM 6/4/2003 -0400, Chris Winters wrote: >I'm hoping to get an early beta of OpenInteract 2 out shortly (Monday June >9). Most features should work but there will need quite a bit of polish -- >I haven't done much CSS work at all yet, there isn't any data migration or >automation for all aspects of porting packages, Apache2 isn't yet >supported, and probably a bunch of other things aren't yet done. But it >seems to be working well so far and I'd like to get something out, if only >to let people know the project is still kicking :-) > >I'm sure a document discussing what changed would be useful (it'll be >here), but is anyone interested? > >Later, > >Chris > > > >------------------------------------------------------- >This SF.net email is sponsored by: Etnus, makers of TotalView, The best >thread debugger on the planet. Designed with thread debugging features >you've never dreamed of, try TotalView 6 free at www.etnus.com. >_______________________________________________ >openinteract-dev mailing list >ope...@li... >https://lists.sourceforge.net/lists/listinfo/openinteract-dev |
From: Chris W. <ch...@cw...> - 2003-06-05 02:54:39
|
Andrew Hurst wrote: > I'm interested, and we might use it for an internal application here, > but it remains to be seen if we can use it or not. "I'm not totally > convinced to use OI yet" -- my boss. We might use Oracle Forms instead :( Whenever I think OI is heavyweight I look at something like that and breathe a sigh of relief :-) Let me know if I can help with any convincing. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
From: Andrew H. <hu...@ll...> - 2003-06-05 15:50:35
|
At 11:14 PM 6/4/2003 -0400, Chris Winters wrote: >Andrew Hurst wrote: >>I'm interested, and we might use it for an internal application here, but >>it remains to be seen if we can use it or not. "I'm not totally >>convinced to use OI yet" -- my boss. We might use Oracle Forms instead :( > >Whenever I think OI is heavyweight I look at something like that and >breathe a sigh of relief :-) Yeah, its rather large. It is quick to get things developed, but thats not the problem I have with it. Its that its a PL/SQL client side application (I think C underneath) and the web enabled version just puts a Java "face" on it. So its rather difficult (in my experience) to really leverage the features of http well. Also, writing complex logic in PL/SQL sucks :) Nothing like doing in 10 lines of PL/SQL what 1 line of perl can do. >Let me know if I can help with any convincing. Thanks for the offer. I might end up writing a comparison/contrast of the two (unbiased, of course ;) to see which fits more for our situation. I might ask for some input then. The main deal I think my boss has with OI is the licensing. He's all for Open Source, but the problem is giving the changes back. We probably won't be distributing it, so that wouldn't be an issue. But if I make good changes / add features I'm going to do what I can do get them back in the main tree even though the license doesn't call for it. To do that, requires a code audit though from a few tech guys, for obvious reasons (national security, etc). Yes even for simple web apps. Its a rather arduous process. I'll keep you posted on the developments here... -Andrew >Chris > >-- >Chris Winters (ch...@cw...) >Building enterprise-capable snack solutions since 1988. |
From: Perrin H. <pe...@el...> - 2003-06-05 18:45:15
|
On Thu, 2003-06-05 at 11:50, Andrew Hurst wrote: > The main deal I think my boss has with OI is the licensing. He's all for > Open Source, but the problem is giving the changes back. We probably won't > be distributing it, so that wouldn't be an issue. But if I make good > changes / add features I'm going to do what I can do get them back in the > main tree even though the license doesn't call for it. To do that, > requires a code audit though from a few tech guys, for obvious reasons > (national security, etc). Yes even for simple web apps. Its a rather > arduous process. Giving back code is nice, but there are other ways to contribute to an open source project if your company is uptight about sending patches. Things like documentation fixes, good bug reports, and even helping answer questions on the mailing list are valuable and appreciated. - Perrin |
From: Perrin H. <pe...@el...> - 2003-06-04 20:15:56
|
On Wed, 2003-06-04 at 15:00, Chris Winters wrote: > I'm sure a document discussing what changed would be useful (it'll > be here), but is anyone interested? I'm interested, but probably won't have time to pay much attention to it until my OSCON talk is done. Releasing it sounds like a good idea though. - Perrin |
From: Peter D. <pet...@us...> - 2003-06-04 22:38:59
|
>I'm hoping to get an early beta of OpenInteract 2 out shortly Great! From what you have discussed on Wiki, I think you are going down the right road (removing the repository, going for one server per application area). Our previous experience with mod_perl and business applications (converting a 3GL style CGI perl framework to OO perl suitable for mod_perl) means we think you've got it right. We chose OI because it implements at least 50% of what we need elegantly and efficiently in a cross-platform and cross-database way. That's no mean feat. The changes you are making for OI2 will it even easier. >I'm sure a document discussing what changed would be useful (it'll >be here), but is anyone interested? We are. I guess you are writing a paper for your presentation at the Linux conf, would that be adequate ? Andrew wrote: >"I'm not totally convinced to use OI yet" -- my boss. >We might use Oracle Forms instead :( Sounds like when I tried to convince my employers, many moons ago, to use GNU C instead of paying money to Sun for the SunSPRO C compiler. "But it's commercially supported" was the argument, never mind that Gnu was better supported, faster and worked better. We went Open Source because it seems to us that the rate of innovation and level of support is superior to proprietary. It's easier to learn, too. Years ago I used Oracle Forms 3 and PL/SQL on Solaris, now I think I'll stick with Template Toolkit, OI and perl on Linux :-) -Peter --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 24/04/2003 |
From: Chris W. <ch...@cw...> - 2003-06-05 13:35:49
|
Peter Dragon wrote: > From what you have discussed on Wiki, I think you are going down the right > road (removing the repository, going for one server per application area). > ... Excellent. I think the changes will make OI easier to adapt as well. In theory you could write a mail server (or at least responder) based on OI... > We are. I guess you are writing a paper for your presentation at the > Linux conf, would that be adequate ? Actually the presentation I'm doing at YAPC::NA is on generating Java code with Perl. I submitted one for OI2 as well but it wasn't accepted. I'm planning on doing a BOF at YAPC::NA if anyone's interested -- will anyone from here be at YAPC::NA? Chris |