--- Log opened Thu Dec 08 00:00:19 2005 00:46 >> #punt-dev JOIN nhv (n=nhv@dsl0-1.cape.com) 03:32 >> SignOff: CIA-5 () [#punt-dev] 03:32 >> #punt-dev JOIN CIA-5 (i=cia@flapjack.navi.cx) 10:24 >> #punt-dev JOIN mazop (n=mazop@dsl-155-63.utaonline.at) 13:24 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 13:24 >> #punt-dev JOIN nhv_ (n=nhv@dsl0-1.cape.com) 13:25 >> nhv_ is now known as nhv 15:56 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 15:57 >> #punt-dev JOIN nhv_ (n=nhv@dsl0-1.cape.com) 16:35 >> nhv_ is now known as nhv 16:35 < CIA-5> mashiharu * Punt/PluginSDK/Configuration/SettingsBase.cs: Fixes failure to save settings when the previous load failed (due to a corrupt/empty settings file) 16:49 < CIA-5> mashiharu * Punt/GNU.Gettext/GNU.Gettext.cs: Stops exception from being thrown when language dll is missing. 16:56 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 16:56 >> #punt-dev JOIN nhv_ (n=nhv@dsl0-1.cape.com) 16:58 >> nhv_ is now known as nhv 17:01 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 17:02 >> #punt-dev JOIN nhv_ (n=nhv@dsl0-1.cape.com) 17:02 >> nhv_ is now known as nhv 17:17 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 17:18 >> #punt-dev JOIN nhv_ (n=nhv@dsl0-1.cape.com) 17:19 >> nhv_ is now known as nhv 17:40 >> SignOff: nhv ("ChatZilla 0.9.61 [Mozilla rv:1.7.12/20050915]") [#punt-dev] 18:30 >> #punt-dev JOIN nhv (n=nhv@dsl0-1.cape.com) 18:30 >> #punt-dev PART mazop (n=mazop@dsl-155-63.utaonline.at) () 18:44 >> dpatton is now known as dpatton_away 19:45 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 19:48 >> dpatton_away is now known as dpatton 19:48 >> #punt-dev JOIN nhv__ (n=nhv@dsl0-1.cape.com) 20:57 < CIA-5> mashiharu * Punt/ (2 files in 2 dirs): Restored previous formatting (spaces -> tabs) 21:09 >> nhv__ is now known as nhv 21:43 < CIA-5> mashiharu * Punt/PluginSDK/Configuration/SettingsBase.cs: Removed left behind comment 22:08 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 22:09 >> #punt-dev JOIN nhv__ (n=nhv@dsl0-1.cape.com) 22:09 >> nhv__ is now known as nhv 22:25 >> SignOff: nhv (Read error: 104 (Connection reset by peer)) [#punt-dev] 22:25 >> #punt-dev JOIN nhv__ (n=nhv@dsl0-1.cape.com) 22:31 >> nhv__ is now known as nhv 23:06 < CIA-5> dpatton * Punt/GNU.Gettext/GNU.Gettext.cs: Update comments(and minor code update) for prior code change. 23:11 < adamhill_work> i just posted this over in WW - do you guys have any opinions? 23:11 < adamhill_work> [17:12] looks like I am going to officially add network loadable config files (starting with /Images) i was thinking of 1) a single element in a local XML file that points to the network resource or 2) a single file that points to all of the network available files or 3) a new file in the /NASA/WW/ directory that points to a #2 via URL (static or dynamic) 23:11 < adamhill_work> [17:13] after this is working I am going to add a tag to the schema for layers 23:11 < adamhill_work> [17:14] any opinons on 1 2 or 3? 23:20 * mashi is confused 23:20 < mashi> maybe something like what they do in Google Earth? 23:21 < mashi> file with 1 or more urls in it? 23:28 >> SignOff: adamhill_work ("CGI:IRC (Ping timeout)") [#punt-dev] 23:32 >> #punt-dev JOIN adamhill_work (n=86a3fd7e@70.84.174.194) 23:35 >> #punt-dev JOIN adamhill_worlk (n=86a3fd7e@70.84.174.194) 23:35 < adamhill_worlk> mashi: that is #2 23:37 < adamhill_worlk> we have the added burden of wanting to 'push' new lists of layers out to clients as well from the network (maybe even common config and other directories in the end) 23:37 < dpatton> adamhill_worlk: there you go again with the multiple IRC nicknames that make it hard for others! ;-) 23:37 >> SignOff: adamhill_work ("CGI:IRC (Ping timeout)") [#punt-dev] 23:38 < dpatton> what do you mean by "the network"? 23:38 >> adamhill_worlk is now known as adamhill_work 23:38 < adamhill_work> local WAN or just simple HTTP 23:40 < dpatton> local WAN is simple - just configure Punt to use a network drive location for the config files 23:46 < adamhill_work> i know how to to that easily enough, but they dont have pemanently assigned Network drive letters here, but they do have an good HTTP based deployment/app/resource infrastructure here 23:49 < dpatton> I haven't thought about it, but my first thought is to always try and use existing standards, so I'd begin by seeing if something like WFS GetCapabilities could be adapted, and if not, at least pattern my solution after something like that --- Log closed Fri Dec 09 00:00:48 2005