goanna-developers — Project Goanna Developer Discussions

[Goanna-developers] Goanna moved to Origo

[Till G. B. <til...@in...>]

Dear all -

I moved Goanna to Origo: http://goanna.origo.ethz.ch

I was able to find Origo users for Alexander Kongentkov and Patrick
Ruckstuhl. I was not sure if Colin an Neal already have an Origo
account, so if all of you could check and let me know, so I can add you
to the project, that would be fantastic.

I disabled cvs and svn access on the sourceforge repositories to prevent
commits to the wrong repo.

We will work on migrating the documentation to the new goanna site on
Origo. This will be done in the next two weeks.


Thanks,
	Till

-- 
Till G. Bay
Software Engineering, ETH Zurich
http://se.inf.ethz.ch/people/bay

Re: [Goanna-developers] Sourceforge or Origo?

[Till G. B. <til...@in...>]

Till G. Bay wrote:
>> 1) Do the migration to Origo, making the documentation updates as
>> you suggest. 2) Update all the front entrances to the goanna
>> project on the sourceforge site, indicating that the project has
>> now moved to Origo. But don't make this a simple indirection. Just
>> have it as an additional (but HIGHLY prominent) link. This way
>> Goanna (and Eiffel) will still be visible on the sourceforge site.
> 
> That's how I would have wanted to do it, yes. Especially to keep the 
> door open to get back to Sourceforge - if the developers are not
> happy with Origo.

I didn't hear back from Neal - I'll put everything in place and try to
add all users that already have an Origo account.

I will post an update on this list once I have done the migration.

Till

Re: [Goanna-developers] Sourceforge or Origo?

[Till G. B. <til...@in...>]

Colin Adams wrote:
> Maybe we can get the best of both sites in this way:
> 
> 1) Do the migration to Origo, making the documentation updates as you
> suggest. 2) Update all the front entrances to the goanna project on
> the sourceforge site, indicating that the project has now moved to
> Origo. But don't make this a simple indirection. Just have it as an 
> additional (but HIGHLY prominent) link. This way Goanna (and Eiffel) 
> will still be visible on the sourceforge site.

That's how I would have wanted to do it, yes. Especially to keep the
door open to get back to Sourceforge - if the developers are not happy
with Origo.

Thanks for answering so fast,
	Till

> On 01/11/2007, Till G. Bay <til...@in...> wrote:
>> Dear all -
>> 
>> as Origo matures, I am posting a follow-up on my question about the
>>  possibility of moving Goanna to Origo.
>> 
>> Till G. Bay wrote:
>>> Eric Bezault wrote:
>>>> Colin Paul Adams wrote:
>>>>> I received a bounced message directed towards this list from 
>>>>> Till, saying that there was difficulty accessing the repo,
>>>>> and asking if perhaps we should be using origo instead.
>>>>> 
>>>>> My thoughts on this:
>>>>> 
>>>>> 1) It might not be a bad idea. But what would the pros of
>>>>> using origo be? An obvious con that occurs to me is that
>>>>> Origo is far less well-known than Sourceforge. I don't
>>>>> suppose this really matters though, if there are positive
>>>>> benefits from using origo.
>>>>> 
>>>>> 2) If there are identifiable benefits, and the concensus of
>>>>> the active developers is to move, then the occaision should
>>>>> be used to consider the structure of the software in Goanna,
>>>>> what should be in, what shouldn't, what needs reviewing, what
>>>>> code is dead, etc., and to plan an announcement for a 1.0
>>>>> release.
>>>> For what it is worth, here are the reasons why I don't want to
>>>> move the Gobo project to Origo:
>>>> 
>>>> *) if we want Eiffel to be better known, I think that it is
>>>> better to be hosted with other non-Eiffel projects by well
>>>> known host rather than having all Eiffel projects segregated
>>>> into a ghetto. (The same applies to the choice of licenses by
>>>> the way, EiffelForum license vs. MIT/BSD...)
>>> That's true. If we want Origo to rock we will have to provide a
>>> way to connect it to traffic bringing sources.
>> 
>> In the meantime we host more than 450 projects - mainly non Eiffel
>> and non ETH. So Origo can not really be considered an Eiffel or ETH
>> ghetto anymore.
>> 
>> 
>>>> *) What are the guarantees that Origo will still work when Till
>>>>  will leave ETH? Or if/when Bertrand will leave ETH for greener
>>>>  pasture?
>>> If Origo is a success, I believe that the continued development
>>> will be ensured. But at the moment it is too early to say if it
>>> will be popular among developers. (it is with my students for now
>>> ;-) )
>> In the meantime we are working on long term ETH independent
>> financing of Origo. Furthermore I think we could give it a try to
>> move the goanna repository here and then move it back if really i
>> should be considered not good to have it hosted on Origo.
>> 
>> I see one argument for this:
>> 
>> It is a matter of a minute to make a svn dump and load that into
>> another svn server. So migrating the code to Origo or back to SF
>> would be really easy and we would not loose anything.
>> 
>>>> As you can see, these are only political reasons. I didn't
>>>> study the technical merits of one host compare to the other.
>>>> Another political reason that one might argue in favor of Origo
>>>> is that it is written in Eiffel and therefore it is our
>>>> interest to make it successful as a kind of killer application.
>>>> Decisions are never easy to make!
>>> It is indeed my hope to make Eiffel better known by showing Origo
>>> to the world, but of course the traffic and popularity of
>>> sourceforge is beneficial as well. My message before was because
>>> I couldn't access the SVN repository on sourceforge anymore, but
>>> I then found out that they had changed URL's - so that is solved.
>>> 
>> So to conclude I would like to ask you (the Goanna developers)
>> again if you could agree to hosting Goanna on Origo?
>> 
>> My main motivation is that I would like to improve the Goanna 
>> documentation, but I can't really be bothered to edit the html
>> pages of the Goanna site on Sourceforge, but would rather have the
>> wiki functionality of Origo.
>> 
>> Thanks for your comments,
>> 
>> Till

-- 
Till G. Bay
Software Engineering, ETH Zurich
http://se.inf.ethz.ch/people/bay

Re: [Goanna-developers] Sourceforge or Origo?

[Colin A. <col...@go...>]

Maybe we can get the best of both sites in this way:

1) Do the migration to Origo, making the documentation updates as you suggest.
2) Update all the front entrances to the goanna project on the
sourceforge site, indicating that the project has now moved to Origo.
But don't make this a simple indirection. Just have it as an
additional (but HIGHLY prominent) link. This way Goanna (and Eiffel)
will still be visible on the sourceforge site.

On 01/11/2007, Till G. Bay <til...@in...> wrote:
> Dear all -
>
> as Origo matures, I am posting a follow-up on my question about the
> possibility of moving Goanna to Origo.
>
> Till G. Bay wrote:
> > Eric Bezault wrote:
> >> Colin Paul Adams wrote:
> >>> I received a bounced message directed towards this list from
> >>> Till, saying that there was difficulty accessing the repo, and
> >>> asking if perhaps we should be using origo instead.
> >>>
> >>> My thoughts on this:
> >>>
> >>> 1) It might not be a bad idea. But what would the pros of using
> >>> origo be? An obvious con that occurs to me is that Origo is far
> >>> less well-known than Sourceforge. I don't suppose this really
> >>> matters though, if there are positive benefits from using origo.
> >>>
> >>> 2) If there are identifiable benefits, and the concensus of the
> >>> active developers is to move, then the occaision should be used
> >>> to consider the structure of the software in Goanna, what should
> >>> be in, what shouldn't, what needs reviewing, what code is dead,
> >>> etc., and to plan an announcement for a 1.0 release.
> >> For what it is worth, here are the reasons why I don't want to move
> >>  the Gobo project to Origo:
> >>
> >> *) if we want Eiffel to be better known, I think that it is better
> >> to be hosted with other non-Eiffel projects by well known host
> >> rather than having all Eiffel projects segregated into a ghetto.
> >> (The same applies to the choice of licenses by the way, EiffelForum
> >>  license vs. MIT/BSD...)
> >
> > That's true. If we want Origo to rock we will have to provide a way
> > to connect it to traffic bringing sources.
>
>
> In the meantime we host more than 450 projects - mainly non Eiffel and
> non ETH. So Origo can not really be considered an Eiffel or ETH ghetto
> anymore.
>
>
> >> *) What are the guarantees that Origo will still work when Till
> >> will leave ETH? Or if/when Bertrand will leave ETH for greener
> >> pasture?
> >
> > If Origo is a success, I believe that the continued development will
> > be ensured. But at the moment it is too early to say if it will be
> > popular among developers. (it is with my students for now ;-) )
>
> In the meantime we are working on long term ETH independent financing of
> Origo. Furthermore I think we could give it a try to move the goanna
> repository here and then move it back if really i should be considered
> not good to have it hosted on Origo.
>
> I see one argument for this:
>
> It is a matter of a minute to make a svn dump and load that into another
> svn server. So migrating the code to Origo or back to SF would be really
> easy and we would not loose anything.
>
> >> As you can see, these are only political reasons. I didn't study
> >> the technical merits of one host compare to the other. Another
> >> political reason that one might argue in favor of Origo is that it
> >> is written in Eiffel and therefore it is our interest to make it
> >> successful as a kind of killer application. Decisions are never
> >> easy to make!
> >
> > It is indeed my hope to make Eiffel better known by showing Origo to
> > the world, but of course the traffic and popularity of sourceforge is
> > beneficial as well. My message before was because I couldn't access
> > the SVN repository on sourceforge anymore, but I then found out that
> > they had changed URL's - so that is solved.
>
> So to conclude I would like to ask you (the Goanna developers) again if
> you could agree to hosting Goanna on Origo?
>
> My main motivation is that I would like to improve the Goanna
> documentation, but I can't really be bothered to edit the html pages of
> the Goanna site on Sourceforge, but would rather have the wiki
> functionality of Origo.
>
> Thanks for your comments,
>
>         Till
>
> --
> Till G. Bay
> Software Engineering, ETH Zurich
> http://se.inf.ethz.ch/people/bay
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Goanna-developers mailing list
> Goa...@li...
> https://lists.sourceforge.net/lists/listinfo/goanna-developers
>

Re: [Goanna-developers] Sourceforge or Origo?

[Till G. B. <til...@in...>]

Dear all -

as Origo matures, I am posting a follow-up on my question about the
possibility of moving Goanna to Origo.

Till G. Bay wrote:
> Eric Bezault wrote:
>> Colin Paul Adams wrote:
>>> I received a bounced message directed towards this list from 
>>> Till, saying that there was difficulty accessing the repo, and 
>>> asking if perhaps we should be using origo instead.
>>> 
>>> My thoughts on this:
>>> 
>>> 1) It might not be a bad idea. But what would the pros of using 
>>> origo be? An obvious con that occurs to me is that Origo is far 
>>> less well-known than Sourceforge. I don't suppose this really 
>>> matters though, if there are positive benefits from using origo.
>>> 
>>> 2) If there are identifiable benefits, and the concensus of the 
>>> active developers is to move, then the occaision should be used 
>>> to consider the structure of the software in Goanna, what should 
>>> be in, what shouldn't, what needs reviewing, what code is dead, 
>>> etc., and to plan an announcement for a 1.0 release.
>> For what it is worth, here are the reasons why I don't want to move
>>  the Gobo project to Origo:
>> 
>> *) if we want Eiffel to be better known, I think that it is better 
>> to be hosted with other non-Eiffel projects by well known host 
>> rather than having all Eiffel projects segregated into a ghetto. 
>> (The same applies to the choice of licenses by the way, EiffelForum
>>  license vs. MIT/BSD...)
> 
> That's true. If we want Origo to rock we will have to provide a way 
> to connect it to traffic bringing sources.


In the meantime we host more than 450 projects - mainly non Eiffel and
non ETH. So Origo can not really be considered an Eiffel or ETH ghetto
anymore.


>> *) What are the guarantees that Origo will still work when Till 
>> will leave ETH? Or if/when Bertrand will leave ETH for greener 
>> pasture?
> 
> If Origo is a success, I believe that the continued development will 
> be ensured. But at the moment it is too early to say if it will be 
> popular among developers. (it is with my students for now ;-) )

In the meantime we are working on long term ETH independent financing of
Origo. Furthermore I think we could give it a try to move the goanna
repository here and then move it back if really i should be considered
not good to have it hosted on Origo.

I see one argument for this:

It is a matter of a minute to make a svn dump and load that into another
svn server. So migrating the code to Origo or back to SF would be really
easy and we would not loose anything.

>> As you can see, these are only political reasons. I didn't study 
>> the technical merits of one host compare to the other. Another 
>> political reason that one might argue in favor of Origo is that it 
>> is written in Eiffel and therefore it is our interest to make it 
>> successful as a kind of killer application. Decisions are never 
>> easy to make!
> 
> It is indeed my hope to make Eiffel better known by showing Origo to 
> the world, but of course the traffic and popularity of sourceforge is
> beneficial as well. My message before was because I couldn't access
> the SVN repository on sourceforge anymore, but I then found out that
> they had changed URL's - so that is solved.

So to conclude I would like to ask you (the Goanna developers) again if
you could agree to hosting Goanna on Origo?

My main motivation is that I would like to improve the Goanna
documentation, but I can't really be bothered to edit the html pages of
the Goanna site on Sourceforge, but would rather have the wiki
functionality of Origo.

Thanks for your comments,

	Till

-- 
Till G. Bay
Software Engineering, ETH Zurich
http://se.inf.ethz.ch/people/bay

Re: [Goanna-developers] Sourceforge or Origo?

[Till G. B. <ba...@in...>]

Dear all -

Eric Bezault wrote:
> Colin Paul Adams wrote:
>> I received a bounced message directed towards this list from Till, saying
>> that there was difficulty accessing the repo, and asking if perhaps we
>> should be using origo instead.
>>
>> My thoughts on this:
>>
>> 1) It might not be a bad idea. But what would the pros of using origo
>>    be? An obvious con that occurs to me is that Origo is far less
>>    well-known than Sourceforge. I don't suppose this really matters
>>    though, if there are positive benefits from using origo.
>>
>> 2) If there are identifiable benefits, and the concensus of the active
>>    developers is to move, then the occaision should be used to
>>    consider the structure of the software in Goanna, what should be
>>    in, what shouldn't, what needs reviewing, what code is dead, etc.,
>>    and to plan an announcement for a 1.0 release.
> 
> For what it is worth, here are the reasons why I don't want to move
> the Gobo project to Origo:
> 
> *) if we want Eiffel to be better known, I think that it is better to
>     be hosted with other non-Eiffel projects by well known host rather
>     than having all Eiffel projects segregated into a ghetto. (The same
>     applies to the choice of licenses by the way, EiffelForum license
>     vs. MIT/BSD...)

That's true. If we want Origo to rock we will have to provide a way to
connect it to traffic bringing sources.

> *) What are the guarantees that Origo will still work when Till will
>     leave ETH? Or if/when Bertrand will leave ETH for greener pasture?

If Origo is a success, I believe that the continued development will be
ensured. But at the moment it is too early to say if it will be popular
among developers. (it is with my students for mow ;-) )

> As you can see, these are only political reasons. I didn't study the
> technical merits of one host compare to the other. Another political
> reason that one might argue in favor of Origo is that it is written
> in Eiffel and therefore it is our interest to make it successful as a
> kind of killer application. Decisions are never easy to make!

It is indeed my hope to make Eiffel better known by showing Origo to the
world, but of course the traffic and popularity of sourceforge is
beneficial as well.
My message before was because I couldn't access the SVN repository on
sourceforge anymore, but I then found out that they had changed URL's -
so that is solved.

Anyway - I am happy for every project hosted on Origo, but we haven't
made any official announcement yet because we're not really at the
functionnality we want to have yet.

Thanks, Till

Re: [Goanna-developers] Sourceforge or Origo?

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
> I received a bounced message directed towards this list from Till, saying
> that there was difficulty accessing the repo, and asking if perhaps we
> should be using origo instead.
> 
> My thoughts on this:
> 
> 1) It might not be a bad idea. But what would the pros of using origo
>    be? An obvious con that occurs to me is that Origo is far less
>    well-known than Sourceforge. I don't suppose this really matters
>    though, if there are positive benefits from using origo.
> 
> 2) If there are identifiable benefits, and the concensus of the active
>    developers is to move, then the occaision should be used to
>    consider the structure of the software in Goanna, what should be
>    in, what shouldn't, what needs reviewing, what code is dead, etc.,
>    and to plan an announcement for a 1.0 release.

For what it is worth, here are the reasons why I don't want to move
the Gobo project to Origo:

*) if we want Eiffel to be better known, I think that it is better to
    be hosted with other non-Eiffel projects by well known host rather
    than having all Eiffel projects segregated into a ghetto. (The same
    applies to the choice of licenses by the way, EiffelForum license
    vs. MIT/BSD...)

*) What are the guarantees that Origo will still work when Till will
    leave ETH? Or if/when Bertrand will leave ETH for greener pasture?

As you can see, these are only political reasons. I didn't study the
technical merits of one host compare to the other. Another political
reason that one might argue in favor of Origo is that it is written
in Eiffel and therefore it is our interest to make it successful as a
kind of killer application. Decisions are never easy to make!

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

[Goanna-developers] Sourceforge or Origo?

[Colin P. A. <co...@co...>]

I received a bounced message directed towards this list from Till, saying
that there was difficulty accessing the repo, and asking if perhaps we
should be using origo instead.

My thoughts on this:

1) It might not be a bad idea. But what would the pros of using origo
   be? An obvious con that occurs to me is that Origo is far less
   well-known than Sourceforge. I don't suppose this really matters
   though, if there are positive benefits from using origo.

2) If there are identifiable benefits, and the concensus of the active
   developers is to move, then the occaision should be used to
   consider the structure of the software in Goanna, what should be
   in, what shouldn't, what needs reviewing, what code is dead, etc.,
   and to plan an announcement for a 1.0 release.
-- 
Colin Adams
Preston Lancashire

Re: [Goanna-developers] string escape in xmlrpc

[Patrick R. <pa...@ta...>]

I added some code to GOA_XRPC_SCALAR_VALUE that does the escaping, I 
looked around the code but didn't find something I could reuse so I did 
a simple replace of the few characters that make trouble.

Regards,
Patrick
> it seems that there is no escaping for strings in xmlrpc requests and
> replies done. Did I miss something? What would be the best place to add
> this?
>   

[Goanna-developers] string escape in xmlrpc

[Patrick R. <pa...@ta...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

it seems that there is no escaping for strings in xmlrpc requests and
replies done. Did I miss something? What would be the best place to add
this?

Thanks and regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGgSQ0aA/ofYi4EMoRAqdlAJ0cT2+IwPww7CBud58rnJIsOy9SnwCgkMM9
3d4VU85YdDRY/UVjgVLG7qM=
=LdZQ
-----END PGP SIGNATURE-----

Re: [Goanna-developers] [eiffel_software] Large web applications

[Colin A. <col...@ho...>]

>From: javier hector <vrh...@ya...>

>* The application code is not transparent with the connector (FastCGI, 
>stand  alone , or  custom connector)

This is certainly something I have wanted to tackle for a long time, but I 
don't have the time.
It will require some significant restructuring, but it certainly ought to be 
possible (I envisage a command-line option when starting the server).

_________________________________________________________________
Solve the Conspiracy and win fantastic prizes.  
http://www.theconspiracygame.co.uk/

[Goanna-developers] Fwd: Re: [eiffel_software] Large web applications

[Neal L. <ne...@3d...>]

>
>Neal,
>
>I think that Goanna is a wonderful framework,  but in comparision 
>with ROR these are the disadvantages.
>
>* Create a new application with Goanna is more dificult.
>* The application code is not transparent with the connector 
>(FastCGI, stand  alone , or  custom connector)
>* If a need to talk with a Database I need to create a lot of code.
>
>Thanks
>Javier

[Goanna-developers] Fwd: Re: [eiffel_software] Large web applications

[Neal L. <ne...@3d...>]

>
>Neal,
>
>In my opinion these are the characteristics of ROR that seem to me=
 interesting
>
>Instant Gratification
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>When you install the Rails framework, you also get a new command-line
>tool, rails, which is used to construct each new=20
>Rails application that you write.
>
>Create new app example
>
>$ rails example
>$ cd example
>and you will see
>example directory
>
>README       Installation and usage information
>Rakefile         Build script
>app/               Model, View, and Controller files go here
>components/  Reusable components
>config/             Configuration and database connection parameters
>db/         Schema and migration information
>doc/        Autogenerated documentation
>lib/        Shared code
>log/       Logfiles produced by your application
>public/     Web-accessible directory. Your application runs from here
>script/     Utility scripts that are useful for developers
>test/       Unit, functional, and integration tests, fixtures, and mocks
>tmp/        Runtime temporary files
>vendor/     Imported code
>
>
>Testing
>=3D=3D=3D=3D
>then you can run the server  (WEBrick is a=20
>pure-Ruby web server that is distributed with Ruby , for development )
>
> >ruby script/server  (Defautl WEBrick)
>
>then you can test your sample application
>http://localhost:3000
>
>
>
>Convention over configuration:
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>Rails applications all have the same project=20
>structure, with directories to handle=20
>application code, database configuration, public=20
>static files, and scripts for managing Web=20
>servers and Web-based functional testing.
>
>
>Immediate feedback
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>With Rails, most of what you do can give you=20
>immediate feedback. Migrations can instantly=20
>show you changes after updates to your database.
>
>I think that the following articles can give you a better introduction
>http://www.onlamp.com/pub/a/onlamp/2006/12/14/revisiting-ruby-on-rails-revi=
sited.html
>http://www.onlamp.com/pub/a/onlamp/2007/01/05/revisiting-ruby-on-rails-revi=
sited-2.html
>http://www.slash7.com/articles/2005/01/24/really-getting-started-in-rails
>
>
>Thanks
>Javier
>
>Neal Lester <ne...@3d...> escribi=F3:
>At 06:13 AM 4/11/2007, you wrote:
> >Web Applications
> >I think that Eiffel need a framework like Ruby on Rails(Convention
> >over Configuration).
> >This framework could be done usign
> >-->Goanna
> >-->Gobo
> >-->Eposix
> >-->DAO (EiffelStore, ECLI, EPOM, etc)
> >-->Orhers
>
>Javier,
>
>What are the specific design features of ROR which you prefer over
>the Goanna Application library? I would appreciate as much detail as=
 possible.
>
>Thanks,
>
>Neal
>
>
>
>
>Pregunt=E1. Respond=E9. Descubr=ED.
>Todo lo que quer=EDas saber, y lo que ni imaginabas,
>est=E1 en Yahoo! Respuestas (Beta).
><http://ar.answers.yahoo.com>Probalo ya!

Re: [Goanna-developers] [eiffel_software] Large web applications

[javier h. <vrh...@ya...>]

javier hector <vrh...@ya...> escribió: Neal,

I think that Goanna is a wonderful framework,  but in comparision with ROR these are the disadvantages.

* Create a new application with Goanna is more dificult. 
* The application code is not transparent with the connector (FastCGI, stand  alone , or  custom connector) 
* If a need to talk with a Database I need to create a lot of code. 

Thanks
Javier
 

 

Neal Lester <ne...@3d...> escribió: At 06:13 AM 4/11/2007, you wrote:
>Web Applications
>I think that Eiffel need a framework like Ruby on Rails(Convention 
>over Configuration).
>This framework could be done usign
>-->Goanna
>-->Gobo
>-->Eposix
>-->DAO (EiffelStore, ECLI, EPOM, etc)
>-->Orhers

Javier,

What are the specific design  features of ROR which you prefer over 
the Goanna Application library? I would appreciate as much detail as possible.

Thanks,

Neal



           

---------------------------------
  Preguntá. Respondé. Descubrí.
  Todo lo que querías saber, y lo que ni imaginabas,
 está en Yahoo! Respuestas (Beta).
  Probalo ya! 

       
---------------------------------
 Preguntá. Respondé. Descubrí.
 Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
 Probalo ya! 

Re: [Goanna-developers] [eiffel_software] Large web applications

[javier h. <vrh...@ya...>]

javier hector <vrh...@ya...> escribió: Neal, 

In my opinion these are the characteristics of ROR that seem to me interesting

Instant Gratification
============
When you install the Rails framework, you also get a new command-line
tool, rails, which is used to construct each new Rails application that you write.

Create new app example

$ rails example
$ cd example
and you will see
example directory

README       Installation and usage information
Rakefile         Build script
app/               Model, View, and Controller files go here
components/  Reusable components
config/             Configuration and database connection parameters
db/         Schema and migration  information
doc/        Autogenerated documentation
lib/        Shared code
log/       Logfiles produced by your application
 public/     Web-accessible directory. Your application runs from here
script/     Utility scripts that are useful for developers
test/       Unit, functional, and integration tests, fixtures, and mocks
tmp/        Runtime temporary files
vendor/     Imported code

  
Testing 
====
then you can run the server  (WEBrick is a pure-Ruby web server that is distributed with Ruby , for development )

>ruby script/server  (Defautl WEBrick)

then you can test your sample application  
http://localhost:3000 



Convention over  configuration:
==================
Rails applications all have the same project structure, with directories to handle application code, database configuration, public static files, and scripts for managing Web servers and Web-based functional testing.


Immediate feedback
============= 
With Rails, most of what you do can give you immediate feedback. Migrations can instantly show you changes after updates to your database.


I think that the following articles can give you a better introduction
http://www.onlamp.com/pub/a/onlamp/2006/12/14/revisiting-ruby-on-rails-revisited.html
http://www.onlamp.com/pub/a/onlamp/2007/01/05/revisiting-ruby-on-rails-revisited-2.html
http://www.slash7.com/articles/2005/01/24/really-getting-started-in-rails


Thanks
Javier

Neal Lester <ne...@3d...> escribió: At 06:13 AM 4/11/2007, you wrote:
>Web Applications
>I think that Eiffel need a framework like Ruby on Rails(Convention 
>over Configuration).
>This framework could be done usign
>-->Goanna
>-->Gobo
>-->Eposix
>-->DAO (EiffelStore, ECLI, EPOM, etc)
>-->Orhers

Javier,

What are the specific design features of ROR which you prefer over 
the Goanna Application library? I would appreciate as much detail as possible.

Thanks,

Neal



           

---------------------------------
  Preguntá. Respondé. Descubrí.
  Todo lo que querías saber, y lo que ni imaginabas,
 está en Yahoo! Respuestas (Beta).
  Probalo ya! 

       
---------------------------------
 Preguntá. Respondé. Descubrí.
 Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
 Probalo ya! 

Re: [Goanna-developers] Problems with new new xml_document validation

[Stephan C. <cla...@st...>]

Hi Neal

I think I found the bug which caused the rejection of the empty element.
I'll commit the changes right after this mail.

The |= operator will have to wait until the weekend.

greets
Stephan




Neal Lester wrote:
> Hi Stephan,
>
> I've started testing the new xml authoring generation/xml validation code.
>
> I have a rnc which has an element:
>
> level_2_button = element standard_page:level_2_button { name, value, 
> display_value, tool_tip?, text_item? }
> display_value = attribute display_value { text }
>
> name and value are attributes declared in goa_common
> tool_tip and text_item are elements declared in goa_common
>
> if I call:
>
> start_level_2_button_element ("Name", "Value", "Display Value")
> end_current_element
>
> I get an exception although this element is permitted to be empty. 
> The generated validity statement looks like:
>
> level_2_button_content_validity: GOA_XML_ELEMENT_SCHEMA is
> 		-- Schema representing valid contents of a(n) level_2_button element
> 	once
> 		create Result.make (
> 			create {GOA_XML_SCHEMA_ELEMENT_CONJUNCTION}.make_required (
> 			<<
> 			create {GOA_XML_SCHEMA_ELEMENT}.make_optional (tool_tip_element_code),
> 			create {GOA_XML_SCHEMA_ELEMENT}.make_optional (text_item_element_code)
> 			>>)
> 			)
> 		end
>
> Shouldn't the conjunction also be make_optional?
>
> Also, it appears that using the |= operator no longer works when 
> combining schemas.  I noticed the template to deal with that in (I 
> think) flatten_2 was commented out.  I just removed the only place 
> I'm using that operator (you may have noticed todays change in 
> goa_common.rnc) so fixing this is a lower priority (if it won't be 
> done for a while we should update the documentation accordingly).
>
> Neal
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Goanna-developers mailing list
> Goa...@li...
> https://lists.sourceforge.net/lists/listinfo/goanna-developers
>
>   

Re: [Goanna-developers] [eiffel_software] Large web applications

[Neal L. <ne...@3d...>]

At 06:13 AM 4/11/2007, you wrote:
>Web Applications
>I think that Eiffel need a framework like Ruby on Rails(Convention 
>over Configuration).
>This framework could be done usign
>-->Goanna
>-->Gobo
>-->Eposix
>-->DAO (EiffelStore, ECLI, EPOM, etc)
>-->Orhers

Javier,

What are the specific design features of ROR which you prefer over 
the Goanna Application library? I would appreciate as much detail as possible.

Thanks,

Neal

[Goanna-developers] Problems with new new xml_document validation

[Neal L. <ne...@3d...>]

Hi Stephan,

I've started testing the new xml authoring generation/xml validation code.

I have a rnc which has an element:

level_2_button = element standard_page:level_2_button { name, value, 
display_value, tool_tip?, text_item? }
display_value = attribute display_value { text }

name and value are attributes declared in goa_common
tool_tip and text_item are elements declared in goa_common

if I call:

start_level_2_button_element ("Name", "Value", "Display Value")
end_current_element

I get an exception although this element is permitted to be empty. 
The generated validity statement looks like:

level_2_button_content_validity: GOA_XML_ELEMENT_SCHEMA is
		-- Schema representing valid contents of a(n) level_2_button element
	once
		create Result.make (
			create {GOA_XML_SCHEMA_ELEMENT_CONJUNCTION}.make_required (
			<<
			create {GOA_XML_SCHEMA_ELEMENT}.make_optional (tool_tip_element_code),
			create {GOA_XML_SCHEMA_ELEMENT}.make_optional (text_item_element_code)
			>>)
			)
		end

Shouldn't the conjunction also be make_optional?

Also, it appears that using the |= operator no longer works when 
combining schemas.  I noticed the template to deal with that in (I 
think) flatten_2 was commented out.  I just removed the only place 
I'm using that operator (you may have noticed todays change in 
goa_common.rnc) so fixing this is a lower priority (if it won't be 
done for a while we should update the documentation accordingly).

Neal

[Goanna-developers] Reliance on prefix order

[Colin P. A. <co...@co...>]

I noticed in the readme just published for the RELAX NG to Eiffel
generator the following:

> The transforms assume that the xslt processor will return namespace
>+   prefixes in the order declared in the grammar element (Saxon does).

That is a really bad reliance. It could very easily change to reverse
order, for instance.

Also, why the mention of Saxon? The Gobo Eiffel library ought to be
used by default by now.
-- 
Colin Adams
Preston Lancashire

[Goanna-developers] Custom errors/faults in xml rpc

[Patrick R. <pa...@ta...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

is there a good way to generate custom failures during an xmlrpc call
on the server side? E.g. the call should query some information from a
database but the database server is down.
What I did at the moment was to modify GOA_SERVER_PROXY to have a
last_failure STRING and in GOA_XMLRPC_SERVLET check if last_failure is
set and create a GOA_XRPC_FAULT for it. Is there a better way for this
or should errors be handled completely different?

Regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGAs/JaA/ofYi4EMoRAqPIAJ9ADbkOPorrpnVm5byuXihfi4AxPgCfQOKr
Ym/LBiZ5F0UCw7zG5+maq/w=
=OnT2
-----END PGP SIGNATURE-----

Re: [Goanna-developers] Happy Birthday Franck!

[Colin P. A. <co...@co...>]

>>>>> "Colin" == Colin Adams <col...@ho...> writes:

    Colin> I've made the necessary changes to
    Colin> XM_ATTRIBUTE_DEFAULT_FILTER, so it can now forward DTD
    Colin> events by calling:

    Colin> create filter.set_next (next_callback_filter)
    Colin> filter.set_next_dtd (next_dtd_filter)

Oops! I sent the message to the wrong list.
-- 
Colin Adams
Preston Lancashire

[Goanna-developers] Happy Birthday Franck!

[Colin A. <col...@ho...>]

I've made the necessary changes to XM_ATTRIBUTE_DEFAULT_FILTER, so it can 
now forward DTD events by calling:

create filter.set_next (next_callback_filter)
filter.set_next_dtd (next_dtd_filter)

_________________________________________________________________
Get Hotmail, News, Sport and Entertainment from MSN on your mobile.  
http://www.msn.txt4content.com/

[Goanna-developers] Bounced message from Till Bay

[Colin P. A. <co...@co...>]

The following message was posted by Till Bay yesterday, but bounced,
so I am re-posting it:

>From: "Till G. Bay" <til...@in...>
>Subject: Yaesockets obsolete
>To: goa...@li...
>Date: Thu, 11 Jan 2007 14:46:42 -0800

Dear all -

I hope to have caught all occurrences of YAESOCKETS in Goanna and Log4e
- however what is needed for the whole thing to work has not yet
surfaced in a pre release of eposix. For the few of us using Goanna at
the moment I thought it was OK if I pointed you to our patched eposix
that already has a socket multiplexer.

http://origo.ethz.ch/index.php/Goanna_and_Eposix_setup

hope not having caused too much trouble with that move, but we're six
people here working with it and it is just easier if the changes are in
the repository.

thanks and happy new year.

	Till

-- 
Colin Adams
Preston Lancashire

[Goanna-developers] A couple of fixes for Mac OS X

[Till G. B. <til...@in...>]

Dear all -

In case you were wondering what the check-ins I made today were supposed
to mean:

I am working on the mac and have a couple of patches to the build
infrastructure of Eposix to make it work with the mac. I will propose
these to Berend. The modified build files of Goanna are already prepared
for these modifications now.

I am also happy to say that thanks to Neal's help, Samuele Lucchini is
now able to do everything he needs for Origo. Thanks a lot. And happy
holidays to all,
	Till

-- 
Till G. Bay
Software Engineering, ETH Zurich
http://se.inf.ethz.ch/people/bay

Re: [Goanna-developers] new developer: Stephan Classen

[Colin A. <col...@ho...>]

Good news. Welcome aboard Stephan.

>From: Till Bay <ba...@in...>
>
>Dear all -
>
>as of today Stephan Classen is starting on a Goanna related semester
>thesis (the next 4 months) with me. He is building a Goanna based web
>application of our games page at ETH (http://games.ethz.ch).
>
>In parallel to this effort we hope that the work will contribute the
>following things to Goanna:
>* removing the yaesockets dependency that was already discussed a bit
>* fixing all non running examples
>* improving the Goanna web page and documentation
>
>I hope that all this is in the spirit of the project and would like to
>welcome Stephan!

_________________________________________________________________
Windows Live™ Messenger has arrived. Click here to download it for free! 
http://imagine-msn.com/messenger/launch80/?locale=en-gb