On Tue, 2010-03-23 at 20:55 +0100, HB-GRAL wrote:
> Geoff McLane schrieb:
> > But his good work _IS_ being used, extensively -
> > 1 left TOC
> > 2 CSS design
> > 3 XHTML 1.0
> > 
> > I have added a little more today...
> >  http://geoffair.net/fg/site 
> > including a bottom TOC - presently not quite the
> > same as the left, but it will be...
> 
> Geoff,
> I am actually not pointing to the work you did. And I am not pointing to 
> your design elements.
> 
> > 
> > There does not seem any need to go totally Googly
> > when all that Pete has done can be done to the
> > current site, in an incremental page-by-page way...
> >
> 
> No.
> 
> Once we have to finish this contradictory page-by-page way. It is not a 
> problem of Googly or not. What Pete bring to us can run on every server 
> - also without the Google API.
> 
> The proposal from Pete includes a real change. His solution is a 
> state-of-the-art Open Source Website and not a proprietary hand-driven 
> Web-link-page with own standards. Pete makes use of code and standards 
> which are open in any direction and which invites other developers to 
> work on this project. He made a clever bridge to all the stuff around. 
> And of course - his page can be maintained by every Webmaster.
> 
> What he has done is that kind of simple and modern solutions which runs 
> on every platform and with every front-end (and can -BTW- also integrate 
> every hand-driven out-of-googly-style-html-page you want). Maybe he used 
> the Google API to show a new track but I think he did not want to 
> discuss about Google-Or-Not-To-Google.
> 
> So what is the real reason that we are not using such professional 
> contribution at all? Why are we going one step forward and then 10 miles 
> backwards?
> 
> - Yves
> 

I do not want to continue to labor the point on this, but
one last try ;=))

As Pete asked back on Feb 13 - Who is the "active" developer...
and he got an answer of sorts - maybe the name which can be read
at the bottom of the main site page ;=)) You could also do a
WHOIS search on the domain 'flightgear.org'...

As far as I know, the English site is _NOT_ open to other 
maintainers, web-masters - full stop! And that includes the
'www' repository... But by the same token the site maintainer
does read and watch for site suggestions, fixes, changes, 
etc... and acts upon them as time permits... as seen with
the Wiki link fix in progress...

So our _ONLY_ path is to make such suggestions, as Pete has
done on the Google app/Django engine, and as I, using MS VWD,
and others have done, and are continuing to do... as you
know several of us have our own sites, or sub-sites 
_DEDICATED_ to FG...

And we have the French, Portuguese, Japanese, Russian, 
(Spanish seems missing now?) sites - each of these are 
run using the 'technology' liked, preferred by the respective
owners... php/wiki/CMS/whatever, be it by 'hand' or with
a shovel ;=))

So what exactly are you asking? If you want to take over
the main English site, or at least open it to other
web-masters, then you can continue to press for that, 
but good luck! I will back the OWNER ;=))

Pete's example copied some pages from the current site,
and it got some brief rave reviews, but it is VERY incomplete,
so we do not know what he intends for the rest of the 
site pages... the rest of the links... my last count,
of the www repo was over 200 pages, and it too seems
missing some later updates (at least of about a week ago)...

And he left out the Google ads. How is he going to fit
these necessary evils into the site? Positioning and
quantity? Ideas on doing this and maintaining his current
very clean look, which I like, while keeping the ads
prominent enough to be of some use, would be very, very
welcome...

He added some new things, which is great, like the mp server
status, but assume this depends on the python to get information,
so this may not be portable, but would certainly like to 
incorporate this in my example also, if possible... How
to do it is the question?

So I would encourage you, Pete and others, through collaboration
with others, if desired, and/or through cvs/git usage, to
continue in this very worthy endeavor... and I would certainly
contribute, if given commit rights...

Even if nothing is taken from it, it provides another 
flightgear information center... which is beneficial...
but some ideas have been taken from it already, at least 
in my examples...

Now whether using the Google advertising revenue toys is more
'professional' than what - a 'proprietary hand-driven 
Web-link-page with own standards' - is a mute point. Both
produce 'web-link-pages' ;=))

Yes, Pete, we _ARE_ replicating work, but the more 'examples'
the better it seems to me... We _DO_ want to encourage Curt
to lift the site out of the 'so last century' as your
nephew put it, but we should do that by encouragement,
plentiful examples, good ideas, etc ;=))

So again, we should consider who OWNS the site, and fully
RESPECT what he might want, and not INSIST on what we 
want to see... but at the same time freely offer what we
would like to see...

Just an opinion. Regards,

Geoff.



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to