This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 56738 - [41cat] Xml syntax coloring doesn't work after import from 4.0
Summary: [41cat] Xml syntax coloring doesn't work after import from 4.0
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Text-Edit (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Marek Fukala
URL:
Keywords:
: 57964 59674 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-21 14:10 UTC by marcpaes
Modified: 2007-09-25 01:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Config (81.86 KB, application/x-compressed)
2005-03-21 14:33 UTC, Roman Strobl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marcpaes 2005-03-21 14:10:36 UTC
[ BUILD # : 20050315 ]
[ JDK VERSION : 1.5.0_02 ]

When importing settings from netbeans 4, if you changed the base font, all imported colors turn to black.
Comment 1 Roman Strobl 2005-03-21 14:32:38 UTC
I was able to reproduce this issue with the attached config from userdir. Try to
import the settings to 4.1dev build, most colors for XML editor are black. Thus
it looks as if xml syntax coloring would not work.
Comment 2 Roman Strobl 2005-03-21 14:33:58 UTC
Created attachment 20992 [details]
Config
Comment 3 Martin Roskanin 2005-03-21 14:48:37 UTC
I will look at this.
Comment 4 Martin Roskanin 2005-03-21 15:27:13 UTC
Caused by fix of issue #53996
Particularly:
http://www.netbeans.org/source/browse/xml/text-edit/src/org/netbeans/modules/xml/text/syntax/XMLSettingsInitializer.java?logsort=date&search=&hideattic=1&sortby=file&r2=1.17&hidecvsroot=1&diff_format=h&r1=1.16

Hard coded coloring settings cannot be removed yet. Still there is needed to
maintain both declarations in XMLSettingsinitializer.java and *_fontsColors.xml
files...

Reassigning to xml module
Comment 5 _ pkuzel 2005-03-25 14:48:24 UTC
I hate the hardcoded settings. 
 
Martin, is there in editor a utility method to load the XML file? I guess you 
need it internally anyway. I'd call it from XML,DTD,CSS,... settings 
initializers. 
 
OSLO reason, I eliminated hardcoded setting because these are not brandable. 
One cannot brand classes unfortunately. XML files can be branded. 
 
MOVED to editor, ideally fix in the editor framework. If it's not possible 
then please disclose the utility method and return back. Thank you. 
Comment 6 Martin Roskanin 2005-03-29 09:20:23 UTC
We would like to fix this "duality" problem in editor for the next release. (It
is too risky thing to do it to nb41) 
For now, there is no simple utility method for that. You should create your
MIMEOptionsFolder and load the settings similarly as in
BaseOptions.loadDefaultAbbreviations. I believe this should work. If not, I see
the best solution to rollback you changes :-(
Comment 7 Jiri Kovalsky 2005-04-18 10:01:59 UTC
*** Issue 57964 has been marked as a duplicate of this issue. ***
Comment 8 akoltsov 2005-04-26 20:25:14 UTC
Workaround:
delete directory
%USERPROFILE%\.netbeans\4.1rc\config\Editors\text\xml
Comment 9 Roman Strobl 2005-06-07 14:19:57 UTC
*** Issue 59674 has been marked as a duplicate of this issue. ***
Comment 10 _ pkuzel 2005-10-17 13:23:40 UTC
How imports 4.1 => 5.0?
Comment 11 Marek Fukala 2005-11-30 13:05:48 UTC
Jirko, could you please check whether the 4.1 to 5.0 import works? There has
been a lot of changes in the options recently so I guess it could work now.
Comment 12 Jiri Kovalsky 2005-11-30 13:24:49 UTC
I checked it and can't say if it's fixed or not because of many exceptions
thrown on import of settings which resulted in all editors displaying plain text
- no syntax coloring, code completion - simply nothing. I will dig further to
find out what's the cause.
Comment 13 Marek Fukala 2005-12-09 09:47:38 UTC
Jirka cannot reproduce the issue since there are other problems during imports.
So I cannot fix it now, though the issue is already fixed IMHO.
Comment 14 Marek Fukala 2006-06-01 10:04:18 UTC
I belive this is fixed already.