[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dash-dev] How to (or not to) develop on the dashboard commits explorer
|
No... that's why I develop locally and commit changes to CVS in order
to verify the SQL works. But UI and parser stuff can be done locally.
And, for extra credit, you can code your web app so that if the SQL
connection fails, the fallback is to get data from the web API. Works
like a charm... assuming the web API exists and produces the same data
as the web app. For example, see
dashboard/commits/web-{api,app}/commit-count-loc.php and
commit-common.inc.php.
Nick
On Feb 5, 2008 1:15 AM, Bjorn Freeman-Benson
<bjorn.freeman-benson@xxxxxxxxxxx> wrote:
>
> If you can get the pages to run locally, sure. But I can't because I don't
> have a copy of the commits database on my local machine. Do you?
>
>
> Nick Boldt wrote:
> What about the process of developing locally, checking in changes to
> CVS, and using http://dash.eclipse.org/deploy/ to update from cvs?
>
>
>
> --
> [end of message]
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dash-dev
>
>
