Re: [OpenSTA-devel] Alternate GUI for OpenSTA?

[<co...@go...>]

Hey Antony,
I was hoping you'd show up here :)

> Dan and I discussed this at length in Hebden Bridge and I believe that it
> has to be the next big step! 

good to see we have early concensus.


> I'd like to take a look at what you've done but so short of time it would be
> really hard to fit it in... 

Well I am writing a document that goes into some detail on what I have done so
far.. basically I have had 2 marathon hacking weekends working on this, and
thats all.  It wasn't until 2 night ago that I even realized the stuff I'm
working on was applicable for use with OpenSTA.


> So, when you say "dynamic" what do you mean? As in dynamic typing or
> interpreted or just one that has an active community?

I meant in terms of dynamically typed and interpreted (though the definition of
"interpreted" and "compiled" is so blurred these days i'm not sure that even
means anything).


> I'd encourage choosing the language carefully, however. It should be based 
> on the best one for the task. If Python is the language then great! But it
> shouldn't be based on familiarity...

absolutely.. if others have ideas, I'd love to discuss them.   I have lots of
ideas regarding language selection and would happy to elaborate on my
thoughts.
 

> I'd encourage looking at the features we want and start - one by one -
> implementing enough of the GUI, intermediate layers and Bridges (as in
> Bridge Design Pattern) for the core to support each feature (i.e. using an
> Agile approach).


well.. right now as far as I can tell, the developer community is mostly dormant
except for a trickle of bug reports and patches.. nothing is really going on (or
has anything beyond the opensta-devel discussions been done?).  So, if a process
of language selection and architecture is done.. who is willing to implement the
chosen design?  If people are out there watching this list and want to get
involved, please speak up.  I'm sure we all have our ideas about languages and
methodologies and how development should be done.  We went through that
excersize a few years back but nothing much came of it.  Perhaps things have
changed and it is worthwhile to explore again.  I would be happy to participate
in that process.  However, once that concludes, people need to throw down and
start writing code... we never made it there last time.  

What I am saying is that I have something built.. working code.  Whether or not
this is an implementation that others want to collaborate on and extend.. or
feel should be part of the future of OpenSTA.. is another story :)  I am
working on something unrelated to OpenSTA and will have a a full GUI framework
for parsing logs, creating time series, running numerical calculations, and
graphic output.  I was able to adapt it to work with OpenSTA timer logs in < 10
lines of code.  So this is going to be available..  and it's in Python ;)   sort
of independent to discussions by the opensta-devel community.


-Corey Goldberg
 www.goldb.org

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.