[Viking-devel] Plans for 1.0

[Guilhem Bonnefille]

Hi all,

There are a lot of good patches all around improving or adding
features to viking. But currently, I want to release a stable 1.0
before we merge these patches. Before releasing 1.0, there are some
features I want to check.

The first one is auto-refresh feature.

This feature, based on if-modified HTTP header, is quite old now. It
was introduced for OpenStreetMap servers. Since we added this feature,
Mapnik servers evolved to use an other system: Etag HTTP header. Some
patches for this are pending on the Jocelyn's Git repo.
http://github.com/jocelynj/viking/tree/etag

Can tester give an eye on this and return feedback on this list, please?
I think it could be usefull to integrate this feature as it fixes the
auto-refresh feature for OSM server.

The other one is the exit feature.

Currently, Ctrl-W and Ctrl-Q have strange behaviour. This is mainly
because viking is (still) not able to decided if document worth a save
or not. We already discuss about this, but it seems that nobody find
time to address this issue.

Someone interested? Or should I just ignore this?


Please, help me to close these two issue and I promise to release the
most-expected 1.0 release in following weeks. And then, we will
integrate all fantastic and waiting patches.

PS: if you have other really important change, just refresh my mind, please.
-- 
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Re: [Viking-devel] Plans for 1.0

[Greg Troxel]

The release plan sounds good.  I've been meaning to try out all the
rnorris topic branches (and I think his plan of having a bunch of
independent topic branches to be merged is exactly right) but haven't
had time.  But, I think it makes sense to get a 1.0 out and then get
most/all of those integrated, plus changes from other people, and then
have a second stabilization period before 1.1.  There's no rule that
says 1.1 can't follow in a few months.



  Currently, Ctrl-W and Ctrl-Q have strange behaviour. This is mainly
  because viking is (still) not able to decided if document worth a save
  or not. We already discuss about this, but it seems that nobody find
  time to address this issue.

  Someone interested? Or should I just ignore this?

This isn't a regression from the past - it's just still very odd.

If someone has time, I would make ^W close one window and ^Q exit, and
both of them do a popup that says document may or may not have been
modified with discard save cancel.  Sort of what you would do if you
knew it was modified, but always.

After thinking a bit I'm inclined to release 1.0 without changing this.
It feels like an intermediate solution is just a mess.





pgpWZTgKIiqQv.pgp
Description: PGP signature
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/