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

[Antony M. \(e. associates\) <ant...@et...>]

> -----Original Message-----
> From: co...@go...
> 
> Hey Antony,
> I was hoping you'd show up here :)

[Antony Marcano] Glad to oblige  :-)

> 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.

[Antony Marcano] Cool! Look forward to reading about it

> 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).

[Antony Marcano] Fair enough. 

> 
> 
> > 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.

[Antony Marcano] That's why I tried to start a list of categories to help
the short list (see previous e-mail).

 
> 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.

[Antony Marcano] Sounds like a plan. Perhaps, if we get a short-list, we
might then be able to spike a couple of approaches to get a better feel.

> 
> 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.

[Antony Marcano] Cool... if nothing else it prompted this discussion... If I
am honest, I am pushed to the limit in my day-to-day life at the moment but
happy to throw my 2 pence/cents worth in once in a while if it helps in any
small way.

Antony