I'm not a able to get deeper in ticket #908 until the first week in March.
maybe anyone else could find some hints for invoking the little helper script for g.mkfontcap by the wingrass-installer with writing permissions in C:\Program Files\Grass65-svn?
best regards
Helmut
___________________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
I'm not a able to get deeper in ticket #908 until the first week in March.
maybe anyone else could find some hints for invoking the little helper script
for g.mkfontcap by the wingrass-installer with writing permissions in
C:\Program Files\Grass65-svn?
Since the bug is no blocker, let's go ahead and make RC6 in the beginning of
next week?
I'm not a able to get deeper in ticket #908 until the first week in March.
maybe anyone else could find some hints for invoking the little helper script
for g.mkfontcap by the wingrass-installer with writing permissions in
C:\Program Files\Grass65-svn?
Since the bug is no blocker, let's go ahead and make RC6 in the beginning of
next week?
The week is almost over... no feedback.
Any objections that I go ahead and package RC6?
sorry about my mixed up response about the problems vectors display when winGRASS is installed in C:\Program Files
- it was meant to be response to this message not the one about GUI
Helena
On Feb 26, 2010, at 4:31 AM, Markus Neteler wrote:
On Sat, Feb 20, 2010 at 7:27 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Sat, Feb 20, 2010 at 4:26 PM, Helmut Kudrnovsky <hellik@web.de> wrote:
hi,
I think we are very close with the g.mkfontcap and r.patch WinGrass bugs,
so we should wait for those to be confirmed fixed.
I'm not a able to get deeper in ticket #908 until the first week in March.
maybe anyone else could find some hints for invoking the little helper script
for g.mkfontcap by the wingrass-installer with writing permissions in
C:\Program Files\Grass65-svn?
Since the bug is no blocker, let's go ahead and make RC6 in the beginning of
next week?
The week is almost over... no feedback.
Any objections that I go ahead and package RC6?
OSGeo Google SoC application has been submitted, but the GRASS Ideas web page
looks unfinished, in particular there are no mentors signed up for the specific ideas -
so please sign up, edit, add, clarify the ideas so that it is ready
Unfortunately I won't have time to mentor for GRASS this year, so I
have only briefly looked at the ideas page. Perhaps the unfinished
ideas from previous years could be moved to the 2010 page?
Also what do you people think of a project to make vectors so that
they don't have to be all loaded into memory, would that be too big of
a task? Perhaps this has already been fixed in GRASS 7 (I know I
haven't followed up too closely with the progress). Is there some
GRASS 7 task which we could make into a SoC idea?
--Wolf
On Thu, Mar 11, 2010 at 20:28, Helena Mitasova <hmitaso@unity.ncsu.edu> wrote:
OSGeo Google SoC application has been submitted, but the GRASS Ideas web
page
looks unfinished, in particular there are no mentors signed up for the
specific ideas -
so please sign up, edit, add, clarify the ideas so that it is ready
OSGeo Google SoC application has been
submitted, but the GRASS Ideas web page
looks unfinished, in particular there are no mentors signed
up for the specific ideas -
so please sign up, edit, add, clarify the ideas so that it
is ready http://grass.osgeo.org/wiki/GRASS_SoC_Ideas
slowly it improves, but it needs a lot more!
(quality beats quantity..)
I think we need to eventually remove the sections that
don't have any ideas listed -
or to reformulate to e.g. "student ideas welcome"
eventually, but right now we should be in full brainstorming mode.
I made it look a bit less sparse now, but it still needs ideas and
volunteers :).
Unfortunately I won't have time to mentor for GRASS this year,
(and I can only at max co-mentor a possible wxGUI frontend to ps.map)
Perhaps the unfinished ideas from previous years could be moved to
the 2010 page?
mmm, I like to use the new year as an excuse to cull the old wishlists
and only promote the ones with champions (ie likely to find a mentor)
Also what do you people think of a project to make vectors so that
they don't have to be all loaded into memory, would that be too big of
a task? Perhaps this has already been fixed in GRASS 7 (I know I
haven't followed up too closely with the progress).
do you mean building the spatial index each time (already done by MarkusM)
or to deal with vectors with massive (>3m) numbers of features better
while still building topology?
Is there some GRASS 7 task which we could make into a SoC idea?
? better integration with PostGIS / Spatialite (SQLite's version of
PostGIS) ?
but I really worry about projects which need core design decisions made,
as the student wouldn't have the needed codebase and culture experience
for the result to get developer buy-in. I'd much rather them work on
things which were already long thought about and to some extent we know
how we want them done, we just haven't had the time to do them yet.
(and this Especially goes for inter-project proposals such as the carto lib)
looking at the ideas wiki I am wondering whether the mentors should be listed
for the tasks (wxnviz, psmap) rather than broad topics (wxgui, vector).
It seems to be somewhat confusing now.
I did not want to make the change as I was not sure about it
Helena
On Mar 12, 2010, at 9:13 AM, Hamish wrote:
Helena wrote:
OSGeo Google SoC application has been
submitted, but the GRASS Ideas web page
looks unfinished, in particular there are no mentors signed
up for the specific ideas -
so please sign up, edit, add, clarify the ideas so that it
is ready http://grass.osgeo.org/wiki/GRASS_SoC_Ideas
slowly it improves, but it needs a lot more!
(quality beats quantity..)
I think we need to eventually remove the sections that
don't have any ideas listed -
or to reformulate to e.g. "student ideas welcome"
eventually, but right now we should be in full brainstorming mode.
I made it look a bit less sparse now, but it still needs ideas and
volunteers :).