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.
the welcome page layout has been enhanced to show dynamic content from RSS feeds. part of the redesign is an option for netbeans add-on modules and packs to add their own links to getting started section. this is api is based on xml-layer folders and files, please see attached arch.xml document for more details. because of the nb5.5 release deadline the updated code has actually been integrated into trunk already and we're planing to merge it into release5.5 branch on tuesday april 18th. however the xml layer api needs to be reviewed. otherwise i'll revert the getting started back to their static implementation. the welcome page changes have no impact on any other module. it merely adds an option to add additional links to the getting started section.
start page content plan: http://jupiter.czech.sun.com/wiki/view/Netbeans/StartPageContentPlan
Created attachment 29867 [details] welcome page screenshot
Created attachment 29868 [details] The first draft of architecture document
IMPORT NOTE: the plan is that for NetBeans 5.5 there will be no public APIs of the new welcome page (aka Start Page); the layout and the content of the page will be defined by the welcome module itself. Start Page will be open for extensibility in 6.0 release. For the extensibility the current module's mechanisms may simply be made public, or modified and opened then if necessary. A mini-plan document about Start Page will be created soon. I will link to it from this issue.
i merged the new welcome page to release55 branch
Created attachment 29904 [details] release55 merge cvs commit log
Y01 How the files in WelcomePage/GettingStartedLinks get read? By DataFolder.findFolder("WP/GSL").getNodeDelegate() and then processing the nodes or by some other low level technique? Btw. By using the node delegate, one would not need to care about SystemFileSystem.localizingBundle, so I would expect that to be a better alternative. If it has not been used, please explain why. Y02 Tests of XMLFileSystem are not enough to cover this API contract. Please create a test that shows what can be put into WelcomePage/GettingStartedLinks and how it gets interpreted - e.g. that OpenCookie is the important cookie that needs to be present, etc. Y03 You mention RSS feeds. What is the URL of the feed. Imho it is an API. Is it a hardcoded link, brandable link or is it even extensible by something in layers? Anyway mention it as an <api> as at least the URL value is API where others have to put the content of the feeds. Y04 For the 6.0 version please get rid of SystemOption and also reflection to access IDESettings - instead use preferences and coordinate with Radek Matous on exposing the proxy settings using preferences as well Y05 Put the description of the API inside the <api ...>tag</api> so it is better organized in summary page. Y06 Include this module in the list of all APIs of NetBeans project by changing nbbuild/build.properties and making sure it builds without problems. Y07 Split the module to infrastructure and default content. Otherwise, imho, we are going to create similar problem as with Autoupdate. People wanted to reuse Autoupdate but without our content. We had to create an Autoupdate infrastructure module and NetBeans specific Update Centers Module. Imho the same is to happen here. So split the module to infrastructure one (autoload) and default NetBeans content. Put the infrastructure module in some sharable cluster (platform or ide) and keep the NetBeans defaults in nbX.Y cluster. The other reason for this split is that we do not want other clusters to depend on a functionality provided by nbX.Y cluster...
re Y01: links are read using NodeDelegates. the localizingBundle is needed for .url files only. re Y02: i'll add some tests re Y03: RSS feed URLs are in brandable resource bundle. i'm not sure if they represent a full blown api though. there are also other links in the resource bundle (e.g. 'all news', 'all blogs' etc) re Y04: no problem with 6.0 but i think there are (were) some plans to make the new welcome page available at update center for nb5.0 re Y05: will do re Y06: will do re Y07: shouldn't be a big problem as the module packages are already structured that way.
Setting TM to "future" for now.
No longer valid - closing.