[kepler-dev] planned kepler-1.0.0alpha5 release

[Bertram Ludaescher]

Shawn Bowers writes:
 > 
 > Bertram,
 > 
 > I think these kind of additions would be good ... and the underlying 
 > code to do them exists (except for the ontology editing part; unless you 
 > just expose it as a text file). 

I think we should just do that: expose as a text file. But using
Sparrow syntax!

 > What doesn't exist are the gui 
 > components -- and some may require underlying changes to the ptolemy 
 > code itself.  I believe Chad is working on some of these issues right now.

I think a sparrow text window might be all that is needed. At least
initially.

 > On another note, we talked a bit on IRC a few days ago about some of the 
 > needed infrastructure within kepler to handle these changes.  One 
 > problem is that the only way to make an annotation, ontology change, or 
 > any other configuration in Kepler "last" is by checking in the changes 
 > to cvs.  

I'm not sure I understand. Why can't there be a start-up sequence in
which the system looks for user-specific init/config files, after
loading the version specific ones? For example, XEmacs does something
like that on start-up: first load the "default configs" (corresponding
what would be found in the release/cvs) then look for the "user
configs", e.g., at the the place defined by an environment
variable (if it is defined), or if such isn't defined, then at a
"user location" such as ~/.keplerrc 

I'm not sure what Ptolemy II does at start-up, but I wouldn't be
suprised if they'd let you do sth like that (and if they don't,
probably Kepler should do sth like that).

The big advantage of course would be that all user preferences,
configs, workflows, actors etc would "survive" an new Kepler install,
even if done "in-place".

 > This somewhat limits customization ... and is a larger issue 
 > that needs to be addressed.  Matt suggested using their approach in 
 > Morpho which involves copying files at startup, etc., which may be one 
 > way to do it.

I don't think copying is needed (see above)

Bertram

 > 
 > Shawn
 > 
 > 
 > 
 > Bertram Ludaescher wrote:
 > > Hi Matt:
 > > 
 > > A related question: I remember that at some point some Ptolemy actors
 > > were hidden (or otherwise disappeared from the Kepler actor tab). I
 > > assume they are still part of the Kepler distribution though, right?
 > > 
 > > Also: What are the plans for being able to edit actor annotations?
 > > (currently they seem to be "pseudo-hardwired", i.e., via some OWL-ishe
 > > files). As simple text-based form (just like the one for configuring
 > > ports or in fact one that links into that one) might do.
 > > 
 > > The ontology itself should be just a config file that can be changed
 > > via "Preferences" / "Options"..
 > > 
 > > Any comments?
 > > 
 > > Bertram
 > > 
 > > Matt Jones writes:
 > >  > Hi,
 > >  > 
 > >  > On our roadmap that we developed at the last Kepler meeting we said we 
 > >  > would try for an alpha 5 release by Feb 21 (see 
 > >  > http://kepler-project.org/Wiki.jsp?page=KeplerReleaseRoadmap&version=1). 
 > >  >   That hasn't happened but is probably still useful.  I talked with Dan 
 > >  > today, and we thought it would be good to go ahead with a release to try 
 > >  > to get some of the bug fixes and improvements that we've completed now 
 > >  > out there in a more accessible format.  So Dan is planning on pulling 
 > >  > the CVS HEAD on Friday Feb 25 and creating the alpha5 installers then. 
 > >  > If you have anything you want included in this release, please check it 
 > >  > into CVS by Thursday the 24th, and please try not to check in any 
 > >  > experimental code that is likely to break the trunk (use a branch instead).
 > >  > 
 > >  > A revised roadmap is here:
 > >  > 
 > >  > http://kepler-project.org/Wiki.jsp?page=KeplerReleaseRoadmap
 > >  > 
 > >  > The main differences from the previous roadmap version are that: 1) the 
 > >  > documentation framework isn't complete so has been moved to alpha6, and 
 > >  > 2) the R improvements are ongoing and so have been extended to alpha6. I 
 > >  > also added links to the bug lists for each milestone.  The alpha 6 
 > >  > release is slated for April 15th, 2005 (just prior to the SEEK and GEON 
 > >  > meetings and the Ptolemy/Kepler miniconference), and I think we should 
 > >  > try hard to make that deadline.
 > >  > 
 > >  > Cheers,
 > >  > Matt
 > >  > 
 > >  > -- 
 > >  > -------------------------------------------------------------------
 > >  > Matt Jones                                     jones at nceas.ucsb.edu
 > >  > http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
 > >  > National Center for Ecological Analysis and Synthesis (NCEAS)
 > >  > University of California Santa Barbara
 > >  > Interested in ecological informatics? http://www.ecoinformatics.org
 > >  > -------------------------------------------------------------------
 > >  > _______________________________________________
 > >  > kepler-dev mailing list
 > >  > kepler-dev at ecoinformatics.org
 > >  > http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
 > > 
 > > _______________________________________________
 > > kepler-dev mailing list
 > > kepler-dev at ecoinformatics.org
 > > http://www.ecoinformatics.org/mailman/listinfo/kepler-dev