Re: [JPP-Devel] Hi all
Hallo Nils!
I had the very same problem with ColorThemingStyle.
To solve it you need to change the following two things
1. With lyrTest.addStyle(ctStyle) an _additional_ style is added. It's
better to modify the already
existing styles (OpenJUMP creates these automaticly during the creation
of the layer). This
is possible for instance for ColorThemingStyles using the method
ColorThemingStyle.get().
2. To map the attribute values to colors you need to define two maps. One
containing the colours for
the values and another one containing its labels. Use the methods
ColorThemingStyle
.setAttributeValueToBasicStyleMap(), resp.
ColorThemingStyle.setAttributeValueToLabelMap().
Here's my code (in Groovy):
def colorThemingStyle = ColorThemingStyle.get(layer)
colorThemingStyle.setAttributeName("ATTRIBUTE_NAME")
colorThemingStyle.setDefaultStyle(new BasicStyle(Color.gray))
colorThemingStyle.setAttributeValueToBasicStyleMap([
0: new BasicStyle(Color.green),
1: new BasicStyle(Color.red),
] as HashMap)
colorThemingStyle.setAttributeValueToLabelMap([
0: "Linked",
1: "Not linked",
] as HashMap)
colorThemingStyle.setEnabled(true)
layer.fireAppearanceChanged()
Hope this solves your problem :)
Greetings from Hannover,
Benjamin Gudehus
Hi all,
> I am using OJ as a platform for developing GIS-solutions in implementing
> OJ-Plugins.
> I am doing this for maybe one and a half year and first I would like to
> thank everybody who participates in developing OJ now and in the past!
>
> There is a lot of great work in the code and I've learned a lot out of
> it yet.
> Now my question:
> I want to change the style of some layers programmatically and my first
> approach is like this:
>
>
> Layer lyrTest = context.getLayerManager().getLayer("test");
> lyrTest.getBasicStyle().setEnabled(false);
> HashMap attributeToStyleMap = new HashMap();
> attributeToStyleMap.put(18, new BasicStyle(Color.red));
>
> attributeToStyleMap.put(19, new BasicStyle(Color.blue));
> attributeToStyleMap.put(20, new BasicStyle(Color.cyan));
> ColorThemingStyle ctStyle = new
> ColorThemingStyle("BGVNR",attributeToStyleMap,new BasicStyle(Color.gray));
>
> ctStyle.setEnabled(true);
> lyrTest.addStyle(ctStyle);
> lyrTest.fireAppearanceChanged();
>
> This example works fine and the LayerViewPanel shows the changed styles.
> But the OJ-standard-menu "Change styles" isn't updated (the colour
>
> theming isn't enabled and the Fill- and Line-Checkboxes are still set).
> How can I do that???
> I would be happy if anybody could help me!
> Nils
>
>
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Death of our wiki.
It looks like the easiest way to move to MediaWiki is to export to HTML and use: http://toolserver.org/~diberri/cgi-bin/html2wiki/index.cgi Larry On Thu, Sep 17, 2009 at 1:46 PM, Larry Becker wrote: > Not much help here either: > http://www.mediawiki.org/wiki/Manual:FAQ#Importing_from_other_types_of_wiki_software > > Larry > > > On Thu, Sep 17, 2009 at 1:41 PM, Larry Becker wrote: > >> I've maintained a MediaWiki once before. It is very robust. I like it, >> but it doesn't seem to import textile formatting. The only thing I could >> find is a bit of Python code to do some of the conversion at >> http://www.swaroopch.com/notes/Basecamp_to_MediaWiki >> >> def format_content(text): >> '''Given text in Textile syntax, convert to MediaWiki syntax.''' >> >> if text is None: >> return '' >> text = re.sub(r'"([^"]+)":([^\s]+)', r'[\2 \1]', text) # external link >> >> >> text = re.sub(r"(?:\*\*|__)(\w+)(?:\*\*|__)", r"'''\1'''", text) # bold >> >> >> text = re.sub(r"(?:\*|_)(\w+)(?:\*|_)", r"''\1''", text) # italics >> >> >> # TODO Convert links to Writeboards into internal links on this wiki page >> return text >> >> >> Larry >> >> >> On Thu, Sep 17, 2009 at 1:28 PM, Sunburned Surveyor < >> sunburned.surve...@gmail.com> wrote: >> >>> The MediaWiki looks nice Stefan. I think it may be a good option. >>> >>> Landon >>> >>> On Thu, Sep 17, 2009 at 11:25 AM, Stefan Steiniger >>> wrote: >>> > sorry for the many emails: >>> > >>> > but MediaWiki looks nice: >>> > >>> > >>> https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Main_Page >>> > >>> > could be the way to go. And at least people that are part of the SF >>> > project can write to it (which would be good start). >>> > >>> > stefan >>> > >>> > Stefan Steiniger wrote: >>> >> wow... there are quite a bit of features you can get now: >>> >> >>> >> . AN GuestbookGuest Book >>> >> . Bazaar Source Control >>> >> . CodeStriker Code Review >>> >> . CVS Source Control >>> >> . dotProject Project Management >>> >> . Gallery Image Gallery >>> >> . Git Source Control >>> >> . IdeaTorrent Idea Brainstorm >>> >> . LaconicaMicroblog >>> >> . LimeSurvey Survey >>> >> . MantisBTBug Tracking >>> >> . MediaWiki Wiki >>> >> . Mercurial Source Control >>> >> . phpBB Forum >>> >> . phpWebSite Content Management >>> >> . Piwik Web Analytics >>> >> . TaskFreak! Task Management >>> >> . TracWiki / Bug Tracking / Etc >>> >> . URL Shortening Administrative >>> >> . Wordpress Blogging >>> >> >>> >> from my perspective Trak is nice, but doesn't look very pleasing. >>> Maybe >>> >> I enable MediaWiki for testing? (If it doesn't have the SF header). >>> The >>> >> stats tool are nice too (piwiki) >>> >> >>> >> stefan >>> >> >>> >> edgar.sol...@web.de wrote: >>> >>> it is there, i have activated on a project of mine.. but haven't used >>> it yet >>> >>> You have to dig a bit, it is under 'project admin'->'features' .. >>> they >>> >>> also have wordpress >>> >>> >>> >>> .. ede >>> >>> >>> I got a message from sourceforge that project wikis should migrate >>> to TRAC >>> or MediaWiki, but I haven't seen any support for MediaWiki on SF >>> yet. Of >>> course, I can't find anything else either after their 'redesign'. >>> :-( >>> >>> Larry >>> >>> On Thu, Sep 17, 2009 at 9:52 AM, Sunburned Surveyor < >>> sunburned.surve...@gmail.com> wrote: >>> >>> >>> > Thanks for grabbing that back-up Jon! We really appreciate it. >>> > >>> > Stefan, >>> > >>> > What do you think about putting this zip up on the SourceForge site >>> for >>> > now? >>> > >>> > Any suggestions on what we do for a new wiki? Pedro has space, but >>> I >>> > don't know how he would feel about hosting our wiki software. >>> > I might be able to cough up some money for wiki hosting, if we >>> needed >>> > it. Wikidot appears pretty reasonable. $25 for a year for a pro >>> > account. I think I can handle that. >>> > >>> > Let me know what you guys think. >>> > >>> > SS >>> > >>> > On Thu, Sep 17, 2009 at 7:12 AM, Stefan Steiniger < >>> sst...@geo.uzh.ch> >>> > wrote: >>> > >>> >> thanks.. great! >>> >> >>> >> so we haven't lost anything then >>> >> stefan >>> >> >>> >> Jonathan Aquino schrieb: >>> >> >>> >>> OK I managed to keep it up long enough to export the pages in >>> Textile >>> >>> format: >>> >>> http://jonathanaquino.com/wiki-textile-2009-09-15-17-59-49.zip >>> >>> >>> >>> Jon >>> >>> >>> >>> >>> >>> >>> -Original Message- >>> From: Stefan Steiniger [mailto:sst...@geo.uzh.ch] >>> Sent: Wednesday, September 16, 2009 10:15 PM >>> To: OpenJump develop and use; Jonathan Aquino >>> Subject: Re: [JPP-Devel] Death of our wiki. >>> >>> >>
Re: [JPP-Devel] Death of our wiki.
Is there an easy way to get from textile to HTML? SS On Fri, Sep 18, 2009 at 2:38 PM, Larry Becker wrote: > It looks like the easiest way to move to MediaWiki is to export to HTML and > use: http://toolserver.org/~diberri/cgi-bin/html2wiki/index.cgi > > Larry > > On Thu, Sep 17, 2009 at 1:46 PM, Larry Becker > wrote: >> >> Not much help here either: >> http://www.mediawiki.org/wiki/Manual:FAQ#Importing_from_other_types_of_wiki_software >> >> Larry >> >> On Thu, Sep 17, 2009 at 1:41 PM, Larry Becker >> wrote: >>> >>> I've maintained a MediaWiki once before. It is very robust. I like it, >>> but it doesn't seem to import textile formatting. The only thing I could >>> find is a bit of Python code to do some of the conversion at >>> http://www.swaroopch.com/notes/Basecamp_to_MediaWiki >>> >>> def format_content(text): >>> '''Given text in Textile syntax, convert to MediaWiki syntax.''' >>> >>> if text is None: >>> return '' >>> text = re.sub(r'"([^"]+)":([^\s]+)', r'[\2 \1]', text) # external >>> link >>> >>> text = re.sub(r"(?:\*\*|__)(\w+)(?:\*\*|__)", r"'''\1'''", text) # >>> bold >>> >>> text = re.sub(r"(?:\*|_)(\w+)(?:\*|_)", r"''\1''", text) # italics >>> >>> # TODO Convert links to Writeboards into internal links on this wiki >>> page >>> return text >>> >>> Larry >>> >>> On Thu, Sep 17, 2009 at 1:28 PM, Sunburned Surveyor >>> wrote: The MediaWiki looks nice Stefan. I think it may be a good option. Landon On Thu, Sep 17, 2009 at 11:25 AM, Stefan Steiniger wrote: > sorry for the many emails: > > but MediaWiki looks nice: > > > https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Main_Page > > could be the way to go. And at least people that are part of the SF > project can write to it (which would be good start). > > stefan > > Stefan Steiniger wrote: >> wow... there are quite a bit of features you can get now: >> >> . AN Guestbook Guest Book >> . Bazaar Source Control >> . CodeStriker Code Review >> . CVS Source Control >> . dotProject Project Management >> . Gallery Image Gallery >> . Git Source Control >> . IdeaTorrent Idea Brainstorm >> . Laconica Microblog >> . LimeSurvey Survey >> . MantisBT Bug Tracking >> . MediaWiki Wiki >> . Mercurial Source Control >> . phpBB Forum >> . phpWebSite Content Management >> . Piwik Web Analytics >> . TaskFreak! Task Management >> . Trac Wiki / Bug Tracking / Etc >> . URL Shortening Administrative >> . Wordpress Blogging >> >> from my perspective Trak is nice, but doesn't look very pleasing. >> Maybe >> I enable MediaWiki for testing? (If it doesn't have the SF header). >> The >> stats tool are nice too (piwiki) >> >> stefan >> >> edgar.sol...@web.de wrote: >>> it is there, i have activated on a project of mine.. but haven't >>> used it yet >>> You have to dig a bit, it is under 'project admin'->'features' .. >>> they >>> also have wordpress >>> >>> .. ede >>> I got a message from sourceforge that project wikis should migrate to TRAC or MediaWiki, but I haven't seen any support for MediaWiki on SF yet. Of course, I can't find anything else either after their 'redesign'. :-( Larry On Thu, Sep 17, 2009 at 9:52 AM, Sunburned Surveyor < sunburned.surve...@gmail.com> wrote: > Thanks for grabbing that back-up Jon! We really appreciate it. > > Stefan, > > What do you think about putting this zip up on the SourceForge > site for > now? > > Any suggestions on what we do for a new wiki? Pedro has space, but > I > don't know how he would feel about hosting our wiki software. > I might be able to cough up some money for wiki hosting, if we > needed > it. Wikidot appears pretty reasonable. $25 for a year for a pro > account. I think I can handle that. > > Let me know what you guys think. > > SS > > On Thu, Sep 17, 2009 at 7:12 AM, Stefan Steiniger > > wrote: > >> thanks.. great! >> >> so we haven't lost anything then >> stefan >> >> Jonathan Aquino schrieb: >> >>> OK I managed to keep it up long enough to export the pages in >>> Textile >>> format: >>> http://jonathanaquino.com/wiki-textile-2009-09-15-17-59-49.zip >>> >>> Jon >>> >>> >>> -O
[JPP-Devel] Question on LayerPrinter2 and on OpenJUMPConfiguration
I have been running around the source code in the core over the last couple of days, and I had questions on a couple of classes I found there. - What is the purpose of the LayerPrinter2 class? I didn't find any documentation on in the source code or Javadoc that indicated what it did that was significantly different from the LayerPrinter class? - What is the purpose of the OpenJUMPConfiguration class? Is it really needed? Can't we have OpenJUMP plug-ins loaded via the standard mechanism in by placing a JAR file in the lib/ext directory? How is the functionality of the OpenJUMPConfiguration class duplicated by the plug-in XML file we use? Thanks for any info. Landon -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Death of our wiki.
Got it. On Fri, Sep 18, 2009 at 2:51 PM, Larry Becker wrote: > Just go to the wiki and export in HTML. > > On Fri, Sep 18, 2009 at 4:47 PM, Sunburned Surveyor > wrote: >> >> Is there an easy way to get from textile to HTML? >> >> SS >> >> On Fri, Sep 18, 2009 at 2:38 PM, Larry Becker >> wrote: >> > It looks like the easiest way to move to MediaWiki is to export to HTML >> > and >> > use: http://toolserver.org/~diberri/cgi-bin/html2wiki/index.cgi >> > >> > Larry >> > >> > On Thu, Sep 17, 2009 at 1:46 PM, Larry Becker >> > wrote: >> >> >> >> Not much help here either: >> >> >> >> http://www.mediawiki.org/wiki/Manual:FAQ#Importing_from_other_types_of_wiki_software >> >> >> >> Larry >> >> >> >> On Thu, Sep 17, 2009 at 1:41 PM, Larry Becker >> >> wrote: >> >>> >> >>> I've maintained a MediaWiki once before. It is very robust. I like >> >>> it, >> >>> but it doesn't seem to import textile formatting. The only thing I >> >>> could >> >>> find is a bit of Python code to do some of the conversion at >> >>> http://www.swaroopch.com/notes/Basecamp_to_MediaWiki >> >>> >> >>> def format_content(text): >> >>> '''Given text in Textile syntax, convert to MediaWiki syntax.''' >> >>> >> >>> if text is None: >> >>> return '' >> >>> text = re.sub(r'"([^"]+)":([^\s]+)', r'[\2 \1]', text) # external >> >>> link >> >>> >> >>> text = re.sub(r"(?:\*\*|__)(\w+)(?:\*\*|__)", r"'''\1'''", text) # >> >>> bold >> >>> >> >>> text = re.sub(r"(?:\*|_)(\w+)(?:\*|_)", r"''\1''", text) # italics >> >>> >> >>> # TODO Convert links to Writeboards into internal links on this >> >>> wiki >> >>> page >> >>> return text >> >>> >> >>> Larry >> >>> >> >>> On Thu, Sep 17, 2009 at 1:28 PM, Sunburned Surveyor >> >>> wrote: >> >> The MediaWiki looks nice Stefan. I think it may be a good option. >> >> Landon >> >> On Thu, Sep 17, 2009 at 11:25 AM, Stefan Steiniger >> >> wrote: >> > sorry for the many emails: >> > >> > but MediaWiki looks nice: >> > >> > >> > >> > https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Main_Page >> > >> > could be the way to go. And at least people that are part of the SF >> > project can write to it (which would be good start). >> > >> > stefan >> > >> > Stefan Steiniger wrote: >> >> wow... there are quite a bit of features you can get now: >> >> >> >> . AN Guestbook Guest Book >> >> . Bazaar Source Control >> >> . CodeStriker Code Review >> >> . CVS Source Control >> >> . dotProject Project Management >> >> . Gallery Image Gallery >> >> . Git Source Control >> >> . IdeaTorrent Idea Brainstorm >> >> . Laconica Microblog >> >> . LimeSurvey Survey >> >> . MantisBT Bug Tracking >> >> . MediaWiki Wiki >> >> . Mercurial Source Control >> >> . phpBB Forum >> >> . phpWebSite Content Management >> >> . Piwik Web Analytics >> >> . TaskFreak! Task Management >> >> . Trac Wiki / Bug Tracking / Etc >> >> . URL Shortening Administrative >> >> . Wordpress Blogging >> >> >> >> from my perspective Trak is nice, but doesn't look very pleasing. >> >> Maybe >> >> I enable MediaWiki for testing? (If it doesn't have the SF >> >> header). >> >> The >> >> stats tool are nice too (piwiki) >> >> >> >> stefan >> >> >> >> edgar.sol...@web.de wrote: >> >>> it is there, i have activated on a project of mine.. but haven't >> >>> used it yet >> >>> You have to dig a bit, it is under 'project admin'->'features' .. >> >>> they >> >>> also have wordpress >> >>> >> >>> .. ede >> >>> >> I got a message from sourceforge that project wikis should >> migrate >> to TRAC >> or MediaWiki, but I haven't seen any support for MediaWiki on SF >> yet. Of >> course, I can't find anything else either after their >> 'redesign'. >> :-( >> >> Larry >> >> On Thu, Sep 17, 2009 at 9:52 AM, Sunburned Surveyor < >> sunburned.surve...@gmail.com> wrote: >> >> >> > Thanks for grabbing that back-up Jon! We really appreciate it. >> > >> > Stefan, >> > >> > What do you think about putting this zip up on the SourceForge >> > site for >> > now? >> > >> > Any suggestions on what we do for a new wiki? Pedro has space, >> > but >> > I >> > don't know how he would feel about hosting our wiki software. >> > I might be able to cough up some money for wiki hosting, if we >> > needed >> > it. Wikidot appears pretty reasonable. $25 for a year for a pro >> >
