Actually I'm in favor of getters and setters, XPath is so hellish
error prone that I would prefer that noone needs to touch it ;)
But I never really figured out if getters and setters are part of the
model of the tool in an MVC approach. Having Getters and Setters
would make it easier to crea
I'm +1 for removing placeholder models.
I also think that models usually shouldn't have setter/getter methods as
it adds code and the tools that use the models can generally set/get
using Xpath.
Steven M. Ottens wrote:
> In general I'm not in favor of shipping empty models that are merely
> pl
In going through these, there are a few empty model objects, where it is
planned (or hoped) that they will eventually be filled out with
getter/setter methods appropriate to that document type. Yes, they can
be replaced by the generic Model object, but I'll suggest these can be
kept for future
In general I'm not in favor of shipping empty models that are merely
placeholders for future models to come. On the other hand if there
are no placeholders, people will never know that these models are
there to be expanded. So if we keep them, we need to make clear that
they need work and p
On Jul 23, 2007, at 7:58 PM, Gertjan van Oosten wrote:
> As quoted from Steven M. Ottens:
>> Being archived:
>> /lib/model/Transaction.js MAP-261
>
> You're kidding, right? That one is definitely being used, even by
> the wfs-t
> demo!
Actually I wasn't, I'm a serious guy you know ;)
Anyway,
As quoted from Steven M. Ottens:
> Being archived:
> /lib/model/Transaction.js MAP-261
You're kidding, right? That one is definitely being used, even by the wfs-t
demo!
> As said before, this list isn't definitive, please comment on them in
> one of the (sub)subtasks of http://jira.codehaus.org/
Hi all,
here the list for /lib/tool, /lib/model and /lib/graphics
A clarification of the different states:
Need more info means that from the current information I cannot judge
what the file does and if it is compatible with MapPaneOL and/or is
still needed.
Being deprecated means that they stay
Mike Adair wrote:
> Steven,
> I'm having trouble figuring out which JIRA issue I should be
> commenting on. For the widgets, I'm looking at subtasks of issue
> number 264, is this correct?
That's correct. Map-264 contains all the /lib/widget files
The start issue is: http://jira.codehaus.org/bro
Steven,
I'm having trouble figuring out which JIRA issue I should be commenting
on. For the widgets, I'm looking at subtasks of issue number 264, is
this correct?
Mike
Steven M. Ottens wrote:
> Hi all,
>
> I've worked my way through the jira issues and came up with the
> following list of fil
Hi all,
I've worked my way through the jira issues and came up with the
following list of file in /lib/widget which need more information or can
be archived or deprecated.
I have been a bit harsh on the files, so I can imagine that not
everybody agrees with me. If you feel that a file is wrongl
Note meetings have changed to TUESDAY from now on.
Suggested agenda:
00 Introductions, roll call
05 Directories for languages (Gertjan)
20 Release progress
30 Technical Discussions
40 General Q&A
59 Topics for next meeting
00 Close
PlaceTime
SydneyTu 21:00
Amsterdam (Central European Time
Gertjan, that sounds logical.
I'll add it to the agenda.
Gertjan van Oosten wrote:
> Cameron,
>
> On tomorrow's meeting I'd like to discuss the place of the widgets texts
> within MapBuilder. Currently they are under the skin directory. This
> has the (huge) disadvantage that creating a new skin
Hi andrew,
There have been many changes between the last release and the current
state of trunk. We've completely overhauled the maprendering by
including openlayers as render-engine. This is why there hasn't been a
release for a long time. This integration has finished and we're now
gearing u
Hi all,
when do you plan to release next official version of MapBuilder 1.5? The
last one is marked as alpha1 an is more then half year old. I tried to
find some time plan on the web site but without success.
Thanks
Andrew
-
Cameron,
On tomorrow's meeting I'd like to discuss the place of the widgets texts
within MapBuilder. Currently they are under the skin directory. This
has the (huge) disadvantage that creating a new skin means copying all
widget texts *and maintaining them*. Even the trunk code only has
complet
Hi Cameron, PSC members
Cameron Shorter a écrit :
> Andreas, Olivier, Gertjan,
>
> The current Project Steering Committee have noticed your sustained
> contributions to Mapbuilder and would like to recognize your efforts
> by inviting you to join us on the Mapbuilder Project Steering
> Committe
Hi Chris,
As quoted from Christopher Schmidt <[EMAIL PROTECTED]>:
> I still recommend removing docbook-xsl from the mapbuilder svn repo --
Since docbook-xsl is now only used to generate the design docs, and
those are on the communitymapbuilder.org site, that part can be removed,
after which the w
17 matches
Mail list logo
